This latest release of cloud-based maps styling includes more map features and styling options than the legacy styling, and some changes to be aware of before you update to or use the new map styles. Review Known Issues and the following sections for information about using this release.
Billing
Using cloud-based maps styling requires a map ID. On Maps SDK for Android, Maps SDK for iOS, and JavaScript, using a map ID incurs a charge against the Dynamic Maps SKU. On the Maps Static API, using a map ID incurs a charge against the Static Maps SKU.
Application and website requirements
To display map styles, your websites and applications require the following platform versions:
JavaScript vector-based maps: JavaScript Maps API 3.47 or later. To set up the latest version, see Set up the Maps JavaScript API.
JavaScript raster-based maps: JavaScript Maps API 3.49 or later. To set up the latest version, see Set up the Maps JavaScript API.
iOS: iOS Maps SDK 8.3.1 or later. To set up the latest version, see Set up an Xcode project.
Android: Android SDK version 18.0.0 or later with the new Android Map Renderer and GMSCore container version 23.33.16. To set up the latest version, see Set up an Android Studio project.
Ready to get started? See the Tutorial.
Update legacy styles
Because the order and hierarchy has changed, you may need to make changes to your current styles or your process to use this version. For example, to style Water, you look under Natural>Water. To see all of the new hierarchy, see What you can style on a map.
Existing map styles need to be updated or recreated to use the new features. For a comparison of the current hierarchy to this version, see Map feature changes.
If you need to update legacy map styles, see Update to the latest version.