Latest Contributions by DanPatterson

Follow the instructions in the error 160077: An underlying database error occurred.—ArcGIS Pro | Documentation and try saving to a different folder path since f = "M:\xyzx\Market Planning.gdb\HospitalMaster" throws a unicode path error because of the \x while f = "M:\Axyzx\Market Planning.gdb\HospitalMaster" doesn't ... View more

Do you have the link? It isn't showing up on the Support site using the bug number or even just the word 'apostrophe' as search keys ... View more

You could do a convex hull as a first approximation using the Minimum Bounding Geometry tools to see what it looks like first.  If you want to get a tighter approximation try the concave hull with the points as the input.  Concave Hulls  require points as input. ... View more

sorry, I don't work with the Living Atlas if it is this one, then directing that specific query there may assist you ArcGIS Living Atlas of the World - Esri Community ... View more

suggested previously already.... in short, navigate to the folder containing the raster or the location of the raster in a geodatabase. ... View more

are all the inputs in the same coordinate system?  If not, get the inputs into one common coordinate system prior to buffering and clipping and comparing ... View more

Excel To Table (Conversion)—ArcGIS Pro | Documentation Table to NetCDF (Multidimension)—ArcGIS Pro | Documentation might be something to look at, you might be able to skip the first one ... View more

a bit of a pain, a soft reset might be helpful How To: Perform an ArcGIS pro Soft Reset   ... View more

How To: Convert Raster Pixel Values from Feet to Meters and Meters to Feet in ArcGIS Pro might help ... View more

if you are getting polygons building, why not simplify the polygons to points (which would be their centroid) Feature To Point (Data Management)—ArcGIS Pro | Documentation which would be less onerous buffering than the polygon boundaries.  also your buffer distanc ... View more

I saw that, but it is the error number that is being thrown regardless of the spatial analyst tool being used.  I couldn't tell if your raster was an esri grid or a raster in a geodatabase (since there is no *.tif extension, for example).  If it is an esri grid, then the path cannot contain spaces. The fact that the red x occurs on the line where the percentage threshold is located isn't related to the error message. There is nothing related to that particular tool in the public facing suppor site, only errors relating to spatial analyst tools and that particular error number.  Tech Support may have access to non-public causes for this error if my suggestion still doesn't pan out. Good luck ... View more

are edits saved prior to querying? ... View more

Near (Analysis)—ArcGIS Pro | Documentation comes to mind ... View more

see your original thread for a suggestion The output path contains spaces. - Is this a bug? - Esri Community If it is the one, then it says This issue is addressed in ArcGIS Pro 3.7. ... View more

probably not directly related,but there are a few errors associated with 010819 number relating to how the input data sets are accessed BUG-000179464 for ArcGIS Pro in short, navigate to the folder containing the raster or the location of the raster in a geodatabase... don't select the layer name, but navigate to the source data.  esri grids don't work if the source folder contains spaces ... View more