Hyper-optimized reverse geocoding API

#1

Post by tananaev » Thu, Mar 19, 2026, 2:38 PM UTC

Hyper-optimized reverse geocoding API
github.com

Re: Hyper-optimized reverse geocoding API

#2

Post by tananaev » Thu, Mar 19, 2026, 2:38 PM UTC

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.

Re: Hyper-optimized reverse geocoding API

#3

Post by Heer_J » Thu, Mar 19, 2026, 3:37 PM UTC

[dead]

Re: Hyper-optimized reverse geocoding API

#4

Post by majorchord » Thu, Mar 19, 2026, 3:52 PM UTC

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?

Re: Hyper-optimized reverse geocoding API

#5

Post by macrolet » Thu, Mar 19, 2026, 3:53 PM UTC

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.

Re: Hyper-optimized reverse geocoding API

#6

Post by supriyo-biswas » Thu, Mar 19, 2026, 3:58 PM UTC

I don’t get the point in writing another geocoder when such programs already exist, e.g: https://pelias.io/

Re: Hyper-optimized reverse geocoding API

#7

Post by [deleted] » Thu, Mar 19, 2026, 4:01 PM UTC

[deleted]

Re: Hyper-optimized reverse geocoding API

#8

Post by gniv » Thu, Mar 19, 2026, 4:13 PM UTC

tananaev wrote: post #2

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?

Re: Hyper-optimized reverse geocoding API

#9

Post by KomoD » Thu, Mar 19, 2026, 4:24 PM UTC

> docker run -e PBF_URLS="https://download.geofabrik.de/planet-latest.osm.pbf"

Geofabrik doesn't offer a "planet" pbf.

Re: Hyper-optimized reverse geocoding API

#10

Post by KomoD » Thu, Mar 19, 2026, 4:47 PM UTC

gniv wrote: post #8

tananaev wrote: post #2

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