Hi everyone,
I use the Living Atlas "Terrain: Hillshade" layer on a daily basis for my work. Until yesterday, this layer was always fairly high resolution (I'm not sure exactly what it was, but I would estimate somewhere between 5m and 1m). I need this fine detail to outline and classify relatively small features in the topography. The resolution of this layer was the exact same as the individual lidar tiles I've been provided for my state, except I don't have to load each one individually (and there are thousands upon thousands of them), and streaming the layer from Living Atlas is actually faster than trying to get the individually loaded tiles to display. In short, this layer is a lifesaver.
When I opened my ArcGIS Pro project this morning, the Terrain: Hillshade layer was extremely "pixelated" and obviously at a much coarser scale than normal. Nothing about my map had changed, and this very same layer worked perfectly fine yesterday. I removed the layer, searched for it again in the Living Atlas, and added it back to my map, but the problem remained. I can't see any of the details I need to see to do my work, and it's going to be a huge time-sink if I have to load my own lidar tiles manually.
Is anyone else having this problem, or have you had this problem before? I'm open to any suggestions. Thanks.
Quick edit: I've just checked another layer that I use in similar ways - "Terrain: Slope Map" - and it's having the same issue.
Edit 11/6/2024:
I reported the issue to Esri. I went through the troubleshooting process over a Zoom call with an Esri support specialist, who also had the same issue on their end, and we were not able to resolve the issue. I was told that the Living Atlas was being updated and that this may have something to do with it, but the support specialist couldn't directly confirm this. He said he would continue to look into it.
As of the afternoon of 11/5/2024, the imagery layer is now back to the correct resolution with no changes made on my end. I'm assuming that this problem was related to something on Esri's end, probably the updates to the Living Atlas. I'm adding this update for anyone else who stumbles across this thread in the future with a similar issue.
I will also add a separate comment down below to increase the visibility of this thread.
