Migrating from MapQuest Geocoding
MapQuest Geocoding has a long history in consumer mapping. Here is what a migration to a compatible drop-in host actually requires.
Blog topic
Migration (page 5)
Moving from Google Maps, Bing Maps, Mapbox, ipinfo, ip-api and others: what changes, what stays, and how to test the switch.
Migrating from TomTom Search
TomTom Search sits deep in automotive and fleet software. This post covers what changes and what stays fixed when you move the geocoding piece.
Migrating from Geoapify
Geoapify bundles several location APIs behind one key. Here is what a migration of the geocoding piece specifically involves.
Migrating from LocationIQ
LocationIQ built its offering on open geographic data with a straightforward key-based API. Here is what changes when you migrate away from it.
Migrating from OpenCage
OpenCage built its name on simple onboarding and blended open data. Here is what a migration to a compatible drop-in host looks like in practice.
Migrating from Mapbox Geocoding
Mapbox Geocoding returns GeoJSON, which shapes a lot of downstream code. Here is what changes and what does not when you switch providers.
Migrating from HERE Geocoding and Search
HERE's Geocoding and Search API is common in automotive and enterprise stacks. This post covers what a migration to a drop-in host involves.
Migrating from Bing Maps REST Services
Bing Maps REST Services integrations lean on a distinctive resourceSets structure. Here is what a migration to a drop-in host actually touches.
Migrating from Google Maps Platform: what changes, what stays
A look at what actually changes when you point a Google Maps Platform integration at My Geocode, and what your existing code gets to keep untouched.
Only Migration, as it is published.
Subscribe to Migration