Self-hosted reverse geocoder with sub-millisecond query latency. C++ builder parses OSM PBF files into a compact binary index using S2 geometry cells. Rust server memory-maps the index and serves a Nominatim-compatible API. Docker support with automatic HTTPS.
Great. But look at the query feature of OSM. Try it. At higher zoom levels like 15, querying for features at the same coordinates as your example reveals nearby features. Like hotel buildings, post offices, recycling points, etc. The nominatin format is not enough. What is more, an extended feature set could be used together with an LLM. I am very interested in that, so, feel free to reach out to me if you want to discuss more.
I just want a regular (non-reverse) geocoding system that's actually easy to self-host.
Windows CE apps were doing this 20 years ago with single file databases of only a few GBs, why do I need a 500GB+ postgres monster to do the same thing today?
Self-hosted reverse geocoder with sub-millisecond query latency. C++ builder parses OSM PBF files into a compact binary index using S2 geometry cells. Rust server memory-maps the index and serves a Nominatim-compatible API. Docker support with automatic HTTPS.
How long does it take to build the whole index?
I tried the "Australia and Oceania" pbf which is really small and it took ~15min
I don’t get the point in writing another geocoder when such programs already exist, e.g: https://pelias.io/
I don't get the point in making other types of food when pizza already exists.
> docker run -e PBF_URLS="https://download.geofabrik.de/planet-latest.osm.pbf"
Geofabrik doesn't offer a "planet" pbf.
Great. But look at the query feature of OSM. Try it. At higher zoom levels like 15, querying for features at the same coordinates as your example reveals nearby features. Like hotel buildings, post offices, recycling points, etc. The nominatin format is not enough. What is more, an extended feature set could be used together with an LLM. I am very interested in that, so, feel free to reach out to me if you want to discuss more.
I just want a regular (non-reverse) geocoding system that's actually easy to self-host.
Windows CE apps were doing this 20 years ago with single file databases of only a few GBs, why do I need a 500GB+ postgres monster to do the same thing today?
Have you tried MOTIS with only the geocoding enabled? This should be 1-2 orders of magnitude smaller.