(opens in a new tab)gmap cloud
Talk to usContact
Getting startedIntermediate2 min read

Moving from Google Maps Platform to GMap Cloud: an API mapping

If your app uses Google Maps Platform, most features have a GMap Cloud equivalent. This guide lists each pair and what to change when you switch.

· GMap Cloud

API mapping

Google Maps PlatformGMap Cloud
Maps JavaScript APIMapLibre GL JS + /api/tiles/style/basemap (or darkmap)
Geocoding API (address → coordinates)GET /api/idunn/v1/search
Geocoding API (coordinates → address)GET /api/idunn/v1/reverse/{lat}:{lon}
Places AutocompleteGET /api/idunn/v1/autocomplete
Place DetailsGET /api/idunn/v1/places/{id}
Directions APIGET /api/route/v1/{mode}/{coordinates}
Distance Matrix APIPOST /api/tsp/route/sources_to_targets
Route OptimizationPOST /api/tsp/route/optimized_route
—Isochrones, VN-2000 conversion, 63/34-province addresses, parcels

What to change in your code

  • Coordinate order: GeoJSON uses [longitude, latitude], not { lat, lng } objects.
  • Pass the key in the x-api-key header or query parameter.
  • Search results are GeoJSON FeatureCollections; the address label is properties.geocoding.label.
  • Maps use MapLibre: google.maps.Marker becomes maplibregl.Marker, InfoWindow becomes maplibregl.Popup.
  • Addresses can include both the 63-province and 34-province form (subtype addr63/addr34).

Migration plan

  1. List the map calls you use and the traffic for each.
  2. Run both side by side on a sample of your own addresses and compare.
  3. Switch one feature at a time (maps, search, routing) and keep a way back.
  4. Agree keys, traffic and data coverage with GMap before switching everything.