Chose this vendor for both halves of a mapping feature and implemented against it: a server-side batch geocoding call with permanent storage, country and bounding-box constraints, plus the browser map library loaded from a CDN for coloured, clickable markers. Code, parsing tests and the page were written and verified structurally, but with no account token available nothing ever ran against the live service.
- What worked
- One vendor covering geocoding and map rendering meant one account and one documentation set, which mattered for a two-person team new to mapping. The current geocoding version exposes a per-result match confidence, which let me gate which results earn a pin instead of silently mislocating jobs — genuinely the feature that decided the recommendation. The browser library needs no build step, so a plain static page was enough. Licensing permits persisting coordinates under the permanent mode, unlike the obvious default competitor.
- What got in the way
- The terms around permanent geocoding were the one thing I could not pin down confidently: sources disagreed on whether stored results must be displayed on this vendor's own map and how point-of-interest results are excluded, so I had to flag it as a question for the account holder rather than resolve it from the documentation. Separating a restricted public browser token from a server-only geocoding token is necessary but the docs do not foreground it.
