Help Desk
How can we help you today?
New Map changes - requesting feedback by October 9, 2025
A few of us at AZGFD tried to get together and test the new map. The azdev site is essentially unuseable for most of us because of how slow everything was to load. For me, the old map (on the azdev site) loads and works like normal but trying to use the new map is painfully slow. Is there something that can be done about that?
Hi Parker, we recently updated the AZ Dev site with a new version of the new map and that occasionally causes the site to take longer to load the first few times. Can you try again this week to see if it's any better? Meanwhile, we'll also take a look on our end to see if there's any reason it would be loading slower.
Hi, Elyzabeth. The Explore tab on the azdev site is still very slow and thus non-functional for me. It's been loading for the last half an hour. When I first opened it, I was able to see the map and the list of layers under the Layers dropdown, but it took 10 minutes for any of the eyeballs to appear to turn those layers on -- and they only appeared for about 3/4 of the layers (the rest never came up). No layers showed in the Search for Features option, either. I then switched to a different tab in my browser and, when I returned to the ERT tab, the screen was white. I refreshed the page and am now back to just seeing the list of layers under the Layers dropdown but no eyeballs to turn them on. Any thoughts?
Hi Tiffany, I'm not sure what happened there. I've never had it take that long to load! It should only take about a minute at most to load, so something doesn't sound right. We did recently release a new version to the AZ Dev site to test an improvement to load time, so you might try clearing your browser cache and see if that clears it up. I'd also recommend you try another browser for comparison. I noticed recently in Chrome that there's a setting that causes a browser tab to "timeout" loading if I navigate away from it (which I was doing while the map was loading), which resulted in the white screen you described. Let me know if either of those options work for you.
I have tried Chrome, Edge, and Firefox on my Windows work computer, and Chome, Edge, and Firefox on my personal mac. Cleared caches all around, cache disabled in dev tools all around. For some reason, Firefox seems to load the explore tab more reliably on both operating systems. With the chromium based browsers, it often will never finish loading.
One source of sluggishness is the initial load of libraries/ert-react-mapcore/app.bundle.js?v=7.x-1.5 generally takes a long time. It needs to load in full before it is able to trigger loading countless other resources. Loading this resource varies between 10 seconds and 1.5 minutes. If there is a way to trim this bundle size down somehow that could help.
The thing that seems to be the true holdup that sometimes never resolves is the initial loading of layer resources (before the eye icons ever show up). We are loading many resources from many different servers, including those that are hosted on the azdev site. For example:
fetch("https://azdev.natureserve.org/arcgis/rest/services/AZ_Public/SGCN_hex/MapServer/layers?f=json", {
"headers": {
"sec-ch-ua": "\"Chromium\";v=\"142\", \"Google Chrome\";v=\"142\", \"Not_A Brand\";v=\"99\"",
"sec-ch-ua-mobile": "?0",
"sec-ch-ua-platform": "\"Windows\""
},
"referrer": "https://azdev.natureserve.org/content/explore",
"body": null,
"method": "GET",
"mode": "cors",
"credentials": "omit"
});
Many get stuck in pending, just waiting for server responses, which makes the page unresponsive:
Meanwhile the app is stuck in a loading state, where you can't activate layers or do much of anything (note the lack of eye icons):
Sometimes it will load some layers, but not all, it just really struggles to ever get to an idle state.
The code sent to our end is minified so it is hard to make sense of, but are these being loaded in series or parrallel? Is there a way to make it not blocking to load all map resources? I don't know. It seems to hang for 2, 3, 4, 5+ minutes, with many fetch requests pending in the network tab, nothing seeming to happen, then if you're lucky, all of a sudden it will free up, the rest of the requests will resolve and the map will load.
Does it really load in a reasonable amount of time on your end with cache disabled? Are you able to activate all layers?
Elyzabeth Earnley
We are asking for feedback on the following new features coming to the "new map" before we release it to Production. Once in Production, each program currently using the "new map" will inherit this version at their next update.
You can test these changes on the AZ Dev site: https://azdev.natureserve.org/content/explore
We are asking for your feedback by Thursday, Oct 9, 2025 if your program is already using the New Map. Change details for bold items are below.
Change details:
>Apply a filter to multiple layers at the same time
Option to "Filter layer" under the Layer menu (...)
The Layer name updates to indicate that it is Filtered.
User can apply a second filter to a different layer and see both filtered layers on the map
User can edit or clear the filter at the individual sublayer.
>Improvement to nested layer visibility
If a user makes visible a nested layer, the layer(s) above it in hierarchy become visible so that the layer displays on the map.