4

I've had raster tools fail while working in an MXD, but work just fine using the same steps in a new blank MXD or in Catalog. Always worth a shot to try out if you're stumped.


2

This can be an issue when you have a project-on-the-fly situation, which cause resampling into your process. You might want to try working on the environment Output Coordinate System. Try to set input the same information as the raster data your are filling. Here is the ESRI error code help page to use as reference.


2

The Extract By Mask tool honours the Scratch Workspace environment. Try setting a different arcpy.env.scratchWorkspace for each script run with the python tempfile.mkdtemp function. import tempfile, shutil import arcpy from arcpy.sa import * tmpdir = tempfile.mkdtemp() arcpy.env.scratchWorkspace = tmpdir reclass_clp = ExtractByMask(reclass, ...


1

Here's the for my original post. Since my feature class layer generates so many overlapping polygons so Zonal stats as a table did not work. So, I broke up my original multi-polygon feature class into separate shapefiles and then extracted LU per each polygon based on Zontal Stats and append all tables generated into a single table- which is what I needed. ...


1

A quick distinction: In ArcMap, "Point Density" will yield a heat map (mostly used for visualization) while something like "Hot Spot Analysis (Getis-Ord Gi*)" will yield a true statistical hot spot analysis. Here is a link with a bit of information on the distinction: https://www.gislounge.com/difference-heat-map-hot-spot-map/ also this GIS SE post: ...


Only top voted, non community-wiki answers of a minimum length are eligible