AnsweredAssumed Answered

Raster value field type incorrectly identified

Question asked by isburns on Nov 4, 2016
Latest reply on Nov 5, 2016 by curtvprice

I have an 8-bit raster (TIFF, IMG, and FGDB rasters all exhibit the same behavior) with the pixel type of unsigned integer. In ArcMap 10.2, the value field is being incorrectly identified as a double, so it can't be used in tools like Tabulate Area that require an integer field for the zone field. In ArcMap 10.3 and 10.4.1, the value field is correctly identified as a long. The problem seems to be an introduced one because the value field in the original raster is correctly identified as a long. The original raster was the 2011 NLCD Land Cover (Multi-Resolution Land Characteristics Consortium (MRLC)), which was then clipped using the Clip tool (Clip—Help | ArcGIS for Desktop), and the result of this is where the value field is misidentified as a double.

 

In summary:

  • In ArcMap 10.2, 10.3, and 10.4.1, executing Clip on an integer raster with the output saved as a TIFF, IMG, or FGDB raster results in the value field being incorrectly identified as a double in ArcMap 10.2, but correctly identified as a long in ArcMap 10.3 and 10.4.1
  • In ArcMap 10.2, 10.3, and 10.4, executing Clip on an integer raster with the output saved as a GRID results in the value field being correctly identified as a long in ArcMap 10.2, 10.3, and 10.4.1
  • Exporting the clipped TIFF, IMG, or FGDB raster to a GRID results in the field being correctly identified as a long in ArcMap 10.2, 10.3, and 10.4.1
  • Exporting the clipped TIFF, IMG, or FGDB raster to a TIFF, IMG, or FGDB raster results in the field being incorrectly identified as a double in ArcMap 10.2, but correctly identified as a long in ArcMap 10.3 and 10.4.1

Has anyone experienced this bug, or can you reproduce it?

Outcomes