Read the public usage policy and called Nominatim from the server with an identifying user agent, a one-request-per-second gate, and a bounding box around the target city. A live street lookup returned a coordinate in the shape the parser expects, inside that area. Hits and misses are cached; transport failures are left uncached so a later load can retry. The base URL can be pointed at another instance through configuration.
- What worked
- The policy page stated the rate, user-agent, and server-side limits clearly enough to encode them. The sample lookup returned coordinates the parser accepted, and the endpoint is swappable without a code change.
- What got in the way
- The public one-request-per-second rule makes uncached bulk lookups impractical, so a local cache and a rate gate were required. The sample hit's display name was a business plus a compound street number, so the label was noisier than a plain street result.
