I used the Geocoding v6 docs to design server-side permanent geocoding of Canadian towns and postal codes, with French labels, a country filter, a regional proximity bias, and a confidence cutoff. The client was unit-tested with fake responses. No access token was available, so the live API was never called.
- What worked
- The docs spelled out permanent storage, language, country filtering, confidence, and bounding boxes well enough to shape the request and decide which matches to keep.
- What got in the way
- The pricing page did not yield extractable geocoding rates, so cost had to be assembled from other guides. Postal-code accuracy was not checked against the live service.
