Note: For more information on data coverage changes, see Mapbox Boundaries Changelog.
Your Mapbox boundary options will automatically be migrated when you upgrade to Strategy ONE (March 2024) similar to the following parameters:
Mapbox boundary option table upgrades:
Although Strategy automatically migrates your boundary options, Strategy recommends checking whether your boundaries are configured correctly.
If your Mapbox visualizations cannot render as expected after upgrading to Strategy ONE (March 2024), refer to the following cases to troubleshoot:
Some name changes are expected as part of the update. For example, "British Indian Ocean Territory (the)" was updated to "British Indian Ocean Territory". Strategy ONE (March 2024) cannot render the related shape for "British Indian Ocean Territory (the)". The name in your data should be updated to "British Indian Ocean Territory" to render correctly.
For more information on the correct locator names, see the Mapbox Boundaries Explorer.
You can use name conversion to resolve the locator name issue. For more information, see Resolving Differences in Location Names.
Though your Mapbox boundary options are automatically migrated after you upgrade, incorrect mappings may still exist. For example, the postal options are now split into 4 boundary options (Postal 1-4). If your postal code date should be rendered by the postal1-postal3, Mapbox shapes will render incorrectly. Strategy recommends that you review and change the boundary option to the corresponding postal code.
Mapbox updates some data between Boundary types. For example, the Canadian city related boundary information was updated from adm4 to Sta3, so you might need to change the boundaries option from administrative to Statistical to render Canadian cities.
To check your data boundary type and level if you have concerns about the boundary type changes, see the Mapbox Boundaries Explorer.
The layered grouping of geographical boundaries in Mapbox Boundaries v4 was also updated. Strategy supports three of the Mapbox-powered boundary types:
In cases where Mapbox moves some data's boundary type from the three boundary types to legislative or locality, the corresponding boundary information is missing from Strategy. For example, some communes in France which used to be under the Administrative boundary were migrated to the Legislative boundary type, and will no longer be seen in maps after the upgrade.
To check your data boundary type and level if you have concerns about whether the given data names are missing, see the Mapbox Boundaries Explorer.
Mapbox Boundaries v4 contains more boundaries and name aliases than the older version, so you can expect to see more accurate boundaries and more detailed information than in previous versions.
For more information, see How do I add a secondary geo-attribute to ensure the right location is mapped?
