Latest Contributions by DanPatterson_Retired

"image service is not supported by the current license" seems to be the root cause, you had better check your licensing ... View more

I suspect it is the aggregation step what affect do you think that has on the output given your parameters How Aggregate works—Help | Documentation  The change in cell size seems to be the issue ... View more

How Fill works—Help | Documentation  Since I am not sure what your intent is in your workflow, then the comment from the above link may be pertinent to it. The Fill tool uses the equivalents of several tools, such as Focal Flow, Flow Direction, Sink, Watershed, and Zonal Fill, to locate and fill sinks. The tool iterates until all sinks within the specified z limit are filled. As sinks are filled, others can be created at the boundaries of the filled areas, which are removed in the next iteration. ... View more

probably because you bands aren't named as in that example  '\Band_4' will therefore fail. Since you already have the spatial analyst extension there is no advantage to using numpy and unless you know how to account for nodata values which may exist, then your results may be suspect.  I have several blog posts on using numpy with raster data which you might want to look at if you want to persist on using a non-SA solution ... View more

the statement that "new sinks can be created" during the process How Sink works—Help | Documentation  And I am not sure why you would resample the Fill rather than the dem if you want the sinks at a coarser resolution ... View more

First, check the raster properties to see if the raster does have bands 4 and 5. Second, why don't you use... NDVI—Spatial Analyst module | Documentation  ... View more

If it is a bug, it isn't in the posted bug list, so maybe it hasn't been reported https://support.esri.com/en/Search-Results#search?q=memory%20workspace&content-type=Bugs Kory Kramer‌  5000 sounds familiar, but not sure if it is associated with the memory workspace ... View more

What specifically are you using in the two toolsets? An overview of the Data Reviewer toolbox—Data Reviewer toolbox | Documentation  ... View more

In fact, you indicated that the attributes are the same, which suggests that the fields are the same, so the code sample is much easier import arcpy arcpy.env.workspace = "C:/path_to_your/data.gdb" arcpy.Append_management(["featureclass1", "featureclass2"], "TEST")‍‍‍ ... View more

also check that the field containing the dat is indeed Id and doesn't have any trailing space. And if you have any nulls in the field, you will have to edit your code OR, just query the field for all values no equal to None eg <null> ... View more

Append—Data Management toolbox | Documentation  to an existing file Merge—Data Management toolbox | Documentation  to a new file ... View more

have you inserted a map into the project?  that is usually a start for most people, then adding some data to the map. Think of "insert" as project level functionality and 'add' as object level functionality. ... View more

Create Address Locator—Help | Documentation  Create Composite Address Locator—Help | Documentation  No pane, no view, there are these tools, just for you ... View more

The 'warning' could be corrected in the csv file prior to performing the join, if you can identify what field it is.  The mismatch in records may indicate that more data is available than the number of locations in the destination table... that isn't an issue.  The data in join fields are text-case sensitive if you have blank rows. Hope you got it done. ... View more

def Reclass(Level): becomes def Reclass(Id): You need to replace Level by Id without the ! marks.  or... replace all the Id 's in your code block by Level. If isn't a good idea to use the field name inside the def, but you did ... View more