Migrating from Google Maps
Migrating from Google Maps to the Radar Maps Platform is simple, and usually involves just a few lines of code. Find the Google Maps offerings used in your application below and learn about the corresponding cost-effective, developer-friendly Radar alternative.
#
MapsGoogle's maps offering is used for rendering maps in applications. Radar provides vector base maps with beautiful out-of-the-box styles as an alternative. Check out the maps explorer in the dashboard to see them in action.
Google Maps Feature | Radar Feature |
---|---|
Dynamic Maps | Dynamic Maps |
Static Maps | Static Maps |
#
PlacesGoogle's Places APIs enable finding and geocoding locations such as addresses and points of interest. Radar's Geocoding and Search APIs provide fully featured geocoding, autocomplete, address validation, and geolocation APIs as an alternative.
Google Maps API | Radar API |
---|---|
Geocoding API | Forward Geocoding API |
Reverse Geocoding API | Reverse Geocoding API |
N/A | IP Geocoding API |
Autocomplete API | Autocomplete API |
Place Autocomplete UI | Autocomplete Component |
Address Validation API | Address Validation API |
Nearby Search API | Places Search API |
Current Place API | Context API |
#
RoutesGoogle's Routes APIs are used to calculate routes between locations or snap to roads. Radar's routing APIs provide a suite of distance, matrix, directions, route match, and optimize APIs to power these use cases and more.
Google Maps API | Radar API |
---|---|
Distance Matrix API | Distance Matrix API |
Directions API | Directions API |
Snap to Roads API | Route Matching API |
Speed Limits API | Route Matching API, with speedLimit included in the roadAttributes parameter |
Compute Routes API | Matrix API, Directions API, or Route Optimization API |
#
SupportHave questions or feedback on migrating from Google Maps to Radar? Let us know! Contact us at radar.com/support.