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

Reclassify Tool Remaps Incorrectly

JeromeHaaland

Starting in 10.7... the reclassify tool fails to have the same number of classification break values as the legend in the TOC. The tool now always has 9 breaks or ranges, regardless of the number of breaks in the input raster layer in the TOC.

By default this tool is supposed to use the exact same classification break values as the input raster layer in the TOC.

Was hoping this bug would be fixed in 10.8, nope.

ESRI does such a bad job of fixing bugs. I have used ESRI products extensively for close to 15 years. All software has bugs... but ESRI has so many bugs, they seem to say "We totally don't care."

Reclassify—Help | Documentation

Find more posts tagged with

Accepted answers

All comments

KoryKramer

Hi Jerome. I'm sorry that you're running into a bug. Since your organization is already attached to it, you should be able to escalate that through the process described here: https://community.esri.com/groups/technical-support/blog/2016/03/28/how-to-escalate-a-defect

That said, in the link that Dan pointed to, there is the following workaround which seems simple.

I hope that helps.

DanPatterson_Retired

I don't make excuses. I try to help people (I am not an employee either).

Good luck

Kory Kramer‌ perhaps you can confirm if it is the bug and pass it along

JeromeHaaland

That makes absolutely no sense.

If ESRI can not keep track of their own list of bugs... and not show some sort of prudent judgement pertaining to fixing those bugs... it simply shows an extreme lack of responsibility, pride in their work and basic good management.

You can make all the excuses you like. I have watched them for years with bug after bug. They are soooo sloppy.

DanPatterson_Retired

Report and/or Subscribe ... that's how fixes get escalated.

JeromeHaaland

That does appear to be the bug.

DanPatterson_Retired

This bug?

BUG-000120325: When the input raster is a layer from Table of Conte..

If it is, there is a Subscript button beside the bug number to track and see if it is resolved.

There are a number of others, but much older

https://support.esri.com/en/Search-Results#search?q=%22reclassify%20tool%22&content-type=Bugs

if you see a pattern.

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.