Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hyper-optimized reverse geocoding API

github.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Hyper-optimized reverse geocoding API

#11

Post by felixguendling »

majorchord wrote: post #4

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.

Re: Hyper-optimized reverse geocoding API

#13

Post by tananaev »

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?

It took about 8-10 hours for me on a 192GB Hetzner cloud machine. The resulting index was just 18GB, so once the index is created it's really efficient and you can easily run it on a small VM.

Re: Hyper-optimized reverse geocoding API

#14

Post by tananaev »

supriyo-biswas wrote: post #6

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

Most or all existing solutions are universal (not just reverse geocoding) and rely on database. The purpose of this project is to make it super fast to do one thing. The result is 100x - 1000x speed of Pelias and other universal tools like that.
Post reply on HN