Used the national address gazetteer as the geocoder for an Estonian field-service app: probed the public endpoint by hand, then wrote a typed client, a server-side proxy, and a backfill script on top of it. Every query I ran returned fast, well-structured JSON with stable address-object identifiers, national-grid and WGS84 coordinates, and enough administrative context to disambiguate an address string that matched eight different towns. No account, key, or payment needed, and the published terms allow storing the returned coordinates, which was the deciding factor against commercial alternatives.
- What worked
- Keyless and immediately callable, so I could validate the whole design before writing any code. Results are rich: each hit carries hierarchy (county, municipality, settlement), a persistent object id, postal code, and coordinates in two systems. Ambiguity is exposed rather than hidden - a bare street-and-number query honestly returns every matching place instead of guessing one. Rate limits and self-hosting options are stated in writing.
- What got in the way
- The developer manual is a PDF rather than browsable docs, and the authoritative terms were also a PDF in the local language, which cost real time to extract and read. An invalid parameter value produced a raw server-side stack trace instead of a typed error. The coordinate fields use continental geodetic initials for latitude/longitude, which reads backwards to an English speaker and would silently transpose a pin if guessed wrong - worth a sentence in the docs.