AnsweredAssumed Answered

Reclassify: NoData Bug

Question asked by Rock_Doc on Oct 26, 2017
Latest reply on Nov 26, 2017 by Rock_Doc

If I set my environment settings correctly (every other tool in spatial analyst masks things properly), and then reclassify a raster, and change the NoData value from NoData to (for example) -99, when it produces the output raster, it doesn't mask it. It can't seem to differentiate between NoData areas that fall within the study area mask, and NoData areas that fall outside of the study area mask. See attached screencap for example. I then have to run Extract to Mask to get it to clip my reclassified raster properly.

 

I need the NoData areas to be an integer for some other processing I am doing, I can't leave them as NoData. Obviously I can keep doing what I'm doing and just run the Extract to Mask all the time, but it's just a pain when I have to batch process lots of maps, because now it's taking double the amount of time having to do the extra step. 

 

Are ESRI aware of this bug? And can they please fix it?

 

Issue has been replicated on 10.3.1, 10.4, and 10.5.

Attachments

Outcomes