Latest Contributions by curtvprice

According to the first table on that help page, ordinary kriging does support trend removal. However, if you have known trends or other issues, I recommend looking into EBK which is designed to automatically do a lot of the work required for a valid kriging analysis. It also provides a lot of diagnostics the other methods do not. ... View more

You are missing the Collect Values tool in your submodel, then the submodel will pass back the generated list of rasters.. See the help for an example. (UPDATED LINK) In ArcGIS Pro, Zonal Statistics as Table has been updated to support overlapping polygons.    ... View more

It's possible the polygon is corrupt, try checking it with Check Geometry tool. The other thing that comes to mind is your polygon may be too complex for these tools to handle (ie many vertices) in which case making a copy of the polygon feature class and running Generalize on the copy may help. ... View more

Sorry, I was in lab and didn't want you to go down that rabbit-hole. 🙂  If you check the Recursive box in the iterate feature class tool, it will iterate through a list of all the feature classes in the geodatabase, the paths will include the full paths which can then parse using the approach I suggested. One iterator should cover all the feature classes in the geodatabase this way, no need for a complicated nested iterator in a submodel. ... View more

From the help: Model Parameters Symbology You can save a layer file with a defined symbology and use that layer file as a template for how your model outputs will be symbolized when added to a map. This can be accomplished in two ways: Set the Symbology option of an output parameter to a layer file path such as C:\Data\LandUseOverlay\Symbolized.lyrx on the Parameters tab of the tool's Properties window. Add the Apply Symbology From Layer tool to the end of your model, and set the Symbology Layer parameter to a layer file path.   ... View more

Nope ... View more

parsepath.png The input SDE path above is C:\Users\mbeal\AppData\Roaming\ESRI\ArcGISPro\Favorites\OCGIS_2020.DBO.CadastralReference\OCGIS_2020.DBO.GeorgiaMilitiaDistricts The Calculate Value expression I'm using above is: r"%name (2)%.%Extension (2)%" which when executed becomes OCGIS_2020.DBO.CadastralReference After this you would use Calculate Value like before to assemble the pieces of your path, when it is correct you can use it for Append as you were before, except the path will be correct. ... View more

Example: First parse path: input: C:\test.gdb\fds\fc output:c:\testgdb\fds Second parse path input: C:\Testgdb\fds output: fds ... View more

Try the Parse Path tool to manipulate the Feature Class pathname. Then include that variable (containing the feature class name) in your output path. You'll need to use it twice, first to pull out the full path to the feature dataset, a second run to strip out the feature dataset name. ... View more

I would try to run the append command manually first. If the inputs paths are correct this is not a ModelBuilder problem. Feature datasets could possibly mess with the path issue (requiring more complex logic for your Calculate Value expression) but you said the paths were correct. Wondering about your "Favorites" paths - have the EGDBs been added to the project? I don't know if that matters or not. ... View more

Here's my attempt at a workflow for you, which I set up using file geodatabases; should work the same with Enterprise if the paths are correct. The tricky part is that Calculate Value expression is   (a) a Python string expression and (b) the "r" is a raw string to protect the backslashes. Run this thing and if the paths look right, add the Append tool to the model, connecting the two feature class variables (old and new) to the append tool. The preconditions both document what you are doing and also make sure that the model variables used within the Calculate Value expression are up to date during each iteration. Hope this helps you out! path_model.jpg   ... View more

I would delete the append tool for now and use the Calculate Value tool with an expression like this to generate the output path: output\enterprise\geodatabasepath\%Name% Then run the iterator model and see if the output paths are correct. If they look good, add the Append back and connect that Calculate Value output  (set its data type to feature class in the CV tool first)  to the Append tool as an input. ... View more

You need to do an iterator and then use the %Name% field to find the input for the append tool. I think a good approach to getting started is to use an iterator with the Calculate Value tool to generate the paths you need, when you get that working, you can feed those paths to the append tool. ... View more