nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Combing Multiple Models

CraigCarsley

I'm starting to get a feel for Model Builder, but I can't figure this out:

I've got 9 geoprocessing models that are all part of the same essential process. I want to have one model, or script, that will run each one of them consecutively. I tried doing everything in a single model, but I got red exes on some of the tools because I am overwriting some datasets. At the same time, it could be useful to keep each step separated anyway.

So, does anyone know of anyway to automate running 9 models consecutively?

Thanks!

Encuentra más publicaciones etiquetadas con

Accepted answers

RussellBrennan

Hi Mike,
What I think is the easiest way to do this is to call each of your models from a script. If all of your models are in a single toolbox this is really easy. This is a much cleaner way to execute the custom functions without having to write any??? complex python.

Write a python script that looks like this (sorry for the lame names in the example):

import arcpy  #Import the toolbox containing the models. arcpy.ImportToolbox(r"c:\temp\toolboxname.tbx", "toolboxAlias")  #Run each model as though it were a tool arcpy.ModelName_toolboxAlias() arcpy.Model2Name_toolboxAlias() arcpy.Model3Name_toolboxAlias()

In the example above I have a toolbox named 'toolboxname' that stores all of my models. In this toolbox I have three models named ModelName, Model2Name, Model3Name. In the example I have also chosen an alias for my tools. The alias is 'toolboxAlias', the alias is just used to differentiate your tools from other system tools so there are not name collisions. This is similar to some core tools that have a _management or _analysis alias. Each of the models do not take any input parameters hence the (). If one or many inputs were required for these models you would put them between the () brackets (ex: arcpy.ModelName_toolboxAlias('c:\temp\test.gdb\featureclass'))

You can then run this very simple script to call your models in sequence.

A (slightly) better example might look like this:

import arcpy  #Import the toolbox containing the models. arcpy.ImportToolbox(r"c:\temp\my_analysis.tbx", "models")  #Run each model as though it were a tool arcpy.CustomBufferIntersect_models() arcpy.CreateNewFeatures_models() arcpy.MakeSurface_models()

All comments

CraigCarsley

Michael,

Yes, I went ahead and just did it. Generated a few other errors, but I think its working now.
Thank you all for your input!

mvolz47

Craig:

I believe you need to convert the VB Expression to a python expression to support ArcGIS Server services. There should be plenty of help to assist you in the python format, but if you can not locate help I'll try to dig up some sample syntax for you.

CraigCarsley

Russell,

That was definitely the problem I was running into, so thank you!
Unfortunately, I've hit another error. Have you ever seen something like this:

[ATTACH=CONFIG]27171[/ATTACH]

I can't tell if the script just hit a snag on one of the values, or if I really can't execute a VB Expression as part of one of the models.
Would love to have your thoughts.

Thanks!

RoadClass_Error.JPG

RussellBrennan

Go into your model properties and check that the name of the model is what you are using. The label is what appears in ArcCatalog when you are browsing. The name is what python uses to find the tool. You can have a name and label that are completely different from one another.

CraigCarsley

Casing is all correct.
I commented out Tool0_PreScript because it returned the error. After that, Tool1_DeleteStreets returned the error. The script seems to stumble over any line in that part of the script.

RussellBrennan

Check your casing. Python is case sensitive.
Double check that the tool name is spelled correctly.

If you un-comment out the first tool does it execute successfully?

CraigCarsley

Thanks for the help Russell. I'm still having a little trouble. This is my code:

import arcpy

arcpy.ImportToolbox(r"X:\GIS_Projects\Street_Centerlines\Update.tbx","Streets")

#arcpy.Tool0_PreScript_Streets()
arcpy.Tool1_DeleteStreets_Streets()
arcpy.Tool2_CopyData_Streets()
arcpy.Tool3_CalcROADCLASS_Streets()
arcpy.Tool4_AppendStreets_Streets()
arcpy.Tool5_CalcPSAP_Streets()
arcpy.Tool6_CalcMUNILEFT_Streets()
arcpy.Tool7_CaclMUNIRIGHT_Streets()

I'm getting this error at the moment:

Traceback (most recent call last):
File "X:/GIS_Projects/Street_Centerlines/Python_Scripts/Automate_StreetUpdate2", line 6, in <module>
arcpy.Tool1_DeleteStreets_Streets()
AttributeError: 'module' object has no attribute 'Tool1_DeleteStreets_Streets'

I can't quite figure out what I'm doing wrong... any thoughts?

Thanks

RussellBrennan

Hi Gavin,

When you import your toolbox using arcpy.ImportToolbox the models within your toolbox function just like any other tool. Essentially each model becomes a tool. You will then have the ability to use try/except blocks catch any failures. You could also parse messages returned from 'arcpy.getmessages()' if there are specific messages you are interested in investigating.


import arcpy#Import the toolbox containing the models.arcpy.ImportToolbox(r"c:\temp\my_analysis.tbx", "models")#Run each model as though it were a tool#use try/except for finding major failures.#use getmessages to find more specific info.try:    arcpy.CustomBufferIntersect_models()    msg = arcpy.GetMessages()    if msg.lower().find('error 000375'):        print "Do something!"    else:        print "That's not working, do something else!"    arcpy.CreateNewFeatures_models()    arcpy.MakeSurface_models()except:    print 'Oh no! Something went wrong'

When calling the model from a script you do not get granularity at the tool level you just get the entire model. This is what we usually recommend for people who want to do some sort of automated process but do not want to write much Python. The problem with the scripts exported from models is that they are very messy and hard to read. Also you can end up with a lot of redundant code.

Hope this helps.

GavinMcDade

Hey guys,

I work with Mike and the models/scripts in question are actually mine. Our main reason for exporting our models to Python scripts and running them as such is mainly because of the ability to augment the scripts to include Try/Except error-handling, etc. That said, I wouldn't mind implementing your script below, Russel - albeit, to call the Python scripts instead of the models themselves. Does that function the same way as calling a model?

Gavin

RussellBrennan

import arcpy  #Import the toolbox containing the models. arcpy.ImportToolbox(r"c:\temp\toolboxname.tbx", "toolboxAlias")  #Run each model as though it were a tool arcpy.ModelName_toolboxAlias() arcpy.Model2Name_toolboxAlias() arcpy.Model3Name_toolboxAlias()

import arcpy  #Import the toolbox containing the models. arcpy.ImportToolbox(r"c:\temp\my_analysis.tbx", "models")  #Run each model as though it were a tool arcpy.CustomBufferIntersect_models() arcpy.CreateNewFeatures_models() arcpy.MakeSurface_models()

CraigCarsley

That helps, thanks!

mvolz47

Craig:

The echo statements allow for messages to be written to the log file (for understanding how processes are working), as well as to the DOS prompt.

I am able to call just the python script name because I am running on a 64 bit server with only the 32 bit version of python installed (c:\Python26\ArcGIS10.0\python.exe) and the PYTHONPATH environmental variable set to c:\Python26\ArcGIS10.0. [If you are running on a server with ArcGIS Server also installed with background processing enabled this gets trickier as you will also have a 64 bit version of python installed on the machine.]

>>update_parcel.log after the call to the python script allows me to use print statements in the python script that get written out to the log file.

I use the %time% statements to write out important times in the process to the log file which helps to diagnose problems and determine how long processes run so I can optimize times when scripts are run, especially when order of the scripts is important and I need to work around database maintenance times.

CraigCarsley

I must be less apt for this than I thought.. I can't make any sense out of that. Any chance you could explain a little more?

mvolz47

@echo off

echo Start time: %time% > update_parcel.log

echo ------------ Update time: %time%
echo ------------ 06 Truncating parcel feature class -----------------------
echo ------------ 06 Truncating parcel feature class ----------------------- >> update_parcel.log
06_truncate_parcels.py >> update_parcel.log

echo ' ' >> update_parcel.log
echo Update time: %time% >> update_parcel.log
echo ' ' >> update_parcel.log

echo ------------ Update time: %time%
echo ------------ 07 Appending parcel feature class -----------------------
echo ------------ 07 Appending parcel feature class ----------------------- >> update_parcel.log
07_append_parcels.py >> update_parcel.log

echo ' ' >> update_parcel.log
echo Update time: %time% >> update_parcel.log
echo ' ' >> update_parcel.log

@echo on

CraigCarsley

Thanks Michael,

I have been trying to figure out how to do just that. I'm not much of a python whiz.
Would you, please, provide an example?

Thanks again

mvolz47

I would export your models out to python scripts and then call them consecutively from a bat file that is called from a scheduled task.

I can provide a sample bat file if you need it.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.