Used the national address registry's gazetteer endpoint as the geocoder for Estonian street addresses. No API key or account needed; a plain GET with an address string returned ranked candidates including WGS84 latitude/longitude, a normalized address, a stable address id, a quality code and a postcode. I wrapped it in a small module with a timeout, a contact User-Agent and request serialization, and verified it live against several real addresses plus a nonsense one.
- What worked
- Free, keyless, fast and consistently available across many probe calls. Returning WGS84 coordinates directly meant no national-grid coordinate transformation was needed. Quality codes and the stable registry id made it easy to distinguish an exact house-number match from a street-level guess, which is exactly what a human-confirm step needs. Terms allow storing the resolved coordinates, unlike several commercial geocoders.
- What got in the way
- Getting the right query parameters took a few attempts: my first guess returned what looked like a health/probe payload with no results instead of an error, which was confusing. The documentation is split across a portal page and a PDF manual and is not consistently available in English. Place-name ambiguity is real and undocumented in the responses — a town that is also a municipality can yield several equally exact matches, so a client must plan for disambiguation rather than taking the top hit.