Geoprocessing, Int much slower than RasterCalculator

Kevin_Andras

I need to convert floating point rasters to integers.  Seemed logical to use the Int (Spatial Analyst) function.   

Turns out this sits around for 2 or 3 minutes (at 0% completed) before it even does the processing. 

When I do the same thing with a raster calculator expression, it takes 7 seconds. 

Same behavior whether I call this via my add-in or just executing geoprocessing tools.

 Any clue why Int takes forever?

 

DanPatterson

Interesting.  Perhaps it might have something to do with the optional Environment parameters that the Int tools supports

Int (Spatial Analyst)—ArcGIS Pro | Documentation

check to make sure that the cell size, extent etc is the same as the input float raster.

I also notice that the output raster type seems to be different in the examples that you provided (unless the first output name is truncated.)

Do the comparison with the same output type if this is not the case