How-to documents introduce you to not so obvious ways to customize geoprocessing functionality to you, and your teams', needs and thus improve your geoprocessing experience. They are written in tutorial style and each document guides you step-by-step through a customization or model building process.
The Introducing Geoprocessing panel presents a collection of a dozen frequently used geoprocessing tools - Append, Buffer, Clip, Dissolve, Erase, Identity, Intersect, Merge, Multipart to Singlepart, Near, Point Distance, Union - along with easy access to these tools and their help. In this document you will learn how to add the Introducing Geoprocessing panel to your menu or toolbar for easy access to this geoprocessing functionality.
Merge is one of the twelve most frequently used tools included in the Introducing Geoprocessing panel.* The ArcGIS 9.1 version of Merge is extended to include a Field Map control for easy Output Field management. You can rename, reformat, delete, add, and define Output Fields using existing Input Fields. In addition, you can delete duplicate Input Fields, or merge them into one existing Input Field. In this document you will learn how to work with the Field Map on the Merge tool.
* It is also available from the ArcToolbox window in the General toolset in the Data Management Tools.
For easy, speedy, and productive project work, create your own look and feel for the ArcToolbox window by setting global, project, and tool environments specific to each of your projects. In this document you will learn how to easily customize the ArcToolbox window for your project work.
To make your project work more productive, you can further customize the Geoprocessing environment. Very useful features include setting preferences of workspaces, output coordinate systems, tolerances, and grid sizes. In this document you will learn how to set different levels of environment settings for easy project work.
In ModelBuilder, unloading geodatabase feature classes to shapefiles for further geoprocessing represents a challenge because the initial unloading is a many-to-one operation: Many geodatabase feature classes are unloaded into a single workspace or folder and simultaneously converted to shapefiles. ModelBuilder has no way of knowing how many feature classes there are and what their names are, information needed for further geoprocessing processes. Currently, the most elegant solution is through a script, especially if all features are processed the same. In this document you will learn how to unload geodatabase feature classes and subsequently buffer and uniquely name the output shapefiles using a script tool.