March 19, 2026
Map beef at millisecond speed
Hyper-optimized reverse geocoding API
Blazing-fast DIY address finder lands — fans hype, skeptics cry “Yet Another Geocoder”
TLDR: Traccar launched a super‑fast, self‑hosted tool that turns GPS coordinates into street addresses. The crowd split fast: fans love the speed and simplicity, while critics say it duplicates existing projects, lacks forward search, and even includes a dodgy example link—classic open‑source brawl over how maps should be built and used.
A new self‑hosted tool from Traccar promises lightning‑quick reverse geocoding—aka turning GPS dots into real street addresses—using free OpenStreetMap data. The dev behind it boasts sub‑millisecond lookups and a simple web API, plus a one‑click Docker setup. Translation: run your own address engine without renting Big Tech’s map brain.
But the comments? Absolute mapcore mayhem. Some are hyped for speed and control, while others roll their eyes at “yet another geocoder” and point to rivals like Pelias. One nostalgic voice drops a meme‑bomb: Windows CE apps “did this 20 years ago” with tiny databases, so why do modern tools feel like a “500GB Postgres monster” just to find an address? That hit a nerve.
Then came feature‑hunters: one user says the classic Nominatim‑style response isn’t enough—they want nearby points like hotels and post offices, maybe even tie it to an AI assistant. Meanwhile, a sharp‑eyed commenter flags a gotcha in the docs: Geofabrik doesn’t host a planet‑wide file, so that example URL? Yeah… not real. Cue facepalms.
Verdict from the crowd: Speed and simplicity are 🔥, but there’s drama over duplication, missing forward search (finding coordinates from a typed address), and whether this should become a full “what’s around me?” engine. It’s the classic open‑source showdown: builders ship, purists nitpick, and everyone argues over which geocoder reigns supreme.
Key Points
- •Traccar Geocoder is a self-hosted reverse geocoding service built on OpenStreetMap data, returning street-level addresses.
- •It exposes a Nominatim-compatible GET /reverse API that accepts lat and lon and omits unavailable fields in responses.
- •Performance is achieved via memory-mapped binary indexes built with S2 geometry cells, enabling sub-millisecond query latency.
- •Deployment options include Docker and Docker Compose with automatic PBF download, index building, serving, and automatic HTTPS via Let's Encrypt.
- •The system comprises a C++ Builder to parse OSM PBF files into 14 binary index files and a Rust Server to serve HTTP/HTTPS queries.