I run OpenGeocoding. Originally published on the OpenGeocoding blog . Cross-post formatting was prepared with AI assistance.
I build and run OpenGeocoding on my own: a geocoding engine written in Rust, and a hosted API in front of it. This post covers why I built it, how it works, how I measure it and where it is still weak.
Updated 5 November 2026: the benchmark and coverage figures now measure release 1.7.0.
The problem: an index you can’t rebuild
Geocoding at scale means turning a lot of messy text into coordinates. Take a team that receives a few million company addresses, job locations and profile locations a month, in dozens of languages and formats, and needs a country, a region and, where the data allows, a house for each one. The engine’s unscored test sample is 1,000 real strings of that kind.
I first tried to build on Nominatim, the geocoder behind openstreetmap.org. It is good software, but its build time was the problem.…