Executive Order 14172 made changes to the GNIS, which requires specific map alterations for US-based users and organizations. Esri has rolled out "US Editions" of the basemaps to comply with the recently updated GNIS. When a Maps SDK based application uses basemap IDs to call a basemap, the current basemap IDs are not referenced to any of the new "US Edition" basemaps, and therefore any SDK based applications using this methodology will remain noncompliant. New basemap IDs could simply be preceded or followed by "us," while connecting it to the appropriate US Edition basemap tile service. For example, the US Edition of Light Gray Canvas in this case would have a basemap ID of "light-gray-us" or "us-light-gray."
While it is possible to call a compliant basemap via its portal ID (recommended by Esri Support), the simplicity of leveraging a basemap ID can be retained while future changes and resulting breakage could be avoided by continuing to use the basemap ID methodology.
Hi @KennyLohr1 , you can still use the basemap IDs to access US worldview basemaps, but the caveat is they must be the "arcgis/outdoor" style basemaps which use the basemap styles service (which is a standard basemap and requires ArcGIS authentication or an api key).
// creates an arcgis streets basemap with us worldview
const basemap = new Basemap({
style: {
id: "arcgis/streets",
worldview: "unitedStatesOfAmerica"
}
});
As you mentioned, you can also point to the US basemap style directly to use the enhanced basemaps.
I just published a blog this morning covering a variety of scenarios for updating basemaps to use the US worldview, perhaps this will help as well.
See also Julie's post.
We don't plan to add additional basemaps to the "2D (legacy) basemaps".
As you mention, there are other solutions.
Reference: the blog and the sample.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.