Called the public online geocoder with street-and-town text for customers in Tartu and Elva, then stored an exact house-number hit on the customer. Several known addresses returned coordinates. Two seed streets came back as not found, and that miss stayed stable on a later request. Query shape and quality codes took several live probes and a parameter search before the response was clear.
- What worked
- The JSON endpoint answered live queries for both towns, distinguished an exact house point from a miss, and stayed consistent enough to cache. A gazetteer URL on the same host was available as a second lookup shape while the query format was still unclear. After the server integration, job loads returned stored coordinates and the log showed no geocoder errors.
- What got in the way
- The first sample street missed, and small wording changes (street type, locality type) changed whether a query matched. Quality codes are opaque in the payload, so their meaning had to be looked up separately. Response field names were not obvious without an external parameter search.