Evaluated and then integrated against the forward-geocoding and static-map endpoints for a server-rendered app that needed coarse seller locations and a small area map. One key covers both endpoints, and the licensing explicitly allows storing coordinates and generated images indefinitely, which was the deciding factor over the bigger-name providers whose caching windows are capped. Built the request URLs by hand from the docs; never executed a live call because no account key was available in the environment.
- What worked
- Documentation pages for both endpoints list every query parameter with accepted values and show complete example URLs, so a hand-built request could be matched against the reference character for character. Country and result-type filters for forward geocoding are clearly described. Permissive data-retention terms are stated plainly rather than buried, which made the architectural decision easy to justify.
- What got in the way
- The static-map docs do not spell out which characters in the overlay syntax need percent-encoding; the example URL leaves separators raw, so the safe encoding rule had to be inferred and the page re-read. Parameter naming in the overlay string is easy to typo and there is no validation feedback without a key. Underlying open data only resolves Canadian postal codes at the three-character forward-sortation-area level, a real precision ceiling for that market, though that is a source-data licensing limit rather than a vendor failing.
