For some reason I can’t display an raster elevation DEM layer in ArcGIS Pro 3.3 using the Classify symbology. It displays without a problem using the Stretch symbology, but when I select “Classify” instead, it immediately starts “Generating unique values” which runs for awhile. Then, I get an error. I tried increasing the number of values in Options up to 100,000,000, but I still get the error. And, the Statistics don’t show up in the Symbology Pane. The Statistics are shown in the Layer Properties however. See the screenshots below.
When I do the same thing in ArcMap 8.2, I can select the the Classified display and specify the # of classes and class breaks for display, and view the histogram and statistics.
Why is this simple raster display a problem in ArcGIS Pro??
Solved! Go to Solution.
There is BUG-000167647 - "Issues with classifying the symbology of a raster dataset using continuous floating-point values in ArcGIS Pro 3.3" It's scheduled to be fixed in ArcGIS Pro 3.4 later this year. Workarounds include:
Good to know this is a known issue scheduled for a fix. Thanks!
way at the bottom of this link
Change the symbology of imagery—ArcGIS Pro | Documentation
describes Classified
I would suggest using anything other than Classify in your last image. you elevations are floating point and setting the number of classes to more than 10 classes isn't going to make it look better
Thanks Dan, I appreciate the suggestion. But the purpose of my post is not to ask about symbolizing floating point elevation data in general. I'm trying to understand why a basic raster display option is not working in ArcGIS Pro. What I really was trying to do is use a 2 class raster display in ArcGIS Pro to quickly visually show elevations above and below a specific value to get an idea of upland vs wetland in a particular area. This is a simple classification that I have done many times in ArcMap, so why not in ArcGIS Pro?
The default in the Project backstage, Raster and Imagery, did you set the maximum number of unique values there as well? the default is 65536, perhaps throwing the 100m in symbology throws the warning.
Pro display engine isn't the same as arcmap's so I wouldn't expect them to behave exactly the same
i was having the same issue, but once i change it to 100 Million then my problem was solved! Thank you Dan for your help!
There is BUG-000167647 - "Issues with classifying the symbology of a raster dataset using continuous floating-point values in ArcGIS Pro 3.3" It's scheduled to be fixed in ArcGIS Pro 3.4 later this year. Workarounds include:
Good to know this is a known issue scheduled for a fix. Thanks!
I can confirm that BUG-000167647 is fixed at ArcGIS Pro 3.4 which is scheduled to be released Q4 2024.
This is still broken.
Correct. This was BUG-000167647 that was detected in the ArcGIS Pro 3.3 application - which is the current version of ArcGIS Pro 3.x. I did see that the BUG is fixed and will be deployed when ArcGIS Pro 3.4 is released later this year.