Used for raster tiles and one-time server-side forward geocoding with regional bias, with coordinates cached in the database so map views cost tiles only. Integration code and proxy routes built successfully, but no live calls were made because no API key or database was available in the environment.
- What worked
- Documentation made pricing predictable with a flat monthly plan that scales from few to many technicians, and the tile plus geocoding API model fit the cache-once approach well. Server-side key handling and regional bias were straightforward to design around.
- What got in the way
- Live geocoding and tile serving could not be verified without an API key and database, so address match quality for local street addresses remains unconfirmed.
