nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can’t display classified raster in ArcGIS Pro 3.3

LizLotz_mc2

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??

Find more posts tagged with

Desktop

Accepted answers

Robert_LeClair

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:

Use the Apply Symbology From Layer tool to import the symbology from a similar layer.
Edit the 'Maximum number of unique values to display' parameter within the Raster and Imagery ArcGIS Pro options.

LizLotz_mc2

Good to know this is a known issue scheduled for a fix. Thanks!

All comments

DanPatterson

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

LizLotz_mc2

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?

DanPatterson

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

Robert_LeClair

Use the Apply Symbology From Layer tool to import the symbology from a similar layer.
Edit the 'Maximum number of unique values to display' parameter within the Raster and Imagery ArcGIS Pro options.

LizLotz_mc2

Good to know this is a known issue scheduled for a fix. Thanks!

TroyCarmann

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!

idcrickmore

This is still broken.

Robert_LeClair

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.

CorrineCoakley

I had high hopes, but nope, it isn't fixed. This makes it seriously difficult to symbolize multiple NDVI rasters with scientific values from -1 to 1. ArcPro won't let me set those class limits because I don't have values that go all the way to -1.

Robert_LeClair

I can confirm that BUG-000167647 is fixed at ArcGIS Pro 3.4 which is scheduled to be released Q4 2024.

ricardoaravena

This bug didn't exist in 3.2. How is it that ESRI is including bugs in their updates?

Now I have to uninstall and roll back.

adminJDN

@Robert_LeClair

BUG-000167647: ain't fixed.

Still broken in 3.4

LizLotz_mc2

That is disappointing! I had hoped this would be fixed as planned at 3.4.

Robert_LeClair

I'm looking at the Esri Support Services internals for BUG-000167647 and it shows fixed at ArcGIS Pro 3.4 although from your message it appears not to be fixed. The workaround at 3.3 was:

Use the Apply Symbology From Layer tool to import the symbology from a similar layer.
Edit the 'Maximum number of unique values to display' parameter within the Raster and Imagery ArcGIS Pro options.

I'd recommend reaching out to Esri Support Services to create a case for the analyst to investigate.

adminJDN

I need to correct myself. Sensu strictu, the bug has been fixed. It is possible to use Classify renderer for single band in v3.4.
Although there is no backward compatibility with projects created earlier (v3.1)

LizLotz_mc2

Thanks for clarifying

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.