Hi Sarah,
Thanks, right after I sent the email, I noticed osm.org had it available
which prompted my checking github.
I'm cloning the source right now. Do I need to use that commit? I had
thought master was fully updated for that feature, is master no longer
compatible with 2.5.0?
Thanks!
-Brooks
On 03/17/2016 01:00 PM, Sarah Hoffmann wrote:
Hi,
On Thu, Mar 17, 2016 at 11:59:07AM -0400, Brooks Isoldi wrote:
Is there a way to get a bounding box back from Nominatim when doing
a reverse geocode search or a relatively easy change (with my own
install of Nominatim) that would allow that - perhaps a simple
inclusion of the bounding box into the response?
As it happens, we added this feature just last week (thanks Mark!).
You can try it out on nominatim.osm.org. If you want to include it
into your own installation, I recommend getting the source from github
and then check out commit
b097840ba4fd83d432e2c9aa3e9176e3fa3267a9.
That's the newest version that is still compatible with the 2.5 release.
Kind regards
Sarah
I am hoping to use the reverse geocode to turn a lat/lon point into
a sane bounding box that covers the specific boundaries of whatever
element the point falls within.
If not possible, can I put in a feature request for that as well as
a standardized bounding box format?
Thank you!
-Brooks
_______________________________________________
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding
--
Brooks Isoldi, Software Developer
Traversed
7164 Columbia Gateway Drive, Suite 120A
Columbia, MD 21046
_______________________________________________
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding
