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; } } }

ArcGIS Pro 3.4.2: Reclassifying a raster into two classes results in three,

JamalNUMAN

In the screenshots below, I attempted to classify a raster into two classes using the “Reclassify” tool, but the output ends up with three classes.

What could be causing this issue?

The data raster is attached.

NDVI.gdb.zip

Shwu-jingJeng_0-1620251915607.png

Trouver plus de publications taguées avec

Desktop

Accepted answers

All comments

JonM32

@JamalNUMAN The value of 0 is for the No Data cell in the raster.

I'd try running the tool again with the check box marked for 'change missing values to nodata' and see what happens.

Otherwise, you could assign a value for the no data cell, to either 1 or 2 value you're working with or something else.

Jon

JamalNUMAN

I set the 'New' value for NODATA to 7. However, the Reclassify tool produces 4 classes, even though the number of classes is set to 3, as shown in the screenshots below.

What could be the reason behind the class with the value '0'?

JonM32

I'm honestly not sure.

Maybe check the statistics of the dataset you're reclassifying to see if the values being changed are within it.

Or try to reclassifying using different ranges of values and see what happens?

JamalNUMAN

Does it indicate anything that the cell taking the value 0 originally had a value of -0.149068, which is the minimum value in the original raster? Why is a separate class automatically created for this value?

JonM32

If I had to guess, it's a rounding thing that occurs when the tool is run. You could always try to reclass a value below the -0.149068 and see what happens. For example, reclass anything from -1 to 0.744594 to 1

JamalNUMAN

I changed -0.149068 to -0.15 in the classification, and the classes were then created as expected.
This seems like strange behavior in Pro—could it be a bug? Why isn’t -0.149068 recognized as a value in the first class?

JonM32

Not sure why - that's likely how they wrote the code to assess values.

Glad it worked for you!

Jon

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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