What is geoprocessing?
Last modified December 9, 2008
Print all topics in : "Geoprocessing"
Geoprocessing is for everyone that uses ArcGIS. Whether you're a new user or an old pro, geoprocessing will become an essential part of your day-to-day work with ArcGIS.
The fundamental purposes of geoprocessing are to allow you to automate your GIS tasks and to perform spatial analysis and modeling. Almost all uses of GIS involve the repetition of work, and this creates the need for methods to automate, document, and share multiple-step procedures known as workflows. Geoprocessing supports the automation of workflows by providing a rich set of tools and a mechanism to combine a series of tools in a sequence of operations using models and scripts.
The kinds of tasks to be automated can be mundane—for example, to wrangle herds of data from one format to another. Or the tasks can be quite creative, using a sequence of operations to model and analyze complex spatial relationships—for example, calculating optimum paths through a transportation network, predicting the path of wildfire, analyzing and finding patterns in crime locations, predicting which areas are prone to landslides, or predicting flooding effects of a storm event.
Geoprocessing is based on a framework of data transformation. A typical geoprocessing tool performs an operation on an ArcGIS dataset (such as a feature class, raster, or table) and produces a new dataset as the result of the tool. Each geoprocessing tool performs a small yet essential operation on geographic data, such as projecting a dataset from one map projection to another, adding a field to a table, or creating a buffer zone around features. ArcGIS includes hundreds of such geoprocessing tools.
Geoprocessing allows you to chain together sequences of tools, feeding the output of one tool into another. You can use this ability to compose an infinite number of geoprocessing models (tool sequences) that help you automate your work and solve complex problems.
The workflow example below uses two geoprocessing tools, Project and Clip. This is but one example of a number of tasks you can automate with geoprocessing.
Suppose you've received 20 coverages and shapefiles from a colleague, and they're in different map projections and contain lots of features that are outside your study area. Your task is to change the map projection of each of the 20 datasets, remove the extraneous features ("clip" the datasets), and put them all into a file geodatabase.
By far the easiest way to accomplish this task is to use geoprocessing. First, you would use the geoprocessing Project tool, which applies a new projection to an input feature class to create a new output feature class. The illustration below shows the Project tool dialog box with its input features shown in the upper left and the projected features in the upper right. The projected coordinate system is Albers Equal Area Conic.
The second step is to use the geoprocessing Clip tool to clip the data that falls outside your study area. The Clip tool takes two inputs, a feature class of any type (point, polyline, polygon) and a polygon feature class (the clip feature class), and creates a new feature class of just those features that fall inside the clip polygons.
Both the Project and Clip tool can be used in Batch mode, which lets you input the list of your 20 feature classes, and the tools automatically execute once for each of the feature classes. You can create the list by dragging and dropping the feature classes from ArcCatalog onto the tool dialog box.
Or better yet, you can quickly create a geoprocessing model that chains together the Project and Clip tools, feeding the output of Project into the input of Clip, and use the model in Batch mode. The model you create becomes a new tool in your geoprocessing environment.
Here is a bit more complex use of geoprocessing that performs a simplified site selection for parks and produces a dataset of potential park sites that can be further evaluated. The site selection logic is to find areas that are close to densely populated areas but are not close to any existing parks, the logic being that you want parks close to people, but you don't want parks clustered tightly together. Furthermore, it is deemed more important to have parks close to populated areas than it is to place a new park further away from existing parks. As noted, this is very simple logic and only serves to identify potential sites for further evaluation (such as compatible land use, site availability, and site qualities).
In the illustration below, the Potential park sites map shows more suitable locations in dark purple, while less suitable areas are shown in lighter shades. Gray areas mark the locations of existing parks. The illustration also shows that Population density is a more influential factor, that is, has a higher influence (60), in site selection than Distance to parks (40). (These weights are entirely arbitrary.)
The following geoprocessing model illustrates the preceding logic. There are five steps in this model, each labeled with a blue circle.