Nominatim

It's possible these days to run an entirely open source geocoding stack of your own. Here's one of the better options for that: https://github.com/osm-search/Nominatim I wouldn't recommend it though: it needs a beefy machine and applying updates on an ongoing basis is fiddly. Better to use a commercial option and have that as an escape hatch.

I have had a lot of "fun" with this feature in the past. It has earned a permanent place in my setup script: ALTER SYSTEM SET jit=off; Basically a performance blackhole for more complex queries. Most OSM related projects disable it straight away as it only creates headaches. https://github.com/osm-search/Nominatim/pull/2559 https://github.com/gravitystorm/openstreetmap-carto/blob/mas...

Run your own: https://github.com/osm-search/Nominatim You can find many other open source projects that utilize OSM (and support autocomplete and other features).

29 of 309 = 10% https://github.com/openstreetmap/Nominatim/

The email list https://lists.openstreetmap.org/listinfo/geocoding List of small https://github.com/openstreetmap/Nominatim/issues?q=is%3Aiss... and larger projects https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/20...

We use it extensively for http://nominatim.org/ It's superior when writing loops or even recursive queries that usually require follow-up queries (and thus multiple back-and-forths between your app and the database). Debugging and test-driven development on the other hand is hard. So is versioning functions and updating them. I'd only recommend it if all other options of improving the performance of database queries were tried. https://github.com/openstreetmap/Nominatim/blob/master/sql/f...

It's different software. openstreetmap.org uses Nominatim: https://github.com/openstreetmap/Nominatim The photon link uses Photon: https://github.com/komoot/photon Nominatim processes OSM data, associating items of interest with features like town boundaries that enclose the item, or place markers that are nearby, and then is also a fairly pedantic search interface for that data. Photon takes the data that Nominatim generates and sticks a more flexible search on top of it. Checking for/creating an issue for Nominatim describing the address format that doesn't work well would be a useful thing to do, as global support is a goal there.

It can be stale or contain weird opinions, but the OSM wiki certainly serves as an adequate inventory (maybe not perfectly organized). http://wiki.openstreetmap.org/wiki/Software To your specific question: https://github.com/twain47/Nominatim#installation with a viewbox: http://wiki.openstreetmap.org/wiki/Nominatim#Search

I'm using it for a photo app (I only need town/city level granularity), and it works well for my needs. Note that the dataset is based upon populated places though, so YMMV if you need to lookup somewhere in the middle of nowhere. Here is a JavaScript library I wrote for it, along with some scripts for munging the GeoNames dataset: https://github.com/lucaspiller/offline-geocoder/ If you need higher granularity, take a look at this OSM project: https://github.com/twain47/Nominatim/

And nominatim is open source ( https://github.com/twain47/Nominatim ), so if there's some silly embarassing thing that it gets wrong (like the address of your headquarters), then you can fix it yourself.