Chapter 3 Notes:
Types of tools, batch processing. Model tools vs script tools, how to automate workflows. Dynamic naming for batch processing %Name%. Took me about 40 minutes to read thoroughly.
Chapter review questions:
Describe some of the general elements of the geoprocessing framework in ArcGIS Pro?
Collection of tools organized into toolboxes, python window for executing python, geoprocessing history, Model Builder.
What are the three types of tools in ArcGIS Pro?
Geoprocessing, analysis tools, geocoding, cartography.
Explain the difference between system tools and custom tools.
System tools are premade executable tools that you can drag and drop your files into to complete a task/output. Custom tools are obtained by the user through their own creation or collection of third-party tools.
Provide examples of commonly used environments and how they impact running geoprocessing tools.
Environments are where the workspace is located essentially, and environments can be modified to use specific values for the output of the geoprocessing tools.
What are the strengths and limitations of batch processing in ArcGIS Pro?
Batch processing uses the same tool multiple times using different parameters. Different iterations use different parameters to finish their processing. For tools with multiple input parameters, you can only choose one to use as a batch parameter.
Explain the use of dynamic naming in batch processing.
Creates a different output for each individual parameter. %Name% uses the input variable name and combines it with the remaining part of the naming scheme. %Name%_final will turn all inputs into separate outputs with their respective names.
What are some of the differences and similarities between model tools and script tools in ArcGIS Pro?
Model tools help you execute multiple tools at the same time, while script tools help you create your own detailed tool by connecting applications, better programming logic, and can be run by themselves on a stand-alone script reader.
Why would you automate a specific workflow instead of a model?
It’s more reliable to automate one workflow and observe it, rather than automating a model and trying to decipher the results after all functions are completed running.
What are ways to run python code in the context of automating workflows in ArcGIS Pro?
Scheduling python scripts to run at an exact time, by using the task scheduler.