topic Re: Model Builder exported to Script defciency in Geoprocessing Questions

Model Builder exported to Script defciency

KarenWitsell — Thu, 21 Feb 2019 21:57:21 GMT

Exporting a script from model builder with the hope of creating a functional python script. I need to be able to have the option of selecting my inputs. Some locations have data while others do not. I want to be able to run the script and select my inputs, while ignoring other inputs. I have multiple potential feature classes as inputs. I've identified these as variables but after running the python script, I receive the following error message.

ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000735: Input Datasets: Value is required
Failed to execute (Merge).

Here is the script:

# Import arcpy module
import arcpy

# Script arguments
PotentialArea_A = arcpy.GetParameterAsText(0)

ProtectiveZone_A = arcpy.GetParameterAsText(1)

Wetland_A = arcpy.GetParameterAsText(2)

...

# Local variables:
Merge = "...Merge"
Dissolve = "...Dissolve"

# Process: Merge
arcpy.Merge_management("'';'';'';'';'';'';'';'';'';''", Merge, "")

# Process: Dissolve
arcpy.Dissolve_management(Merge, Dissolve, "", "", "SINGLE_PART", "DISSOLVE_LINES")

Re: Model Builder exported to Script defciency

ColeAndrews — Thu, 21 Feb 2019 22:15:59 GMT

If you want the geoprocessing to be interactive ("need to be able to have the option of selecting my inputs"), then what is the reason you do not want to leave it as a tool/model in ArcGIS?

Re: Model Builder exported to Script defciency

KarenWitsell — Thu, 21 Feb 2019 22:33:32 GMT

I would like to move the code into python and out of model builder. I think the model itself is not as functional as I want it to be. Hoping to find more functionality in python.

Re: Model Builder exported to Script defciency

DanPatterson_Retired — Thu, 21 Feb 2019 23:22:44 GMT

Karen, your input parameters should be associated with parameters in a toolbox,

Running the script in standalone mode, given the number of parameters, would require you to do a lot of typing.

If you haven't created a convention tool in Arctoolbox, and are using ArcGIS Pro, then have a look

/blogs/dan_patterson/2016/05/19/toolbox-creation-in-arcgis-pro

The principles are essentially the same as in ArcMap.