Hot answers tagged modelbuilder
This isn't an issue with ArcGIS, but rather a limitation of the DBF fille format. DBF files have a maximum of 255 fields. See: Maximum number of rows and columns can a DBF file contain
Download the ET Geowizards toolbox (Free) and use the createCenterlines tool. I think that should do the trick.
Currently we just keep toolboxes on a Windows file server and roll back using the "Previous Versions" functionality if anything breaks. I am looking into storing toolboxes in Git (using TortoiseGit and GitHub Enterprise), which we already use for Python scripts and FME workspaces. Since regular toolboxes are binary, you aren't able to diff and interactively ...
Set up your model as shown below Use Iterate Feature Selection in your model Use the watershed name/id field as group by field Use Value in the clip tool as part of the output name. %Value% Value contains the name/id of the watershed.
in_memory workspace is styled as a gdb so it should work if you delete the ".shp" http://resources.arcgis.com/en/help/main/10.2/index.html#//002w0000005s000000 "A table, feature class, or a raster written to the in-memory workspace will have the source location of GPInMemoryWorkspace, as illustrated below."
In order to load your "Stops" data into the in_memory workspace, use the Copy Features geoprocessing tool. The output featureclass should be referenced as "in_memory\stops". Really, though, there is limited value in loading the source data (on disk) into memory first. Rather, you should simply output all of your interim geoprocessing tasks into the ...
In order to perform this task in ArcGIS 10.1, you will require the Spatial Analyst Extension which can perform analysis on rasters including Least-Cost Path. ESRI has created a series of tutorials to get you started with Spatial Analyst. The last of which creates the optimal route to a site. If you follow the tutorial you should be on your way to finding ...
Most of what you are asking for is not really feasible or applicable to ModelBuilder. Either it works or it doesn't. Sometimes you get useful error messages, other times you just have to tweak things, futz around, send in bug reports, stand on one leg, make ritual sacrifices to the ModelBuilder gods, etc. There are a couple of useful "debugging" tips I ...
I would write a Python script that checks the model inputs, returning True or False. Then create a script tool for the script. You can drop this tool into your model, as the first node. This basically mimics the validation class of a Python script tool. You can add as many functions and classes as you need, import any module too. Add a script to a model
The Understanding validation in script tools page implies that customizing tool validation is only available to Python script tools in regular toolboxes and the tools you write as Python classes in Python (only) toolboxes. It should be possible to write a Python script tool (or a tool in a Python toolbox) that takes parameters, does the validation and then ...
The images below are a different way to solve this. In the Summary statistics tool I am collecting the Count of the ObjectID field and then appending this into a pre-existing empty table.
You are close. In both models you will need to add the model only tool Calculate Value. The output of that tool should also be an output parameter of the inner model. You can't use the output of collect values as the input directly so set it as the precondition. Then set the expression of Calculate Value to: sum_counts('%Row Counts%') %Row Counts% is ...
As I suggested above the solution to this is to edit the polygons and then using the explode multi-part polygon tool separate the triangles from the rest of the feature, select and delete.
I haven't done anything like this before but my guess is you need to make a Near Table. To do this, I'm thinking you'll need to create points from the raster first. Then make your Near Table and include the optional "Add Location Field". Once you have that table you'll need to figure out the elevation of the points from the road feature that are in the ...
I see two issues. First, it doesn't look like you are actually setting the output parameter. In the first script, you have: folder = arcpy.GetParameterAsText(0) outfolder = arcpy.GetParameterAsText(1) and then later: arcpy.SetParameterAsText(0,'pom') That last line essentially tries to assign 'pom' to the same parameter that you got your folder ...
I don't think there is any way of tracking change in a model as you build it and I'm not sure why you would want to do that anyway? What is important is explaining to others the reasoning behind your model. For example why do your inputs need to be in a file geodatabase, why did you create a field and divide a value by some other number? This sort of ...
Only top voted, non community-wiki answers of a minimum length are eligible