Geocode-sqlite: Geocode rows in an SQLite database table

Re:Geocode-sqlite: Geocode rows in an SQLite database table by teruakohatu on Monday May 17, 2021 @01:52AM (#27180427)

Just keep in mind while there is no API key required for OSM's Nominatum, there are no guarantees and they explicitly discourage bulk geocoding, with no clarification on what is bulk. [1] The lack of clarification seems intentional, which is understandable.

geocode-sqlite does support non-OSM hosted instances of Nominatum so find an alternative if you have large or regular geocoding tasks.

[1] https://operations.osmfoundation.org/policies/nominatim/

[ Parent | on HN ]

Re:Geocode-sqlite: Geocode rows in an SQLite database table by kvutza on Monday May 17, 2021 @07:33AM (#27182307)

The example of Nominatum use at the geocode-sqlite page shows using a local, thus non-OSM hosted, instance of Nominatum.

nominatum = Nominatum(user_agent="this-is-me", domain="nominatum.local.dev", scheme="http")

I have not tried it myself, thus if it fails, could you please report on what goes wrong there?

[ Parent | on HN ]

Re:Geocode-sqlite: Geocode rows in an SQLite database table by mtmail on Monday May 17, 2021 @08:31AM (#27182702)

> from geopy.geocoders import Nominatum

It's called Nominatim, not Nominatum. If you run into issues then reporting it on github repository might be the best option. It's not clear if the HN user is the author of the library.

[ Parent | on HN ]

Re:Geocode-sqlite: Geocode rows in an SQLite database table by dawnerd on Monday May 17, 2021 @02:00AM (#27180474)

I've been trying to find a good self hosted docker version but just haven't had any luck. I have about 30k addresses I need to geocode and the paid solution are way out of budget.

[ Parent | on HN ]