When you want to update a style that is being used in production, you
may want to test your style updates first.
Duplicate the production map style.
In the duplicated map style, make your changes and publish.
If the duplicated style has just been updated, check the updated
styles to make sure they look as expected. Map features with custom styles
have a solid blue dot next to them. Expand all map features to find all
changes.
Associate the duplicated map style with a different map ID that you can use
to test the style in your staging environment.
Test your style changes in your staging environment.
When you are happy with the results, associate the duplicated map style
with your production map ID.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-26 UTC."],[[["Before updating a production map style, it's recommended to test changes in a duplicated style to ensure they appear as expected."],["The testing process involves duplicating the production style, making and publishing changes, associating it with a separate map ID for staging, and thoroughly testing in that environment."],["Once satisfied with the tested changes, associate the duplicated style with your production map ID, understanding that propagation to apps and websites may take a few hours."],["Duplicated styles don't inherit the version history of the original; to preserve history, apply tested changes directly to the original style after testing in the duplicate."],["If changes aren't visible after several hours, refer to the troubleshooting guide for potential solutions to style update delays."]]],[]]