ArcGIS 9

Geoprocessing Commands Quick Reference Guide

Copyright 2004, 2005 ESRI All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts and Legal Services Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. The information contained in this document is subject to change without notice.

Contributing Writers Melanie Harlow, Ghislain Prince, Catherine Jones, Corey Tucker, Jeff Reinhart

U.S. GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 52.227-14 Alternates I, II, and III (JUN 1987); FAR 52.227-19 (JUN 1987) and/or FAR 12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS 252.227-7015 (NOV 1995) (Technical Data) and/or DFARS 227.7202 (Computer Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. ESRI, ArcView, ArcGIS, ArcInfo, ArcCatalog, ArcToolbox, ArcSDE, ModelBuilder, ARC/INFO, ArcMap, 3D Analyst, ArcEditor, and www.esri.com are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions. Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners.

Table of Contents

Introduction ArcGIS Desktop core geoprocessing tools

Analysis toolbox Cartography toolbox Conversion toolbox Coverage toolbox Data Management toolbox Geocoding toolbox Linear Referencing toolbox Multidimension toolbox Spatial Statistics toolbox Server toolbox

1 3
5 11 15 23 41 79 81 83 85 93

ArcGIS Desktop extensions geoprocessing tools

3D Analyst toolbox Data Interoperability toolbox Geostatistical Analyst toolbox Network Analyst toolbox Spatial Analyst toolbox Tracking Analyst toolbox

97
99 119 121 123 127 177

Index Appendix A: Tool licensing

179 A-1

Introduction
Introduction This reference guide is designed to provide an easy and quick reference for those wanting to use the ESRI command language at the ArcGIS command line and for those writing scripts. All commands (otherwise known as tools) are maintained in toolsets within the ArcGIS toolboxes. A toolbox can contain tools, toolsets, and scripts and is organized according to the collection of geoprocessing commands it contains. A toolset can contain tools, toolsets, and scripts and is organized according to the geoprocessing commands it contains. There are four different kinds of tools, and they differ only in how they are created and added to a toolbox. However, regardless of their type, all tools can be executed from their dialog or from the command line and can be used in models and scripts. System toolthese tools are installed and registered on your system. Usually, these tools are installed and registered when you install ArcGIS, although third-party developers can also create and register system tools. System tools are sometimes called function tools by developers. Model toolthese tools are created by you with ModelBuilder. Some of the tools in the system toolboxes are model tools. Script toolthese tools are created by you with a scripting language editor (typically an enhanced text editor). Some of the tools in the system toolboxes are script tools. Custom toolcustom tools are built by system developers and have their own unique user interface for creating the tool. The ArcGIS Data Interoperability extension contains custom tools. This guide describes the following toolboxes:
Analysis toolbox Cartography toolbox Conversion toolbox Coverage toolbox Data Interoperability toolbox Data Management toolbox Geocoding toolbox Geostatistical Analyst toolbox Linear Referencing toolbox Multidimension toolbox Network Analyst toolbox Server toolbox Spatial Analyst toolbox Spatial Statistics toolbox Tracking Analyst toolbox 3D Analyst toolbox

Each toolbox contains a list of the toolsets and tools as they are organized within ArcToolbox. The Index section at the end of this guide contains an alphabetical list of each tool, script, toolset, and toolbox.

Introduction

All tools are available with the ArcInfo license or the extension with which they are associated. However, many are available for use with ArcView or ArcEditor (sometimes with limited functionality). Those available with ArcView and ArcEditor are denoted with a , and those available with ArcEditor are denoted with a . Some tools, such as Clip, exist in multiple toolboxes. Therefore, an alias can be added as a sufx to the tool name when more than one toolbox is available. Examples of alias usages are clip_arc, where clip is the tool and arc is the sufx representing the Coverage toolbox, or clip_analysis, where the sufx represents the Analysis toolbox. The alias list: Analysis toolbox _analysis Cartography toolbox _cartography Conversion toolbox _conversion Coverage toolbox _arc Data Interoperability toolbox _di Data Management toolbox _management Geocoding toolbox _geocoding Geostatistical Analyst toolbox _ga The syntax of an example tool:
Union_arc <in_cover> <union_cover> <out_cover> {fuzzy_tolerance} {JOIN | NO_JOIN}

Linear Referencing toolbox Multidimension toolbox Network Analyst toolbox Server toolbox Spatial Analyst toolbox Spatial Statistics toolbox Tracking Analyst toolbox 3D Analyst toolbox

_lr _md _na _server _sa _stat _ta _3d

Where: Union_arc is the tool and the components that follow are the parameters. < > indicates required parameters. { } indicates optional parameters; these do not need to be included. One can be skipped using # if you need to apply only a portion of them. The | indicates mutually exclusive arguments, and only one of the arguments in the list of options can be specied. In some commands, there may be an ellipsis between two arguments, such as item1...item4. This indicates that you can give one or more (up to four in this example) names or values for that argument. Example:
Union_arc Treepolycov Newtreecov Finaltreecov # JOIN

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

ArcGIS Desktop core geoprocessing tools

Analysis toolbox
A suite of geoprocessing tools used to solve spatial or statistical problems. Extract toolset

Contains tools used to manipulate data into manageable datasets containing only the desired features and attributes.

Analysis toolbox

Clip: Extracts those features from an input feature class that overlap with features from a clip feature class.
Clip <in_features> <clip_features> <out_feature_class> {cluster_tolerance}

The output feature class will have the attributes of the input features. The input features may be any geometry type, but clip features must have polygon geometry. Select: Extracts selected features from an input feature class or layer and stores them in the output feature class.
Select <in_features> <out_feature_class> {where_clause}

If no SQL expression is included, then all features will be included in the output feature class. If a SQL expression is used but returns nothing, the output feature class will be empty. Split: Clips the input features and stores them in multiple output datasets.
Split <in_features> <split_features> <split_eld> <out_workspace> {cluster_tolerance}

The split eld data type must be character. The output feature classes will be named for split eld values; therefore, they must start with a valid character. The number of output feature classes equals the total number of unique values in the split eld. Table Select: Extracts selected attributes from an input table or table view and stores them in an output table.
TableSelect <in_table> <out_table> {where_clause}

The input can be an INFO table, a dBASE table, a geodatabase table, a VPF table, a feature class, or a table view. If a SQL expression is used but returns nothing, the output table will be empty.

Overlay toolset

Contains tools for topological integration of features based on symmetry. Erase: Copies input features falling outside the erase polygon feature boundaries to the output.
Erase <in_features> <erase_features> <out_feature_class> {cluster_tolerance}

Analysis toolbox

Input feature polygons that are coincident with erase feature polygons will be removed. The erase features must be polygons. Identity: Intersects two feature classes. The output contains the input features as well as those overlapping features of the identity feature class.
Identity <in_features> <identity_features> <out_feature_class> {ALL | NO_FID | ONLY_FID} {cluster_tolerance} {NO_RELATIONSHIPS | KEEP_RELATIONSHIPS}

The input features must be point, multipoint, line, or polygon. The inputs cannot be annotation features, dimension features, or network features. The identity features must be polygons. Intersect: Creates an output feature class containing features that fall within the area common to both input datasets.
Intersect <features {Ranks};features {Ranks}...> <out_feature_class> {ALL | NO_FID | ONLY_FID} {cluster_tolerance} {INPUT | LINE | POINT}

The input features must be point, multipoint, line, or polygon. The inputs cannot be annotation features, dimension features, or network features. If the inputs have different geometry types (that is, line on poly, point on line, and so on), the output feature class geometry type will default to the same as the input features with the lowest dimension geometry. Spatial Join: Creates a type of table join in which elds from one layers attribute table are appended to another layers attribute table based on the relative locations of the features in the two layers.
SpatialJoin <target_features> <join_features> <out_feature_class> {JOIN_ONE_TO_ONE | JOIN_ONE_TO_MANY} {KEEP_ALL | KEEP_COMMON} {eld_mapping} {INTERSECTS | IS_WITHIN | CONTAINS} {search_radius} 6 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 A count eld is added to the output for all joins where the join operation is ONE_TO_ONE. For nearest joins, a distance eld is also added to the output. Visually the map options look as follows:

Analysis toolbox

Symmetrical Difference: Creates an output feature class containing features or portions of features common only to one of the inputs.
SymDiff <in_features> <update_features> <out_feature_class> {ALL | NO_FID | ONLY_FID} {cluster_tolerance}

The input and difference feature class and the output feature layer must have polygon geometry. Union: Creates an output feature class containing all features from both inputs.
Union <features {Ranks};features {Ranks}...> <out_feature_class> {ALL | NO_FID | ONLY_FID} {cluster_tolerance} {GAPS | NO_GAPS}

All input feature classes and feature layers must have polygon geometry. With ArcView and Editor licenses, the number of input feature classes or layers is limited to two. Update: Updates the attributes and geometry of the input using the update feature class or layer they overlap.
Update <in_features> <update_features> <out_feature_class> {BORDERS | NO_BORDERS} {cluster_tolerance}

 The input features and update features must be of type polygon, and their names must match.

Proximity toolset

Contains tools to determine spatial relationships among features, with respect to the distance relationships between features. Buffer: Creates buffer polygons to a specied distance around the input features.

Analysis toolbox

Buffer <in_features> <out_feature_class> <buffer_distance_or_eld> {FULL | LEFT | RIGHT} {ROUND | FLAT} {NONE | ALL | LIST} {dissolve_eld;dissolve_eld...}

Features will not be buffered if their buffer distance is zero. When buffering polygon features, negative distances can be used to create buffers on the inside of the polygon features. Create Thiessen Polygons: Converts input points to an output feature class of Thiessen proximal polygons.
CreateThiessenPolygons <in_features> <out_feature_class> <ONLY_FID | ALL>

Thiessen polygons have the unique property that each polygon contains only one input point, and any location within a polygon is closer to its associated point than to the point of any other polygon. Thiessen polygons can be used to apportion a point coverage into polygons known as Thiessen or Voronoi polygons. Multiple Ring Buffer: Creates a new feature class of buffer features using a set of buffer distances.
MultipleRingBuffer <input_features> <output_feature_class> <distances;distances...> {DEFAULT | CENTIMETERS | DECIMALDEGREES | FEET | INCHES | KILOMETERS | METERS | MILES | MILLIMETERS | NAUTICALMILES | POINTS | YARDS} {eld_name} {ALL | NONE}

If the eld name is not set, the default name for the eld containing the distance value is distance. The eld type is double.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Near: Computes the distance from each point in the input to the nearest feature in the near feature class or layer, within the search radius.
Near <in_features> <near_features> {search_radius} {NO_LOCATION | LOCATION} {NO_ANGLE | ANGLE}

Analysis toolbox

The results are recorded in the input features attribute table. Fields for distance and feature ID of the closest feature are added or updated. The eld names are NEAR_DIST and NEAR_FID. Point Distance: Computes the distance between each point in a feature class or layer to all points in a different feature class or layer.
PointDistance <in_features> <near_features> <out_table> {search_radius}

The results are recorded in an output table containing items for the features ID and DISTANCE. The eld names are INPUT_FID, NEAR_FID, and DISTANCE.

Statistics toolset

Contains tools that perform standard statistical analysis on attribute data. Frequency: Calculates frequency statistics for one or more elds in a table.
Frequency <in_table> <out_table> <frequency_elds;frequency_elds...> {summary_ields; summary_elds...}

The output table will contain the eld frequency and the specied frequency eld(s) and summary eld(s). Summary Statistics: Calculates summary statistics for one or more elds in a table.
Statistics <in_table> <out_table> <eld{Statistic Type};eld{Statistic Type}...> {case_eld}

The following statistical operations are available with this tool: sum, mean, maximum, minimum, range, standard deviation, rst, and last. The median operation is not available. The Add Field button, used to dene the statistics elds, is used only in ModelBuilder.

Cartography toolbox
Contains tools designed to produce data and support map production for specic maps in a way that meets a specic cartographic standard. Graphic Quality toolset

Contains a tool that allows you to construct polygons that identify the location where two features share the same graphic space. Detect Graphic Conict: Detects graphic conicts between feature representations and stores the overlaps as polygons in the output feature class.
DetectGraphicConict <in_features> <conict_features> <out_feature_class> {conict_ distance} {line_connection_allowance}

Cartography toolbox

This tool works on feature representations only, not feature geometries. The input and conict feature layers must contain representations; otherwise, the tool will not execute. The conict calculation is based on a reference scale. If you access this tool from ArcMap, the reference scale of the data frame containing the input layers will be used unless an explicit reference scale has been set in the ArcToolbox environment settings. If you access the tool from ArcCatalog, a reference scale must be specied in the environment settings; otherwise, the tool will not execute. The output feature class stores polygons, each representing an area of graphic conict between an input representation and a conict representation.

Masking toolset

Contains tools to construct masking polygons to use with variable depth masking in ArcMap, which obscures some feature symbology to help make clearer and more legible maps. Cul-De-Sac Masks: Creates a feature class of polygon masks from a symbolized input line layer.
CuldeSacMasks <input_layer> <output_feature_class> <reference_scale> <spatial_reference> <margin> {ONLY_FID | NO_FID | ALL}

This tool only accepts line layers as input. This tool only creates masks at the unconnected ends of lines in the input layer. These unconnected ends in the input layer are referred to as cul-de-sacs. A line end is considered connected if it shares its endpoint with the endpoint of another line. If the input line layer contains multipart line geometries, then cul-de-sac masks are created for all unconnected line ends, including the ends of parts within multipart lines. Feature Outline Masks: Creates mask polygons at a specied distance and shape around the symbolized features in the input layer.
FeatureOutlineMasks <input_layers> <output_feature_class> <reference_scale> <spatial_reference> <margin> <CONVEX_HULL | BOX | EXACT_SIMPLIFIED | EXACT> <ALL_FEATURES | ONLY_PLACED> {ONLY_FID | NO_FID | ALL}

This tool accepts point, line, and polygon feature layers as well as geodatabase annotation layers as input. Margin values are specied in either page units or map units. Most of the time you will want to specify your margin distance value in page units. If the input layer is an annotation layer, the reference scale will be automatically set to the reference scale of the layers feature class to ensure accurate calculation of the mask.

11

Intersecting Layers Masks: Creates masking polygons at a specied shape and size at the intersections of symbolized input layers.
IntersectingLayersMasks <masking_layer> <masked_layer> <output_feature_class> <reference_scale> <spatial_reference> <margin> <CONVEX_HULL | BOX | EXACT_SIMPLIFIED | EXACT> <ALL_FEATURES | ONLY_PLACED> {ONLY_FID | NO_FID | ALL}

Cartography toolbox

This tool accepts point, line, and polygon feature layers as well as geodatabase annotation layers as input. When creating masks, it is important to know that adding masks to maps adds complexity that will slow map drawing and affect map printing and exporting. Generally, there are three things to consider when creating masks for a map: (1) the number of masks, (2) the complexity of the masks, and (3) whether the masks will be used to mask polygon features lled with marker or line symbols. Masks will be created if the margin distance is zero or negative. A margin size of zero will create a polygon that represents the exact shape of the symbolized feature. A negative margin will result in a polygon smaller than the symbolized feature. Generally, a margin value larger than zero will be specied to produce the desired masking effect.

Representation Management toolset

Contains tools that manage feature class representations and representation overrides. Add Representation: Adds a feature class representation to a feature class.
AddRepresentation <in_features> <representation_name> {rule_id_eld_name} {override_ eld_name} {STORE_CHANGE_AS_OVERRIDE | MODIFY_FEATURE_SHAPE} {import_rule_layer} {ASSIGN | NO_ASSIGN}

The input must be a geodatabase feature class. Specify an import rule layer to import representation rules from an existing layer le that symbolizes features with a feature class representation. All the representation rules of the import rule layer le will be copied into this feature class representation. If the import rule layer has the same source feature class as the input feature class, you can check Assign Rule IDs (or use the ASSIGN option in a script or at the command line) to assign representation rules to features to match the RuleID assignments of the import rule layer. Calculate Representation Rule: Applies existing representation rules to features in a feature class representation by calculating the RuleID eld.
CalculateRepresentationRule <in_features> <representation> <representation_rule>

Drop Representation: Deletes a feature class representation from a feature class.

DropRepresentation <in_features> <representation>

Once a feature class representation is deleted from a feature class, all representation rules and feature overrides associated with that representation are deleted. Remove Override: Removes geometry overrides and/or representation property overrides from a feature class representation.
RemoveOverride <in_features> <representation> {BOTH | GEOMETRY_OVERRIDE | REPRESENTATION_ PROPERTY_OVERRIDE}

Once the override of a feature is removed, the standard representation rule will apply.

12

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Select Feature By Override: Selects features within a feature class representation that have shape and/ or representation property overrides.
SelectFeatureByOverride <in_representations> {BOTH | GEOMETRY_OVERRIDE | REPRESENTATION_ PROPERTY_OVERRIDE}

Update Override: Moves feature representation overrides from the default override eld to explicit elds as dened by the representation rules in a feature class representation.
<in_features> <representation> {REPRESENTATION_PROPERTY_OVERRIDE | GEOMETRY_OVERRIDE | BOTH}

The elds to be updated must be added and associated with the correspondent override attributes prior to using this tool.

Cartography toolbox

Symbolization Renement toolset

Contains tools that allow you to enrich the symbology used by your representations, including the alignment and type of symbols, as well as create custom symbology for bridges and tunnels. Align Marker To Stroke Or Fill: Aligns the representation marker symbols of a point feature class to the nearest stroke or ll representation symbols in a line or polygon feature class within a specied search distance.
AlignMarkerToStrokeOrFill <in_point_features> <in_line_or_polygon_features> <search_ distance> {PERPENDICULAR | PARALLEL}

Markers beyond the search distance are not affected. The changes will be stored as overrides. Calculate Geodesic Angle: Calculates geodesic angles for the input features according to the dened coordinate system and assigns the angle values to the specied eld in the feature class that contains the input features.
CalculateGeodesicAngle <in_features> <angle_eld>

The input features can be points, lines, or polygons. For a point feature, the point location will be used to calculate the geodesic angle. For a line or polygon feature, the center point (centroid) of geometry will be used. You can use the Add Field tool to add a numerical eld to the feature class containing the input features to store the calculated values. The coordinate system used in the calculation is dened in the geoprocessing Environment Settings > Cartography Settings. If it is not dened, the tool will use the one from the map if you are in ArcMap, or it will not execute if you are in ArcCatalog. The stored angles are in decimal degrees. Calculate Line Caps: Calculates the cap type (ending style) for double-line symbols in the input representations.
CalculateLineCaps <in_representations> {BUTT | SQUARE} {CASED_LINE_DANGLE |TRUE_DANGLE}

The line cap type denes how the ends of line segments are drawn using a double-line symbol. By default, a round line cap will be used. You can use this tool to change the cap type to BUTT or SQUARE. The calculated cap types will be stored as representation property overrides. To change back to round caps, you can just remove the representation property overrides.

13

 The dangle options are very specic. The TRUE_DANGLE means the end of a linear feature, for example, the dead-end of a road. When this option is used, the tool will calculate line caps for true dangles only. The CASED_LINE_DANGLE is where a linear feature still continues, but the representation changes from a double-line or cased-line symbol to a single-line symbol. When this option is used, the tool will calculate line caps for both true dangles and cased-line dangles. Calculate Polygon Main Angle: Calculates the main angles of the input polygon features and assigns the angle values to the specied eld in the feature class that contains the polygon features.
CalculatePolygonMainAngle <in_features> <angle_eld>

Cartography toolbox

You can use the Add Field tool to add a numerical eld in the feature class containing the input featues to store the calculated values. The longest side of a polygon is considered the main axis of the polygon. The angle of the main axis will be the main angle of the polygon. The stored angles are in decimal degrees. Create Overpass: Generates mask polygons at the intersections of stroke representations to symbolize one set of strokes passing above the other.
CreateOverpass <in_above_features> <in_below_features> <margin_along> <margin_across> <out_overpass_feature_class> <out_mask_relationship_class> {where_clause} {out_ decoration_feature_class} {ANGLED | PARALLEL | NONE} {wing_tick_length}

Requires the indication of features participating in the creation of an overpass. Feature classes without representations are not supported by this tool. When above and below representations are the same, a SQL expression is encouraged for further renement of feature selection. Overpass masks are created based on the user-indicated margin sizes. Existing overpass feature classes and existing mask relationship classes will not be overwritten if the same name is specied. Create Underpass: Generates mask polygons at the intersections of stroke representations to symbolize one set of strokes passing under the other.
CreateUnderpass <in_above_features> <in_below_features> <margin_along> <margin_across> <out_underpass_feature_class> <out_mask_relationship_class> {where_clause} {out_ decoration_feature_class} {ANGLED | PARALLEL | NONE} {wing_tick_length}

Requires the indication of features participating in the creation of an underpass. Feature classes without representations are not supported by this tool. When above and below representations are the same, a SQL expression is encouraged for further renement of feature selection. Underpass masks are created based on the user-indicated margin sizes. Set Representation Control Point By Angle: Finds a vertex along a line or polygon boundary where the inner angle is equal to or less than the specied Maximum Angle, sets the vertex as a representation control point, and stores the result as a geometry override.
SetRepresentationControlPointByAngle <in_features> <maximum_angle>

An inner angle is the angle between the two line segments, measured less than 180 degrees, at a vertex. The smaller the inner angle is, the sharper turn it indicates.

14

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Conversion toolbox
Contains tools that are used to convert data into various formats. From Raster toolset

Contains tools to output raster datasets to other formats. Raster to ASCII: Converts a raster dataset to an ASCII le representing raster data.
RasterToASCII <in_raster> <out_ascii_le>

Both integer and oating point rasters can be converted to an ASCII format. The NODATA_VALUE is the value in the ASCII le that will be assigned to the NoData cells in the input raster. This value is normally reserved for those cells whose true value is unknown. The end of each row of data from the raster is terminated with a carriage return in the le. Raster to Float: Converts a raster dataset into a le of binary oating-point values representing raster data.
RasterToFloat <in_raster> <out_oat_le>

Conversion toolbox

The output will be a oating-point text le, as an IEEE oating-point format, 32-bit signed binary le. Two outputs are created, an IEEE oating-point format, 32-bit signed binary le with a .t extension and an ASCII header le with a .hdr extension. Both will use the same output oating-point raster le name. The NODATA_VALUE is the value in the output le assigned to those cells in the input raster that contain NoData. This value is normally reserved for those cells whose true value is unknown. By default, NoData values on the input raster will have a value of -9999 in the output oat le. Raster to Point: Converts a raster dataset to a point feature dataset.
RasterToPoint <in_raster> <out_point_features> {raster_eld}

For each cell of the input raster dataset, a point will be created in the output feature class. The points will be positioned at the centers of cells that they represent. The NoData cells will not be transformed into points. The input raster can have any cell size and may be any valid raster dataset. The feature output is assumed to be a shapele. Raster to Polygon: Converts a raster dataset to a polygon feature dataset.
RasterToPolygon <in_raster> <out_polygon_features> {SIMPLIFY| NO_SIMPLIFY} {raster_eld}

The input raster can have any cell size and may be any valid raster dataset. The Field parameter allows you to choose which column in the raster dataset will become an attribute in the output polygon le. The column containing the cell values (VALUE) will become a column with the heading Grid_code in the attribute table of the output feature class. Raster to Polyline: Converts a raster dataset to a polyline feature dataset.
RasterToPolyline <in_raster> <out_polyline_features> {ZERO | NODATA} {minimum_dangle_ length} {SIMPLIFY| NO_SIMPLIFY} {raster_eld}

The input raster can have any cell size and may be any valid raster dataset. The Field parameter allows you to choose which column in the raster dataset will become an attribute in the output polyline le. The column containing the cell values (VALUE) will become a column with the heading Grid_code in the attribute table of the output feature class. The feature output is assumed to be a shapele.
15

Metadata toolset

Contains the tools to validate the metadata content according to a specic metadata standard or to export the metadata content to stand-alone metadata les that can be used with other metadata software. ESRI Metadata Translator: Uses ESRIs metadata translation engine to export metadata content from ArcCatalog to a stand-alone le.
ESRITranslator <source> <output> {translator} {logle}

Metadata Publisher: Publishes an XML metadata document to a metadata catalog such as an ArcIMS Metadata Service.
MDPublisher <source> <publisher> {url} {service} {user} {password}

If you connect to ArcIMS in ArcCatalog with the same user name and password provided with this tool, the Metadata Services icon will show a hand holding a pencil if you have permission to publish documents to that service. USGS MP Metadata Translator : Uses metadata parser to export or validate metadata content created using the FGDC metadata editor.
USGSMPTranslator <source> {cong} {XML | NONE | HTML | TEXT | FAQ | SGML | DIF} {output} {errors}

Conversion toolbox

Documentation for the metadata parser utility can be found on the USGS Web site. An metadata parser conguration le can be used to specify an extension le that will recognize metadata elements that are dened in FGDC CSDGM proles. Extension and conguration les that will recognize ESRI-dened metadata elements and ESRI-ISO metadata elements can be found at ESRIs metadata Web page. When metadata is edited using ArcCatalog, the XML elements will not be in the correct order as specied by the FGDC CSDGM rules. As a result, metadata parser will record warnings in the error le. XSLT Translator: Uses an XML parser to transform an XML metadata document using an XSLT style sheet and export the result to a stand-alone le.
XSLTranslator <source> <xslt> <output>

To CAD toolset

Contains tools to convert geodatabase features to native CAD formats. Add CAD Fields: Adds elds to the input table by selecting from groups of CAD-specic elds, which have the appropriate name and type recognized by the Export to CAD tool.
AddCADFields <input_table> <ADD_ENTITY_PROPERTIES | NO_ENTITY_PROPERTIES> {ADD_LAYER_PROPERTIES | NO_LAYER_PROPERTIES} {ADD_TEXT_PROPERTIES | NO_TEXT_ PROPERTIES} {ADD_DOCUMENT_PROPERTIES | NO_DOCUMENT_PROPERTIES} {ADD_XDATA_PROPERTIES | NO_XDATA_PROPERTIES}

If the input is a table view or a feature layer with a joined table, the elds are only added to the base table. Adding CAD elds to a feature class intended for export and calculating values into those elds is a quick way to specify the various CAD properties for export. It is useful to add Entity Property elds, Layer Property elds, Text Property elds, and CAD Document property elds to separate tables to keep a normalized set of lookup tables that can be joined to express an organized CAD standard of how CAD les should be generated from feature class data.

16

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Create CAD XData: Creates a table formatted to be recognized by the Export to CAD tool as AutoCAD extended entity data.
CreateCADXData <in_table> <elds;elds...> <RegApp> <ADE | TRADITIONAL>

All input feature classes and/or feature layers are valid inputs to this tool. XData is only read by AutoCAD. The XDList eld that is created by this function is read by the Export to CAD tool when exported to AutoCAD. Export to CAD: Creates one or more CAD drawings based on the values contained in one or more input feature classes or feature layers and supporting tables.
ExportCAD <in_features;in_features...> <DWG_R2000 | DGN_V8 | DWG_R14 | DXF_R14 | DXF_R2000 | DWG_R2004 | DXF_R2004 | DWG_R2005 | DXF_R2005> <Output_File> {IGNORE_FILENAMES_IN_ TABLES | USE_FILENAMES_IN_TABLES} {OVERWRITE_EXISTING_FILES | APPEND_TO_EXISTING_ FILES} {Seed_File}

All input feature classes and/or feature layers and shapeles are valid inputs to this tool. This tool is generally used as the nal tool in the process of converting feature class data to new or existing CAD drawing les according to a predened set of CAD drawing standards. If the CAD drawing les specied by the attributes of the exported features exist, CAD objects will be appended to those les. If the CAD les do not exist, the specied CAD les will be created with the standard defaults or using the optional Seed Drawing specied. If the CAD entity properties are not specied, then entities will be generated using the default entity properties of the drawing le or any existing layer symbology included in the optional seed drawing. Set CAD Alias: Renames one or more existing eld name aliases by matching columns from the input table with a list of CAD-specic elds of appropriate names, which are recognized by the Export to CAD tool.
SetCADAlias <input_table> <eld_info>

Conversion toolbox

If a feature class intended for export already contains values useful for driving CAD properties, such as layer name, but the elds have different names, assigning a CAD eld alias on that table using the Assign CAD Alias tool is an efcient way to have the Export to CAD tool recognize those values as CAD properties. Shapeles are not valid input to this function, since they cannot maintain aliases for elds. If you need to use a shapele as input, convert the shapele to a layer le. Layer les or feature classes from a personal geodatabase or ArcSDE geodatabase are valid inputs to this tool. This tool overwrites the input, so be sure to make a backup of the original data.

To Coverage toolset

Contains a tool to convert any supported feature class format to a coverage. Feature Class to Coverage: Creates a single coverage from one or more input feature classes or layers.
FeatureClassToCoverage <features{Type};features{Type}...> <out_cover> {cluster_tolerance} {DOUBLE | SINGLE}

The cluster tolerance acts the same as the fuzzy tolerance in ArcInfo Workstation. The fuzzy tolerance of the output coverage will be the same as the cluster tolerance specied when executing this tool. If no cluster tolerance is specied, a default is calculated. It is suggested you run the Create Labels tool after successfully executing Feature Class To Coverage to ensure all polygon features have an accurate label.

17

To dBASE toolset

Contains a tool to convert tables into a dBASE format. Table to dBASE: Converts INFO, OLE DB, or geodatabase tables to dBASE tables.
TableToDBASE <input_tables;input_tables...> <output_folder>

The name of the output tables will be based on the name of the input table. To explicitly control the output name and for some additional conversion options, use the Table To Table tool. Copy Rows and Table To Table can also be used to convert a table to a dBASE le. If the name of the output table already exists in the output folder, a number will be appended to the end to make it unique (for example, OutputTab_1.dbf).

To Geodatabase toolset

Contains tools to convert any supported vector or raster data type to a geodatabase. Feature Class to Feature Class: Copies a feature class into a geodatabase or to a shapele.
FeatureClassToFeatureclass <in_features> <out_path> <out_name> {where_clause} {eld_mapping} {conguration_keyword}

Conversion toolbox

The Copy Features tool can also be used to convert a shapele, coverage feature class, or geodatabase (personal or SDE) feature class to a shapele or geodatabase (personal or SDE) feature class. Spatial indexes may be specied when creating an SDE or personal geodatabase feature class. The spatial index is used to quickly locate features that match the criteria of a spatial search. For most data, only a single spatial index is required. Feature Class to Geodatabase (multiple): Copies one or more feature classes or layers to a geodatabase feature class.
FeatureclassToGeodatabase <input_features;input_features...> <output_geodatabase>

The inputs can include shapeles, coverage feature classes, VPF feature classes, or geodatabase feature classes. The inputs can also be feature layers. If the input is a layer with selected features, only those selected features will be written to the new output feature class. The name of the output feature classes will be based on the name of the input feature class. For example, if the input is c:\myworkspace\gondor.shp, the output feature class will be named gondor. If the name already exists in the output geodatabase, a number will be appended to the end to make it unique, for example, _1. Import CAD Annotation: Converts a collection of CAD annotation features into a geodatabase annotation feature class.
ImportCADAnnotation <input_features;input_features...> <output_feature_class> <reference_scale> {CLASSES_FROM_LEVELS | ONE_CLASS_ONLY} {NO_MATCH | MATCH_FIRST_INPUT} {NO_SYMBOL_REQUIRED | REQUIRE_SYMBOL} {STANDARD | FEATURE_LINKED} {linked_feature_ class} {AUTO_CREATE | NO_AUTO_CREATE} {AUTO_UPDATE | NO_AUTO_UPDATE}

Choose a reference scale that is roughly equal to the scale at which the annotation will normally be displayed. Based on this reference scale, symbols and text will appear larger as you zoom in on the annotation and smaller as you zoom out from your annotation. The conversion requires an exclusive lock so it may not be opened by another application. It also requires that if the annotation feature class is in an ArcSDE geodatabase, it will not be registered as versioned.

18

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Import Coverage Annotation: Imports coverage annotations into a geodatabase annotation feature class.
ImportCoverageAnnotations <input_features;input_features...> <output_feature_class> <reference_scale> {CLASSES_FROM_LEVELS | ONE_CLASS_ONLY} {NO_MATCH | MATCH_FIRST_INPUT} {NO_SYMBOL_REQUIRED | REQUIRE_SYMBOL} {STANDARD | FEATURE_LINKED} {linked_feature_ class} {AUTO_CREATE | NO_AUTO_CREATE} {AUTO_UPDATE | NO_AUTO_UPDATE}

You can convert each coverage annotation level to individual annotation classes or merge them into a single class. The conversion requires an exclusive lock so it may not be opened by another application. It also requires that if the annotation feature class is in an ArcSDE geodatabase, it will not be registered as versioned. If you select coverage annotation features and/or use a denition query, only those features that are selected and visible will be converted. You can create a selection set of coverage features and create a new layer from the selection. If you use that new layer as input to the conversion, only those features in the layer will be converted. Import from CAD: Imports from one or more CAD les to a geodatabase.
ImportCAD <input_les;input_les...> <output_personal_geodatabase> {spatial_reference} {DO_NOT_EXPLODE_COMPLEX | EXPLODE_COMPLEX}

Conversion toolbox

A xed set of feature classes will be generated in the specied output feature dataset. These feature classes contain the geometry for the lines, areas, points, and document extent, and optionally, point feature classes can be generated for each unique block or cell name. This tool creates a new geodatabase and will not append to an existing one. CAD text and attribute entities are converted to point features. Raster to Geodatabase (multiple): Loads multiple raster datasets into a geodatabase or raster catalog.
RasterToGeodatabase <input_rasters;input_rasters...> <output_geodatabase> {conguration_keyword}

The output is the location of the geodatabase where you will store the raster. When converting the raster dataset to a personal geodatabase, the raster dataset is actually stored on the regular le system in a hidden folder. When converting the raster dataset to an ArcSDE geodatabase, the raster dataset is stored on the ArcSDE server as a Raster SDE format. Table to Geodatabase (multiple): Converts dBASE, INFO, or OLE DB tables to geodatabase tables and copies tables from one geodatabase to another.
TableToGeodatabase <input_table;input_table...> <output_geodatabase>

The inputs can include dBASE, INFO, VPF, OLE DB, or geodatabase tables. The inputs can also be table views. The name of the output table will be the same as the input. If a tables name already exists in the output geodatabase, a number will be appended to the end to make it unique (for example, gondor_1). Table to Table: Converts or copies dBASE, INFO, OLE DB, or geodatabase tables to a dBASE or geodatabase table.
TableToTable <in_rows> <out_path> <out_name> {where_clause} {eld_mapping} {conguration_keyword}

The inputs can include dBASE, INFO, VPF, OLE DB, or geodatabase tables. The inputs can also be table views.
19

 To drop elds during the conversion, set their Field Info Visible property to FALSE. This will not affect the input table. If the input is a table view with a selection, only those rows that are selected will be transferred to the output.

To Raster toolset

Contains tools to convert any supported raster format to GRID, ERDAS IMAGINE, TIFF, or geodatabase format. ASCII to Raster: Converts an ASCII le representing raster data into a raster dataset.
ASCIIToRaster <in_ascii_le> <out_raster> {INTEGER | FLOAT}

The ASCII le must consist of header information containing a set of keywords, followed by cell values in row-major order. The le format is:
<NCOLS xxx> <NROWS xxx> <XLLCENTER xxx | XLLCORNER xxx> <YLLCENTER xxx | YLLCORNER xxx> <CELLSIZE xxx> {NODATA_VALUE xxx} row 1 row 2 . . . row n

Conversion toolbox

where xxx is a number, and the keyword NODATA_VALUE is optional and defaults to -9999. Row 1 of the data is at the top of the grid, row 2 is just under row 1, and so on. The NODATA_VALUE is the value in the ASCII le to be assigned to those cells whose true value is unknown. In the raster, they will be assigned to NoData. Cell values should be delimited by spaces. No carriage returns are necessary at the end of each row in the grid. The number of columns in the header is used to determine when a new row begins. The number of cell values must be equal to the number of rows times the number of columns, or an error will be returned. DEM to Raster: Converts a USGS DEM le into a raster dataset.
DEMToRaster <in_dem_le> <out_raster> {FLOAT | INTEGER} {z_factor}

The resulting raster will have square cells. If the DEM has a different sample point spacing in the x and y directions, it is resampled during the conversion process. It is resampled using bilinear interpolation at a cell size equal to the smaller of the point spacings of the DEM in the x or y. For output to a grid raster, DEM to Raster transfers the projection and units information contained in the DEM header record to a map projection le in the output grid directory. If the output raster is not a grid, the projection information will be transferred to the .aux le. Feature to Raster: Converts a feature dataset to a raster dataset.
FeatureToRaster <in_features> <eld> <out_raster> {cell_size}

Any shapele, coverage, or geodatabase feature class containing point, line, or polygon features can be converted to a raster dataset. If the input eld contains oating-point values, the output raster will be oating point; otherwise, it will be integer. The output cell size will determine the size of each pixel in the output raster dataset.
20 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Float to Raster: Converts a le of binary oating-point values representing raster data into a raster dataset.
FloatToRaster <in_oat_le> <out_raster>

The input le is an IEEE oating-point format, 32-bit signed binary le. Two inputs are required: the binary oating-point le with a .t extension (<in_oat_le>.t) and an ASCII header le with a .hdr extension (<in_oat_le>.hdr). You only specify the .t le; however, there needs to be an existing .hdr le in the same directory with the same le name. The ASCII le consists of header information containing a set of keywords. The le format is:
NCOLS xxx NROWS xxx XLLCENTER xxx | XLLCORNER xxx YLLCENTER xxx | YLLCORNER xxx CELLSIZE xxx NODATA_VALUE xxx BYTEORDER <MSBFIRST | LSBFIRST>

where xxx is a number, and the keyword NODATA_VALUE is optional. Point to Raster: Converts point features to a raster dataset.
PointToRaster <in_features> <value_eld> <out_raster_dataset> {MOST_FREQUENT | SUM | MEAN | STANDARD_DEVIATION | MAXIMUM | MINIMUM | RANGE} {priority_eld} {cellsize}

Conversion toolbox

Any shapele, coverage, or geodatabase feature class containing point or multipoint features can be converted to a raster dataset. Multipoints are treated as individual points. The output cell size is the size of each pixel in the output raster dataset. Priority eld is only used with the MOST_FREQUENT option. Polygon to Raster: Converts polygon features to a raster dataset.
PolygonToRaster <in_features> <value_eld> <out_raster_dataset> {CELL_CENTER | MAXIMUM_ AREA | MAXIMUM_COMBINED_AREA} {priority_eld} {cellsize}

Any shapele, coverage, or geodatabase feature class containing polygon features can be converted to a raster dataset. If the input eld contains oating-point values, the output raster will be oating point; if the input eld contains integer values, the output raster will be integer; and if the input eld contains string values, the output raster will contain an integer value eld and a string eld. The output cell size is the size of each pixel in the output raster dataset. Polyline to Raster: Converts polyline features to a raster dataset.
PolylineToRaster <in_features> <value_eld> <out_raster_dataset> {MAXIMUM_LENGTH | MAXIMUM_COMBINED_LENGTH} {priority_eld} {cellsize}

Any shapele, coverage, or geodatabase feature class containing polyline features can be converted to a raster dataset. If the input eld contains oating-point values, the output raster will be oating point; if the input eld contains integer values, the output raster will be integer; and if the input eld contains string values, the output raster will contain an integer value eld and a string eld. The output cell size is the size of each pixel in the output raster dataset.

21

Raster to Other Format (multiple): Converts one or more raster dataset formats supported by ArcGIS to a BMP, GIF, GRID, IMAGINE, JPEG, JPEG 2000, PNG, TIFF, or geodatabase raster dataset format.
RasterToOtherFormat <input_rasters;input_rasters...> <output_workspace> {GRID | BMP | GIF | IMAGINE Image | JP2000 | JPEG | PNG | TIFF}

The input raster datasets can be any valid raster dataset that ArcGIS can recognize. Allows you to batch convert raster datasets into another raster dataset format. This is useful if you receive raster datasets in one format, but you (or your client) prefer to use BMP, GIF, GRID, IMAGINE, JPEG, JPEG2000, PNG, or TIFF.

To Shapele toolset

Contains a tool to create shapeles from feature classes. Feature Class to Shapele (multiple): Exports one or more feature classes to shapeles in a designated folder.
FeatureclassToShapele <input_features;input_features...> <output_folder>

The name of the output shapele will be the name of the input feature class. For example, if the input is c:\gdb.mdb\gondor, the output shapele will be named gondor.shp. To explicitly control the output shapele name and for some additional conversion options, see the Feature Class to Feature Class tool. If the output shapele already exists in the output folder, a number will be appended to the end to make it unique (for example, gondor_1.shp). The coordinate system of each output shapele will be the same as the input feature classes. If the Output Coordinate System Environment is set, the output will be projected to that coordinate system.

Conversion toolbox
22

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Coverage toolbox
Contains the original ArcInfo Workstation commands used to perform geoprocessing tasks with coverages. Analysis toolset

Contains tools and toolsets used for geospatial processing.

Extract toolset

Contains tools used to select features or parts of features to create a new coverage. Clip: Extracts, using a cookie-cutter method, those features or portions of features from an input coverage that overlap with a clip coverage polygon.
Clip <in_cover> <clip_cover> <out_cover> {POLY | LINE | POINT | NET | LINK | RAW} {fuzzy_tolerance}

Clip maintains linear data belonging to different planar graphs in the same coverage. These may include arcs representing utility cables at different levels or a road passing over a stream. If there are arcs that appear to intersect but do not, nodes will not be inserted at the apparent intersection. Coincident and colinear line segments are preserved; additional vertices may be inserted. Two colinear arcsone representing a road that follows the second, a streamare maintained. The clip coverage must have polygon topology. Boundaries of interior polygons in the clip coverage are not used in Clip. Any clip coverage polygon whose internal number is greater than one is considered inside the Clipping window. Select: Extracts features from the input coverage and stores them in an output coverage based on logical expressions or by applying the criteria contained in a selection le.
Reselect <in_cover> <out_cover> <info_express;info_express...> {POLY | LINE | POINT | ANNO.subclass | ROUTE.subclass | SECTION.subclass | REGION.subclass} {selection_le} {out_feature_type}

Coverage toolbox

When using the same input coverage and output coverage for feature classes Anno, Section, Route, or Region, the output feature class subclass name must be different from the input feature class subclass name. Use of indexed items in the Query Builder can speed up the logical selection process. You can use the Index Item tool to create an attribute index. Split: Clips portions of the input coverage into multiple coverages.
Split <in_cover> <split_cover> <split_item> <path> {POLY | LINE | POINT | NET | LINK | RAW} {fuzzy_tolerance}

23

 The output coverages will be named for Split Item values; therefore, they must start with a valid character. The split coverage must have polygon topology. The feature attribute table for each output coverage contains the same items as the input coverage feature attribute table.

Overlay toolset

Contains tools used to calculate the various options when overlaying two coverages. Erase: Erases the input coverage features or portions of features that overlap with the erase coverage polygons.
Erase <in_cover> <erase_cover> <out_cover> {POLY | LINE | POINT | NET | LINK | RAW} {fuzzy_tolerance}

Coverage toolbox

Input coverage polygons that are coincident with erase coverage polygons will be removed. User-IDs for all features will be the same in the output coverage as they are in the input coverage. Boundaries of interior polygons in the erase coverage are not used in Erase. Any erase coverage polygon whose internal number is greater than one is considered inside the erasing window; an internal polygon number of one is considered outside. Only those input features (or portions of them) that are outside the erasing region are stored in the output coverage. Identity: Computes the geometric intersection of two coverages, where all features of the input coverage and only those overlapping from the identity coverage are preserved.
Identity <in_cover> <identity_cover> <out_cover> {POLY | LINE | POINT} {fuzzy_tolerance} {JOIN | NO_JOIN}

The identity coverage must have polygon topology. Label points are generated in each output coverage polygon when the POLY option is used. The new polygon User-IDs are set equal to the polygon internal number minus one. When the LINE option is used, User-IDs of the input coverage are maintained. Intersect: Computes the geometric intersection of two coverages, where only those features in the area common to both coverages will be preserved.
Intersect <in_cover> <intersect_cover> <out_cover> {POLY | LINE | POINT} {fuzzy_tolerance} {JOIN | NO_JOIN}

24

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The intersect coverage must have polygon topology. Label points are generated in each output coverage polygon when the POLY option is used. The new polygon User-IDs are set equal to the polygon internal number minus one. Union: Computes the geometric intersection of two polygon coverages. All polygons from both coverages will be split at their intersections and preserved in the output coverage.
Union <in_cover> <union_cover> <out_cover> {fuzzy_tolerance} {JOIN | NO_JOIN}

The input coverage and the union coverage must have polygon topology. Label points are generated in each output coverage polygon. The new polygon User-IDs are set equal to the polygon internal number minus one. Existing input coverage annotation is copied to the output coverage by Union. Update: Replaces the input coverage areas with the update coverage polygons using a cut-and-paste type of operation.
Update <in_cover> <update_cover> <out_cover> {POLY | NET} {fuzzy_tolerance} {KEEP_BORDER | DROP_BORDER}

Coverage toolbox

The input coverage and the update coverage must have polygon topology. New label point positions are only generated for the output coverage polygons when necessary. The User-ID for each polygon is equal to its old input coverage User-ID (the update coverage User-ID for updated polygons). Thus, you should attempt to make the User-ID values in the input coverage different from User-ID values in the update coverage to avoid having duplicate User-IDs in the output coverage. If DROP_BORDER is used, polygon boundaries along the outer edge of the update coverage are dropped. Even though the outer boundaries of some update polygons are dropped, the item values for the update polygons that overlap input coverage polygons will be assigned to the polygons in the output coverage. The DROP_BORDER option is not recommended for region coverages because of the possibility that some output regions may not be maintained.

Proximity toolset

Contains tools used in geoprocessing analysis involving distance. Buffer: Creates buffer polygons around specied input coverage features.
Buffer <in_cover> <out_cover> {LINE | POLY | POINT | NODE} {buffer_item} {buffer_table} {buffer_distance} {fuzzy_tolerance} {ROUND | FLAT} {FULL | LEFT | RIGHT}

25

 Negative and positive distances can be used for buffer distance with the POLY option. It is possible to shrink some polygons and grow others in the same coverage when the buffer item contains positive and negative numbers. The ROUND, FLAT, FULL, LEFT, and RIGHT options apply only to line data. The Buffer function works in Euclidean space and uses a two-dimensional algorithm. A buffer will be the same width no matter what the coordinate system is. It will not reect the curvature or the shape of the earth. For the best results, generate the buffer in a map projection that minimizes distortion in the area of interest. Near: Computes the distance from each point in a coverage to the nearest arc, point, or node in another coverage.
Near <in_cover> <near_cover> <out_cover> {LINE | POINT | NODE} {search_radius} {NO_LOCATION | LOCATION}

Distance values are recalculated if this item already exists in the input coverage. If the distance item is added, it will be in the same precision as the coverage. The calculated distance from point to arc will be from the point to the nearest location along the arc. The calculated distance from point to node will be between the nearest node locations on the arcs.

Coverage toolbox

Point Distance: Computes the distances between point features in one coverage to all points in a second coverage that are within the specied search radius.
PointDistance <from_cover> <to_cover> <out_info_table> {search_radius}

Distance is set to zero when no match is found within the search radius for a particular point. If no matching points are found, the tool gives a warning and no output INFO table is created. The output INFO table can become very large when both coverages contain many points. Use a smaller search radius to limit the number of combinations. The results are recorded in an output table containing items for the internal numbers and distance. The input with the highest precision for distance is the one used for the output INFO distance eld. Point Node: Transfers attributes from a point feature class to a node feature class.
PointNode <point_cover> <node_cover> {search_radius}

26

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The coverage-ID number for each matching point is stored as the node-ID number in the NAT. If there are no matches to a node, then the node-ID is equal to the internal node number. The point cover must have a point attribute table (PAT) for this command to work. The node cover can be the same as the point cover, in which case the attributes of the PAT are transferred to the NAT within the point coverage. Thiessen: Converts a point coverage to a coverage of Thiessen or proximal polygons.
Thiessen <in_cover> <out_cover> {proximal_tolerance}

Thiessen polygons can be used to apportion a point coverage into regions known as Thiessen or Voronoi polygons. Each region contains only one input coverage point. Each region has the unique property that any location within a region is closer to the regions point than to the point of any other region. All items in the input coverage point attribute table are copied to their associated polygons in the output coverage pat.

Conversion toolset

Contains tools and toolsets to convert a coverage to or from another le format.

Coverage toolbox

From Coverage toolset

Contains tools used to convert a coverage into various le formats. Export to DLG: Converts a coverage to an optional digital line graph (DLG-3) le format.
ArcDLG <in_cover> <out_dlg_le> {in_point_cover} {in_projection_le} {x_shift} {y_shift} {in_header_le} {TRANSFORM | NO_TRANSFORM}

Before creating a digital line graph (DLG) le using Export to DLG, each node should be sequentially numbered using the Renumber Nodes tool. This will ensure that all arc, node, and polygon feature internal numbers are sequential. There are two distribution formats for a DLG le, standard and optional. This tool writes a DLG in the optional format only. Coverage topology is saved in the DLG le using conventions that are similar to the way topology is stored in a coverage (for example, polygons are dened in clockwise loops islands as counterclockwise loops, each feature has a unique identication number, negative numbers for lines indicate reverse directions, and so on). Export to Interchange File: Converts a coverage to an interchange le (.e00).
Export <COVER | FONT | GRID | INFO | LINESET | MAP | MARKERSET | PLOT | SHADESET | STACK | STACKALL | TEXT | TEXTSET | TIN> <in_dataset> <interchange_le> {NONE | PARTIAL | FULL} {max_lines}

When exporting a coverage, all associated INFO tables are written to the interchange le. For example, if the coverage name specied for input data is Forest, an INFO table named Forest.LABEL would be saved in the interchange le. A table named Forest1.LABEL, however, would not be saved in the interchange le. Export les created with the compression option set to FULL can be signicantly smaller than export les created with the PARTIAL or NONE options.
27

Export to S57: Converts a coverage to an S-57 object format.

ArcS57 <in_workspace> <log_le> {out_workspace}

S-57 is a data standard developed by the International Hydrographic Organization (IHO) to be used for the exchange of digital hydrographic data. The output log le is created in the process and holds the report of the export. Export to SDTS: Converts a coverage or grid to an SDTS Topological Vector Prole (TVP) or Point Prole Transfer le.
SDTSExport <TVP | POINT | RASTER> <in_dataset> <out_transfer_prex> {in_point_cover} {out_DD_transfer} {conversion_control_le}

SDTS is a large standard composed of smaller, more limited subsets that are federally approved as part of the SDTS FIPS 173 standard. These subsets are known as proles. The TVP (designed specically for planar vector data with topology), raster, and point proles are the only proles supported by Export to SDTS. The following conditions must be met when creating a TVP transfer: The coverage must have polygon topology. The coverage cannot have a mask le; only clean coverages will export. The coverage must have a projection dened or it will not be exported. Export to VPF: Converts a coverage into either a VPF coverage or VPF tile.
VPFExport <in_cover> <out_le> {tile_name} {control_le} {EXTRA | NO_EXTRA} {NO_FIT | FIT}

The coverage must not have a mask le. Use the Clean tool to remove mask les. A full VPF pathname must be specied with output VPF coverage or table. The VPF standard species only coverages in geographic coordinates. Using units of decimal degrees, on the WGS 1984 datum, you cannot clean a coverage that has units in decimal degrees. You should build the coverage in this case or understand how cleaning will affect your coverage. Ungenerate: Creates a text le of x,y coordinates from a coverage.
Ungenerate <in_cover> <out_generate_le> <LINE | POINT | POLY | TIC | LINK | REGION.subclass | ANNO.subclass> {NODES | NO_NODES} {EXPONENTIAL | FIXED}

Coverage toolbox

Ungenerate provides a useful mechanism to create simple coordinate les from coverages. This allows you to easily transfer coverages to other mapping systems or view and update individual coordinates using your computers text editor. The coordinates created by Ungenerate are in the same coordinate precision as the input coverage. Single-precision coordinates are generated for single-precision coverages, and double-precision coordinates for double-precision coverages.

To Coverage toolset

Contains tools used to convert various le formats into coverages. Advanced Tiger Conversion: Performs the Basic Tiger Conversion, followed by advanced operations including joining, dening a projection, and building topology.
TigerTool <in_tiger_le_prex> <out_cover_prex> {NO_JOIN | JOIN} {UTM | STATE} {zone_number} {1995 | 1997 | 1998 | 1999 | 2000 | 2002} {NO_RESTART | RESTART}

Advanced Tiger Conversion converts all versions released after April 1989. The Advanced Tiger Conversion tool does not support Record Types F and G released with the 1992 School District version. These are temporary record types, not found in earlier or subsequent versions.
28 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The output coverages created in the TIGER le conversion will always be in double precision. TIGER/Line les often contain tiny line segments that would be lost if converted to single precision. Basic Tiger Conversion: Converts U.S. Bureau of Census TIGER/Line les into one or more coverages.
TigerArc <in_tiger_le_prex> <out_cover> {out_point_cover} {out_landmark_cover} {1995 | 1997 | 1998 | 1999 | 2000 |2002}

Basic Tiger Conversion converts all versions released after April 1989. The minimum input required by Basic Tiger Conversion is Record Types 1 and 2. The Basic Tiger Conversion tool does not support Record Types F and G released with the 1992 School District version. These are temporary record types, not found in earlier or subsequent versions. The output coverages for the Basic Tiger Conversion tool will always be in double precision. TIGER/ Line les often contain tiny line segments that would be lost if converted to single precision. Generate: Creates a coverage from raw coordinates stored in a text le.
Generate <in_le> <out_cover> <LINES | ANNOTATIONS | CIRCLES | CURVES | FISHNET | LINKS | POINTS | POLYGONS | TICS>

Generate creates new coordinate features but does not create topology or attributes for these features. Other tools, such as Build or Clean, can be used to create feature topology. The coordinate precision of the output coverage is determined by the precision setting. To convert a double-precision le to a double-precision coverage, the precision must be set to double. Import from DLG: Converts a standard or Ooptional formatted Digital Line Graph le into a coverage.
DLGArc <in_dlg_le> <out_cover> {out_point_cover} {NOFIRST | ALL | ATTRIBUTED} {x_shift} {y_shift} {category}

Coverage toolbox

Topology data contained in the DLG le is ignored. You can use the Build tool after running Import From DLG, creating topology on the newly created coverage. Sometimes the coverage will have arc intersections and will need to be cleaned using the Clean tool. The output coverage may require editing before polygons or lines can be built and feature attribute tables created. For example, checks should be made on the output coverage to ensure that label points occur within their polygons, arcs match at nodes, polygons close, arcs do not cross, and so on. Import from Interchange File: Converts an interchange le (.e00) into a coverage.
Import <AUTO | COVER | FONT | GRID | INFO | LINESET | PLOT | MAP | MARKERSET | SHADESET | STACK | TEXT | TEXTSET | TIN> <interchange_le> <out_dataset>

Import reads any export le that has been fully or partially compressed as well as decompressed. Import automatically recognizes whether the export le is compressed. For the COVER option, all INFO data les saved in the interchange le whose names contain the coverage name prior to the last period in the INFO data le name are written to the workspace INFO database for the output coverage. Import from S57: Converts data from an S-57 le format to a coverage.
S57Arc <in_s57_le> <out_workspace> {CLEAN | NO_CLEAN}

S-57 is a data standard developed by the International Hydrographic Organization (IHO) to be used for the exchange of digital hydrographic data. Each S-57 exchange dataset contains one catalog le and one or more base cells. Import From S57 reads the catalog le, converts it to an INFO le, then converts each base cell le to one or two ArcInfo coverages. One of these coverages will contain all the isolated nodes (for instance, spatial point objects); the other coverage will contain all the spatial and feature objects in addition to the data descriptive information.
29

 The Import From S57 tool creates either one or two ArcInfo coverages per base cell le, depending on the types of objects contained within the le. Import from SDTS: Creates coverages or grids from an SDTS Topological Vector Prole (TVP) or Point Prole Transfer le.
SDTSImport <in_transfer_prex> <output> {out_point_cover} {layer_name} {DD | DROP_DD} {PRESERVE | CONVERT}

SDTS is a large standard composed of smaller, more limited subsets that are federally approved as part of the SDTS FIPS 173 standard. These subsets are known as proles. The TVP (designed specically for planar vector data with topology), raster, and point proles are the only proles supported by Import From SDTS. The type of prole being converted is automatically determined by the command. Import From SDTS can read U.S. Bureau of the Census TIGER data, USGS DLG-3 vector data, National Geodetic Survey geodetic control point data, and USGS DEM raster data in SDTS format. Polygon and line topology is generated for TVP data. Point topology is generated for Point Prole data. Import from VPF: Converts a VPF table into an INFO table or converts a VPF coverage or tile into a coverage.
VPFImport <input_vpf> <output> {tile_name} {control_le} {NO_EXTRA | EXTRA}

Full VPF pathnames must be specied with the Input VPF Coverage or Table. If the VPF coverage was created using the Export To VPF tool with the option to convert all tables selected, then the Output Coverage will be identical to the Input VPF Coverage.

Coverage toolbox

Data Management toolset

Contains tools and toolsets to manage, manipulate, and maintain coverages and their attribute tables.

Aggregate toolset

Contains tools used to combine coverages. Append: Combines an unlimited number of coverages into one coverage.
Append <in_covers;in_covers...> <out_cover> {FEATURES_ONLY | FEATURES_ATTRIBUTES} {POLY | LINE | POINT | NODE | NET | LINK | ANNO.subclass | SECTION.subclass | ROUTE.subclass | REGION.subclass} {NO | TICS_ONLY | FEATURES_ONLY | FEATURES_TICS}

All input coverages to be appended must contain the feature class or set of feature classes and feature attribute tables to be appended. For example, if the NET feature type option is used, all coverages should have line and polygon features and corresponding AATs and PATs. The item denitions of the feature attribute tables must be the same and in the same order for all appended coverages (unless the FEATURES_ONLY option is used).

30

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Composite Features toolset

Contains tools to create or convert regions within a coverage and to convert line features to routes. Line Coverage to Region: Converts arcs to preliminary regions in a new or existing coverage or appends preliminary regions to an existing region subclass.
RegionClass <in_cover> {out_cover} <out_subclass> {in_region_item} {out_region_item} {selection_le} {MULTIRING | SINGLERING}

The input coverage must have an AAT to specify the input region item. The arcs in each group, which are determined by the unique value of the input region item, must form closed loops. When the input region item is not specied, each arc in the input coverage becomes a preliminary region and should form a closed loop. If a selection le is not specied, all arcs are selected and available for grouping into regions. However, arcs in the input coverage that are already part of one or more fully structured regions are not available for appending to the subclass since they may not form closed rings when grouped. Line Coverage to Route: Creates a route system by creating whole arc sections for each arc in the input coverage. It can also be used to append arcs to an existing route system.

Coverage toolbox

ArcRoute <in_cover> <out_route_system> {in_route_item} {out_route_item} {measure_item} {UL | UR | LL | LR} {BLANK | NO_BLANK}

Creates a route system from lines or appends lines to a route system. It groups lines that are topologically connected and have unique values for the input item to create the route system. The unique values of the input item are always written to the output item in the route attribute table (RAT); these values help identify routes once they have been created. When appending routes to an existing route system, output route item must be the name of an existing item on the route attribute table of the route system. The tool will append a section to an existing route for every input arc having an input item equal to an output route item in the route attribute table, provided the input arcs are topologically connected to the route being appended. The measure item on the original part of the route being appended is updated based on the measures assigned to the new sections and the specied starting node. For those groups of arcs having values for the input route item not found in the output route item, a new route is created. Polygon Coverage to Region: Converts a polygon coverage to a region subclass. Each polygon in the in_cover becomes a region of the output subclass.
PolyRegion <in_cover> <out_cover> <out_subclass>

Polygon Coverage To Region can be used on an input coverage that does not have arc topology; however, the input coverage must have polygon topology. The tool builds region topology for the output subclass. Topology in the input coverage is maintained in the output coverage. When the output coverage is the same as the input coverage, the subclass is created in that coverage. Region to Polygon Coverage: Converts a region subclass into a polygon coverage and creates an INFO table containing overlapping region information.
RegionPoly <in_cover> <out_cover> <in_subclass> {out_table}

31

 All items in the region subclass polygon attribute table are maintained in the output coverage PAT. The output coverage PAT contains only the attributes of the rst region associated with each polygon. Values of zero indicate void areas in which the subclass does not exist. The attributes of the second to the nth regions associated with each polygon are stored in the output table. If only one region is associated with each polygon (a planar region subclass), then the output table does not need to be specied. However, an output table must be specied when using nonplanar region subclasses.

Generalization toolset

Contains tools to derive data with less detail and complexity from coverage features. Aggregate Polygons: Combines disjointed and adjacent polygons into new area features based on a distance.
AggregatePolygons <in_cover> <out_cover> <cell_size> <distance> {NON_ORTHOGONAL | ORTHOGONAL}

Coverage toolbox

This tool involves GRID functions and requires the ArcGIS Spatial Analyst extension software license. The input coverage must have a polygon topology. Due to the possibility of creating overlapping boundaries, preliminary regions are used as the resulting features. To create fully built regions from the preliminary regions, use the Clean tool with the POLY option on the output coverage. Collapse Dual Lines to Centerline: Derives centerlines (single lines) from dual-line features, such as road casings, based on specied width tolerances.
CollapseDualLineToCenterline <in_cover> <out_cover> <maximum_width> {minimum_width}

In addition to the standard items, the output coverage AAT will contain the following ve new items: LTYPEContains a line type value of: 1 centerlines 2 unused lines and outlines of complicated intersections 3 partition lines LL#Carries the left source arc record number. RL#Carries the right source arc record number. L-IDCarries the left source arc user ID. R-IDCarries the right source arc user ID.
32 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The values for item_width, output_width, and item_type in the item denition for all these items are 4, 5, and B. Dissolve: Merges adjacent polygons, lines, or regions that have the same value for a specied item.
Dissolve <in_cover> <out_cover> <dissolve_item> {POLY | LINE | NET | REGION.subclass}

Dissolve is used to create a simplied coverage from one that is more complex. Although the input coverage may contain information concerning many feature attributes, the output coverage contains information only about the dissolve item. The merging of polygons with Dissolve is the counterpart of intersecting polygons in overlays. Dissolve will remove the boundaries. With the POLY option, Dissolve will remove dangling arcs and pseudo nodes. The output coverage PAT with the POLY option or the output coverage AAT with the LINE option will only contain the dissolve item but no additional attributes. If #ALL is used as the dissolve item, then input coverage item denitions and data are preserved in the output coverage but User-IDs will be altered. Eliminate: Merges selected polygons with neighboring polygons that have the largest shared border between them or the largest area.
Eliminate <in_cover> <out_cover> <info_express;info_express...> {NO_KEEP_EDGE | KEEP_EDGE} {POLY | LINE} {selection_le} {BORDER | AREA}

Coverage toolbox

Only the selected set of polygons or lines will be eliminated. Polygons that border the background polygon will not be eliminated when KEEP_EDGE is specied. For the POLY option, an arc with a negative User-ID will never be eliminated, even if its the longest arc in a selected polygon. When this happens, the next longest arc is eliminated unless its along the coverage boundary when the Keep polygon boundary option is selected (KEEP_EDGE). Use of indexed items can speed up logical feature selection in Eliminate. See Index Item for details. Find Conicts: Searches a region coverage for overlapping and closely spaced buildings, based on a specied distance, and records the occurrences.
FindConicts <in_cover> <out_cover> <conict_distance>

33

 This tool will help you locate where buildings are within the specied distance; that is, they are in spatial conict. A buffer will be created around each building or group of connected buildings. The buffers overlap indicates a conict. An item, FREQUENCY, will be added to the out_cover.PAT, carrying the number of buffers that share each polygon. A FREQUENCY value of 1 means no conict; a value of 2 or more, according to how many buffers overlap, indicates a conict area. Buildings connected in one group are not considered conicting with each other. Only the outer boundary of such a group will be checked with neighboring buildings or groups of buildings. The output coverage is created only if conicts are identied. Since the input buildings are regions, the buffers in the output coverage are also regions with a subclass BUF. You can select and view the conict areas (the polygons with a FREQUENCY value of 2 or more) and make necessary edits. Simplify Building: Simplies the boundary or footprint of building polygons while maintaining their essential shape and size.
SimplifyBuilding <in_cover> <out_cover> <simplication_tolerance> {minimum_area} {selection_le} {NOT_CHECK | CHECK_CONFLICT}

The input coverage must have a polygon topology. Due to the possibility of creating overlapping boundaries, preliminary regions are used as the resulting features. To create fully built regions from the preliminary regions, use Clean with the POLY option on the out_cover. If a selection le is not specied or if it contains no polygons, all polygons in the input coverage are selected for simplication. If the selection le does not contain the polygon feature class or if it does not match the input coverage (that is, the selection le was not derived from the input coverage), the program will stop. Simplify Line or Polygon: Removes small uctuations or extraneous bends from a line or polygon, while preserving its essential shape.
SimplifyLineOrPolygon <in_cover> <out_cover> <simplication_tolerance> {POINT_REMOVE | BEND_SIMPLIFY} {NO_ERROR_CHECK | ERROR_CHECK}

Coverage toolbox

34

If the input coverage already contains intersecting lines or if you want a quick result and dont care about topological errors in the output coverage, use the default option, which is not to Check for topological errors. Any topological errors introduced by the process will not be checked and corrected. If the input coverage contains intersecting lines, and you choose to Check for topological errors, it will fail at the input data validation, and the program will terminate with a message: Intersecting lines are found in in_cover. The program is terminated. If the input coverage contains no intersecting lines, check the Check for topological errors option to nd and avoid errors generated by the simplication process. If any topological errors are found, the involved arcs will be regeneralized using a reduced tolerance. The result will be checked for topological errors again. The process iterates until no errors are found. With this option, the program will run much longer than with the default option.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Indexes toolset

Contains tools to add or remove attribute indexes. Drop Index: Drops an attribute index from the specied item and INFO table.
DropIndex <in_info_table> {index_item;index_item...}

If there are no indexes on a coverage, the dialog box will not show any elds on which to drop an index. Index Item: Creates an attribute index to increase access speed to the specied item during query operations.
IndexItem <in_info_table> <index_item>

Indexed items speed up selection operations of large INFO les. Item indexes are preserved when the coverage or INFO table is copied to a new location.

Items toolset

Contains tools to add or remove items (elds) in INFO tables. Add Item: Adds a blank or zero item to an INFO table.
AddItem <in_info_table> <out_info_table> <item_name> <item_width> <output_width> <BINARY | CHARACTER | DATE | FLOATING | INTEGER | NUMERIC> {decimal_places} {start_item}

Do not insert items before the Cover-ID in a feature attribute table. Do not insert items before the COUNT item in a grid VAT. If item Type denes a character, blanks are inserted for each record. If item type denes a numeric item, then zeroes are inserted for each record. Drop Item: Deletes one or more items from an INFO table.
DropItem <in_info_table> <out_info_table> <drop_item;drop_item...>

Coverage toolbox

The output info table can be the same name as the input INFO table. However, if the output INFO table already exists, it will be replaced. Do not drop items before the User-ID in feature attribute tables. Redened items will be dropped if their item denition relates to an item that was dropped.

Joins toolset

Contains a tool to join INFO tables. Join Info Tables: Joins the item denitions and values of two tables based on a shared item.
JoinItem <in_info_table> <join_info_table> <out_info_table> <relate_item> {start_item} {LINEAR | ORDERED | LINK}

To maintain the integrity of a feature INFO table, do not insert items before the input INFO table id (when the output INFO table equals the input INFO table). If the same item name is encountered in both tables, the item from the input INFO table is maintained and the join INFO table item is excluded.

35

 The speed of execution will depend on the organization of the les being joined. In general, LINK is the fastest matching operation, then LINEAR with an indexed relate item, then ORDERED. Although it is the fastest option, LINK cannot be applied to most cases.

Projections toolset

Contains tools to set a projection or reproject or transform a coverage. Dene Projection: Creates or modies the coordinate system information (including projection parameters, such as datum and spheroid) stored in the coverages projection denition le (.prj).
DeneProjection <in_cover> <projection_le>

This command can be used if the input dataset or feature class does not have a projection dened. If the input dataset or feature class already has a projection dened, a warning will be raised but the tool will execute successfully. Dene Projection will not change the coordinates of the output dataset. To project a dataset from one projection to another, you must use the Project command. Project: Changes the coordinate system of a coverage including its datum or spheroid.
Project <in_cover> <out_cover> <projection_le>

Coverage toolbox

It can convert a dataset from a spherical coordinate system with angular units (such as Geographic) to a planar coordinate system with linear units. Most Coverage tools, among them Build and Clean, assume you have a planar, two-dimensional dataset. So if your dataset is in a geographic coordinate system in decimal degrees (DD, angular units), the Project tool projects your dataset to any suitable projected coordinate system in linear units (meters or feet). Output projection information can be specied using a projection le or from an empty output coverage. The projection le must contain both input and output projection denitions. Use of a projection le will override any projection information stored in the datas .prj le. Transform: Moves all features in the coverage based on a set of from and to control points.
Transform <in_cover> <out_cover> {AFFINE | PROJECTIVE | SIMILARITY}

The output coverage must already exist with a tic le containing x,y coordinates for at least two in the desired location and units. Except for the tics, any existing features in the output coverage will be replaced by features from the input coverage. The input coverage tic le and the output coverage tic le must contain at least two coverages that have the same Tic-IDs and represent corresponding locations in both coverages. The two coverages do not have to have identical tics; only those tics whose IDs are common to both coverages will be used in the transformation.

36

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Tables toolset

Contains tools used for editing the associated attribute tables. Add XY Coordinates: Calculates and adds x,y coordinates of labels or points to the coverage PAT or x,y coordinates of nodes to the coverage NAT.
AddXY <in_cover> {POINT | NODE}

If the items X-COORD and Y-COORD already exist, they will be overwritten. If the point or node locations are moved after using Add XY Coordinates, the X-COORD and Y-COORD values will not represent the new locations. To update their values to the new location, rerun the tool. The values for X-COORD and Y-COORD are not modied by other tools, such as Project and Transform. If your input coverage is in a geographic coordinate system, the X-COORD and Y-COORD represent the longitude and latitude, respectively. Renumber Nodes: Updates arc-node topology by renumbering nodes for coverage arcs and identies arcs that share the same node locations.
Renode <in_cover> {from_item} {to_item}

Coverage toolbox

If the input coverage has a node attribute table, Renumber Nodes does the same thing as Build with the NODE option. All nodes in the input coverage are sequentially renumbered starting with 1. All feature attribute tables as well as polygon topology and arc-node topology are maintained by Renumber Nodes. Update IDs: Updates User-IDs in a coverage after they have been modied in a feature attribute table.
IDEdit <in_cover> <POLY | LINE | POINT | ANNO.subclass>

Tools, such as Add Item and Calculate Field, can be used to add or modify User-IDs in a coverages feature attribute table before Update IDs is used. If the Create Labels tool has been used to create new label points for coverage polygons, the polygon User-IDs stored in the coverage PAT are not equal to the new label point User-IDs. Create Labels stores the new label points and their User-IDs in the LAB le. Update IDs may be used to change the label point User-IDs to be equal to the User-IDs stored in the PAT.

37

Tolerances toolset

Contains a tool to adjust coverage-associated tolerances. Tolerance: Sets the tolerances associated with a coverage.
Tolerance <in_cover> {FUZZY | DANGLE | TIC_MATCH | EDIT | NODESNAP | WEED | GRAIN | SNAP} {tolerance_value}

A tolerance value of zero will not be accepted for the following options: FUZZY, EDIT, NODESNAP, WEED, GRAIN, and SNAP. If no tolerance type is specied, the default type is FUZZY.

Topology toolset

Contains tools used to develop the topologic relationship within a coverage. Build: Creates or updates feature attribute tables and polygon topology.
Build <in_cover> <POINT | LINE | POLY | NODE | ANNO> {anno_subclass}

Coverage toolbox

If a coverage feature attribute table exists, the additional items in the feature attribute table will be updated using the old internal number of each of the features specied as the relate item. User-dened items in existing feature attribute tables are always maintained. When using Build with the POLY option, polygons must have label points to retain their attributes. If there are no attributes, label points are not required to generate a PAT. Polygons containing no label points will be assigned a User-ID of zero. Build does not create polygon labels. Build and Clean are similar commands as they are both used to dene coverage topology. The basic difference is that Clean can detect and create intersections but Build cannot. However, since Build does not use a fuzzy tolerance, the coordinates will not be adjusted while topology is being built. Clean: Generates a coverage with correct polygon or arc-node topology.
Clean <in_cover> {out_cover} {dangle_length} {fuzzy_tolerance} {POLY | LINE}

If the input coverage has either PAT or AAT feature attribute tables, they are automatically updated in the output coverage for the POLY option. Only the AAT will be updated when using the LINE option. The internal number of each input coverage feature is used to relate attribute information from the input coverage feature attribute table to the output coverage to ensure that the attributes are properly joined to the output feature attribute tables. Feature User-IDs do not have to be unique to ensure that each input feature keeps its attributes in the output coverage. Clean with the POLY option creates one additional polygon known as the background or universe polygon. It is always given polygon internal number 1, and its area is the total sum of the areas of all other polygons in the coverage. It is shown as a negative area in the PAT. The dangle length and fuzzy tolerance for the output coverage are set and veried by Clean.

38

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Create Labels: Creates label points for polygons that have no labels and assigns each a User-ID.
CreateLabels <in_cover> {id_base}

The input coverage must contain polygon topology. After Create Labels, the polygon User-IDs stored in the input coverage PAT are not equal to the new label point User-IDs generated by Create Labels. You must use Build or Update IDs to make them equal. If a coverage contains polygons and only some of the polygons have label points, Create Labels will only generate labels in those polygons for which no labels exist if you specify an ID base. VPF Tile Topology: Creates cross-tile topology for all tiled coverages in a Vector Product Format database library or creates topology for an individual tile in a VPF library.
VPFTile <VPF_library> {sig_digits} {93 | 96} {ALL | VPF_cover}

Military Standard MIL-STD-2407 (June 28, 1996) renes the denition of cross-tile topology. The VPF Tile Topology command has been updated to meet the new specication. You may use the optional parameter to choose the 93 or 96 VPF standard. VPF Tile Topology works on all tiled coverages of a VPF library or a single coverage within that library. The last optional parameter, VPF_cover, allows you to select a particular coverage in which cross-tile topology should be populated. It is more efcient, however, to implement VPF Tile Topology after all coverages for a library have been converted from ArcInfo to VPF format.

Coverage toolbox

Workspace Management toolset

Contains a tool to manage coverages within a workspace. Create Coverage: Creates a new, empty coverage.
Create <out_cover> {template_cover}

The coordinate precision of the output coverage is determined by the precision for derived coverages environment, regardless of whether the template coverage is specied. To establish the location of the tics in the output coverage, specify a template coverage or edit the output coverage manually. You can then use the output coverage as the destination (output) coverage of the transform tool.

39

Data Management toolbox

Contains the tools to develop, manage, and manipulate feature classes, datasets, and layers. Data Comparison toolset

Contains tools to compare one dataset with another dataset and report any similarities and differences. Feature Compare: Compares two feature classes or layers and returns the comparison results.
FeatureCompare <in_base_features> <in_test_features> <sort_eld;sort_eld...> {ALL | GEOMETRY_ONLY | ATTRIBUTES_ONLY | SCHEMA_ONLY | SPATIAL_REFERENCE_ONLY} {IGNORE_M | IGNORE_Z | IGNORE_POINTID | IGNORE_EXTENSION_PROPERTIES} {xy_tolerance} {m_tolerance} {z_tolerance} {eld {Tolerance};eld {Tolerance}...} {omit_eld;omit_eld...} {NO_CONTINUE_COMPARE | CONTINUE_COMPARE} {out_compare_le}

The tool returns messages showing the comparison result. By default, the tool will stop executing after encountering the rst miscompare. To report all differences, set the continue compare option to true. Multiple sort elds may be specied. The rst eld is sorted, then the second eld, and so on, in ascending order. Sorting by a common eld in both the input base features and the input test features ensures that you are comparing the same row from each input dataset. By default, the compare type is set to ALL. File Compare: Compares two les and returns the comparison results.
FileCompare <in_base_le> <in_test_le> {ASCII | BINARY} {NO_CONTINUE_COMPARE | CONTINUE_COMPARE} {out_compare_le}

The tool returns messages showing the comparison result. By default, the tool will stop executing after encountering the rst miscompare. To report all differences, set the continue compare option to true. File Compare does support masking out of characters, words, and lines of text in an ASCII le. ASCII is the default le type. If entering binary les, change the le type to BINARY. The output compare le will contain all similarities and differences between the input base le and the input test le. This le is a comma-delimited text le that can be viewed and used as a table in ArcGIS. Raster Compare: Compares the properties of two rasters datasets or two raster catalogs and returns the comparison result.
RasterCompare <in_base_raster> <in_test_raster> {RASTER_DATASET | GDB_RASTER_DATASET | GDB_RASTER_CATALOG} {BANDCOUNT | EXTENT | COLUMNS AND ROWS | PIXEL TYPE | NODATA | SPATIAL REFERENCE | PIXEL VALUE | COLORMAP | RASTER ATTRIBUTE TABLE | STATISTICS | METADATA | PYRAMIDS EXIST | COMPRESSION TYPE} {NO_CONTINUE_COMPARE | CONTINUE_COMPARE} {out_compare_le}

Data Management toolbox

The tool returns messages showing the comparison result. Table Compare: Compares two tables and returns the comparison results.
TableCompare <in_base_table> <in_test_table> {sort_eld;sort_eld...} {ALL | ATTRIBUTES_ONLY | SCHEMA_ONLY} {IGNORE_EXTENSION_PROPERTIES} {eld {Tolerance}; eld {Tolerance}...} {omit_eld;omit_eld...} {NO_CONTINUE_COMPARE | CONTINUE_COMPARE} {out_compare_le}

The tool returns messages showing the comparison result. By default, the tool will stop executing after encountering the rst miscompare. To report all differences, set the continue compare option to true. Multiple sort elds may be specied. The rst eld is sorted, then the second eld, and so on in ascending order. Sorting by a common eld in both the input base table and the input test table ensures that you are comparing the same row from each input dataset. By default, the compare type is set to ALL.
41

TIN Compare: Compares two triangulated irregular networks (TINs) and returns the comparison results.
TinCompare <in_base_tin> <in_test_tin> {ALL | PROPERTIES_ONLY | SPATIAL_REFERENCE_ONLY} {NO_CONTINUE_COMPARE | CONTINUE_COMPARE} {out_compare_le}

The tool returns messages showing the comparison result. By default, the tool will stop executing after encountering the rst miscompare. To report all differences, set the continue compare option to true. The output compare le will contain all similarities and differences between the input base features and the input test features. This le is a comma-delimited text le that can be viewed and used as a table in ArcGIS. For example, this table can be queried to obtain all the object ID values for all the rows that are different.

Database toolset

Contains tools that improve database performance. Compact: Reduces the size and optimizes the performance of a le or personal geodatabase.
Compact <in_workspace>

You should compact your databases on a regular basis if you do a lot of data entry and deletion. Personal and le geodatabases are stored in binary les on your disk drive. As you add/remove/edit data in these les, they will become fragmented, resulting in a decrease in performance. It is recommended that you compact your personal geodatabase when its size increases to more than 250 MB. Compress: Compresses an ArcSDE geodatabase by removing states not referenced by a version and redundant rows.
Compress <in_workspace>

When you delete a record from a database, it is only marked as deleted; it is not actually removed from the associated table. Therefore, the table will remain the same size after you delete records. To actually remove deleted records from the database, you must compress the database. To improve database performance, the database should be compressed periodically. Once a database is compressed, deleted records cannot be recovered. Only the SDE administrator can perform compression. After compressing the database or editing the data, the Analyze command should be executed to update the database statistics for each dataset or feature class. This will improve display and query performance. Upgrade Spatial Reference: Upgrades a low precision datasets spatial reference to high precision.
UpgradeSpatialReference <input_dataset> {xy_resolution} {z_resolution} {m_resolution}

Data Management toolbox

42

Valid input is stand-alone feature class, feature dataset, or raster catalog with low-resolution spatial reference and stored in an upgraded or current version of a personal or ArcSDE geodatabase.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Disconnected Editing toolset

Contains tools to allow remote or mobile users to transfer data from a central database to remote or mobile locations, enabling users to operate independently. Check In: Checks in changes made in a checkedout ArcSDE, le, or personal geodatabase to the master ArcSDE geodatabase.
CheckIn <in_workspace> <dest_workspace> {NON_RECONCILE | RECONCILE}

You must have permission to edit the data you are checking in. Once checked in, the changes (edits) will be reected in the master geodatabase and viewable by all users. Data cannot be checked in or checked out in ArcView. Check In from Delta: Checks in a geodatabase from a delta database or delta XML le. A delta le contains only the changes exported from a checkout geodatabase.
CheckInDelta <in_delta_database> <dest_workspace> {NON_RECONCILE | RECONCILE}

Instead of checking in edits directly from the checkout geodatabase, you can export the changes only from the checkout geodatabase to a delta database or delta XML le. Delta databases and XML les are smaller than the original checkout geodatabase. When the check-in from the delta database or XML le succeeds, the checkout in the master geodatabase will be unregistered. Checking in changes from a delta database or XML le does not automatically unregister the checkout in the associated checkout geodatabase; this must be done manually. Check Out: Checks out datasets from an ArcSDE geodatabase to an ArcSDE, le, or personal geodatabase for ofine editing.
CheckOut <in_data;in_data...> <out_workspace> <out_name> <DATA | SCHEMA_ONLY> <NO_REUSE | REUSE> <RELATED | NO_RELATED>

Data Management toolbox

The tool accepts layers or tables that reference data from one ArcSDE server. Either add them to the list in the dialog box or create a semicolon-delimited list at the command line or in a script. The layers and tables must reference versioned ArcSDE feature classes and tables for which you have permissions to edit. If the checkout is to a personal geodatabase that does not exist, one will be created. Export to Delta: Exports changes in a check-outgeodatabase to a delta database or XML le. A delta le contains only the changes exported from a check-out geodatabase.
ExporttoDelta <in_workspace> <dest_delta_database>

Instead of checking in edits directly from the checkout geodatabase, you can export the changes only from the checkout geodatabase to a delta database or delta XML le. Delta databases and XML les are smaller than the original checkout geodatabase. The changes in the delta database or XML le may be checked in as a pull check-in from the master geodatabase.

43

Distributed Geodatabase toolset

Contains tools that allow organizations to disperse their data as necessary from central servers to regional or local ofces that may be in a connected or disconnected environment. Add Global IDs: Adds global IDs to a list of geodatabase classes, tables, and/or feature datasets.
AddGlobalIDs <in_datasets;in_datasets...>

If the geodatabase is a personal or le geodatabase, then the datasets must be schema only. Compare Replica Schema: Generates a report le XML comparing an input replica geodatabase and an XML schema le or geodatabase.
CompareReplicaSchema <in_geodatabase> <in_source_le> <Output_replica_schema_changes_ le>

Create Replica: Creates a replica personal, le, or ArcSDE geodatabase from a specied list of feature classes, layers, datasets, and/or tables in an ArcSDE geodatabase.
CreateReplica <in_data;in_data...> <TWO_WAY_REPLICA | ONE_WAY_REPLICA | CHECK_OUT> <out_ geodatabase> <out_name> {FULL | SIMPLE} {CHILD_DATA_SENDER | PARENT_DATA_SENDER} {USE_ DEFAULT_FILTERS | ADD_WITH_SCHEMA_ONLY | ALL_ROWS | DO_NOT_ADD} {DO_NOT_REUSE | REUSE} {GET_RELATED | DO_NOT_GET_RELATED}

All datasets must be from the same ArcSDE database. The spatial extent in the environment setting can be used to set the replica geometry. This can be set using another feature classes extent. The reuse schema option is only available for checkout replicas. Create Replica Footprints: Creates a feature class that contains the geometries for all the replicas in a geodatabase.
CreateReplicaFootPrints <in_geodatabase> <out_geodatabase> <output_feature_class_name>

Data Management toolbox

44

Create Replica From Server: Creates a replica using a specied list of feature classes, layers, datasets and/or tables from a remote geodatabase using a geodata service published on ArcGIS Server.
CreateReplicaFromServer <in_geodataserver> <datasets;datasets...> <TWO_WAY_REPLICA | ONE_WAY_REPLICA | CHECK_OUT> <out_geodatabase> <out_name> {FULL | SIMPLE} {CHILD_DATA_ SENDER | PARENT_DATA_SENDER} {USE_DEFAULT_FILTERS | ADD_WITH_SCHEMA_ONLY | ALL_ROWS | DO_NOT_ADD} {DO_NOT_REUSE | REUSE} {GET_RELATED | DO_NOT_GET_RELATED}

Export Acknowledgement Message: Creates an output delta le to acknowledge the reception of a data change message from an input replica and replica geodatabase.
ExportAcknowledgementMessage <in_geodatabase> <out_acknowledgement_le> <in_replica>

Checkout replicas are not listed. Export Data Change Message: Creates an output delta le containing replica updates from an input replica and replica geodatabase.
ExportDataChangeMessage <in_geodatabase> <out_data_changes_le> <in_replica> <DO_NOT_ SWITCH | SWITCH> <UNACKNOWLEDGED | NO_UNACKNOWLEDGED> <NEW_CHANGES | NO_NEW_CHANGES>

Export Replica Schema: Creates an output XML le with the schema of an input one- or two-way replica.
ExportReplicaSchema <in_geodatabase> <output_replica_schema_le> <in_replica> ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Import Message: Imports changes from a delta le to a replica geodatabase.

ImportMessage <in_geodatabase> <source_delta_le> {output_acknowledgement_le} {MANUAL | IN_FAVOR_OF_IMPORTED_CHANGES | IN_FAVOR_OF_DATABASE} {BY_OBJECT | BY_ATTRIBUTE} {DO_ NOT_RECONCILE | RECONCILE}

After importing a data change message, you have the option to immediately export an acknowledgement message. Import Replica Schema: Applies replica schema differences using an input replica geodatabase and XML schema le or geodatabase.
ImportReplicaSchema <in_geodatabase> <in_source>

Re-Export Unacknowledged Messages: Creates an output delta le containing unacknowledged replica updates from an input one- or two-way replica geodatabase.
ReExportUnacknowledgedMessages <in_geodatabase> <output_delta_le> <in_replica> <ALL_ UNACKNOWLEDGED | MOST_RECENT>

This command is not available for checkout replicas. Synchronize Changes: Synchronizes updates between two replica geodatabases in a direction specied by the user.
SynchronizeChanges <geodatabase_1> <in_replica> <geodatabase_2> <BOTH_DIRECTIONS | FROM_GEODATABASE2_TO_1 | FROM_GEODATABASE1_TO_2> <IN_FAVOR_OF_GDB1 | IN_FAVOR_OF_GDB2 | MANUAL> <BY_OBJECT | BY_ATTRIBUTE> <DO_NOT_RECONCILE | RECONCILE >

Once checked in, the changes (edits) will be reected in the master geodatabase and viewable by all users.

Domains toolset

Contains tools for the management of domains, both coded and attribute, within a workspace. Add Coded Value to Domain: Adds a new value to a domains coded value list.
AddCodedValueToDomain <in_workspace> <domain_name> <code> <code_description>

Data Management toolbox

A coded value domain can apply to any type of attributetext, numeric, date, and so onand species a valid set of values for an attribute. For example, a coded value list for a text attribute might include valid pipe material values: CLcast iron pipe, DLductile iron pipe, ACPasbestos concrete pipe, or a coded value list might include the numeric values representing valid pipe diameters: 0.753/4, 22, 2424, and 3030. The coded value domain includes both the actual value that is stored in the database (for example, 1 for pavement) and a description of what the code value means (for example, pavement). Assign Domain to Field: Sets the domain for a particular eld and optionally for a subtype.
AssignDomainToField <in_table> <eld_name> <domain_name> {subtype_code;subtype_code...}

If no subtype is specied, the domain is only assigned to the specied eld. When an attribute domain is associated with a table or feature class, an attribute validation rule is created in the database. This attribute validation rule describes and constrains the valid values of a eld type. One attribute domain can be associated with multiple elds in the same table, feature class, or subtype as well as in multiple tables and feature classes.

45

Create Domain: Creates an attribute domain in the specied workspace.

CreateDomain <in_workspace> <domain_name> <domain_description> <SHORT | LONG | FLOAT | DOUBLE | TEXT | DATE> {CODED | RANGE} {DEFAULT | DUPLICATE | GEOMETRY_RATIO} {DEFAULT | SUM_VALUES | AREA_WEIGHTED}

Coded value domains support only default value, duplicate split policies, and default value merge policies. Range domains support all split and merge policies. After a Split or Merge operation, the attribute values of output features are calculated based on the numeric values of the input features and the specied split or merge policy. Delete Coded Value from Domain: Removes a value from a coded value domain.
DeleteCodedValueFromDomain <in_workspace> <domain_name> <code;code...>

The Code Value parameter Add Value button is used only in ModelBuilder. In ModelBuilder, where the preceding tool has not been run or its derived data does not exist, the Code Value parameter may not be populated with values. The Add Value button allows you to add expected values so you can complete the Delete Coded Value From Domain dialog box and continue to build your model. Delete Domain: Deletes a domain from a workspace.
DeleteDomain <in_workspace> <domain_name>

A domain cannot be deleted if it is associated with a feature class or table. Use the Remove Domain From Field tool to remove the association between a feature class or table and a domain. Domain to Table: Creates a table from an attribute domain.
DomainToTable <in_workspace> <domain_name> <out_table> <code_eld> <description_eld> {conguration_keyword}

Data Management toolbox

46

Creating a table from an attribute domain allows for additional editing of the table in ArcMap. For example, a table could be created from a coded value domain, additional code values could be added to the coded value list, and the Table To Domain tool could be used to update the original domain. Remove Domain from Field: Removes an attribute domain association from a feature class eld.
RemoveDomainFromField <in_table> <eld_name> {subtype_code;subtype_code...}

The Remove Domain From Field function is the opposite operation of the Assign Domain To Field function. Removing a domain from a eld removes the association between a eld and an attribute domain. When a domain is removed from a eld, the attribute validation rule for that eld is removed from the database. Set Value for Range Domain: Sets the minimum and maximum values for an existing range domain.
SetValueForRangeDomain <in_workspace> <domain_name> <min_value> <max_value>

A range domain species a valid range of values for a numeric attribute. For example, a valid range of water main pressure values might be between 50 and 75 psi. Table to Domain: Creates or updates a coded value domain from a table.
TableToDomain <in_table> <code_eld> <description_eld> <in_workspace> <domain_name> <domain_description> <APPEND | REPLACE>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Feature Class toolset

Contains tools designed to perform basic feature class management including creating, appending, integrating, and updating multiple feature classes. Append Annotation Feature Classes: Creates a new geodatabase annotation feature class by combining annotation from multiple input geodatabase annotation feature classes into a single feature class with annotation classes.
AppendAnnotation <input_features;input_features...> <output_feature_class> <reference_scale> {CREATE_CLASSES | ONE_CLASS_ONLY} {NO_SYMBOL_REQUIRED | REQUIRE_SYMBOL} {AUTO_CREATE | NO_AUTO_CREATE} {AUTO_UPDATE | NO_AUTO_UPDATE}

The output geodatabase annotation feature class cannot be registered as versioned. If you select an output annotation feature class that already exists, the features will be appended into that feature class and the tool will project the annotation features into the destination spatial reference. Calculate Default Cluster Tolerance: Calculates a default cluster tolerance value.
CalculateDefaultClusterTolerance <in_features>

The value returned by Calculate Default Cluster Tolerance is the same cluster tolerance value used as a default for other geoprocessing tools. Calculate Default Spatial Grid Index: Calculates a spatial grid value, used to quickly locate features in a dataset that match the criteria of a spatial search.
CalculateDefaultGridIndex <in_features>

The spatial index calculated by Calculate Default Spatial Grid Index cannot be added to a personal or le geodatabase because it needs the existing index to maintain its integrity. When you create a new feature class in a personal or le geodatabase, you can specify a spatial index. Spatial grid indexes can be added to ArcSDE geodatabase feature classes using Add Spatial Index. Create Feature Class: Creates a new, empty feature class.
CreateFeatureClass <out_path> <out_name> <POLYGON | POINT | MULTIPOINT | POLYLINE> {template;template...} {DISABLED | SAME_AS_TEMPLATE | ENABLED} {DISABLED | SAME_AS_TEMPLATE | ENABLED} {spatial_reference} {conguration_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

Data Management toolbox

The type of a feature class created depends on the format of the pathname specied: a geodatabase feature class for ArcSDE and personal or le geodatabase pathnames or a shapele feature class for a le system folder. The Create Feature Class function only creates simple feature classes. Custom feature classes (annotation, dimensions, and so on) can be created in ArcCatalog. Create Fishnet: Creates a shnet of rectangular cells.
CreateFishnet <out_feature_class> <origin_coord> <y_axis_coord> <cell_width> <cell_ height> <number_rows> <number_columns> {corner_coord} {LABELS | NO_LABELS} {template}

If zero is specied for the cell size width and the cell size height, then specify the number of rows and columns, and the opposite corner of the shnet (X, Y). The extent of the shnet can be entered by specifying the coordinates or using a template dataset. When entering a template, the shnet origin coordinate and y-axis coordinate are populated. You will still be required to enter the number of rows and columns. If zero is specied for the rows and columns, then specify the opposite corner of the shnet (X, Y). If zero is entered for the cell size width or cell size height, then it will be automatically computed based on the number of rows and columns and the opposite corner of the shnet.
47

 Labels are generated by default. To generate polygon features from the line features, you must use the Feature To Polygon tool. Create Random Points: Creates a user-specied number of random points in an extent, in the polygons of a feature class, or along the lines of a feature class.
CreateRandomPoints <out_path> <out_name> {constraining_feature_class} {constraining_ extent} {number_of_points}

Integrate: Compares features and makes any lines, points, or vertices within a certain distance range identical or coincident.
Integrate <features{Ranks};features{Ranks}...> {cluster_tolerance}

The value for cluster tolerance is critical for Integrate. A cluster tolerance that is too large may collapse polygons or merge arcs and points that should not be merged. To minimize error, the value you choose for cluster tolerance should be as small as possible. The input features may include any combination of point, multipoint, line, and polygon feature classes. Integrate can use feature classes from read-only data such as CAD or coverages, as input. The data will be used as part of the integration process but will not be modied. This can be useful for integrating (snapping) the features in a shapele, or geodatabase feature class to the features in the read-only format. To be effective, you may want to assign a higher rank (1) to the read-only format. Copy your inputs before attempting this.

Data Management toolbox

48

Update Annotation Feature Class: Updates the input annotation feature class with text attribute elds and optionally populates the value of each new eld for every feature in the feature class.
UpdateAnnotation <in_features> {POPULATE | DO_NOT_POPULATE}

This tool will update the schema of the feature class and, optionally, each annotation feature within the feature class. The schema update will add elds to the feature class (bold, italic, text, and so on) and also ensure that there is a symbol within the symbol collection. Without a symbol in the symbol collection, you cant use the improvements for constructing annotation features.

Features toolset

Contains tools to manage and enrich feature classes, such as inspecting and correcting potential errors with data and creating different geometries. Add XY Coordinates: Adds the elds POINT_X and POINT_Y to the point input features and calculates their values.
AddXY <in_features>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 If the elds POINT_X and POINT_Y elds already exist, the values will be updated. If the features are moved after using Add XY Coordinates, the POINT_X and POINT_Y values will not represent the new locations. To update their values to the new location, rerun the tool. The values for POINT_X and POINT_Y are not modied by other tools, such as Project. Add XY Coordinates will also add POINT_Z and POINT_M elds when the input features are z- and menabled. Adjust 3D Z: Allows the modication of all z-values in a z-enabled feature class.
Adjust3DZ <in_features> {NO_REVERSE | REVERSE} {adjust_value} {MILLIMETERS | CENTIMETERS | METERS | INCHES | FEET | YARDS | FATHOMS} {MILLIMETERS | CENTIMETERS | METERS | INCHES | FEET | YARDS | FATHOMS}

Bathymetry data often has positive z-values. You may want to reverse the signs of all the data in the feature class to make it negative. Z-enabled data could be referenced to a vertical datum that is not appropriate for your geoprocessing needs. This tool could apply a bulk-shift of all the z-values in the feature class to adjust the data either up or down vertically. Check Geometry: Checks the validity of the geometries of features.
CheckGeometry <in_features;in_features...> <out_table>

The output table will have one record for each problem found. If no problems are found, the output table will have no records. The output table has the following elds: CLASSThe full path to and name of the feature class in which the problem was found. FEATURE_IDThe feature ID or object ID for the feature with the geometry problem. PROBLEMA short description of the problem. The PROBLEM eld will contain one of the following: short segment, null geometry, incorrect ring ordering, incorrect segment orientation, self intersections, unclosed rings, or empty parts. For multipoint features, only the null geometry and empty part problems apply. For point features, only the null geometry problem applies. Copy Features: Copies the selected features to a new feature class.
CopyFeatures <in_features> <out_feature_class> {conguration_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

Data Management toolbox

The input features (geometry and attributes) will be copied to the output feature class. This tool can be used for data conversion as it can read many feature formats (any you can add to map) and write these out to shapele or geodatabase (le, personal, or ArcSDE). If the output feature class already exists, it will be overwritten. Delete Features: Deletes features from the input feature class or layer.
DeleteFeatures <in_features>

Both the geometry and the attributes will be deleted from the affected features. ArcSDE, le, or personal geodatabase feature classes; shapeles; and layers of these data types are valid input features. Feature Envelope to Polygon: Creates polygons from the envelopes of each feature in the input feature class.
FeatureEnvelopeToPolygon <in_features> <out_feature_class> {SINGLEPART | MULTIPART}

49

 Valid inputs are line, polygon, and annotation feature classes. When the envelope of a feature is an invalid polygon (height or width is zero), the polygon will not be written to the output. The multipart parameter will have no effect on the result when the input is a single-part feature. Feature to Line: Creates a new output line feature class from input polygon or line features.
FeatureToLine <in_features;in_features...> <out_feature_class> {cluster_tolerance} {ATTRIBUTES | NO_ATTRIBUTES}

The attributes of the input features are transferred to the output feature class lines. To get lines with right and left polygon IDs as attributes from a polygon feature class, use the Polygon To Line tool instead. An output line features will be created for each input line and each input polygon boundary. If input lines or polygon boundaries cross, the output lines will be split into different features at those locations. Feature to Point: Creates a point feature class based on an input polygon, line, or multipoint feature class.

Data Management toolbox

50

FeatureToPoint <in_features> <out_feature_class> {CENTROID | INSIDE}

If the input features are polygons, the CENTROID option will result in points that are at the center of gravity for that polygon. These may not actually be inside the polygons area. To insure that the point created is inside the polygons area, use the Inside option. If the input features are lines and the CENTROID option is used, the output points will be coincident with the center of the features envelope (rectangular window that contains a specic feature). If the INSIDE option is used, the point on the line closest to the center of the features envelope will be used. Feature to Polygon: Creates a new polygon feature class from input line and/or polygon features.
FeatureToPolygon <in_features;in_features...> <out_feature_class> {cluster_tolerance} {ATTRIBUTES | NO_ATTRIBUTES} {label_features}

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The input features must be lines or polygons. The label features parameter allows for a feature class of label attributes to be applied to the output polygons. Feature Vertices to Points: Creates a point feature class from the vertex locations of the input features.
FeatureVerticesToPoints <in_features> <out_feature_class> {ALL | MID | START | END | BOTH_ENDS}

The attributes of the input features are copied to the output feature class points. Input features can be lines or polygons. Multipart to Singlepart: Breaks any multipart features into single features.
MultipartToSinglepart <in_features> <out_feature_class>

Data Management toolbox

Features that already have single-part geometry will not be affected. The opposite of this tool is Dissolve, which creates multipart features from single-part features based on a common attribute value. Polygon to Line: Creates a new line feature class from a polygon feature class including the feature IDs of the left and right polygons for the new lines.
PolygonToLine <in_features> <out_feature_class>

All input feature classes and/or feature layers must be polygon geometry.
51

 The right and left polygon FIDs are maintained in the output line feature class. Polygon boundaries are split at nodes in the output line feature class. Repair Geometry: Repairs geometry problems in a feature class or layer.
RepairGeometry <in_features>

The Check Geometry tool can be used to identify feature classes and features within those feature classes that have geometry problems. Problems repaired with this tool include null geometry, short segment, incorrect ring ordering, incorrect segment orientation, self intersections, unclosed rings, and empty parts. Line features that are m aware will not be modied (repaired) for any of the cases above unless they are short segments or null geometry. Split Line at Vertices: Splits each line feature at every vertex contained in a feature class.
SplitLine <in_features> <out_feature_class>

All input feature classes and/or feature layers must be line geometry. Splits each line feature at every vertex for the newly created feature class. The output feature class can be a much larger le, since all the new features have been created. This will depend on how many vertices are in the input feature class.

Fields toolset

Data Management toolbox

52

Contains tools to add and make changes to the elds in the tables of a feature class. Add Field: Adds a eld to the table of a feature class, layer, or raster catalog.
AddField <in_table> <eld_name> <LONG | TEXT | FLOAT | DOUBLE | SHORT | DATE | BLOB | RASTER> {eld_precision} {eld_scale} {eld_length} {eld_alias} {NULLABLE | NON_NULLABLE} {NON_REQUIRED | REQUIRED} {eld_domain}

A eld of type raster allows you to have a raster image as an attribute. It is stored within or alongside the geodatabase. This is helpful when a picture is the best way to describe a feature. Precision, scale, and length cannot be set for elds of type raster. Coverages, stand-alone tables, feature classes from ArcSDE and personal or le geodatabases, layer les, raster catalogs, and shapeles will work as valid input for this command. VPF and CAD feature data overlays will not work, since they are read-only formats that are not native to ArcGIS. The added eld will always be displayed at the end of the table. The Field Length parameter is only applicable on elds of type text or BLOB. For coverages, shapeles, and dBASE tables, if eld type denes a character, blanks are inserted for each record. If eld type denes a numeric item, zeros are inserted for each record. For geodatabases, if eld type denes a character or number, <null> is inserted into each record if the FieldIsNullible parameter default is accepted. A shapele does not support alias for elds, so you cannot add a eld alias to a shapele.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Assign Default to Field: Creates a default value for a specied eld and automatically applies a userdetermined value to a certain eld for every row added to the table or feature class.
AssignDefaultToField <in_table> <eld_name> <default_value> {subtype_code; subtype_code...}

The default value is dependent on the eld type chosen in the Field Name parameter. If you pick a eld that is type LONG, the default value has to be type LONG too. For example, a valid number would be anything less than 10 numeric characters. A eld in the feature class or table must be assigned as the subtype eld before new subtypes can be added. This is done using the Set Subtype Field tool. Calculate End Date: Populates the values for a specied end date eld with values calculated using the start date eld specied.
CalculateEndDate <input_table> <unique_ID_elds;unique_ID_elds...> <start_date_eld> <end_date_eld>

The value for the last row of the end date eld will be the same as the value set for the last row of the start date eld. This tool is useful when the intervals between start date eld values are not regular and you want to animate the feature class or table through time or some other value using the Animation toolbar. To use this tool, the start date eld must be able to be sorted in ascending order. To test this, open the attribute table for the feature class, right-click the eld, and click Sort Ascending. If the eld cannot be sorted in ascending order, the eld must be reformatted before using this tool. Calculate Field: Calculates the values of a eld for a feature class, feature layer, or raster catalog using an expression.
CalculateField <in_table> <eld> <expression> {VB | PYTHON} {code_block}

Calculate Field computes and assigns a value to the specied eld of the Input table. The calculation can only be applied to one eld per operation.

Data Management toolbox

Delete Field: Deletes one or more elds from a table of a feature class, feature layer, or raster catalog.
DeleteField <in_table> <drop_eld;drop_eld...>

Delete Field can be used with any table; ArcSDE, le, or personal geodatabase feature class; coverage; raster catalog; or shapele. You cannot delete elds from nonnative data formats in ArcGIS, such as VPF and CAD datasets, because they are read-only les. Transpose Time Fields: Shifts elds that have time as a eld name and their values from columns to rows in a table or feature class.
TransposeTimeFields <input_feature_class_or_table> <elds_to_transpose;elds_to_ transpose...> <output_feature_class_or_table> <time_eld_name> <value_eld_name> {attribute_elds;attribute_elds...}

If you want the output to be a table, you need to specify the input as a table.
53

 Shapele is not a supported format for an output feature class. The output must be a geodatabase feature class. Object ID (such as OID, FID, and so on) and shape elds should not be set as attribute elds.

File Geodatabase toolset

Contains tools that convert individual le geodatabase vector feature classes and tables into a compressed format. Compress File Geodatabase Data: Converts a le geodatabase feature class from standard to compressed format.
CompressFileGeodatabaseData <in_data>

Once compressed, a feature class or table is read-only and cannot be edited or modied in any way, except for changing its name and modifying attribute indexes and metadata. Compression is ideally suited to mature datasets that do not require further editing. However, if required, a compressed dataset can always be uncompressed to return it to its original, read-write format. You can compress a geodatabase, feature dataset, stand-alone feature class, or table. When you compress a geodatabase, all feature classes and tables within it compress. When you compress a feature dataset, all its feature classes compress. You cannot individually compress or uncompress a feature class in a feature dataset to produce a mixed state where some feature classes are compressed and others are not. Uncompress File Geodatabase Data: Converts a le geodatabase feature class or table from compressed to standard format.
UncompressFileGeodatabaseData <in_data> {conguration_keyword}

Data Management toolbox

54

You can uncompress a geodatabase, feature dataset, stand-alone feature class, or table. When you uncompress a geodatabase, all feature classes and tables within it uncompress. When you uncompress a feature dataset, all its feature classes uncompress. You cannot individually compress or uncompress a feature class in a feature dataset to produce a mixed state where some feature classes are compressed and others are not. Compressed feature datasets allow you to add an uncompressed feature class to the feature dataset through operations such as creating a new, empty feature class; copying and pasting; and importing. However, once youve nished adding feature classes, you should recompress or uncompress the feature dataset so that all its feature classes are either compressed or uncompressed.

General toolset

Contains tools allowing for aggregation of features and provides simple semantic changes. Append: Combines multiple input datasets into an already existing target dataset.
Append <inputs;inputs...> <target> {TEST | NO_TEST} {eld_mapping}

Input datasets can be point, line, or polygon feature classes, tables, rasters, or raster catalogs. Use Append when you want to combine two or more adjacent layers into one large layer that contains all their features. All input features must be of the same feature type (all area features, all line, or all point).
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Calculate Value: Returns a value based on a user-specied Python expression.

CalculateValue <expression> {code_block}

The ArcGIS.Rand() function is supported by the Calculate Value tool. The ArcGIS.Rand() function has been created for ArcGIS tools and should not be confused with the Python Rand() function. Expressions can be created in a standard Python format. Copy: Copies feature datasets, feature classes, or tables and pastes them to another location.
Copy <in_data> <out_data> {data_type}

The Copy tool copies data from one location and name to a new location and name. The input and output of Copy will be the same data type. Therefore, if the input type is a shapele, the output type will also be shapele. Be sure the output workspace supports the output data type. For example, do not try to copy a shapele into a geodatabase. Delete: Deletes feature datasets, feature classes, rasters, or tables.
Delete <in_data> {data_type}

The data to be deleted should not be open anywhere on the operating system; that is, no other user should have the le open. For example, a feature class cannot be deleted if it is open in ArcMap. When deleting items with the Delete tool, ancillary les associated with the item are also deleted. For example the metadata, projection, and index les that may accompany a shapele will be deleted if the shapele is deleted. Merge: Combines input features from multiple input sources (of the same data type) into a single, new, output feature class.
Merge <inputs; inputs...> <output> {eld_mappings}

Data Management toolbox

Use Merge when there are features from multiple input sources that need to be combined into one feature class. Input data sources need not be adjacent; overlap is allowed. The type of input data, such as polygons or tables, must be the same for all inputs. A single output eld can be generated from multiple input elds. This happens if more than one input feature class or table contains a eld of the same name, or it can happen if a new eld is created and the contents of the output eld are generated from multiple (differently named) user-selected elds. Merge identies elds based on their name, not on their data type. Input elds are identied by their name and grouped into an output eld of the same name. The data type of an output eld will default to the data type of the rst input eld (of that name) it encounters. The data type may be changed manually at any time to any valid data type. All valid data types will be listed if the tools dialog box is used. Merge Branch: Merges two or more logical branches into a single output.
MergeBranch {in_values;in_values...}

This tool is intended for use only in ModelBuilder. The tool looks at the list of inputs variables and returns the rst variable that is in the has been run state.
55

 This tool outputs a variant that can be used as the feedback variable to any other input data element in the model. Rename: Changes the name of data, such as feature datasets, feature classes, rasters, tables, or toolboxes.
Rename <in_data> <out_data> {data_type}

The output name cannot already exist. The data to be renamed should not be open anywhere on the operating system; that is, no other user should be accessing the data. For example, a feature class cannot be renamed if it is open in ArcMap. When renaming items with the Rename tool, ancillary les associated with the item are also renamed. For example, the metadata, projection, and index les that may accompany a shapele will also be renamed. Select Data: Selects any data type on disk as input.
SelectData <in_data_element> <out_data_element>

The Select Data tool is intended for use only in ModelBuilder, not at the command line. Selecting the child from the parent using this tool enables you to continue processing after performing a task where the output data is a container, such as a feature dataset, and the next tool in the model requires a feature class.

Generalization toolset

Contains tools to derive data with less detail and complexity from a dataset. Aggregate Polygons: Combines disjoint and adjacent polygons into new area features based on a distance.
AggregatePolygons <in_features> <out_feature_class> <aggregation_distance> {minimum_area} {minimum_hole_size} {NON_ORTHOGONAL | ORTHOGONAL}

Data Management toolbox

The aggregation will only happen where two polygon boundaries are within the specied aggregation distance to each other. There will be no self-aggregation, meaning no aggregation within a polygon itself where one area of its boundary is less than the distance to another or between two parts of a multipart polygon. The output feature class will not contain any geographic attributes from the source features. A oneto-many relationship table with the name of output_feature_class_Tbl will be created that links the aggregated polygons to their source polygons. This table will contain two elds, OUTPUT_FID and INPUT_FID, which hold the aggregated object IDs and their input object IDs, respectively. With this link, you can derive necessary attributes for the output features using other geoprocessing tools. The link can become incorrect when either the input or output polygons are modied. The output may contain overlapping polygons and self-crossing boundaries and some connecting zones may be too narrow; therefore, further inspection and editing may be needed.
56

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Collapse Dual Lines to Centerline: Derives centerlines (single lines) from dual-line features, such as road casings, based on specied width tolerances.
CollapseDualLinesToCenterline <in_features> <out_feature_class> <maximum_width> {minimum_width}

This tool is designed to work with fairly regular, near parallel pairs of lines, such as road casings. Centerlines will be created only between open-ended lines, not inside closed lines, which are likely street blocks. Centerlines will be derived based on the specied width parameters. A dual-line feature wider than the maximum width or narrower than the minimum width will not be centerlined. Use known road widths if available. However, since casings usually become wider at intersections, set the maximum width slightly greater than the known maximum width. You may need to experiment to nd suitable parameters. Since the tool is not designed for natural features, such as irregularly shaped rivers, you may get unexpected results if you apply it to such features. Dissolve: Aggregates features based on one or more specied attributes.
Dissolve <in_features> <out_feature_class> {dissolve_eld;dissolve_eld...} {eld{Statistics_Type}; eld{Statistics_Type}...} {MULTI_PART | SINGLE_PART}

Data Management toolbox

The attributes of the aggregated features may be summarized using a statistic type. For example, when aggregating sale territories, the revenue for each feature within a territory could be summed to obtain the total sales revenue for that territory (revenue sum). The statistic type used to summarize attributes is added to the output feature class as a single eld: statistic_eld. Eliminate: Merges the selected polygons with neighboring polygons with the largest shared border or the largest area.
Eliminate <in_features> <out_feature_class> {LENGTH | AREA}

Features to be eliminated are determined by a selected feature set applied to a polygon layer. The selected set must be determined in a previous step by using Select Layer by Attribute, using Select Layer by Location, or querying a map layer in ArcMap.
57

 Only the selected set of polygons from a temporary feature layer will be eliminated. Simplify Building: Simplies the boundary or footprint of building polygons while maintaining their essential shape and size.
SimplifyBuilding <in_features> <out_feature_class> <simplication_tolerance> {minimum_area} {NO_CHECK | CHECK_CONFLICTS}

The output feature class will carry all the input elds. Simplify Line: Removes small uctuations or extraneous bends from a line in a feature class while preserving its essential shape.
SimplifyLine <in_features> <out_feature_class> <POINT_REMOVE | BEND_SIMPLIFY> <tolerance> {NO_CHECK | PRESERVE_SHARED | RESOLVE_ERRORS} {KEEP_COLLAPSED_POINTS | NO_KEEP}

Data Management toolbox

58

The tool will produce two output feature classes, a line feature class, and a point feature class. The line output will store all the simplied lines, and the point output will store points, if any, representing closed lines that are collapsed to zero length as the result of simplication and cannot be written to the line output. The line output will carry all the input elds. The point output will not. Simplify Polygon: Simplies a polygon by removing small uctuations or extraneous bends from its boundary while preserving its essential shape.
SimplifyLine <in_features> <out_feature_class> <POINT_REMOVE | BEND_SIMPLIFY> <tolerance> {minimum_area} {NO_CHECK | PRESERVE_SHARED | RESOLVE_ERRORS} {KEEP_COLLAPSED_POINTS | NO_KEEP}

The tool will produce two output feature classes, a polygon feature class, and a point feature class. The polygon output will carry all the input elds. The point output will not.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Smooth Line: Smoothes a line to improve its aesthetic or cartographic quality.

SmoothLine <in_features> <out_feature_class> <PAEK | BEZIER_INTERPOLATION> <tolerance> {FIXED_CLOSED_ENDPOINT | NO_FIXED} {NO_CHECK | FLAG_ERRORS}

The Polynomial Approximation with Exponential Kernel (PAEK) algorithm produces smoothed lines; each may have more vertices than its source line. The tolerance you specify is the length of a moving path used in calculating the new vertices. The longer the length, the more smoothed the line. A small tolerance will result in a long processing time, so begin with a relatively large tolerance and a small number of lines. The Bezier Interpolation algorithm does not require any tolerance. If you are using the command line or scripting, you still need to type zero in place of the smooth_tolerance.

Indexes toolset

Contains tools to create, alter, and remove indexes. Add Attribute Index: Adds an index to an existing table, feature class, shapele, coverage, or attributed relationship class.
AddIndex <in_table> <elds;elds...> {index_name} {NON_UNIQUE | UNIQUE} {NON_ASCENDING | ASCENDING}

An attribute index can improve the performance of queries against your data. Attribute indexes are used with tables and feature classes, whereas spatial indexes are used with graphical queries of spatial features within feature classes. Add Spatial Index: Creates a new spatial index for a shapele, le geodatabase feature class, or an ArcSDE feature class.
AddSpatialIndex <in_features> {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

Data Management toolbox

This command will only work with shapeles, feature classes in an ArcSDE geodatabase, or feature classes in a le geodatabase. The spatial index cannot be added to a personal geodatabase because it needs the existing index to maintain its integrity. When you create a new feature class in a personal geodatabase, you can specify a spatial index or accept the default spatial index. Indexed items speed up selection and relate operations. A load-only mode disables spatial index management until loading is completed. An attribute index cannot be added to a versioned feature class. Remove Attribute Index: Deletes an index from an existing table, feature class, shapele, coverage, or attributed relationship class.
RemoveIndex <in_table> <index_name;index_name...>

Attribute indexes are used with tables and feature classes, whereas spatial indexes are used with graphical queries of spatial features within feature classes. Indexed items speed up ArcInfo Selection and Relate operations.
59

Remove Spatial Index: Deletes the spatial index for a shapele, le geodatabase feature class, or ArcSDE feature class.
RemoveSpatialIndex <in_features>

The spatial index can only be deleted from an ArcSDE feature class that is not versioned. An ArcSDE geodatabase has up to three spatial indexes. They are all subindexes of the parent index, so if you remove the spatial index, all subindexes will be removed. The spatial index cannot be deleted from a personal geodatabase, because it needs the index to maintain its integrity.

Joins toolset

Contains tools to add or remove a table join. Add Join: Links a layer to a table (or a table to a table) based on a common eld.
AddJoin <in_layer_or_view> <in_eld> <join_table> <join_eld> {KEEP_ALL| KEEP_COMMON}

Data Management toolbox

60

The input must be a feature layer or a table view; it cannot be a feature class or table. This tool is not limited to ArcMap; it works on layers and table views in ArcCatalog and in scripts. The Make Feature Layer tool makes a layer for a feature class, and the Make Table View creates a table view from an input table or feature class. The join table can be any of the following types of tables: a geodatabase table (ArcSDE, le or personal), a dBASE le, an INFO table, or an OLE DB table. Indexing the elds in the input layer or table view and join table on which the join will be based can improve performance. This can be done with the Add Attribute Index tool or by right-clicking the input in ArcCatalog and using the dialog box to add an index to the desired eld. Remove Join: Removes a join from a feature layer or table view.
RemoveJoin <in_layer_or_view> <join_name>

The join name is the name of the table that was joined to the input layer or table view. When a layer is joined to two tables and the rst join is removed, then both joins will be removed. For example, Layer1 is joined to TableA. Then Layer1 is joined to TableB. If the join to TableA is removed, the join to TableB is also removed.

Layers and Table Views toolset

Contains tools for creating and manipulating layers, layer les, and table views. Make Feature Layer: Creates a temporary feature layer from an input feature class or layer le.
MakeFeatureLayer <in_features> <out_layer> {where_clause} {workspace} {eld_info}

The feature layer can be used as input to any geoprocessing tool that accepts a feature class as input. The tool does not accept data from le geodatabases.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The temporary feature layer can be saved as a layer le using the Save To Layer File tool or saved as a new feature class using the Copy Features tool. If a SQL expression is used but returns nothing, the output feature layer will be empty. Make Query Table: Represents the results of a SQL query to a database in a layer or table view.
MakeQueryTable <in_table;in_table...> <out_table> {USE_KEY_FIELDS | ADD_VIRTUAL_KEY_ FIELD | NO_KEY_FIELD} {in_key_eld;in_key_eld...} {eld{Alias};eld{Alias}...} {where_clause}

Make Query Table accepts data from an ArcSDE geodatabase, a personal geodatabase, or an OLE DB connection. All input feature classes or tables must be from the same input workspace. If a Shape column is added to the eld list, the result is a layer; otherwise, it is a table view. Make Raster Catalog Layer: Makes a temporary raster catalog layer that will be available to select as a variable while working in the same ArcMap or ArcCatalog session.
MakeRasterCatalogLayer <in_raster_catalog> <layer_name> {where_clause} {workspace} {eld_info}

To make your layer permanent, right-click the layer in the ArcMap table of contents and click Save As Layer File or use the Save To Layer File tool. Make Raster Layer: Makes a temporary raster dataset layer that will be available to select as a variable while working in the same ArcMap or ArcCatalog session.
MakeRasterLayer <in_raster> <out_raster_layer> {where_clause} {envelope}

To make your layer permanent, right-click the layer in the ArcMap table of contents and click Save As Layer File or use the Save To Layer File tool. Make Table View: Creates a temporary table view from an input table or feature class.
MakeTableView <in_table> <out_name> {where_clause} {workspace} {eld_info}

Data Management toolbox

This tool is commonly used to create a table view with a selected set of attributes or elds. ArcCatalog does not display these table views, but they can be used as inputs to other geoprocessing tools in the current ArcGIS session. Once ArcGIS exits, the tables in memory are removed. Table views created in ArcCatalog cannot be used in ArcMap. If a SQL expression is used but returns nothing, the output table view will be empty. Make XY Event Layer: Creates a temporary point layer based on x and y coordinates from a source table.
MakeXYEventLayer <table> <in_x_eld> <in_y_eld> <out_layer> {spatial_reference}

This tool allows you to create a layer based on x and y columns from an input table. If the table is editable, you will be able to edit the layer. However, you wont be able to interactively move a point on the map; you must change the coordinates in the table. Save to Layer File: Creates an output layer le that references geographic data stored on disk.
SaveToLayerFile <in_layer> <out_layer>

The input layer can be an in-memory layer created by the Make Feature Layer tool, a layer le stored on disk, or a feature layer in ArcMap. The feature layer or layer le may have a subset of records and elds.

61

Select Layer by Attribute: Creates, updates, or removes the selection on a layer or table view using an attribute query.
SelectLayerByAttribute <in_layer_or_view> {NEW_SELECTION | ADD_TO_SELECTION | REMOVE_ FROM_SELECTION | SUBSET_SELECTION | SWITCH_SELECTION | CLEAR_SELECTION} {where_clause}

The input must be a feature layer or a table view. It cannot be a feature class or table. This tool is not limited to working in ArcMap; it works on layers and table views in ArcCatalog and in scripts. The Make Feature Layer tool makes a layer for a feature class, and the Make Table View tool does the equivalent for a table. If an extent or a denition query is present on the input layer or table view, only those features or rows that match the extent and/or denition query will be available to be selected. Select Layer by Location: Creates, updates, or removes a selection on the input layer based on spatial relationships to select features.
SelectLayerByLocation <in_layer> {INTERSECT | WITHIN_A_DISTANCE | COMPLETELY_CONTAINS | COMPLETELY_WITHIN | HAVE_THEIR_CENTER_IN | SHARE_A_LINE_SEGMENT_WITH | BOUNDARY_TOUCHES | ARE_IDENTICAL_TO | CROSSED_BY_THE_OUTLINE_OF | CONTAINS | CONTAINED_BY} {select_ features} {search_distance} {NEW_SELECTION | ADD_TO_SELECTION | REMOVE_FROM_SELECTION | SUBSET_SELECTION | SWITCH_SELECTION}

The input must be a feature layer or a table view. It cannot be a feature class or table. This tool is not limited to working in ArcMap; it works on layers and table views in ArcCatalog and in scripts. The Make Feature Layer tool makes a layer for a feature class, and the Make Table View tool does the equivalent for a table. If an extent or a denition query is present on the input layer or table view, only those features or rows that match the extent and/or denition query will be available to be selected.

Projections and Transformations toolset

Contains tools to set the projection as well as reproject or transform a dataset.

Data Management toolbox

62

Create Custom Geographic Transformation: Creates a transformation method for converting data between two geographic coordinate systems or datums.
CreateCustomGeoTransformation <geo_transformation_name> <in_coordinate_system> <out_coordinate_system> <custom_geo_transformation>

The output of this tool can be used as a transformation method for any tool with a parameter that requires such a method. All custom geographic transformation les are saved with a .gtf extension. Custom transformation les cant be edited. To update the le you must create a new custom geographic transformation and overwrite the existing le. Any geoprocessing tool that uses geographic transformations will look at all custom transformations in the default storage location and present them as valid transformation options on the dialog box (for example, the Project tool). Dene Projection: Records the coordinate system information for the specied input dataset or feature class including any associated projection parameters, datum, and spheroid.
DeneProjection <in_dataset> <coordinate_system>

This command can be used if the input dataset or feature class does not have a projection dened. If the input dataset or feature class has a projection dened, a warning will be raised but the tool will execute successfully. The coordinate system information of the input is created or modied by this tool. No separate output feature class will be created.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Feature (Projections and Transformations) toolset

Contains tools to convert a geographic dataset from one coordinate system to another. Batch Project: Changes the coordinate system of your input feature classes or feature datasets, including the datum or spheroid, and denes the location of points on a planar surface.
BatchProject <input_feature_class_or_dataset; input_feature_class_or_dataset...> <output_workspace> {output_coordinate_system} {template_dataset} {transformation}

This tool will not work with layers as input. All input feature classes and/or feature datasets are valid inputs to this tool. If you have a feature class that does not have a dened projection and .prj le, then use the Dene Project tool. The name of the output feature classes will be based on the name of the input feature class. For instance, if the input is c:\myworkspace\gondor.shp, the output feature class will be named gondor. If the name already exists in the output workspace, a number will be appended to the end to make it unique (for example, _1). Create Spatial Reference: Creates a spatial reference object for use in ModelBuilder and scripting.
CreateSpatialReference {spatial_reference} {spatial_reference_template} {xy_domain} {z_domain} {m_domain} {template;template...} {expand_ratio}

Setting the spatial reference sets the coordinate system, spatial domains, and precision. The spatial domains and precision of the output spatial reference can be further modied using XY Domain, Z Domain, M Domain, Template XYDomains, and Grow XYDomain By Percentage. Template XYDomains does not have to be in the same coordinate system as that specied in Spatial Reference or Spatial Reference Template. If they are different, the extents will be projected to match. Project: changes the coordinate system of your input dataset or feature class to a new output dataset or feature class with the newly dened coordinate system, including the datum and spheroid.
Project <in_dataset> <out_dataset> <out_coordinate_system> {transform_method; transform_method...} {in_coordinate_system}

Data Management toolbox

All input feature classes and/or feature layers are valid inputs to this tool. If you have a feature class that does not have a dened projection and PRJ le, then use the Dene Project tool rst.

Raster (Projections and Transformations) toolset

Contains tools to set the projection, reproject, reorient, or relocate a raster dataset. Flip: Reorients the raster by turning it over, from top to bottom, along the horizontal axis through the center of the raster.
Flip <in_raster> <out_raster>

63

 Flip ips the grid from top to bottom along the horizontal axis through the center of the region. This may be useful to correct raster datasets that are upside down. Mirror: Reorients the raster by ipping it, from left to right, along the vertical axis through the center of the raster.
Mirror <in_raster> <out_raster>

Mirror ips the raster from left to right along the vertical axis through the center of the region. Project Raster: Transforms a raster dataset from one projection to another.
ProjectRaster <in_raster> <out_raster> <out_coorinate_system> {NEAREST | BILINEAR | CUBIC} {cell_size} {geographic_transform;geographic_transform...} {registration_point} {in_coordinate_system}

The coordinate system denes how your raster data is projected. The NEAREST option, which performs a nearest neighbor assignment, is the fastest of the three interpolation methods. It is primarily used for categorical data, such as a land-use classication, because it will not change the cell values. Do not use NEAREST for continuous data, such as elevation surfaces. The BILINEAR option, bilinear interpolation, determines the new value of a cell based on a weighted distance average of surrounding cells. The CUBIC option, cubic convolution, determines the new cell value by tting a smooth curve through the surrounding points. These are most appropriate for continuous data and may cause some smoothing; also, cubic convolution may result in the output raster containing values outside the range of the input raster. It is not recommended that BILINEAR or CUBIC be used with categorical data because the cell values may be altered.

Data Management toolbox

64

Rescale: Scales a raster by the specied x and y scale factors.

Rescale <in_raster> <out_raster> <x_scale> <y_scale>

The scale factor must be a positive number. A scale factor greater than one means the image will be rescaled to a larger dimension, resulting in a larger extent because of a larger cell size. A scale factor less than one means the image will be rescaled to a smaller dimension, resulting in a smaller extent because of a smaller cell size. Rotate: Turns the raster around the specied pivot point by angle specied in degrees.
Rotate <in_raster> <out_raster> <angle> {pivot_point} {NEAREST | BILINEAR | CUBIC}

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 Rotation is, by default, around the lower left corner of the raster. The rotation point can be changed with the optional Pivot Point parameter. Resampling is only done if the angle is not a multiple of 90. The rotation angle specied must be between 0 and 360. Shift: Slides the raster to a new geographic location based on x and y shift values.
Shift <in_raster> <out_raster> <x_value> <y_value> {in_snap_raster}

This tool is helpful if your raster dataset needs to be shifted to align with another data le. The cell size of the output raster will be the same as that of the input raster. The number of rows and columns in the output raster will be the same as those of the input raster, no matter what parameters are specied. The coordinates of the lower left corner of the output raster will be offset from the input raster by the x and y shift coordinate values specied. Shift does not perform any resampling or warping. Warp: Transforms or rubber sheets a raster dataset along a set of links using a polynomial transformation.
Warp <in_raster> <source_control_points;source_control_points...> <target_control_ points;target_control_points...> <out_raster> {POLYORDER1 | POLYORDER2 | POLYORDER3 | ADJUST | SPLINE} {NEAREST | BILINEAR | CUBIC}

Data Management toolbox

The default polynomial order (1) will perform an afne transformation. Warp is useful when the raster requires a systematic geometric correction that can be modeled with a polynomial. A spatial transformation can invert or remove a distortion by using polynomial transformation of the proper order. The higher the order, the more complex the distortion that can be corrected. The higher orders of polynomial will involve progressively more processing time. To determine the minimum number of links necessary for a given order of polynomial, use the following formula:
n = (p + 1) (p + 2) / 2

where n is the minimum number of links required for a transformation of polynomial order p. It is strongly suggested you use more than the minimum number of links.

65

Raster toolset

Contains tools to create and manage raster datasets and raster catalogs. Add Colormap: Allows you to add a color map to a raster dataset, if it does not already exist.
AddColormap <in_raster> <in_template_raster>

This tool allows you to either create or edit a color map table for a raster dataset. The color map, from a raster dataset, that already exists will be applied to the input raster dataset. Batch Build Pyramids: Allows you to build pyramids on multiple raster datasets.
BatchBuildPyramids <input_raster_datasets;input_raster_datasets...>

Building pyramids for a raster dataset will improve the display performance of large raster datasets. Pyramids can only be built for raster datasets that do not have internal pyramids. Pyramids cannot be built for raster catalogs, but they can be built for each raster catalog member. Batch Calculate Statistics: Allows you to calculate statistics on multiple raster datasets.
BatchCalculateStatistics <input_raster_datasets;input_raster_datasets...> {number_of_columns_to_skip} {number_of_rows_to_skip} {ignore_values;ignore_values...}

The input raster datasets can be any valid raster dataset that ArcGIS recognizes. This tool can calculate statistics in a batch process. Calculating statistics for a raster is required for rendering your raster dataset with any sort of contrast stretch. Build Pyramids: Builds raster pyramids for a raster dataset.
BuildPyramids <in_raster_dataset>

Data Management toolbox

66

Building pyramids for raster datasets will help improve the display speed. You only need to build pyramids once per dataset, then the pyramids can be accessed every time you display that raster dataset. Build Raster Attribute Table: Adds a raster attribute table to a raster dataset or updates an existing one.
BuildRasterAttributeTable <in_raster> {NONE | OVERWRITE}

If you want to delete an existing table and create a new one, check the overwrite check box. A new raster attribute table will be created. If you have an existing table and you do not specify OVERWRITE, the table will be updated. No elds will be deleted, but the values in the table will be up to date. Calculate Statistics: Calculates statistics for a raster dataset.
CalculateStatistics <in_raster_dataset> {x_skip_factor} {y_skip_fator} {ignore_values; ignore_values...}

Calculating statistics for a raster is required for rendering your raster dataset with any sort of contrast stretch.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 A skip factor is the parameter that controls the portion of the raster dataset used when calculating the statistics. The input value indicates the horizontal or vertical skip factor, where a factor of 1 will use each pixel and a value of 2 will use every second pixel. The skip factor can only range from one to the number of columns/rows. The ignore value allows you to exclude a specic value from the calculation of statistics. You may want to ignore a value if it is a NoData value or if it will skew your calculation. Clip: Creates a rectangular spatial subset of a raster dataset.
Clip <in_raster> <rectangle> <out_raster> {in_template_raster}

The Clip tool allows you to extract a portion of a raster dataset based on a rectangular extent. The minimum and maximum x and y extents allow you to dene the clip extents for your output raster dataset. The extent values must be in the same spatial coordinates and units as the raster dataset. Composite Bands: Creates a single raster dataset of multiple bands from multiple single-band raster datasets.
CompositeBands <in_rasters;in_rasters...> <out_raster>

Data Management toolbox

The output raster dataset takes the cell size from the rst raster band in the list. By default, the output raster dataset takes the extent and the spatial reference of the rst raster band with a spatial reference in the list. You can change this by setting Output Extent and Output Coordinate System in the Environment Settings. Copy Raster: Converts a raster to a BMP, GIF, GRID, IMG, JPEG, JPEG2000, PNG, TIFF, or a geodatabase raster dataset and can be used to load raster datasets into a raster catalog.
CopyRaster <in_raster> <out_raster_dataset> {conguration_keyword} {background_value} {nodata_value} {NONE | ONEBITTO8BIT} {NONE | COLORMAPTORGB} {1_BIT | 2_BIT | 4_BIT | 8_BIT_UNSIGNED | 8_BIT_SIGNED | 16_BIT_UNSIGNED | 16_BIT_SIGNED | 32_BIT_UNSIGNED | 32_BIT_SIGNED | 32_BIT_FLOAT | 64_BIT}

If you want to load raster datasets into a raster catalog, you will need to type out the full pathname of the raster catalog as the output location or drag and drop the raster catalog to the output location.

67

Copy Raster Catalog Items: Makes a copy of a raster catalog including all its contents or a subset of its contents if there is a selection.
CopyRasterCatalogItems <in_raster_catalog> <out_raster_catalog> {conguration_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

The input and output of this tool comprise a geodatabase raster catalog. If your raster catalog output is to an ArcSDE geodatabase, a conguration keyword can be set. File and personal geodatabases may have one spatial grid. ArcSDE geodatabases can have up to three spatial grids. Create Ortho-Corrected Raster Dataset: Create an orthorectied raster dataset using the rational polynomial coefcients (RPC) associated with a raster dataset.
CreateOrthoCorrectedRasterDataset <in_raster> <out_raster_dataset> <CONSTANT ELEVATION | DEM> <CONSTANT_ ELEVATION> <in_DEM_raster> {ZFactor} {ZOffset} {NONE | GEOID}

To orthocorrect a raster dataset, the raster must have RPCs associated with it. A DEM can be used in the orthophoto rectication process so that the elevation and curvatures of the earth can be taken into account. If a DEM is used to orthocorrect the raster dataset, the constant elevation value will not be used. Create Pan-Sharpened Raster Dataset: Fuses a high-resolution panchromatic raster dataset with a lower resolution raster dataset to create an RGB raster with the resolution of the panchromatic raster.
CreatePansharpenedRasterDataset <in_raster> <red_channel> <green_channel> <blue_channel> {infrared_channel} <out_raster_dataset> <in_panchromatic_image> <ESRI | IHS | Brovey | SIMPLE MEAN> {red_weight} {green_weight} {blue_weight} {infrared_weight}

Only the areas that fully overlap will be affected by this tool. IHS uses intensity, hue, and saturation color space for data fusion. Brovey uses an algorithm based on spectral modeling for data fusion.

Data Management toolbox

68

Create Random Raster: Creates a random raster based on a user-specied distribution and extent.
CreateRandomRaster <out_path> <out_name> <distribution> <raster_extent> <cellsize>

The uniform, integer, normal, and exponential distribution processing times are independent to their arguments while the poisson, gamma, binomial, geometric, and pascal distribution processing times can vary considerably when arguments are changed. Create Raster Catalog: Creates an empty raster catalog in a geodatabase.
CreateRasterCatalog <out_path> <out_name> {raster_spatial_reference} {spatial_reference} {conguration_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3} {MANAGED | UNMANAGED} {template_raster_catalog;template_raster_catalog...}

Raster datasets within raster catalogs in a geodatabase can either be managed or not managed by the geodatabase. Having the raster catalog managed by the geodatabase means that the raster datasets will be stored within the personal geodatabase. When a row is deleted from the catalog, it is deleted from the geodatabase. When you do not have your raster managed by the geodatabase, there will only be a pointer connecting the raster catalog row to the raster dataset. Raster catalogs stored in ArcSDE are always managed. When creating a raster catalog in an ArcSDE geodatabase, the raster dataset name cannot have spaces. You can use underscores to separate words.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Create Raster Dataset: Creates an empty raster dataset in a geodatabase.

CreateRasterDataset <out_path> <out_name> {cellsize} {8_BIT_UNSIGNED | 1_BIT | 2_BIT | 4_BIT | 8_BIT_SIGNED | 16_BIT_UNSIGNED | 16_BIT_SIGNED | 32_BIT_UNSIGNED | 32_BIT_SIGNED | 32_BIT_FLOAT | 64_BIT} {raster_spatial_reference} {number_of_bands} {conguration_ keyword} {pryamids} {tile_size} {compression} {pyramid_origin}

It is best to choose to build pyramids, because pyramids can speed up the display of raster data since the server or computer returns only the data at a specied resolution that is required for the display. Delete Colormap: Removes a color map that is associated with a raster dataset.
DeleteColormap <in_raster>

Delete Raster Attribute Table: Removes the raster attribute table that is associated with a raster dataset.
DeleteRasterAttributeTable <in_raster>

The input raster dataset can only have a single band. Delete Raster Catalog Items: Deletes the raster catalogs contained in a raster catalog.
DeleteRasterCatalogItems <in_raster_catalog>

Only geodatabase raster catalogs are valid inputs. Get Raster Properties: Returns the properties of a raster.
GetRasterProperties <in_raster> {MINIMUM | MAXIMUM | MEAN | STD | UNIQUEVALUECOUNT | TOP | LEFT | RIGHT | BOTTOM | CELLSIZEX | CELLSIZEY | VALUETYPE | COLUMNCOUNT | ROWCOUNT | BANDCOUNT}

The property returned by the tool will be displayed in the geoprocessing window. Mosaic: Mosaics multiple rasters into a single raster.
Mosaic <inputs;inputs...> <target> {LAST |FIRST | BLEND | MEAN | MINIMUM | MAXIMUM} {FIRST | REJECT | LAST | MATCH} {background_value} {nodata_value} {NONE | ONEBITTO8BIT} {mosaicking_tolerance}

Data Management toolbox

69

Mosaic is useful when a set of adjacent rasters needs to be merged into one entity and also when minimizing the abrupt changes along the boundaries of the overlapping rasters. For mosaicking of discrete data, the First, Minimum, or Maximum options will give the most meaningful results. The Blend and Mean options are best suited for continuous data. For oating-point input raster datasets of different resolutions, it is recommended you resample all the data using bilinear interpolation or cubic convolution before running Mosaic. Otherwise, Mosaic will automatically resample the rasters using nearest neighbor (which is not appropriate for the continuous type of data).

Mosaic to New Raster: Mosaics multiple rasters into a new, single raster dataset.
MosaicToNewRaster <input_rasters;input_rasters...> <output_location> <raster_dataset_ name_with_extension> {coordinate_system_for_the_raster} {8_BIT_UNSIGNED | 1_BIT | 2_BIT | 4_BIT | 8_BIT_SIGNED | 16_BIT_UNSIGNED | 16_BIT_SIGNED | 32_BIT_UNSIGNED | 32_BIT_ SIGNED | 32_BIT_FLOAT | 64_BIT} {cell_size} <number_of_bands> {FIRST | LAST | BLEND | MEAN | MINIMUM | MAXIMUM} {FIRST | REJECT | LAST | MATCH}

The input rasters are all the raster datasets you would like to mosaic together. The inputs must have the same number of bands; otherwise, the Mosaic tool used in the model will not run. Resample: Changes the cell size of a grid.
Resample <in_raster> <out_raster> <cell_size> {NEAREST | BILINEAR | CUBIC | MAJORITY}

The lower left corner of the output raster will be the same map space coordinate location as the lower left corner of the input raster. The numbers of rows and columns in the output raster are determined as follows: columns = (xmax - xmin) / cell size rows = (ymax - ymin) / cell size If there is any remainder from the above equations, then rounding of the number of columns and/or rows is performed. The current environment settings of cell size (if one is specied) and extent are applied to the output. The mask is not used.

Data Management toolbox

70

Workspace to Raster Catalog: Loads all the raster datasets that are stored within the same workspace into an existing raster catalog.
WorkspaceToRasterCatalog <in_workspace> <in_raster_catalog> {NONE | INCLUDESUBDIRECTORIES} {NONE | PROJECT_ONFLY}

The raster catalog must already exist for this tool to run. By default, the spatial reference and geotransformation of the raster datasets are persisted in the raster catalog. If you want to project the raster datasets to the spatial reference of the raster column in the raster catalog during loading, choose the Project On-the-y option. Workspace to Raster Dataset: Creates a raster mosaic from all the raster datasets that are stored within the same workspace.
WorkspacetoRasterDataset <in_workspace> <in_raster_dataset> {NONE | INCLUDE_ SUBDIRECTORIES} {LAST | FIRST | BLEND | MEAN | MINIMUM | MAXIMUM} {FIRST | REJECT | LAST | MATCH} {background_value} {nodata_value} {NONE | ONEBITTO8BIT} {mosaicking_tolerance}

The target raster dataset must already exist for the tool to run. If a raster does not already exist, use the Create Raster Dataset tool to create a new raster dataset. All raster datasets within the specied workspace will be mosaicked into the target raster dataset. Since mosaicking will take place, you will need to specify the mosaic method and color map mode to use.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Relationship Classes toolset

Contains tools to create associations between feature classes as well as feature classes and tables. Create Relationship Class: Creates a relationship class to store an association between elds or features in the origin table and the destination table.
CreateRelationshipClass <origin_table> <destination_table> <out_relationship_class> <SIMPLE | COMPOSITE> <forward_label> <backward_label> <NONE | FORWARD | BACKWARD | BOTH> <ONE_TO_ONE | ONE_TO_MANY | MANY_TO_MANY> <NONE | ATTRIBUTED> <origin_primary_key> <origin_foreign_key> {destination_primary_key} {<destination_foreign_key}

Relationships can exist between spatial objects (features in feature classes), nonspatial objects (rows in a table), or spatial and nonspatial objects. Once created, a relationship class cannot be modied; you can only add, delete, or rene its rules. Relationship classes can be deleted and renamed using ArcCatalog in the same manner as any other object in the database. Table To Relationship Class: Creates an attributed relationship class from the origin, destination, and relationship tables.
TableToRelationshipClass <origin_table> <destination_table> <out_relationship_class> <SIMPLE | COMPOSITE> <forward_label> <backward_label> <NONE | FORWARD | BACKWARD | BOTH> <ONE_TO_ONE | ONE_TO_MANY | MANY_TO_MANY> <relationship_table> <attribute_ elds;attribute_elds...> <origin_primary_key> <origin_foreign_key> <destination_ primary_key> <destination_foreign_key>

Relationships can exist between spatial objects (features in feature classes), nonspatial objects (rows in a table), or spatial and nonspatial objects. Once created, a relationship class cannot be modied; you can only add, delete, or rene its rules. Relationship classes can be deleted and renamed using ArcCatalog in the same manner as any other object in the database. Table To Relationship Class creates a table in the database containing the selected attribute elds of the relationship table. These elds are used to store attributes of the relationship itself that are not attributed to either the origin or destination class. For example, in a parcel database, you may have a relationship class between parcels and owners in which owners own parcels and parcels are owned by owners. An attribute of that relationship may be percentage ownership.

Data Management toolbox

Subtypes toolset

Contains tools to manage the subtypes of a feature class or a table. Add Subtype: Adds a new subtype to the subtypes in the input table.
AddSubtype <in_table> <subtype_code> <subtype_description>

If you add a subtype whose code already exists, the new subtype will be ignored. If you need to change the description of an existing subtype, you would rst have to remove the subtype, then add a new subtype with the same code and a new description. Remove Subtype: Deletes a subtype from the input table using its code.
RemoveSubtype <in_table> <subtype_code;subtype_code...>

Subtypes are removed using their integer code. The subtypes of a feature class or table can also be managed in ArcCatalog. Subtypes can be created and modied using the Subtypes Property page on the datasets Properties dialog box.

71

Set Default Subtype: Sets the default subtype value.

SetDefaultSubtype <in_table> <subtype_code>

The input table must contain subtype codes before setting a default code. Use Add Subtype and Set Subtype Field to create subtype codes. Set Subtype Field: Denes the eld in the feature class or table that stores the subtype codes.
SetSubtypeField <in_table> <eld>

A feature class or table can have only one subtype eld. After a subtype eld is set, subtype codes are added to the feature class or table with the Add Subtype function.

Table toolset

Contains tools to help you create and evaluate tabular data from a variety of sources. Analyze: Updates relational database management system (RDBMS) statistics of business tables, feature tables, and delta tables along with the statistics of those tables indexes.
Analyze <in_dataset> <components;components...>

After data loading, deleting, updating, and compressing operations, it is important to update RDBMS statistics in Oracle, Microsoft SQL Server, DB2, or Informix databases. The Analyze function updates the statistics of business tables, feature tables, raster tables, added tables, and deleted tables, along with the statistics on those tables indexes. The components are BUSINESS, FEATURE, RASTER, ADDS, and DELETES. Change Privileges: Establishes or changes user access privileges to the input ArcSDE dataset, standalone feature class, or table.
ChangePrivileges <in_dataset> <user> {AS_IS | GRANT | REVOKE} {AS_IS | GRANT | REVOKE}

Data Management toolbox

72

To edit ArcSDE datasets, both the View and Edit parameters must be granted. Edit privileges are dependent on the View privilege, since you cant edit what you cant see (view). Edit privileges may be revoked, but you can still view the dataset. However, if the View privilege is revoked, the Edit privileges will automatically be revoked as well. Edit privileges should only be granted on a versioned database. To edit the dataset, the database must be versioned and you must have both View and Edit privileges. The RDBMS equivalent command for the View parameter is Select. The RDBMS equivalent commands for the Edit parameter are Update, Insert, and Delete. All three are granted or revoked simultaneously by the Edit parameter. Copy Rows: Writes the rows from an input table, table view, feature class, or feature layer to a new table.
CopyRows <in_rows> <out_table> {conguration_keyword}

If the input rows are a feature class, then only the attributes, and not the geometry, will be copied to the output table. If the input rows are from a feature class or table, then all rows will be used. If the input rows are from a layer or table view which has a selection, only the selected features or rows will be used. If the output table already exists, it will be overwritten. Create Table: Creates an empty geodatabase or dBASE table.
CreateTable <out_path> <out_name> {template;template...} {conguration_keyword} ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Delete Rows: Deletes rows from a feature class, layer, table, or table view.
DeleteRows <in_rows>

The input rows can be an INFO table, dBASE le, ArcSDE or personal or le geodatabase feature class or table, shapele, layer, or table view. If Delete Rows is used on feature data, the entire row, including the geometry, will be deleted. Coverages, CAD, and VPF data are invalid input to this tool. Rows cannot be deleted from these data types without destroying the integrity of the data. If there is no selection in the input rows, all rows will be deleted. Get Count: Returns the number of rows in the feature class, layer, table, or table view.
GetCount <in_rows>

The row count returned by the tool will be displayed in the geoprocessing window. If the input contains a selected set of records, only the selected records will be counted. This tool can be used in ModelBuilder to set up a precondition. Get Count is used to check the number of records returned by Select. If the record count is zero, then Buffer will not run. Pivot Table: Sorts and summarizes the input table elds, based on the selected pivot eld and value eld, in the output table to reduce redundancy.
PivotTable <in_table> <elds;elds...> <pivot_eld> <value_eld> <out_table>

Data Management toolbox

Pivot Table is used to reduce redundant records and atten one-to-many relationships. If the pivot eld is a numeric type, its value will be appended to its original eld name in the output table.

Topology toolset

Contains tools to establish and manage topological relationships between features. Add Feature Class to Topology: Adds a new feature class to a topological relationship.
AddFeatureClassToTopology <in_topology> <in_feature_class> <xy_rank> <z_rank>

Adding a new rule to a topology automatically makes the entire topology dirty, so when you nish adding feature classes and rules, you will need to revalidate the topology. The new features may create errors, depending on the rules that you add. This new feature class can be empty or may contain existing features. It must be in the same feature dataset as the topology. The input topology cannot be registered as versioned. The input feature class cannot be registered as versioned.

73

Add Rule to Topology: Adds a rule to the management of the topological relationship within a feature dataset.
AddRuleToTopology <in_topology> <MUST NOT HAVE GAPS (AREA) | MUST NOT OVERLAP (AREA) | MUST BE COVERED BY FEATURE CLASS OF (AREA-AREA) | MUST COVER EACH OTHER (AREA-AREA) | MUST BE COVERED BY (AREA-AREA) | MUST NOT OVERLAP WITH (AREA-AREA) | MUST BE COVERED BY BOUNDARY OF (LINE-AREA) | MUST BE COVERED BY BOUNDARY OF (POINT-AREA) | MUST BE PROPERLY INSIDE (POINT-AREA) | MUST NOT OVERLAP (LINE) | MUST NOT INTERSECT (LINE) | MUST NOT HAVE DANGLES (LINE) | MUST NOT HAVE PSEUDO-NODES (LINE) | MUST BE COVERED BY FEATURE CLASS OF (LINELINE) | MUST NOT OVERLAP WITH (LINE-LINE) | MUST BE COVERED BY (POINT-LINE) | MUST BE COVERED BY ENDPOINT OF (POINT-LINE) | BOUNDARY MUST BE COVERED BY (AREA-LINE) | BOUNDARY MUST BE COVERED BY BOUNDARY OF (AREA-AREA) | MUST NOT SELF-OVERLAP (LINE) | MUST NOT SELFINTERSECT (LINE) | MUST NOT INTERSECT OR TOUCH INTERIOR (LINE) | ENDPOINT MUST BE COVERED BY (LINE-POINT) | CONTAINS POINT (AREA-POINT) | MUST BE SINGLE PART (LINE)> <in_feature_ class> {subtype} {in_feature_class2} {subtype2}

To add a rule to a topology, the input topology cannot be registered as versioned. You can type the name of the subtype value to which you want a topology rule to be applied. If you are using the command line and the subtype name consists of more than one word, use single quotes to contain the subtype name. Create Topology: Creates a topology within a feature dataset.
CreateTopology <in_dataset> <out_name> <in_cluster_tolerance>

The topology has a minimum and maximum cluster tolerance that is derived from the precision of the spatial reference of the feature dataset in which you are creating the topology. If the value entered is larger than the maximum cluster tolerance, the value will become the maximum. If the value entered is smaller than the minimum, the minimum (or default) will be used. Remove Feature Class from Topology: Removes a feature class from the topological relationship.
RemoveFeatureClassFromTopology <in_topology> <in_feature_class>

Data Management toolbox

74

Removing a feature class from a topology also removes all the topology rules associated with that feature class. Removing a feature class from a topology will invalidate the entire topology. Removing a feature class from a topology alters the schema of the topology. To remove a feature class, the topology must be unregistered as versioned. Remove Rule from Topology: Removes a rule from a topological relationship.
RemoveRuleFromTopology <in_topology> <in_rule>

When removing a rule from a topology using the command line or scripting, you must specify the feature class ObjectClassID in brackets after the rule name. See the command line syntax for an example. If you are using the Remove Feature Class From Topology tool, the list of rules is presented to you in a drop-down list. Removing a rule will require the topology to be revalidated. Removing a topology rule alters the schema of the topology and requires an exclusive lock. It also requires that the topology be unregistered as versioned. Set Cluster Tolerance: Alters the cluster tolerance in a topological relationship.
SetClusterTolerance <in_topology> <cluster_tolerance>

You cannot alter the cluster tolerance for a topology if the topology has been registered as versioned. Changing the cluster tolerance will require the entire topology to be validated.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Validate Topology: Evaluates the features against the rules and nds any new errors related to new rules or feature classes.
ValidateTopology <in_topology> {FULL_EXTENT | VISIBLE_EXTENT}

If you validate an ArcSDE geodatabase topology in ArcCatalog, the feature dataset that the topology is within must not be registered as versioned. Validate will only process areas of the topology that require validation. If you validate the topology in ArcMap, you can optionally use the visible extent as the area you want to validate. All areas outside the visible extent will not be validated.

Versions toolset

Contains tools to make adjustments to the versions of the data. Alter Version: Alters the properties of any of the versions of the dataset including name, description, and access permissions.
AlterVersion <in_workspace> <in_version> {name} {description} {PRIVATE | PUBLIC | PROTECTED}

Neither personal nor le geodatabases support versioning. Versioning tools only work with ArcSDE data. Versions are not affected by changes occurring in other versions of the database. A versions permission can only be changed by its owner. Create Version: Creates a new version of the specied database.
CreateVersion <in_workspace> <parent_version> <version_name> {PRIVATE | PUBLIC | PROTECTED}

The output version name is prexed by the ArcSDE geodatabase user name, for example, SDE. arctoolbox. The output versions permissions are set as private by default but can be changed using the Alter Version tool. Delete Version: Deletes the specied version from the input workspace.
DeleteVersion <in_workspace> <version_name>

Data Management toolbox

Only the versions owner can rename, delete, or alter the version. A parent version cant be deleted until all dependent child versions are deleted. Versions are not affected by changes occurring in other versions of the database. Post Version: Applies the current edit session to the reconciled target version during versioned geodatabase editing.
PostVersion <in_workspace> <version_name>

Posting synchronizes the edit version with the reconciled version and saves the data. Posting cant be undone since you are applying changes to a version that you are not currently editing. If the reconciled version is modied between reconciling and posting, you will be notied to reconcile again before posting. Reconcile Version: Reconciles a version against a parent version in its lineage.
ReconcileVersion <in_workspace> <version_name> <target_name> {BY_OBJECT | BY_ATTRIBUTE} {FAVOR_TARGET_VERSION | FAVOR_EDIT_VERSION} {LOCK_AQUIRED | NO_LOCK_AQUIRED} {NO_ABORT | ABORT_CONFLICTS} {NO_POST | POST}

75

 The reconcile process requires that you are the only user currently editing the version and that you are the only user able to edit the version throughout the reconcile process until you save or post. The reconcile process requires that you have full permissions to all the feature classes that have been modied in the version being edited. Register as Versioned: Registers an ArcSDE dataset as versioned in ArcCatalog.
RegisterAsVersioned <in_dataset> {NO_EDITS_TO_BASE | EDITS_TO_BASE}

File and personal geodatabases dont support versioning. Versioning tools only work with ArcSDE data. Registering a feature dataset as versioned registers all feature classes within the feature dataset as versioned. Versions are not affected by changes occurring in other versions of the database. A versions permission can only be changed by its owner. Making a feature class or table multiversioned requires a unique integer eld. This is typically the OBJECTID eld. Unregister as Versioned: Unregisters an ArcSDE dataset as versioned in ArcCatalog.
UnregisterAsVersioned <in_dataset> {KEEP_EDIT | NO_KEEP_EDIT} {NO_COMPRESS_DEFAULT | COMPRESS_DEFAULT}

Making a feature class or table multiversioned requires a unique integer eld. Only the owner of the data may register or unregister the object as versioned. Versions are not affected by changes occurring in other versions of the database. A versions permission can only be changed by its owner. Outstanding edits will be lost with the execution of this tool unless the database is compressed rst.

Workspace toolset

Contains tools to create the storage models used with ArcGIS.

Data Management toolbox

76

Create ArcInfo Workspace: Creates a workspace with an INFO subdirectory.

CreateArcInfoWorkspace <out_folder_path> <out_name>

The workspace cannot already exist. Create Feature Dataset: Creates an empty feature dataset within an existing geodatabase.
CreateFeatureDataset <out_dataset_path> <out_name> {spatial_reference}

Create File GDB: Creates a new le geodatabase.

CreateFileGDB <out_folder_path> <out_name>

Each dataset can scale up to 1 TB in size. Create Folder: Creates a new folder.
CreateFolder <out_folder_path> <out_name>

The output folder should not already exist. An error will not occur if the folder already exists.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Create Personal GDB: Creates a new personal geodatabase.

CreatePersonalGDB <out_folder_path> <out_name>

The output personal geodatabase cannot already exist. Geodatabase names must start with a valid letter. The rst character cannot be numeric. A personal geodatabase is usually on the same network as the client application (for example, ArcCatalog) and supports one editor at a time.

Data Management toolbox

77

Geocoding toolbox
Contains tools used to manage a geocoding service and run geocoding actions.
Automate Geocoding Indexes: Creates an automatically updating relationship between the reference data and the geocoding index(es) of an address locator. NOTE: This tool is no longer supported at ArcGIS 9.2, because indexes do not need to be automated. Use the Create Address Locator tool to create a new address locator.
AutomateGeocodingIndexes <in_address_locator>

Create Address Locator: Creates a new address locator.

CreateAddressLocator <in_address_locator_style> <reference_data{Role}; reference_data{Role}...> <in_eld_map> <out_address_locator>

Address locators can be created in the same workspace of the reference data or any other workspace you specied. The role of a reference dataset denes the role that it plays as reference data for the address locator. The address locator styles provided with ArcGIS use the following values to describe the roles of reference datasets: Primary tableDenes the primary reference dataset feature class for a locator, such as a street centerline feature class Alternate Name tableDenes an alternate street name table if the address locator style supports it Alias tableDenes a place-name alias table Deautomate Geocoding Indexes: Removes the automatically updating relationship between the reference data and geocoding index of an address locator. NOTE: This tool is no longer supported at ArcGIS 9.2, because indexes do not need to be deautomated. Use the Create Address Locator tool to create a new address locator.
DeautomateGeocodingIndexes <in_address_locator>

Delete Address Locator: Deletes an address locator. NOTE: This tool is no longer supported at ArcGIS 9.2. Use the Delete (Data Management) tool to delete an address locator.
DeleteAddressLocator <in_address_locator>

Geocoding toolbox

Geocode Addresses: Creates a point feature class from a table of addresses.

GeocodeAddresses <in_table> <address_locator> <in_address_elds> <out_feature_class> {STATIC | DYNAMIC}

The input address table can be any format supported by ArcGIS, including INFO, dBASE, and geodatabase tables. The output feature class can be a shapele or geodatabase feature class. Choose to create a dynamic geocoded feature class if you want edits in the input address table to be automatically reected in the output feature class. This option is only valid if the input address table and output feature class are in the same geodatabase workspace.

79

Rebuild Address Locator: Rebuilds an address locator.

RebuildAddressLocator <in_address_locator>

You must have write privileges on the address locator to use this tool. The reference feature class and tables must be available. You may need to repair the address locator particularly the paths to the reference data if the data has been moved to a different location since the last time the locator was built. Address locators created based on a versioned geodatabase will be rebuilt using the same version. Address locators created with versions prior to ArcGIS 9.2 or address locators provided by any StreetMap products cannot be rebuilt. Rebuild Geocoding Indexes: Rebuilds the indexes of an address locator. NOTE: This tool is no longer supported at ArcGIS 9.2, because address attributes and indexes in the address locator will be refreshed. Use the Rebuild Address Locator tool to rebuild an address locator.
RebuildGeocodingIndex <in_address_locator>

Rematch Addresses: Rematches addresses in a geocoded feature class.

RematchAddresses <in_geocoded_feature_class> {in_where_clause}

The input feature class has to be a feature class that was created by the Geocode Addresses tool or a process where a table of addresses were geocoded. Standardize Addresses: Standardizes the address information in a table or feature class.
StandardizeAddresses <in_address_data> <in_input_address_elds;in_input_address_ elds...> <in_address_locator_style> <in_output_address_elds;in_output_address_ elds...> <out_address_data> {STATIC | DYNAMIC}

If you are using an address locator style that geocodes addresses with house numbers (most address locator styles do this), you must include a eld that contains a numeric value that represents the house number in the input address elds. If your input table or feature class and output table are in the same geodatabase workspace, you can choose to create dynamic output. By default, the Standardize Addresses tool will create static output, unless you explicitly specify to create dynamic output.

Geocoding toolbox
80

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Linear Referencing toolbox

Contains tools to model relative locations along linear features and associate multiple sets of attributes to portions of linear features.
Calibrate Routes: Recalculates route measures using points.
CalibrateRoutes <in_route_features> <route_id_eld> <in_point_features> <point_id_eld> <measure_eld> <out_feature_class> {DISTANCE | MEASURES} {search_radius} {BETWEEN | NO_BETWEEN} {BEFORE | NO_BEFORE} {AFTER | NO_AFTER} {IGNORE | NO_IGNORE} {KEEP | NO_KEEP} {INDEX | NO_INDEX}

If the output route feature class will be written to a geodatabase, an appropriate m domain should be set. The output route feature class will include all the elds from the input features. A search radius of innity cannot be specied. Create Routes: Creates routes from existing lines.
CreateRoutes <in_line_features> <route_id_eld> <out_feature_class> <LENGTH | ONE_FIELD | TWO_FIELDS> <from_measure_eld> <to_measure_eld> {UPPER_LEFT | LOWER_LEFT | UPPER_RIGHT | LOWER_RIGHT} {measure_factor} {measure_offset} {IGNORE | NO_IGNORE} {INDEX | NO_INDEX}

If the output route feature class will be written to a geodatabase, an appropriate m domain should be set. The unique values in the route identier eld are written to output route feature class. Use Make Feature Layer or Make Query Table to effectively reduce the number of lines that will be used to create routes. Use a measure factor to convert between route measure units. For example, to convert from feet to miles, use a factor of 0.00018939394. Dissolve Route Events: Removes redundant information from event tables or separates event tables having more than one descriptive attribute into separate tables.
DissolveRouteEvents <in_events> <in_event_properties> <dissolve_eld; dissolve_eld...> <out_table> <out_event_properties> {DISSOLVE | CONCATENATE} {INDEX | NO_INDEX}

The output table can be a dBASE le or a geodatabase table. If the input events do not have an object ID eld, use Make Query Table prior to Dissolve Route Events to add a virtual object ID eld. An attribute index on the route identier eld speeds up the dynamic segmentation process. If you will be using the output route feature class for dynamic segmentation, it is recommended that you choose to have an attribute index created. Locate Features Along Routes: Computes the intersection of input features (point, line, or polygon) and route features and writes the route and measure information to a new event table.
LocateFeaturesAlongRoutes <in_features> <in_routes> <route_id_eld> <radius_or_ tolerance> <out_table> <out_event_properties> {FIRST | ALL} {DISTANCE | NO_DISTANCE} {ZERO | NO_ZERO} {FIELDS | NO_FIELDS}

Linear Referencing toolbox

81

The output table can be a dBASE le or a geodatabase table. The event type must be POINT when the input features are points and must be LINE when the input features are lines or polygons. Use Make Feature Layer to effectively reduce the inputs that will be processed.

Make Route Event Layer: Creates a temporary feature layer using routes and route events.
MakeRouteEventLayer <in_routes> <route_id_eld> <in_table> <in_event_properties> <out_layer> {offset_eld} {NO_ERROR_FIELD | ERROR_FIELD} {NO_ANGLE_FIELD | ANGLE_FIELD} {NORMAL | TANGENT} {ANGLE | COMPLEMENT} {LEFT | RIGHT} {POINT | MULTIPOINT}

Temporary layers are stored in memory and can be used as input to other geoprocessing functions in your current ArcCatalog or ArcMap session. Use Make Feature Layer on the routes and/or Make Table View on the events prior to Make Route Event Layer to reduce the number of routes and events that will be processed. Overlay Route Events: Combines two input event tables to create a single output event table, using either a union or intersection operation.
OverlayRouteEvents <in_table> <in_event_properties> <overlay_table> <overlay_event_ properties> <INTERSECT | UNION> <out_table> <out_event_properties> {ZERO | NO_ZERO} {FIELDS | NO_FIELDS} {INDEX | NO_INDEX}

Line on line, line on point, point on line, and point on point event overlays can be performed. The input and overlay events should be based on the same route reference. Transform Route Events: Transforms the measures of events from one route reference to another and writes them to a new event table.
TransformRouteEvents <in_table> <in_event_properties> <in_routes> <route_id_eld> <target_routes> <target_route_id_eld> <out_table> <out_event_properties> <cluster_ tolerance> {FIELDS | NO_FIELDS}

Transforming events allows you to use the events from one route reference with another route reference having different route identiers and/or measures. Any whole or partial event that intersects a target route is written to the new event table. The output event type (point or line) must match the input event type. The best results will be achieved when the source routes and the target routes closely overlay. Do not use a large cluster tolerance to try and overcome discrepancies between the source and target routes because it can lead to unexpected results. Use Make Table View prior to Transform Route Events to effectively reduce the number of events that will be processed.

Linear Referencing toolbox

82

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Multidimension toolbox
Contains tools to make a netCDF raster layer, feature layer, or table view; to convert to netCDF from raster, feature, or table; and to select a dimension of a netCDF layer or table to display.
Feature To NetCDF: Converts a feature class to a netCDF le.
FeatureToNetCDF <in_features> <eld {Variable} {Units};eld {Variable} {Units}...> <out_ netCDF_le> {eld {Dimension} {Units};eld {Dimension} {Units}...}

Multidimension toolbox

The default variable name is the same as the eld name specied in the eld_to_variable parameter. The type of variable is the same as the type of eld. The default dimension name is the same as the eld name specied in the eld_to_dimension parameter. The size of a dimension is equal to the number of unique values in the respective eld. Make NetCDF Feature Layer: Makes an in-memory feature layer from a netCDF le.
MakeNetCDFFeatureLayer <in_netCDF_le> <variable;variable...> <x_variable> <y_variable> <out_feature_layer> {row_dimension;row_dimension...} {z_variable} {m_variable} {dimension {Value};dimension {Value}...} {BY_VALUE | BY_INDEX}

The feature layer can be used as input to any geoprocessing tool that accepts a feature class as input. The temporary feature layer can be saved as a layer le using the Save To Layer File tool or saved as a new feature class using the Copy Features tool. An existing feature layer will be overwritten if the same layer name is specied. Make NetCDF Raster Layer: Makes an in-memory raster layer from a netCDF le.
MakeNetCDFRasterLayer <in_netCDF_le> <variable> <x_dimension> <y_dimension> <out_raster_layer> {band_dimension} {dimension {Value};dimension {Value}...} {BY_VALUE | BY_INDEX}

To create a netCDF raster layer from a netCDF variable, the spacing between x-coordinates must be equal and the spacing between y-coordinates must be equal. If the coordinates are unequally spaced, create a netCDF feature layer, then interpolate to raster. The output raster layer type is either oat or integer based on the netCDF variable type. The rst variable in the netCDF le suitable for creating a raster is selected as the default variable. Make NetCDF Table View: Makes a table view from a netCDF le.
MakeNetCDFTableView <in_netCDF_le> <variable;variable...> <out_table_view> {row_dimension;row_dimension...} {dimension {Value};dimension {Value}...} {BY_VALUE | BY_INDEX}

Table views are tables stored in memory and are the same as the table view when a table is added to ArcMap. ArcCatalog does not display these table views, but they can be used as inputs to other geoprocessing tools in the current ArcGIS session. Once ArcGIS exists, the tables in memory are removed. Table views created in ArcCatalog cannot be used in ArcMap. An existing table view will be overwritten if the same table view name is entered.

83

Raster to NetCDF: Converts a raster dataset to a netCDF le.

RasterToNetCDF <in_raster> <out_netCDF_le> {variable} {variable_units} {x_dimension} {y_dimension} {band_dimension} {eld {Dimension} {Units};eld {Dimension} {Units}...}

Multidimension toolbox
84

The input can be any valid raster dataset or raster catalog. The default variable name is the same as the input raster name. The output netCDF variable type is either oat or integer based on the input raster dataset type. Select by Dimension: Updates the netCDF layer display or netCDF table view based on the dimension value.
SelectByDimension <in_layer_or_table> {dimension {Value};dimension {Value}...} {BY_VALUE | BY_INDEX}

Inputs for this tool can be created by using the Make NetCDF Feature Layer, Make NetCDF Raster Layer, or Make NetCDF Table View tools. If a dimension is not specied, its value is set to the rst value. The rst value is considered as the default value. This tool updates the input. In ModelBuilder, an output variable appears to chain the updated input as input to another tool in the model, but the tool does not produce a new output. Table to NetCDF: Converts a table to a netCDF le.
TableToNetCDF <in_table> <eld {Variable} {Units};eld {Variable} {Units}...> <out_netCDF_le> {eld {Dimension} {Units};eld {Dimension} {Units}...}

The default variable name is the same as the eld name specied in the eld_to_variable parameter. The type of the variable is the same as the type of the eld.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Spatial Statistics toolbox

Contains statistical tools for analyzing the distribution of geographic features. Analyzing Patterns toolset
Contains tools to calculate statistical values used to quantify pattern. Average Nearest Neighbor: Calculates a nearest neighbor index based on the average distance from each feature to its nearest neighboring feature.
AverageNearestNeighbor <input_feature_class> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> {FALSE | TRUE} {area}

Spatial Statistics toolbox

The nearest neighbor index is expressed as the ratio of the observed distance divided by the expected distance (hypothetical random distribution). Hence, if the index is less than 1, the pattern exhibits clustering; if the index is greater than 1, the trend is toward dispersion or competition. If an area value is not specied, then a value calculated from the map extent is used [area = (xmaxxmin) * (ymax-ymin)]. The nearest neighbor function, however, is sensitive to the area value (small changes in the area can result in signicant changes in the results). To get better results, an accurate value for area should be used. High/Low Clustering (Getis-Ord General G): Measures the degree of clustering for either high values or low values.
HighLowClustering <input_feature_class> <input_eld> {FALSE | TRUE} <INVERSE DISTANCE | INVERSE DISTANCE SQUARED | FIXED DISTANCE BAND | ZONE OF INDIFFERENCE |POLYGON CONTIGUITY (FIRST ORDER) | GET SPATIAL WEIGHTS FROM FILE> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> <NONE | ROW> <distance_band_or_threshold_distance> {weights_matrix_le}

A high General G value indicates that high values are clustered within the study area; a low General G value indicates that low values tend to cluster. Although this tool will work with polygon or line data, it is really only appropriate for event, incident, or other xed-point feature data. For line and polygon features, geometric centroids are calculated before the central feature is identied. The geometric centroid of a feature may be located outside a features boundary. If centroids must be within feature boundaries, use the Features to Point tool (Inside option) to create centroids before performing the nearest neighbor operation. Multi-Distance Spatial Cluster Analysis (Ripleys K-function): Determines whether a feature class is clustered at multiple different distances. The tool outputs the result as a table and optionally as a popup graphic.
MultiDistanceSpatialClustering <input_feature_class> <output_table> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> <number_of_distance_bands> {0 PERMUTATIONS - NO CONFIDENCE ENVELOPE | 9 PERMUTATIONS | 99 PERMUTATIONS | 999 PERMUTATIONS} {FALSE | TRUE} {weight_ eld} {beginning_distance} {distance_increment} {NONE | SIMULATE OUTER BOUNDARY VALUES | REDUCE ANALYSIS AREA | RIPLEYS EDGE CORRECTION FORMULA} {MINIMUM ENCLOSING RECTANGLE | USER PROVIDED STUDY AREA FEATURE CLASS} {study_area_feature_class} 85

 The output of the tool is a table with two elds named ExpectedK and ObservedK containing the expected k and observed k values, respectively. If a condence interval option is specied, two additional elds named LowConfEnv and HiConfEnv will be present with the condence interval information for each iteration of the tool. The condence envelope is constructed by distributing points randomly in the study area and calculating k for that distribution. Each random distribution of the points is known as a permutation. If 99 permutations is selected, the tool will randomly distribute the set of points 99 times for each iteration. After distributing the points 99 times, the tool selects the k value that deviated above and below the expected by the greatest amount and these values become the condence interval. The number of points distributed for each permutation is equal to the number of points in the input feature class. If the user has specied a weight eld, the weight of the random points will be taken randomly from a list of the weights of the input data. Spatial Autocorrelation (Morans I): Measures spatial autocorrelation based on feature locations and attribute values.

Spatial Statistics toolbox

SpatialAutocorrelation <input_feature_class> <input_eld> {FALSE | TRUE} <INVERSE DISTANCE | INVERSE DISTANCE SQUARED | FIXED DISTANCE BAND | ZONE OF INDIFFERENCE | POLYGON CONTIGUITY (FIRST ORDER) | GET SPATIAL WEIGHTS FROM FILE> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> <NONE | ROW> <distance_band_or_threshold_distance> {weights_matrix_le}

Given a set of features and an associated attribute, Global Morans I evaluates whether the pattern expressed is clustered, dispersed, or random. A Morans I value near +1.0 indicates clustering; a value near 1.0 indicates dispersion.

Mapping Clusters toolset

Contains tools for cluster analysis, such as identifying the locations of statistically signicant hot spots or areas of signicant diversity. Cluster and Outlier Analysis (Anselin Local Morans I): Identies those clusters of points with values similar in magnitude and clusters of points with very heterogeneous values within a set of weighted data points.
ClustersOutliers <input_feature_class> <input_eld> <output_feature_class> <INVERSE DISTANCE | INVERSE DISTANCE SQUARED | FIXED DISTANCE BAND | ZONE OF INDIFFERENCE | POLYGON CONTIGUITY (FIRST ORDER) | GET SPATIAL WEIGHTS FROM FILE> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> <NONE | ROW> <distance_band_or_threshold_distance> {weights_matrix_le}

If the I index value is positive, then that feature has values similar to neighboring features values. If the I index value is negative, then that feature is quite different from neighboring values. The Local Morans I process copies the input feature class to the output feature class and adds two results columns for the index and z score named LMi<distance_method> and LMz<distance_method>. If elds of these names already exist in the input feature class, they will be overwritten in the output feature class.

86

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Cluster/Outlier Analysis with Rendering: Identies clusters of points with values similar in magnitude and clusters of points with very heterogeneous values within a given set of weighted data points and applies a cold to hot type of rendering.
ClustersOutliersRendered <input_feature_class> <input_eld> <output_layer_le> <output_feature_class>

The Cluster/Outlier Analysis with Rendering tool combines the Clusters and Outlier Analysis and Z Score Rendering functions. Hot Spot Analysis (Getis-Ord Gi*): Calculates the Getis-Ord Gi* statistic for hot spot analysis.
HotSpot <input_feature_class> <input_eld> <output_feature_class> <FIXED DISTANCE BAND |INVERSE DISTANCE | INVERSE DISTANCE SQUARED | ZONE OF INDIFFERENCE | POLYGON CONTIGUITY (FIRST ORDER) | GET SPATIAL WEIGHTS FROM FILE> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> <NONE | ROW> <distance_band_or_threshold_distance> {self_potential_eld} {weights_ matrix_le}

Spatial Statistics toolbox

Given a set of weighted data points, the Getis-Ord Gi* statistic identies those clusters of points with values higher in magnitude than you might expect to nd by random chance. (For line and polygon features, centroids are calculated prior to analysis.) The Gi function creates a new feature class that duplicates the input feature class, then adds a new Results column for the Gi z score. The name of the output eld is Gi<distance_method>. If a eld of this name already exists in the input feature class, it will be overwritten in the output feature class. Hot Spot Analysis with Rendering: Calculates Gi* statistics and applies a cold to hot type of rendering to the output Z scores.
HotSpotsRendered <input_feature_class> <input_eld> <output_layer_le> <output_feature_ class> <distance_band_or_threshold_distance>

The Gi* rendered model combines the functions Hot Spot Analysis and Z Score Rendering.

87

Measuring Geographic Distributions toolset

Contains tools to calculate a value that represents a characteristic of the distribution of a set of features, such as the center, compactness, or orientation. Central Feature: Identies the most centrally located feature in a point, line, or polygon feature.
CentralFeature <input_feature_class> <output_feature_class> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE> {weight_eld}{self_potential_weight_eld}

The feature associated with the smallest accumulated distance to all other features is the most centrally located feature; this feature is selected and copied to the newly created output feature class (using Make Feature Layer and Save to Layer File). For line and polygon features, feature centroids are used in the computations. Calculations are based on either Euclidean or Manhattan distance and require projected data to accurately measure distances. Directional Distribution (Standard Deviational Ellipse): Measures whether a distribution of features exhibits a directional trend.
DirectionalDistribution <input_feature_class> <output_ellipse_feature_class> <1 STANDARD DEVIATION | 2 STANDARD DEVIATIONS | 3 STANDARD DEVIATIONS> {weight_eld} {case_eld}

Spatial Statistics toolbox

The following elds are added to the output ellipse feature class to store ellipse information: CenterX stores the x-coordinate of the center of the ellipse, CenterY stores the y-coordinate of the center of the ellipse, XStdDist stores the standard distance in the x direction, YStdDist stores the standard distance in the y direction, and Rotation stores the rotation of the ellipse. (If you specify a case eld, it is also included in the output feature class.) Linear Directional Mean: Identies the general (mean) direction for a set of lines.
DirectionalMean <input_feature_class> <output_feature_clas> <orientation_only> {case_eld}

The input feature class must be a line or polyline feature class. Attribute values for the new line features include Compass Angle (clockwise from due North), Directional Mean (counterclockwise from due East), Circular Variance (an indication of how much directions or orientations deviate from directional mean), Mean Center X and Y Coordinates, and Mean Length.
88 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 Analogous to a standard deviation measure, the circular variance tells how well the directional mean vector represents the set of input vectors. Circular variance ranges from 0 to 1. If all the input vectors have the exact same (or very similar) directions, the circular variance is small (near zero). When input vector directions span the entire compass, the circular variance is large (near 1). Calculations are based on either Euclidean or Manhattan distance and require projected data to accurately measure distances. Mean Center: Identies the geographic center (or the center of concentration) for a set of features.
MeanCenter <input_feature_class> <output_feature_class> {weight_feld} {case_eld} {dimension_eld}

Spatial Statistics toolbox

The mean center is a point constructed from the average x- and y-values for the input feature centroids. If a case eld is specied, the input features are grouped according to case eld values, and a mean center is calculated from the average x- and y-values for the centroids in each group. Standard Distance: Measures the degree to which features are concentrated or dispersed around the points (or feature centroids) in an input feature class.
StandardDistance <input_feature_class> <ouput_standard_distance_feature_class> <1 STANDARD DEVIATION | 2 STANDARD DEVIATIONS | 3 STANDARD DEVIATIONS> {weight_eld} {case_eld}

The standard distance calculation may be based on an optional weight (to get the standard distance of businesses weighted by employees, for example). The standard distance is a useful statistic, as it provides a single summary measure of feature distribution around any given point (similar to the way a standard deviation measures the distribution of data values around the statistical mean). Standard Distance creates a new feature class containing a circle polygon centered on each of the central features (mean centers). Each circle polygon is drawn with a radius equal to the standard distance. The attribute value for each circle polygon is its standard distance. If the underlying pattern in the data is truly random, the one standard deviation polygon will cover approximately 68 percent of the features in the cluster. Two standard deviations will contain approximately 95 percent of the features, and three standard deviations will cover approximately 99 percent of the features in the cluster. A mean center calculation is used to determine the geographic centers of the input feature class.

89

Utilities toolset
Contains tools to perform a variety of data rendering tasks that can be used in conjunction with other tools in the Spatial Statistics toolbox. Calculate Areas: Calculates area values for each feature in a polygon feature class.
CalculateAreas <input_feature_class> <output_feature_class>

This tool is useful in determining a weight for intrazonal interaction. The eld F_AREA is created in the output feature class to store calculated Area values. If a eld of this name already exists in the input feature class, it will be overwritten in the output feature class. Calculate Distance Band from Neighbor Count: Calculates the distance for all features in the input feature class to their nth neighbor (specied in the Neighbors parameter) and examines the distances and returns three values: the maximum distance, the minimum distance, and the average distance.

Spatial Statistics toolbox

CalculateDistanceBand <Input_Features> <Neighbors> <EUCLIDEAN DISTANCE | MANHATTAN DISTANCE>

This tool calculates the distance for all features in the input feature class to their nth neighbor. Then it examines the distances and returns three values: the maximum distance, the minimum distance, and the average distance. The neighborhood of all features will have at least n neighbors if the neighborhood size is greater than the maximum distance reported by the tool. The neighborhood of all features will have fewer than n neighbors if the neighborhood size is less than the minimum distance reported by the tool. Collect Events: Collects event data into weighted point data.
CollectEvents <input_incident_features> <output_weighted_point_feature_class>

Collect Event creates a new feature class and adds a eld named Count to hold the sum of all incidents for each unique location. This function creates as derived output the name of the count eld created and the maximum count value encountered for any one location. These outputs are useful when using the tool in conjunction with a rendering tool in both the model building and scripting environments. Collect Events with Rendering: Collects event data into weighted point data and applies a graduated circle rendering to the count eld.
CollectEventsRendered <input_incident_features> <output_layerle> <output_weighted_ point_feature_class>

The Collect Events Rendered model combines the functions Collect Events and Count Rendering.

90

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Count Rendering: Applies graduated circle rendering to a count type eld of a point feature class.
CountRenderer <input_feature_class> <eld_to_render> <output_layer_le> <number_of_ classes> <MANGO | BRIGHT_RED | DARK_GREEN | GREEN | DARK_BLUE | BRIGHT_PINK | LIGHT_ YELLOW| SKY_BLUE> {maximum_eld_value}

The Count Renderer draws quantities using circle size to show relative values. Export Feature Attribute to ASCII: Exports feature class coordinates and attribute values to a space-, comma-, or semicolon-delimited ASCII text le.
ExportXYv <input_feature_class> <value_eld;value_eld...><SPACE | COMMA | SEMI-COLON> <output_ascii_le>

Spatial Statistics toolbox

Z Score Rendering: Applies a cold or hot graduated color rendering to a eld of z scores.
ZRenderer <input_feature_class> <eld_to_render> <output_layer_le>

This tool is appropriate for rendering output from both Hot Spot Analysis and Diversity Analysis.

91

Server toolbox
Contains tools to generate, update, and delete MapServer and GlobeServer image caches. Caching toolset

Contains tools to generate, update, and delete MapServer and GlobeServer image caches. Delete Globe Server Cache: Deletes an existing GloberService layers cache.
DeleteGlobeServerCache <server_name> <object_name> <layer;layer...>

Server\ toolbox

This tool requires the 3D Analyst extension. This is an unrecoverable operation therefore only use this command if you are sure you no longer need the cache. Delete Globe Server Cache tool can be helpful if you have many caches residing in your server cache directory and want to delete only a particular services cache. Delete Globe Server Cache deletes the entire cache folder. Note that after Delete Globe Server Cache tool runs it will restart the server object. This will in turn generate a new set of caches for each layer in the service that was deleted by the delete operation. This is because all globeservices will require a cache conguration to exist on disk to run. The cache that gets created automatically on start up of a service is a skeleton representation that does not contain any tiles. Delete Map Server Cache: Deletes an existing MapService cache including all associated les on disk.
DeleteMapServerCache <server_name> <object_name> <data_frame> <layer;layer...>

This is an unrecoverable operation therefore only use this command if you are sure you no longer need the cache. If there is more than one data frame in the cache directory only the active data frame of the specied MapService will be removed. If there is only one data frame in the cache directory the entire directory will be removed. After this tool runs the MapService will be restarted. Generate Globe Server Cache: Generates a globe data cache based on ArcGlobes data tiling scheme and using a specied globe server object.
GenerateGlobeServerCache <server_name> <object_name> <out_folder> <Globe - 1:10000000 | Continent - 1:5000000 | Countries - 1:2500000 | Country - 1:1250000 | States - 1:625000 | State - 1:312500 | Counties - 1:156250 | County - 1:78125 | Metropolitan Area - 1:39062 | Cities - 1:19531 | City - 1:9765 | Town - 1:4882 | Neighborhood - 1:2441 | City Blocks - 1:1220 | City Block - 1:610 | Buildings - 1:305 | Building - 1:152 | Houses - 1:76 | House Property - 1:38 | House - 1:19 | Rooms - 1:9 | Room - 1:4> <Room - 1:4 | Rooms - 1:9 | House - 1:19 | House Property - 1:38 | Houses - 1:76 | Building - 1:152 | Buildings - 1:305 | City Block - 1:610 | City Blocks - 1:1220 | Neighborhood - 1:2441 | Town - 1:4882 | City - 1:9765 | Cities - 1:19531 | Metropolitan Area - 1:39062 | County - 1:78125 | Counties - 1:156250 | State - 1:312500 | States - 1:625000 | Country - 1:1250000 | Countries - 1:2500000 | Continent - 1:5000000 | Globe - 1:10000000> {thread_count} <layer;layer...>

This tool requires the 3D Analyst extension. To build a cache using the server object, specify the Globe server host. The tool will automatically list all server objects available on that server. You are able to generate data cache for all the layers contained in the server object or for a single layer. Each data cache generation thread on the client must have access to the data, otherwise that thread will not be able to be used in the generation of the cache.

93

Generate Map Server Cache: Divides a map into a gridded cache of static image tiles organized into a directory hierarchy by scale levels.
GenerateMapServerCache <server_name> <object_name> <data_frame> <out_folder> <NEW | PREDEFINED> <STANDARD | CUSTOM> <number_of_scales> <dpi> <tile_width> <tile_height> {FUSED | MULTI_LAYER} {tiling_schema} {tile_origin} {scale;scale...} {layer;layer...} {thread_count} {NONE | ANTIALIASING}

The two cache types that can be created are: FusedEach tile is created as a fused image of all the layers in the source map document. Mutli-layerThere is one cache, but it is organized into sub-caches containing tiles from each layer in the source map document. This tool is used to create a map cache from an existing ArcMap Document (.mxd) or from an ArcMap Server Object. Only one data frame can be cached at a time. If you wish to cache more than one data frame, the tool will have to be run more than once. Generate Map Server Cache Tiling Scheme: Generates the Map Server cache tiling scheme le that can be used in the Generate Map Server Cache tool.
GenerateMapServerCacheTilingScheme <map_document> <data_frame> <tile_origin> <tiling_ schema> <cache_levels> <scale;scale...> <dpi> <tile_width> <tile_height>

Server toolbox

A tiling scheme describes how clients should reference the tiles in a cache and is a mapping between the spatial reference of the source map document and the tiling grid. The tiling grid uses a level-ofdetail (scale-level), row, and column referencing scheme. The scheme also denes the scale levels (levels of detail) at which the cache has tiles, the size of the tiles in pixels, and the screen resolution for which the tiles are intended to be most commonly displayed. Update Globe Server Cache: Updates an existing Globe Service cache to replace missing tiles, overwrite outdated tiles, or add new tiles in new areas.
UpdateGlobeServerCache <server_name> <object_name> {update_extent} <layer;layer...> <Globe - 1:10000000 | Continent - 1:5000000 | Countries - 1:2500000 | Country - 1:1250000 | States - 1:625000 | State - 1:312500 | Counties - 1:156250 | County - 1:78125 | Metropolitan Area - 1:39062 | Cities - 1:19531 | City - 1:9765 | Town - 1:4882 | Neighborhood - 1:2441 | City Blocks - 1:1220 | City Block - 1:610 | Buildings - 1:305 | Building - 1:152 | Houses - 1:76 | House Property - 1:38 | House - 1:19 | Rooms - 1:9 | Room - 1:4> <Room - 1:4 | Rooms - 1:9 | House - 1:19 | House Property - 1:38 | Houses - 1:76 | Building - 1:152 | Buildings - 1:305 | City Block - 1:610 | City Blocks - 1:1220 | Neighborhood - 1:2441 | Town - 1:4882 | City - 1:9765 | Cities - 1:19531 | Metropolitan Area - 1:39062 | County - 1:78125 | Counties - 1:156250 | State - 1:312500 | States - 1:625000 | Country - 1:1250000 | Countries 1:2500000 | Continent - 1:5000000 | Globe - 1:10000000> {thread_count} <Recreate Empty Tiles | Recreate All Tiles>

This tool requires the 3D Analyst extension. Update GlobeServer Cache tool works on a single layer or on all layers of the Service. There are two modes of operation: Recreate Empty TilesOnly tiles that are empty (have been deleted on disk), or that are new because the cache extent has changed or because new layers have been added to the GlobeService, will be created. Existing tiles will be left unchanged. Recreate All TilesAll tiles, including existing tiles, will be replaced. Additionaly, new tiles will be added if a layers data extent has changed or new layers have been added to the GlobeService. Running update without specifying an extent will update the entire extent of the service being for the specied levels of detail.

94

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Update Map Server Cache: Updates an existing Map Service cache to replace missing tiles, overwrite outdated tiles, or add new tiles in new areas or, in the case of a multi-layer cache, from additional layers.
UpdateMapServerCache <server_name> <object_name> <data_frame> <layer;layer...> {constraining_extent} <levels;levels...> <Recreate Empty Tiles | Recreate All Tiles> {thread_count} {NONE | Antialiasing}

There are two modes of operation: Recreate Empty Tiles - Only tiles that are empty (have been deleted on disk), or that are new because the cache extent has changed or because new layers have been added to a multi-layer cache, will be created. Old tiles will be left unchanged. Recreate All Tiles - All tiles will be replaced and new tiles will be added if the extent has changed or if layers have been added to a mutli-layer cache. Before running this tool, congure the MapService to use as many instances as possible. This will dramatically decrease cache update time.

Server\ toolbox

95

ArcGIS Desktop extensions geoprocessing tools

3D Analyst toolbox
Contains tools to create and modify TIN and raster surfaces, then extract information and features from them.

3D Analyst toolbox

Conversion toolset

Contains a tool used to convert to and from a TIN. Layer 3D to Feature Class: Applies 3D properties associated with a feature layer and writes the result to a new multipatch feature class.
Layer3DToFeatureClass <in_feature_layer> <out_feature_class> {group_eld}

For an input feature to be converted, the result must support representation as a multipatch. For example, points symbolized as 3D markers can be converted whereas extruded points (for instance, vertical lines) cannot. Only certain 3D properties are applied: 3D symbols assigned to points, 3D symbols assigned to lines, extrusion applied to polygons, and texture down-sampling assigned to multipatches.

From Feature Class (Conversion) toolset

Contains tools used to convert from a feature class. Feature Class Z to ASCII: Exports 3D points, multipoints, polylines, or polygons to ASCII text les in xyz or generate format.
FeatureClassZToASCII <in_feature_class> <output_location> <out_le> {GENERATE | XYZ} {SPACE | COMMA} {AUTOMATIC | FIXED} {digits_after_decimal}

MultiPatch Footprint: Converts multipatches into polygons.

MultiPatchFootprint <in_feature_class> <out_feature_class>

The output polygons represent the 2D area covered by the multipatches when viewed from directly above.

From File (Conversion) toolset

Contains tools used to convert 3D features from les. ASCII 3D to Feature Class: Imports 3D features from one or more ASCII text les into a new output feature class.
Ascii3DToFeatureClass <input;input...> <XYZ | GENERATE> <out_feature_class> <MULTIPOINT | POINT | POLYLINE | POLYGON> {z_factor} {input_coordinate_system} {average_point_ spacing} {le_sufx}

Import 3D Files: Imports one or more 3D models into an output feature class.
Import3DFiles <in_les;in_les...> <out_feature_class> {ONE_ROOT_ONE_FEATURE | ONE_FILE_ ONE_FEATURE} {spatial_reference} {Z_IS_UP | Y_IS_UP}

99

3D Analyst toolbox

The output feature class must be placed in a geodatabase, rather than a shapele, if textures (images mapped on geometry faces) are to be preserved. GeoVRML is the only format that has a dened coordinate system. The other formats tend to use local coordinate systems (for instance, centered around 0,0,0). In the latter case, the output shapes will need to be georeferenced. When multiple les are input, the coordinate system of the rst le is used for all the les. For all formats other than GeoVRML, this will be Unknown. LAS to Multipoint: Imports one or more les in LAS format, the industry standard for LiDAR data, into a new multipoint feature class.
LASToMultipoint <input;input...> <out_feature_class> {average_point_spacing} {class_code;class_code...} {ANY_RETURNS | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | LAST_RETURNS} {keyword {Name};keyword {Name}...} {input_coordinate_system} {le_sufx}

The output multipoint feature class must be placed in a feature dataset. This is because the points are spatially sorted into areas (tiles) whose size is determined, in part, by the extent of the feature dataset. If you arent interested in importing points based on their return number or if all returns specied in the le(s) are set to zero because the points have been ltered or classied, select ANY_RETURNS.

From Raster (Conversion) toolset

Contains tools used to convert rasters to 3D features. Raster Domain: Writes the interpolation zone of the input raster surface into a new 3D polyline or 3D polygon feature class.
RasterDomain <in_raster> <out_feature_class> <LINE | POLYGON>

To create a polygon feature class based on the raster surfaces interpolation zone, use the POLYGON option. To create a polyline feature class based on the raster surfaces interpolation zone, use the LINE option. Raster to TIN: Creates a TIN from a raster dataset.
RasterTin <in_raster> <out_tin> {z_tolerance} {max_points} {z_factor}

The default maximum allowable difference between the height of the input raster and the height of the output TIN is 1/10 of the z range of the input raster.

100

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

From Terrain (Conversion) toolset

Contains tools used to convert from terrains. Terrain to Raster: Converts a terrain dataset into a raster.

3D Analyst toolbox

TerrainToRaster <in_terrain> <out_raster> {FLOAT | INT} {LINEAR | NATURAL_NEIGHBORS} {OBSERVATIONS 250 | CELLSIZE 10} {resolution}

The cellsize parameter controls the horizontal resolution of the output raster. The resolution parameter indicates which pyramid level of the terrain to use for conversion. Pyramid levels are dened using z-tolerance, which represents the approximate vertical accuracy relative to the full resolution data. To extract a subset of the terrain, dene the extent using the geoprocessing environment settings. Terrain to TIN: Converts a terrain dataset to a le-based TIN.
TerrainToTin <in_terrain> <out_tin> {resolution} {max_nodes} {TRUE | FALSE}

Dene the extent of the output TIN using the geoprocessing environment extent setting. Use an extent and pyramid level that are not likely to be too large for a TIN. While the maximum size of a TIN that can be used under Win32 is between 15 to 20 million nodes, its recommended to cap the size at a few million. Triangulated surfaces larger than this are best represented by terrain datasets.

From TIN (Conversion) toolset

Contains tools used to convert from TINs. TIN Domain: Extracts the interpolation zone from an input TIN into an output feature class.
TinDomain <in_tin> <out_feature_class> <LINE | POLYGON>

Produces a 3D polygon or polyline feature class. To create a polygon feature class based on the TINs area, use the POLYGON option. To create a polyline feature class based on the TINs extent, use the LINE option. TIN Edge: Extracts the triangle edge from an input TIN into an output feature class.
TinEdge <in_tin> <out_feature_class> {DATA | SOFT | HARD | ENFORCED | REGULAR | OUTSIDE | ALL}

Produces a line feature class whose lines are extracted edges of the input TIN. Use the optional {edge_type} argument to extract a specic type of triangle edge. TIN Line: Writes the hard and soft breaklines from a TIN into a new 3D polyline feature class.
TinLine <in_tin> <out_feature_class> {code_eld} 101

3D Analyst toolbox

The input TIN must have some breaklines for this tool to produce output line features. If you want to convert TIN edges into line features, regardless of whether or not they belong to breaklines, use the TIN Edge tool. TIN Node: Extracts nodes from an input TIN into an output feature class.
TinNode <in_tin> <out_feature_class> {spot_eld} {tag_eld}

Produces a 2D or 3D point feature class whose points are extracted from nodes of the input TIN. Indicate a spot_eld to create a 2D feature class. Omit spot_eld to create a 3D feature class. TIN Polygon Tag: Extracts polygon tag information from an input TIN into an output feature class.
TinPolygonTag <in_tin> <out_feature_class> {tag_eld}

Polygons will be generated for all TIN triangles that have tag values. TIN to Raster: Converts a TIN to a raster.
TinRaster <in_tin> <out_raster> {FLOAT | INT} {LINEAR | NATURAL_NEIGHBORS} {OBSERVATIONS 250 | CELLSIZE 10} {z_factor}

TIN to Raster interpolates cell z-values from the input TIN at the specied resolution or sampling interval to produce the output raster.
102 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The data_type option determines the data type of the output raster. Floating point preserves the accuracy of z-values, possibly at the expense of disk storage space. On average, integer grids require less storage space than oating-point grids when dealing with terrain data. If the accuracy requirements of your z-values are such that they can be represented by integer data, you may want to consider using the INT option. TIN Triangle: Extracts triangles as polygons from an input TIN into an output feature class.
TinTriangle <in_tin> <out_feature_class> {PERCENT | DEGREE} {z_factor} {HILLSHADE} {tag_eld}

3D Analyst toolbox

Produces a polygon feature class whose polygons are constructed from the input TINs triangles.

To KML (Conversion) toolset

Contains tools used to convert to Keyhole Markup Language (KML) les. Layer to KML: Converts an in-memory or le-based feature or raster layer into a KML le containing a translation of ESRI geometries and symbology.
LayerToKML <layer> <out_kml_le> <layer_output_scale> {NO_COMPOSITE | COMPOSITE} {boundary_box_extent} {image_size} {dpi_of_client}

The output KML le cannot already exist. You can reduce the size of the output KMZ document if your layer has a scale-dependent renderer and you choose an appropriate layer_output_scale. Map to KML: Converts an in-memory map or map document into a KML le containing a translation of ESRI geometries and symbology.
MapToKML <in_map_document> <data_frame> <out_kml_le> <map_output_scale> {NO_COMPOSITE | COMPOSITE} {VECTOR_TO_IMAGE | VECTOR_TO_VECTOR} {extent_to_export} {image_size} {dpi_ of_client}

The output KML le cannot already exist. You can reduce the size of the output KMZ document if your layer has a scale-dependent renderer and you choose an appropriate layer_output_scale.

Functional Surface toolset

Contains tools to produce output providing knowledge about height information that is contained in surfaces. Interpolate Shape: Interpolates z-values for a feature class based on an underlying surface.
InterpolateShape <in_surface> <in_feature_class> <out_feature_class> {sample_distance} {z_factor} {method}

103

3D Analyst toolbox

Interpolates a 3D feature class from an input 2D feature class and a surface with the overlapping extent. When using the natural neighbors interpolation option, make sure to specify a reasonable sample distance. This usually falls between 0.5 and 1.0 times the average point spacing of the data used to build the TIN. Line of Sight: Calculates the visibility across a surface between points.
LineOfSight <in_surface> <in_line_feature_class> <out_los_feature_class> {out_obstruction_feature_class} {use_curvature} {use_refraction} {refraction_factor}

The observer is the point from which visibility is determined. The target is the opposite end of the line, to which visibility is determined. Only the endpoints of the input line are used to determine target visibility. Surface Length: Calculates the surface length of each line in a feature class based on a raster or TIN surface.
SurfaceLength <in_surface> <in_feature_class> {out_length_eld} {sample_distance} {z_factor}

Use a smaller sampling distance to increase the accuracy of the surface length calculations. Use {out_length_eld} to give the length eld a custom name. Surface Spot: Calculates surface values for each point of a point feature class by interpolating from a raster or TIN surface.
SurfaceSpot <in_surface> <in_feature_class> {out_spot_eld} {z_factor} {method}

Ensure the input surface and the input feature class have overlapping extents. Use the {z_factor} argument to convert the output eld to the desired units. Surface Volume: Calculates the area and volume of a functional surface above or below a given reference plane.
SurfaceVolume <in_surface> {out_text_le} {ABOVE | BELOW} {base_z} {z_factor} 104 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

3D Analyst toolbox

To determine the volume of an isolated portion of a TIN surface, use the Add Feature Class To TIN tool to add a clip polygon dening your study area. Using a z factor is essential for correct volume calculations when the surface z units are expressed in a different unit of measure than the ground units. Using a z factor does not modify the original data.

Raster Interpolation toolset

Contains tools to create a raster surface from point features. IDW: Interpolates a surface from points using an inverse distance weighted (IDW) technique.
IDW <in_point_features> <z_eld> <out_raster> {cell_size} {power} {search_radius} {in_barrier_polyline_features}

The barriers option is used to specify the location of linear features known to interrupt the surface continuity. These features do not have z-values. Cliffs, faults, or embankments are typical examples of barriers. Barriers limit the selected set of the input sample points used to interpolate output z-values to those samples on the same side of the barrier as the current processing cell. The output value for a cell using IDW is limited to the range of the values used to interpolate. Because IDW is a weighted distance average, the average cannot be greater than the highest or less than the lowest input. Therefore, it cannot create ridges or valleys if these extremes have not already been sampled (Watson and Philip 1985). The best results from IDW are obtained when sampling is sufciently dense with regard to the local variation you are attempting to simulate. If the sampling of input points is sparse or uneven, the results may not sufciently represent the desired surface (Watson and Philip 1985). Krige: Interpolates a surface from points using kriging.
Kriging <in_point_features> <z_eld> <out_surface_raster> <semiVariogram_props> {cell_size} {search_radius} {out_variance_prediction_raster}

The universal kriging types (linear with linear drift and linear with quadratic drift) assume that there is a structural component present and that the local trend varies from one location to another. The advanced parameters allow control of the semivariogram used for Kriging. A default value for Lag size is initially set to the default output cell size. For major range, partial sill, and nugget, a default value will be calculated internally if nothing is specied. Low values within the output variance of prediction raster indicate a high degree of condence in the predicted value. High values may indicate a need for more data points. Natural Neighbor: Interpolates a surface from points using a natural neighbor technique.
NaturalNeighbor <in_point_features> <z_eld> <out_raster> {cell_size}

The Natural Neighbor tool can efciently handle large numbers of input points. Other interpolators may have difculty with large point datasets. Spline: Interpolates a surface from points using a minimum curvature spline technique.
Spline <in_point_features> <z_eld> <out_raster> {cell_size} {REGULARIZED | TENSION} {weight} {number_points}

The resulting smooth surface from Spline passes exactly through the input points.
105

 The REGULARIZED option of Spline usually produces smoother surfaces than those created with the TENSION option. For the REGULARIZED option, higher values used for the Weight parameter produce smoother surfaces. The values entered for this parameter must be equal to or greater than zero. Typical values that are used are 0, 0.001, 0.01, 0.1, and 0.5. The Weight is the square of the parameter, referred to in the literature as tau (t). For the TENSION option, higher values entered for the Weight parameter result in somewhat coarser surfaces but with surfaces that closely conform to the control points. The values entered have to be equal to or greater than zero. Typical values are 0, 1, 5, and 10. The Weight is the square of the parameter, referred to in the literature as phi (). The greater the value of Number of Points, the smoother the surface of the output raster. Topo to Raster: Generates a hydrologically correct raster dataset of elevation.
TopoToRaster <feature_layer{Field} {Type};feature_layer{Field} {Type}...> <out_surface_ raster> {cell_size} {extent} {Margin} {minimum_z_value} {maximum_z_value} {ENFORCE | NO_ENFORCE | ENFORCE_WITH_SINK} {CONTOUR | SPOT} {maximum_iterations} {roughness_ penalty} {discrete_error_factor} {vertical_standard_error} {tolerance_1} {tolerance_2} {out_stream_features} {out_sink_features} {out_diagnostic_le} {out_parameter_le}

3D Analyst toolbox

Topo to Raster will only use four input data points for the interpolation of each output cell. All additional points are ignored. If too many points are encountered by the algorithm, an error may occur indicating the point dataset has too many points. The maximum number of points that can be used is nrows*ncols, where nrows is the number of rows in the output raster and ncols is the number of columns. Stream data always takes priority over point or contour data; therefore, elevation data points that conict with descent down each stream are ignored. Stream data is a powerful way of adding topographic information to the interpolation, further ensuring the quality of the output DEM. Some typical values for the Tolerance 1 and Tolerance 2 settings are: For point data at 1:100,000 scale, use 5.0 and 200.0. For less dense point data at up to 1:500,000 scale, use 10.0 and 400.0. For contour data with contour spacing of 10, use 5.0 and 100.0. Topo to Raster by File: Interpolates a hydrologically correct surface from point, line, and polygon data using parameters specied in a le.
TopoToRasterByFile <in_parameter_le> <out_surface_raster> {out_stream_features} {out_sink_features}

The input data identies the input datasets and, where applicable, elds. There are six types of input: contours, points, sinks, streams, lakes, and boundaries. As many inputs can be used as desired, within reason. The order in which the inputs are entered does not have any bearing on the outcome. <Path> indicates a path to a dataset, <Item> indicates a eld name, and <#> indicates a value to be entered.\ The parameter le is structured with the input datasets listed rst, followed by the various parameter settings, then the output options. Inputs: ContoursContour line dataset with item containing height values.
Contour <Path> <Item>

PointsPoint dataset with item containing height values.

Point <Path> <Item>

SinksPoint dataset containing sink locations. If the dataset has elevation values for the sinks, specify that eld name as the <Item>. If only the locations of the sinks are to be used, use NONE for <Item>.
Sink <Path> <Item>

StreamsStream line dataset. Height values are not necessary.

Stream <Path> 106 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 LakesLake polygon dataset. Height values are not necessary.

Lake <Path>

BoundaryBoundary polygon dataset. Height values are not necessary.

Boundary <Path>

Parameter settings: EnforceControls whether drainage enforcement is applied.

ENFORCE <ON | OFF | ON_WITH_SINK>

3D Analyst toolbox

DatatypePrimary type of input data.

DATATYPE <CONTOUR | SPOT>

IterationsThe maximum number of iterations the algorithm performs.

ITERATIONS <#>

Roughness PenaltyThe measure of surface roughness.

ROUGHNESS_PENALTY <#>

Discretization Error FactorThe amount to adjust the data smoothing of the input data into a raster.
DISCRETE_ERROR_FACTOR <#>

Vertical Standard ErrorThe amount of random error in the z-values of the input data.
VERTICAL_STANDARD_ERROR <#>

TolerancesThe rst reects the accuracy of elevation data in relation to surface drainage, and the other prevents drainage clearance through unrealistically high barriers.
TOLERANCES <#> <#>

Z-LimitsLower and upper height limits.

ZLIMITS <#> <#>

ExtentMinimum x, minimum y, maximum x, and maximum y coordinate limits.

EXTENT <#> <#> <#> <#>

Cell SizeThe resolution of the nal output raster.

CELL_SIZE <#>

MarginDistance in cells to interpolate beyond the specied output extent and boundary.
MARGIN <#>

Output options: Output Stream FeaturesOnly use if Output stream polyline features is set in the Topo to Raster by File dialog box.
OUT_STREAM

Output Sink FeaturesOnly use if Output remaining sink point features is set in the Topo to Raster by File dialog box.
OUT_SINK

Output Diagnostics FileThe location and name of the diagnostics le.

OUT_DIAGNOSTICS <Path>

Trend: Interpolates a surface from points using a trend technique.

Trend <in_point_features> <z_eld> <out_raster> {cell_size} {order} {LINEAR | LOGISTIC} {out_rms_le}

As the order of the polynomial is increased, the surface being tted becomes progressively more complex. A higher-order polynomial will not always generate the most accurate surface; it is dependent on the data. The optional RMS le output contains information on the root mean square (RMS) error of the interpolation. This information can be used to determine the best value to use for the polynomial order by changing the order value until you get the lowest RMS error. For the LOGISTIC option, the z-value eld of input point features should have codes of 0 and 1.

107

Raster Math toolset

Contains the tools used to perform mathematics with raster datasets. Divide: Divides the values of two inputs on a cell-by-cell basis.

3D Analyst toolbox

Divide <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant for Divide. When a number is divided by zero, the output result is NoData. If both inputs are integers, then Divide performs an integer division and the output result is an integer. For example, if 3 is to be divided by 2, the output is 1. If either input is of oating-point type, then Divide performs a oating-point division, and the result is a oating-point value. For example, if 3 is divided by 2.0, the output is 1.5. Float: Converts each cell value of a raster dataset into a oating-point value.
Float <in_raster_or_constant> <out_raster>

Input values are integers and can be positive or negative. Int: Converts each cell value of a raster dataset into an integer value through truncation.
Int <in_raster_or_constant> <out_raster>

If rounding is preferred rather than truncating, add a 0.5 input raster prior to performing Int. The difference between the Round Down and Int functions is that Int always truncates a number:
int on 1.5 becomes 1 int on -1.5 becomes -1

while for the same two values, Round Down returns

round down on 1.5 becomes 1.0 round down on -1.5 becomes -2.0

A second difference between the two functions is that Round Down outputs oating-point values, and Int outputs integer values. Minus: Subtracts the values of the second input from the values of the rst input.
Minus <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

108

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

3D Analyst toolbox

The order of input is relevant in the subtraction expression. Plus: Adds the values of two raster datasets on a cell-by-cell basis.
Plus <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is irrelevant in the addition expression. Times: Multiplies the values in raster datasets on a cell-by-cell basis.
Times <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is irrelevant in the multiplication expression.

Raster Reclass toolset

Contains tools to alter the classes within a raster dataset. Lookup: Creates a new raster dataset by looking up values found in another eld in the table of the input raster dataset.
Lookup <in_raster> <lookup_eld> <out_raster>

If the lookup eld is a numeric type, the values of that eld will be written to the output raster attribute table as Value. Other items in the input raster attribute table will not be transferred to the output raster attribute table. For example, an attribute table of input raster with numeric eld Attr1:
Value Count Attr1 1 294 1 2 345 8 3 654 3

Output attribute table from Lookup on Attr1 eld:

Value Count 1 294 3 654 8 345

Reclass by ASCII File: Reclassies (or changes) the values of the input cells of a raster dataset by using an ASCII remap le.
ReclassByASCIIFile <in_raster> <in_remap_le> <out_raster> {DATA | NODATA}

109

 The output raster will always be of integer type. If the output assignment values in the ASCII le are oating-point values, an error message will be returned and the program will halt. Reclass by Table: Reclassies (or changes) the values of the input cells of a raster dataset by using a remap table.
ReclassByTable <in_raster> <in_remap_table> <from_value_eld> <to_value_eld> <output_value_eld> <out_raster> {DATA | NODATA}

3D Analyst toolbox

The from value eld, to value eld, and output value eld are the eld names in the table that dene the remapping. To reclassify individual values, use a simple remap table of two items. The rst item identies the value to reclassify, and the other item the value to assign it. Set the to value eld to the same as the from value eld. The value to assign to the output is output value eld. To reclassify ranges of values, the remap table must have items dening the start and end of each range, along with the value to assign the range. The item dening the start of the range is the from value eld, and the value dening the end of the range is the to value eld. The value to assign to the output is output value eld. The remap table can be an INFO table, a .dbf le, an Access table, or a text le. The values in the from and to elds can be any numerical item. The assignment values in the output eld must be integers. Values in the from eld of the table must be sorted in ascending order and should not overlap. Reclassify: Reclassies (or changes) the value in a raster dataset.
Reclassify <in_raster> <reclass_eld> <remap> <out_raster> {DATA | NODATA}

The remap table can be stored with the Save button. The Load button allows previously created remap tables to be used. Only remap tables created by the tool should be used in Reclassify. If running the Reclassify tool as part of a model within a ModelBuilder window, run the tools before the Reclassify tool in the model rst. This will allow the values for the input raster to display properly in the Reclassication dialog box. Slice: Slices a range of values of the input cells of a raster by zones of equal interval, equal area, or by natural breaks.
Slice <in_raster> <out_raster> <number_zones> {EQUAL_INTERVAL | EQUAL_AREA | NATURAL_ BREAKS} {base_output_zone}

If a mask has been set, those cells that have been masked out will receive NoData on the output slice raster.

Raster Surface toolset

Contains tools to analyze the surface of a raster dataset. Aspect: Identies the downslope direction of the maximum rate of change in value from each cell to its neighbors.
Aspect <in_raster> <out_raster>

Aspect is the direction of the maximum rate of change in the z-value from each cell in a raster surface.

110

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 Aspect is expressed in positive degrees from 0 to 359.9, measured clockwise from the north. Cells in the input raster of zero slope (for example, at) are assigned an aspect of -1. Contour: Creates contours or isolines from a raster dataset surface.
Contour <in_raster> <out_polyline_features> <contour_interval> {base_contour} {z_factor}

3D Analyst toolbox

Smoother but less accurate contours may be obtained by rst performing a Neighborhood Focal Statistics operation with the mean option on the input raster. A base contour is used, for example, when you want to create contours every 15 meters, starting at 10 meters. Here, 10 would be used for the base contour, and 15 would be the contour interval. The values to be contoured would be 10, 25, 40, 55, and so on. Specifying a base contour does not prevent contours from being created above or below that value. Contour List: Creates contours or isolines from a list of contour values.
ContourList <in_raster> <out_polyline_features> <contour_values;contour_values...>

Smoother but less accurate contours may be obtained by rst performing a Neighborhood Focal Statistics operation with the mean option on the input raster. Curvature: Calculates the curvature of a raster surface, optionally including prole and plan curvature.
Curvature <in_raster> <out_curvature_raster> {z_factor} {out_prole_curve_raster} {out_plan_curve_raster}

The primary output is the curvature of the surface on a cell-by-cell basis, as tted through that cell and its eight surrounding neighbors. Curvature is the second derivative of the surface, or the slope of the slope. Two optional output curvature types are possible; the prole curvature is in the direction of the maximum slope, and the plan curvature is perpendicular to the direction of the maximum slope. A positive curvature indicates that the surface is upwardly convex at that cell. A negative curvature indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. In the prole output, a negative value indicates that the surface is upwardly convex at that cell. A positive prole indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. In the plan output, a positive value indicates that the surface is upwardly convex at that cell. A negative plan indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. Units of the Curvature output raster, as well as the units for the optional output prole curve raster and output plan curve raster, are one over 100 z units, or 1/100 (z units). The reasonably expected values of all three output rasters for a hilly area (moderate relief) may differ from about -0.5 to 0.5, while for the steep, rugged mountains (extreme relief), the values may vary between -4 and 4. Cut/Fill: Calculates cut and ll areas.
CutFill <in_before_surface> <in_after_surface> <out_raster> {z_factor}

The Cut/Fill tool enables you to create a map based on two input surfaces (before and after), displaying the areas and volumes of surface materials that have been modied by the addition or removal of surface material. Negative z-values indicate regions of the input before raster surface that have been lled; positive regions indicate cuts.
111

 To get accurate Cut/Fill results, the z units should be the same as the x,y ground units. This ensures that the resulting volumes are meaningful cubic measures (for example, cubic meters). If they are not the same, use a z-factor to convert z units to x,y units. For example, if your x,y units are meters and your z units are feet, you could specify a z-factor of 0.3048 to convert feet to meters.

3D Analyst toolbox

Hillshade: Computes hillshade values for a raster surface by considering the illumination angle and shadows.
HillShade <in_raster> <out_raster> {azimuth} {altitude} {NO_SHADOWS | SHADOWS} {z_factor}

The Hillshade tool creates a shaded relief raster from a raster. The illumination source is considered at innity. Two types of shaded relief rasters can be output. Having model shadows unchecked outputs a raster that only considers the local illumination angle. Having model shadows checked outputs one that considers the effects of both the local illumination angle and shadow. Observer Points: Identies exactly which observer points are visible from each surface location within the raster dataset.
ObserverPoints <in_raster> <in_observer_point_features> <out_raster> {z_factor} {FLAT_EARTH | CURVED_EARTH} {refractivity_coefcient}

The visibility of each cell center is determined by comparing the altitude angle to the cell center with the altitude angle to the local horizon. The local horizon is computed by considering the intervening terrain between the point of observation and the current cell center. If the point lies above the local horizon, it is considered visible. Slope: Identies the rate of maximum change in z-value from each cell.
Slope <in_raster> <out_raster> {DEGREE | PERCENT_RISE} {z_factor}

Slope is the rate of maximum change in z-value from each cell. The use of a z-factor is essential for correct slope calculations when the surface z units are expressed in units different from the ground x,y units. Degree of slope is a value between 0 and 90. Viewshed: Determines the raster dataset surface locations visible to a set of observer features.
Viewshed <in_raster> <in_observer_features> <out_raster> {z_factor} {FLAT_EARTH | CURVED_EARTH} {refractivity_coefcient}

The visibility of each cell center is determined by comparing the altitude angle to the cell center with the altitude angle to the local horizon. The local horizon is computed by considering the intervening terrain between the point of observation and the current cell center. If the point lies above the local horizon, it is considered visible.

112

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Terrain toolset

Contains tools used to create and manage terrain datasets. Add Feature Class to Terrain: Adds one or more feature classes to a terrain dataset.

3D Analyst toolbox

AddFeatureClassToTerrain <in_terrain> <in_feature_class {height_eld} {SF_type} {group} {min_resolution} {max_resolution} {overview} {embedded} {embedded_name} {embedded_ elds};in_feature_class {height_eld} {SF_type} {group} {min_resolution} {max_ resolution} {overview} {embedded} {embedded_name} {embedded_elds}...>

The feature classes must reside in the same feature dataset as the terrain. Adding a new feature class to a terrain invalidates it. Use the Build Terrain tool after adding feature classes. The input terrain cannot be registered as versioned. The input feature class cannot be registered as versioned. Add Terrain Points: Adds multipoints to an embedded terrain feature class by appending them or by using them to replace existing multipoints that fall within the same extent.
AddTerrainPoints <in_terrain> <terrain_feature_class> <in_feature_class> {APPEND | REPLACE}

This tool functions only on feature classes embedded in a terrain. The terrain and the embedded feature class must already exist. If you want to add points to a regular feature class potentially referenced by a terrain but not embedded in it, use the Append tool. Adding points to an embedded feature class will invalidate the terrain. Run Build Terrain after adding points. Add Terrain Pyramid Level: Adds a new pyramid level to an existing terrain dataset.
AddTerrainPyramidLevel <in_terrain> <ZTOLERANCE> <pyramid_level_denition;pyramid_ level_denition...>

Adding a new pyramid level to a terrain invalidates it. Use the Build Terrain tool after adding a pyramid level. The input terrain cannot be registered as versioned. Build Terrain: Performs the necessary steps to make a terrain usable after its initially dened.
BuildTerrain <in_terrain>

Will perform the work necessary to update the terrain relative to any edits. These include modications to terrain schema (for example, feature class participation, pyramid denition) or to geometry in associated feature classes. Its more efcient to make a collection of edits followed by one build rather than running a build after each individual edit. Change Terrain Reference Scale: Changes the reference scale used by a terrain pyramid level.
ChangeTerrainReferenceScale <in_terrain> <old_refscale> <new_refscale>

This tool is useful when an existing reference scale associated with a terrain pyramid level is known to be inappropriate and needs to be reset. To add or remove a pyramid level, rather than change the denition of an existing pyramid level, use the Add Terrain Pyramid or Remove Terrain Pyramid tools. Create Terrain: Creates a new terrain dataset inside the specied feature dataset.
CreateTerrain <in_feature_dataset> <out_terrain_name> <average_point_spacing> {max_ overview_size} 113

3D Analyst toolbox

This tool is geared toward data automation for use in scripts and ModelBuilder. Consider using the Terrain wizard in ArcCatalog for interactively creating a new terrain. The Average Point Spacing parameter needs to be determined by the data that will be used to build the terrain. This value doesnt need to be exact but should represent a good approximation. If the data has been gathered at signicantly different densities from one location to another, give more weight to the smaller spacing. Remove Feature Class from Terrain: Removes reference to a feature class participating in a terrain dataset.
RemoveFeatureClassFromTerrain <in_terrain> <feature_class>

This tool does not delete the feature class. Rather, it eliminates the terrain datasets reference to it. If the feature class is embedded in the terrain, it will be extracted and dereferenced. The terrain will need to be rebuilt using Build Terrain after using this tool. Remove Terrain Points: Removes points within an area of interest from one or more embedded feature classes.
RemoveTerrainPoints <in_terrain> <data_source;data_source...> <aoi_extents>

This tool functions only on feature classes embedded in a terrain. The terrain and at least one embedded feature class must already exist. A rectangular area of interest (AOI) is required. This denes the area in the embedded feature class where multipoint vertices will be deleted. If a multipoint crosses the AOI boundary, only those vertices within the boundary will be deleted. Remove Terrain Points looks for an existing edit session to piggy-back on. This supports undo if the edit session was initialized to support undo (for example, using the Editor inside ArcMap). If theres no edit session, it starts and stops one itself, in which case there is no chance for an undo. Removing points from an embedded feature class will invalidate the terrain. Run Build Terrain after adding points. Remove Terrain Pyramid Level: Removes a pyramid level from a terrain dataset.
RemoveTerrainPyramidLevel <in_terrain> <resolution>

You have the option of removing any but the highest resolution pyramid (level 0). When used in an ArcSDE database, the input terrain cannot be registered as versioned.

TIN Creation toolset

Contains tools to create and edit TINs. Create TIN: Creates an empty TIN with an extent based on an input geographic dataset.
CreateTin <out_tin> <spatial_reference>

The output TIN cannot already exist. Use the Import button on the spatial reference dialog box to browse for the region of the TIN you are creating, or when using the command line, indicate a dataset with a coordinate system close to that of the region of the TIN you are creating. To add features to the output TIN, use the Edit TIN tool. Delineate TIN Data Area: Denes the data area or interpolation zone of a TIN based on triangle edge length.
DelineateTinDataArea <in_tin> <max_edge_length> {PERIMETER_ONLY | ALL}

114

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

3D Analyst toolbox

This tool modies the input TIN. If you would prefer not to modify the input, use the standard Copy tool and operate on the copied TIN. The value for <max_edge_length> is best determined from the average spacing of nodes in the TIN within areas that are considered to be valid data zones. Provide a value that is larger than the average spacing. Edit TIN: Adds feature classes to an existing TIN and creates surface features of a TIN based on an input feature class.
EditTin <in_tin> <in_feature_class {height_eld} {tag_eld} {SF_type} {use_z}; in_feature_class {height_eld} {tag_eld} {SF_type} {use_z}...>

Multiple feature classes can be added at the same time. Before features can be added to a TIN, the TIN must be dened using the Create TIN tool. Features may be added to a newly created or existing TIN.

TIN Surface toolset

Contains tools to analyze the surface of a TIN dataset. Decimate TIN Nodes: Produces a TIN that is a generalized version of another.
DecimateTinNodes <in_tin> <out_tin> <method> {FALSE | TRUE}

A subset of nodes from an input TIN is selected to produce the new TIN. Extrude Between: Converts polygons into multipatches by extruding them between two input TINs.
ExtrudeBetween <in_tin1> <in_tin2> <in_feature_class> <out_feature_class>

115

3D Analyst toolbox

The output multipatches are written to a new feature class. The input TINs and polygons must all overlap in horizontal extent to produce any output. Interpolate Polygon to Multipatch: Creates surface-conforming areal features by extracting those portions of a surface that fall within the extent of input polygons as multipatches.
InterpolatePolyToPatch <in_tin> <in_feature_class> <out_feature_class> {max_strip_size} {z_factor} {area_eld} {surface_area_eld}

The attributes from the input features are copied to the output. Planimetric and surface area is calculated for each feature and added as attribution to the output. Convert polygons to multipatches if you are having display problems with polygons conforming to a surface. The max_strip_size value must be three or larger. The recommended range is between 128 and 2048. TIN Aspect: Extracts aspect information from an input TIN into an output feature class.
TinAspect <in_tin> <out_feature_class> {class_breaks_table} {aspect_eld}

Aspect is expressed in degrees. TIN Contour: Creates a feature class containing a set of contours generated from a functional surface.
TinContour <in_tin> <out_feature_class> <interval> {base_contour} {contour_eld} {contour_eld_precision} {index_interval} {index_interval_eld} {z_factor}

Use the interval and base contour options to tailor the extent and resolution of the output feature class. Use the out contour eld as the height source for displaying the contours in 3D. TIN Difference: Calculates the volumetric difference between two TINs.
TinDifference <in_tin1> <in_tin2> <out_feature_class>

The input TINs need to overlap in horizontal extent. Its best if the horizontal and vertical coordinate systems of the input TINs are the same.

116

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

TIN Polygon Volume: Calculates the volumetric and surface area between polygons of an input feature class and a TIN surface.
TinPolygonVolume <in_tin> <in_feature_class> <in_height_eld> {BELOW | ABOVE} {out_volume_eld} {surface_area_eld}

3D Analyst toolbox

The input polygons and TIN need to overlap in horizontal extent for surface area or volume to be calculated. TIN Slope: Calculates the slope of the surface as the maximum rate of change in elevation across each triangle.
TinSlope <in_tin> <out_feature_class> {PERCENT | DEGREE} {class_breaks_table} {slope_eld} {z_factor}

Use the class_breaks_table parameter to constrain slope information into specic break intervals of the output feature class. Units are only honored when using a class breaks table.

117

Data Interoperability toolbox

Contains tools to import and export data with the ArcGIS Data Interoperability extension.
Quick Export: Converts one or more input feature classes or feature layers into any format supported by the ArcGIS Data Interoperability extension.
QuickExport <input;input...> <output>

This tool is used either to export data from ArcGIS or as the nal step in a model or script where the destination data is external to ArcGIS. During the export, no change to the data model is made; if this is desired, a custom data export tool should be created and used. Quick Import: Converts data from any format supported by the ArcGIS Data Interoperability extension into a personal geodatabase.
QuickImport <input> <output>

Data Interoperability toolbox

119

This tool is used either to bring data into the ArcGIS environment or as the beginning point in a model or script where data from outside ArcGIS will be processed. The feature classes generated depend on the input data. For instance, if you import two MapInfo MIF/MID les, two feature classes will be created. This tool creates a new personal geodatabase and will not append to an existing one. The feature classes generated from the imported data can be accessed using the Select Data tool on the output staging personal geodatabase. As data is imported, no changes to the data model are made. To transform the data model during import, a Custom Data Import Tool should be created and used.

Geostatistical Analyst toolbox

Contains tools for exploratory spatial data analysis.
Calculate Z-Value: Uses the interpolation model in a geostatistical layer to predict a value at a single location.
GACalculateZValue <in_geostat_layer> <point_coord>

This tool is generally used in a model or in scripting. Create Geostatistical Layer: Uses an existing geostatistical layer to create a new layer, which includes a new feature dataset or variable.
GACreateGeostatisticalLayer <in_ga_model_source> <in_datasets> <out_layer>

Geostatistical model source is either a geostatistical layer or a geostatistical model (XML). The dataset used to create the geostatistical layer is persisted in the layer. However, when an XML version is saved, only the model parameters are saved and not the dataset information. GA Layer to Contour: Exports a geostatistical layer to contours.
GALayerToContour <in_geostat_layer> <CONTOUR | FILLED CONTOUR> <out_feature_class>

Geostatistical Analyst toolbox

You can choose to display the contours in either draft or presentation quality. CONTOUR is the contour or isoline representation of the geostatistical layer. You can display the lines in either draft or presentation quality. FILLED_CONTOUR is the polygon representation of the geostatistical layer. It is assumed for the graphical display that the values between each contour line are the same for all locations within the polygon. You can display the lines in either draft or presentation quality. GA Layer to Grid: Exports a geostatistical layer to a grid.
GALayerToGrid <in_geostat_layer> <out_surface_grid> <cell_size> <points_per_block_horz> <points_per_block_vert>

The output grid will be created at the cell size specied by output cell size. Select the number of predictions for each cell in the horizontal and vertical directions for block interpolation. GA Layer to Points: Exports a geostatistical layer to points.
GALayerToPoints <in_geostat_layer> <in_locations> {z_eld} <out_feature_class>

If a eld is left blank, predictions will be made at the location points. If a eld is selected, predictions will be made and compared to the values in the Z_value_eld and a validation analysis is performed. Get Model Parameter: Gets model parameter value from an existing geostatistical model source.
GAGetModelParameter <in_ga_model_source> <model_param_xpath>

This tool is generally used in a model or in scripting. The geostatistical model source is either a geostatistical layer or a geostatistical model (XML). Moving Window Kriging: Automatically estimates the kriging model for each neighborhood as the kriging interpolation moves through all the location points.
GAMovingWindowKriging <in_ga_model_source> <in_datasets> <in_locations> <neighbors_max> <out_feature_class> {cell_size} {out_surface_grid}

121

 The geostatistical model source is either a geostatistical layer or a geostatistical model (XML). The input dataset must have more than 10 points. However, it is recommended that it has more than 300 points. Neighborhood Selection: Creates a layer of points based on a user-dened neighborhood.
GANeighborhoodSelection <in_dataset> <out_layer> <point_coord> <neighbors_max> <neighbors_min> <minor_semiaxis> <major_semiaxis> <angle> {ONE SECTOR | FOUR SECTORS | FOUR SECTORS SHIFTED | EIGHT SECTORS}

Semivariogram Sensitivity: Varies the semivariogram parameters Nugget, Partial Sill, and Range to perform a sensitivity analysis.
GASemivariogramSensitivity <in_ga_model_source> <in_datasets> <in_locations> {nugget_span_percents} {nugget_calc_times} {partialsill_span_percents} {partialsill_calc_times} {range_span_percents} {range_calc_times} {minrange_span_percents} {minrange_calc_times} <out_table>

Geostatistical Analyst toolbox

122

The geostatistical model source is either a geostatistical layer or a geostatistical model (XML). Set Model Parameter: Sets parameter value in an existing geostatistical model source.
GASetModelParameter <in_ga_model_source> <model_param_xpath> <in_param_value> <out_ga_model>

This tool is generally used in a model or in scripting. The geostatistical model source is either a geostatistical layer or a geostatistical model (XML).

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Network Analyst toolbox

Contains tools for network analysis, building networks, and creating and editing turns. Analysis toolset

Contains tools used to perform analysis when using the Network Analyst extension. Add Field To Analysis Layer: Adds a eld to a network analysis layer.
AddFieldToAnalysisLayer <in_network_analysis_layer> <sub_layer> <eld_name> <LONG | TEXT | FLOAT | DOUBLE | SHORT | DATE | BLOB> {eld_precision} {eld_scale} {eld_length} {eld_alias} {NULLABLE | NON_NULLABLE}

Fields can be added to any of the sublayers of the network analysis layers. These elds can be updated with values and mapped to various eld mappings of the Add Locations tools to provide inputs to the network analysis layer. Add Locations: Adds network locations to a network analysis layer.
AddLocations <in_network_analysis_layer> <sub_layer> <in_table> <eld_mappings> <search_tolerance> {sort_eld} {source {snap type};source {snap type}...} {MATCH_TO_CLOSEST | PRIORITY} {APPEND | CLEAR} {NO_SNAP | SNAP} {snap_offset}

Add Locations can be run repeatedly to append locations to the same sublayer. For example, if stops for a route layer come from two feature classes, Add Locations can be called twice by using the APPEND option. Calculate Locations: Calculates the network location elds for a point feature class.
CalculateLocations <in_point_features> <in_network_dataset> <search_tolerance> <source {snap type};source {snap type}...> {MATCH_TO_CLOSEST | PRIORITY} {source_ID_eld} {source_OID_eld} {position_eld} {side_eld} {snap_X_eld} {snap_Y_eld} {distance_eld}

Network Analyst toolbox

Calculate locations should be used on point data that will be used more than once as input to a network analysis layer. Once the locations have been computed, the Add Locations tool allows the Use Network Location Fields instead of Geometry to be used to load the locations very quickly. Directions: Generates directions information for a network analysis layer with routes. The directions information is written to a le in either XML or text format.
Directions <in_network_analysis_layer> <XML | TEXT> <out_directions_le> <FEET | YARDS | MILES | METERS | KILOMETERS> {REPORT_TIME | NO_REPORT_TIME} {time_attribute}

Directions cannot be generated for analysis layer les (.lyr), only for analysis layers in the ArcMap table of contents or layers created in the same application session, script, or model as the Directions command is run. Make Closest Facility Layer: Makes a closest facility network analysis layer and sets its navigation properties.
MakeClosestFacilityLayer <in_network_dataset> <out_network_analysis_layer> <impedance_attribute> {TRAVEL_TO | TRAVEL_FROM} {default_cutoff} {default_number_ facilities_to_nd} {accumulate_attribute_name; accumulate_attribute_name...} {ALLOW_UTURNS | NO_UTURNS | ALLOW_DEAD_ENDS_ONLY} {restriction_attribute_name; restriction_attribute_name...} {USE_HIERARCHY | NO_HIERARCHY} {hierarchy_settings} {TRUE_LINES_WITH_MEASURES | NO_LINES | STRAIGHT_LINES | TRUE_LINES_WITHOUT_MEASURES}

A closest facility layer can be made on a network currently added to the ArcMap table of contents, or you can browse to a network dataset on disk. Hierarchy options can only be set if the input analysis network has a hierarchy attribute.
123

Make OD Cost Matrix Layer: Makes an origin and destination (OD) cost matrix layer and sets its navigation properties.
MakeODCostMatrixLayer <in_network_dataset> <out_network_analysis_layer> <impedance_attribute> {default_cutoff} {default_number_destinations_to_nd} {accumulate_attribute_name; accumulate_attribute_name...} {ALLOW_UTURNS | NO_UTURNS | ALLOW_DEAD_ENDS_ONLY} {restriction_attribute_name; restriction_attribute_name...} {USE_HIERARCHY | NO_HIERARCHY} {hierarchy_settings} {STRAIGHT_LINE | NO_LINES}

An OD cost matrix layer can be made on a network currently added to the ArcMap table of contents or on a network dataset on disk. Hierarchy options can only be set if the input analysis network has a hierarchy attribute. Make Route Layer: Makes a route network analysis layer and sets its navigation properties.
MakeRouteLayer <in_network_dataset> <out_network_analysis_layer> <impedance_attribute> {USE_INPUT_ORDER | FIND_BEST_ORDER} {PRESERVE_BOTH | PRESERVE_NONE | PRESERVE_ FIRST | PRESERVE_LAST} {NO_TIMEWINDOWS | USE_TIMEWINDOWS} {accumulate_attribute_ name;accumulate_attribute_name...} {ALLOW_UTURNS | NO_UTURNS | ALLOW_DEAD_ENDS_ONLY} {restriction_attribute_name;restriction_attribute_name...} {USE_HIERARCHY | NO_ HIERARCHY} {hierarchy_settings} {TRUE_LINES_WITH_MEASURES | NO_LINES | STRAIGHT_LINES | TRUE_LINES_WITHOUT_MEASURES} {start_date_time}

Network Analyst toolbox

124

The route layer can be made on a network currently added to the ArcMap table of contents or on a network dataset on disk. Hierarchy options can only be set if the input analysis network has a hierarchy attribute. Make Service Area Layer: Makes a service area network analysis layer and sets its navigation properties.
MakeServiceAreaLayer <in_network_dataset> <out_network_analysis_layer> <impedance_ attribute> {TRAVEL_FROM | TRAVEL_TO} {default_break_values} {SIMPLE_POLYS | DETAILED_ POLYS | NO_POLYS} {NO_MERGE | NO_OVERLAP | MERGE} {RINGS | DISKS} {NO_LINES | TRUE_LINES | TRUE_LINES_WITH_MEASURES} {OVERLAP | NON_OVERLAP} {NO_SPLIT | SPLIT} {excluded_source_ name;excluded_source_name...} {accumulate_attribute_name;accumulate_attribute_ name...} {ALLOW_UTURNS | NO_UTURNS | ALLOW_DEAD_ENDS_ONLY} {restriction_attribute_ name;restriction_attribute_name...} {TRIM_POLYS | NO_TRIM_POLYS} {poly_trim_value} {NO_LINES_SOURCE_FIELDS | LINES_SOURCE_FIELDS}

The service area layer can be made on a network currently added to the ArcMap table of contents or on a network dataset on disk. Hierarchy options can only be set if the input analysis network has a hierarchy attribute. Solve: Performs the analysis appropriate to the network analysis layer on which it is executed.
Solve <in_network_analsis_layer> {SKIP | HALT}

Be sure to specify all the parameters necessary to perform the analysis before running Solve.

Network Dataset toolset

Contains a tool used to build network datasets. Build Network: Reconstructs the network connectivity and attribute information of a network dataset.
BuildNetwork <in_nework_dataset>

You can build the network without starting ArcCatalog after making edits to the attributes or the features of a participating source feature class.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Turn Feature Class toolset

Contains tools used to build and edit turn data. Create Turn Feature Class: Creates a new turn feature class.
CreateTurnFeatureClass <out_location> <out_feature_class_name> {maximum_edges} {in_network_dataset} {in_template_feature_class} {spatial_reference} {cong_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

Increase Maximum Edges: Increases the maximum number of edges in a turn feature class.
IncreaseMaximumEdges <in_turn_features> <maximum_edges>

Once the maximum number of edges is increased, it cannot be decreased later. So only increase by the needed amount. Increasing the number of edges by one adds three additional elds to the turn feature class. Take care not to exceed the maximum number of elds allowed by the database being used. For example, personal geodatabase is limited to 255 elds. Populate Alternate ID Fields: Creates and populates additional elds on the turn feature class(es) in a network dataset that reference the edges by alternate IDs.
PopulateAlternateIDFields <in_network_dataset> <alternate_ID_eld_name>

The alternate IDs allow for another set of IDs that can help maintain the integrity of the turn features in case the source edges are being edited. Turn Table to Turn Feature Class: Converts an ArcView GIS turn table or ArcInfo Workstation coverage turn table to an ArcGIS turn feature class.
TurnTableToFeatureClass <in_turn_table> <reference_line_features> <out_feature_class_ name> {reference_nodes_table} {maximum_edges} {cong_keyword} {spatial_grid_1} {spatial_grid_2} {spatial_grid_3}

Network Analyst toolbox

The turn feature class to be created is placed in the same location as the reference line feature class. Update by Alternate ID Fields: Updates all the edge references in each turn feature class in a network dataset using an alternate ID eld.
UpdateByAlternateIDFields <in_network_dataset> <alternate_ID_eld_name>

Use Populate Alternate ID Fields tool before making edits to the input line features. Then this tool can be used to synchronize the turn features based on the alternate ID elds. Update by Geometry: Updates all the edge references in the turn table using the geometry of the feature.
UpdateByGeometry <in_turn_features>

This tool is useful when the IDs listed for the turn can no longer nd the edges participating in the turn.

125

Spatial Analyst toolbox

This toolbox provides tools for performing cell-based (raster) spatial analysis. Conditional toolset

Contains tools to control the output values based on the conditions placed on the input values. Con: Performs a conditional if/else evaluation on each of the input cells of an input raster.
Con <in_conditional_raster> <in_true_raster_or_constant> <out_raster> {in_false_raster_or_constant} {where_clause}

If the evaluation of the expression is nonzero, it is treated as true. If no input false raster or constant is specied, NoData will be assigned to those cells that do not result in True from the expression. From the command line, the {where_clause} should be enclosed in quotes, for example, Value > 5. Pick: Assigns output values using one of a list of rasters determined by the value of an input raster.
Pick <in_position_raster> <in_rasters_or_constants; in_rasters_or_constants...> <out_raster>

Pick is based on the order of the rasters in the input rasters or constant values. If the order of rasters changes, the results will change. The value of each cell of the input position raster determines which input raster (or constant value) will be used to obtain the output raster value. The input position raster should be a positive integer. If a cell value is zero or negative, the result will be NoData. If the cell value is larger than the number of rasters in the input rasters or constant values, the result will be NoData. Set Null: Returns NoData if a conditional evaluation is true and returns the value specied by another raster if it is false on a cell-by-cell basis.
SetNull <in_conditional_raster> <in_false_raster_or_constant> <out_raster> {where_clause}

Spatial Analyst toolbox

If the evaluation of the WHERE clause is true, the cell location on the output raster will be assigned NoData. If the evaluation is false, the output raster will be dened by the input false raster or constant value. If no WHERE clause is specied, the output raster will have NoData wherever the conditional raster is greater than zero.

127

Density toolset

Contains tools used to calculate the spread of values over a surface. Kernel Density: Calculates a magnitude per unit area from point or polyline feature using a kernel function to t a smoothly tapered surface to each point or polyline.
KernelDensity <in_features> <population_eld> <out_raster> {cell_size} {search_radius} {SQUARE_MAP_UNITS | SQUARE_MILES | SQUARE_KILOMETERS | ACRES | HECTARES | SQUARE_YARDS | SQUARE_FEET | SQUARE_INCHES | SQUARE_METERS | SQUARE_CENTIMETERS | SQUARE_MILLIMETERS}

Only the points or portions of a line that fall within the neighborhood are considered in calculating the density. If no points or line sections fall within the neighborhood of a particular cell, that cell is assigned NoData. Larger values of the radius parameter produce a smoother, more generalized density raster. Smaller values produce a raster that shows more detail. If the area unit scale factor units are small relative to the features (distance between points or length of line sections, depending on feature type), the output values may be small. To obtain larger values, select the area unit scale factor for larger units (for example, square kilometers versus square meters). Line Density: Calculates a magnitude per unit area from polyline features that fall within a radius around each cell.
LineDensity <in_polyline_features> <population_eld> <out_raster> {cell_size} {search_radius} {SQUARE_MAP_UNITS | SQUARE_MILES | SQUARE_KILOMETERS | ACRES | HECTARES | SQUARE_YARDS | SQUARE_FEET | SQUARE_INCHES | SQUARE_METERS | SQUARE_CENTIMETERS | SQUARE_MILLIMETERS}

Only the portion of a line within the neighborhood is considered in calculating the density. If no lines fall within the neighborhood at a particular cell, that cell is assigned NoData. If the area unit scale factor units are small relative to the features (length of line sections), the output values may be small. To obtain larger values, use the area unit scale factor for larger units (for example, square kilometers versus square meters). Larger values of the radius parameter produce a smoother, more generalized density raster. Smaller values produce a raster that shows more detail. Point Density: Calculates a magnitude per unit area from point features that fall within a neighborhood around each cell.
PointDensity <in_point_features> <population_eld> <out_raster> {cell_size} {neighborhood} {SQUARE_MAP_UNITS | SQUARE_MILES | SQUARE_KILOMETERS | ACRES | HECTARES | SQUARE_YARDS | SQUARE_FEET | SQUARE_INCHES | SQUARE_METERS | SQUARE_CENTIMETERS | SQUARE_MILLIMETERS}

Spatial Analyst toolbox

128

Only the points that fall within the neighborhood are considered in calculating the density. If no points fall within the neighborhood at a particular cell, that cell is assigned NoData. Larger values of the radius parameter produce a smoother, more generalized density raster. Smaller values produce a raster that shows more detail. If the area unit scale factor units are small relative to the distance between the points, the output raster values may be small. To obtain larger values, use the area unit scale factor for larger units (for example, square kilometers versus square meters).

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Distance toolset

Contains tools used to compute distance across a raster dataset with respect to cost or along a path. Corridor: Calculates the sum of accumulative costs for two input accumulative cost rasters.
Corridor <in_distance_raster1> <in_distance_raster2> <out_raster>

Any two oating point rasters can be used for the input (for example, an accumulative cost raster), but both inputs should be the result of a global cost function. The order of input is irrelevant. Cost Allocation: Calculates for each cell its nearest source based on the least accumulative cost over a cost surface.
CostAllocation <in_source_data> <in_cost_raster> <out_allocation_raster> {maximum_ distance} {in_value_raster} {source_eld} {out_distance_raster} {out_backlink_raster}

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cell locations with NoData in the input cost raster act as barriers in the cost surface functions. Any cell location that is assigned NoData on the input cost surface will receive NoData on all outputs (cost allocation raster and optionally cost distance and cost back-link rasters). The input value raster is useful if the Input source data is a raster and was derived from a function or operator that results; either 1 or zero. These functions lose the original zone values on the input raster that are associated with these locations. The input value raster can either restore these values or allow for analysis on additional combinations of zone values within the source locations. The Maximum distance is specied in the same cost units as those on the input cost raster. Cost Back Link: Denes the neighbor that is the next cell on the least accumulative cost path to the nearest source.
CostBackLink <in_source_data> <in_cost_raster> <out_backlink_raster> {maximum_distance} {out_distance_raster}

Spatial Analyst toolbox

129

 When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cell locations with NoData in the input cost raster act as barriers in the cost surface functions. Any cell location that is assigned NoData on the input cost surface will receive NoData on all outputs (cost back-link raster and optional cost distance and cost allocation rasters). The input value raster is useful if the input source data is a raster and was derived from a function or operator that results in either 1 or zero. These functions lose the original zone values on the input raster that are associated with these locations. The input value raster can either restore these values or allow for analysis on additional combinations of zone values within the source locations. The maximum distance is specied in the same cost units as those on the input cost raster. Cost Distance: Calculates the least accumulative cost distance for each cell to the nearest source over a cost surface.
CostDistance <in_source_data> <in_cost_raster> <out_distance_raster> {maximum_distance} {out_backlink_raster}

Spatial Analyst toolbox

130

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cell locations with NoData in the input cost raster act as barriers in the cost surface functions. Any cell location that is assigned NoData on the input cost surface will receive NoData on all outputs (cost distance raster and optional cost back-link raster). The maximum distance is specied in the same cost units as those on the cost raster. The least cost distance or minimum accumulative cost distance of a cell to a set of source cells is the lower bound of the least cost distance from the cell to all source cells. Cost Path: Calculates the least cost paths from a source to a destination over a surface.
CostPath <in_destination_data> <in_cost_distance_raster> <in_cost_backlink_raster> <out_raster> {EACH_CELL | EACH_ZONE | BEST_SINGLE} {destination_eld}

Cost path produces an output raster that records the least-cost path or paths from selected locations to the closest source cell dened within the accumulative cost surface, in terms of cost distance. When the input destination data is a raster, the set of destination cells consists of all cells in the input raster or feature destination data that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate destination. A destination raster may be conveniently created using the Extract By tools. One or more of the weighted cost functions (Cost Distance, Cost Back Link, or Cost Allocation) are generally required to be run prior to running Cost Path to create the input cost distance raster and the Input cost back-link raster. These are mandatory input rasters to Cost Path.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 When multiple paths merge and follow the remaining distance back to a source on the same route, the segment where the two paths travel together is assigned the value 2. The merged portion of the path cannot be assigned the value of one of the paths since the merged portion belongs to both routes.

Euclidean Allocation: Calculates, for each cell, the nearest source based on Euclidean distance.
EucAllocation <in_source_data> <out_allocation_raster> {maximum_distance} {in_value_ raster} {cell_size} {source_eld} {out_distance_raster} {out_direction_raster}

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. The Euclidean functions are calculated from nonsource cells assigned a NoData value. The input value raster is useful if the input raster or feature source data is a raster derived from a function that results in either 1 or zero. These functions lose their original zone values that are associated with the source cell locations. The input value raster can either restore these values or allow for analysis on additional combinations of zone values within the source cells. The maximum distance is specied in the same map units as the input source data. Euclidean Direction: Computes for each cell the direction to the nearest source, measured in degrees.
EucDirection <in_source_data> <out_direction_raster> {maximum_distance} {cell_size} {out_distance_raster}

Spatial Analyst toolbox

The output values are based on compass directions (90 to the east, 180 to the south, 270 to the west, and 360 to the north), with zero being reserved for the source cells. When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. The Euclidean functions are calculated from nonsource cells assigned NoData values. The maximum distance is specied in the same map units as the input source data. Euclidean Distance: Calculates, for each cell, the Euclidean distance to the closest source.
EucDistance <in_source_data> <out_distance_raster> {maximum_distance} {cell_size} {out_direction_raster} 131

 When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. It must be an integer raster. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. The Euclidean functions are calculated from nonsource cells assigned NoData. The maximum distance is specied in the same map units as the input source data. Path Distance: Calculates, for each cell, the least accumulative cost distance to the nearest source, while accounting for surface distance and horizontal and vertical cost factors.
PathDistance <in_source_data> <out_distance_raster> {in_cost_raster} {in_surface_raster} {in_horizontal_raster} {horizontal_factor} {in_vertical_raster} {vertical_factor} {maximum_distance} {out_backlink_raster}

Spatial Analyst toolbox

132

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cells with NoData act as barriers in the Path Distance functions. The cost distance for cells behind NoData values is calculated by the accumulative cost necessary to move around the NoData barrier. Any cell location that is assigned NoData on any one of the input rasters will receive NoData on all output rasters. The maximum distance is specied in the same cost units as those on the input surface raster. The least-cost-path distance or minimum accumulative cost-distance of a cell from a set of source locations is the lower bound of the least-cost path distance to the cell from all source locations. Path Distance Allocation: Calculates the nearest source for each cell based on the least accumulative cost over a cost surface, while accounting for surface distance and horizontal and vertical cost factors.
PathAllocation <in_source_data> <out_allocation_raster> {in_cost_raster} {in_surface_raster} {in_horizontal_raster} {horizontal_factor} {in_vertical_raster} {vertical_factor} {maximum_distance} {in_value_raster} {source_eld} {out_distance_raster} {out_backlink_raster}

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cells with NoData act as barriers in the Path Distance functions. The cost distance for cells behind NoData values is calculated by the accumulative cost necessary to move around the NoData barrier. Any cell location that is assigned NoData on any one of the input rasters will receive NoData on all output rasters. The maximum distance is specied in the same cost units as those on the input surface raster. The least-cost-path distance or minimum-accumulative-cost distance of a cell from a set of source locations is the lower bound of the least-cost-path distance to the cell from all source locations. Path Distance Back Link: Denes the neighbor that is the next cell on the least accumulative cost path to the nearest source, while accounting for surface distance, horizontal cost factors, and vertical cost factors.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

PathBackLink <in_source_data> <out_backlink_raster> {in_cost_raster} {in_surface_raster} {in_horizontal_raster} {horizontal_factor} {in_vertical_raster} {vertical_factor} {maximum_distance} {out_distance_raster}

When the input source data is a raster, the set of source cells consists of all cells in the source raster that have valid values. Cells that have NoData values are not included in the source set. The value zero is considered a legitimate source. A source raster may be conveniently created using the Extract By tools. Cells with NoData act as barriers in the Path Distance functions. The cost distance for cells behind NoData values is calculated by the accumulative cost necessary to move around the NoData barrier. Any cell location that is assigned NoData on any one of the input rasters will receive NoData on all output rasters. The maximum distance is specied in the same cost units as those on the input surface raster. The least-cost-path distance or minimum accumulative cost distance of a cell from a set of source locations is the lower bound of the least-cost path distance to the cell from all source locations.

Extraction toolset

Contains tools to extract a subset of cells either by the attributes or spatial location of each cell. Extract by Attributes: Extracts the cells of a raster dataset based on a logical query.
ExtractByAttributes <in_raster> <where_clause> <out_raster>

If the WHERE clause evaluates to true, the original inputs value is returned for the cell location. If the WHERE clause evaluates to false, the cell location is assigned NoData. If the input raster is oating point, the query must reference value. For example: value > 10. If an item other than Value of Input raster is specied in the WHERE clause, the original inputs value is returned for the cell location.

Spatial Analyst toolbox

Extract by Circle: Extracts the cell values of a raster dataset based on the boundaries of a circle.
ExtractByCircle <in_raster> <center_point> <radius> <out_raster> {INSIDE | OUTSIDE}

The center of the cell is used to determine whether a cell is within or outside a circle. If the center is within the arc of the circle, the cell is considered fully inside even if portions of the cell fall outside the circle. Cell locations that are not selected are assigned a value of NoData. Extract by Mask: Extracts the cells of a raster dataset that correspond to the areas dened by a mask.
ExtractByMask <in_raster> <in_mask_data> <out_raster>

Where the input raster or feature mask data is a raster, the values for non-NoData input cell locations are copied to the output raster. Tools that can create the mask raster include Con, Test, and the Extraction tools.
133

 Extract by Mask is similar to setting the Mask option in the Environment, except that the mask used in Extract by Mask is only used on the immediate instance, while a mask set in the environment is applied to all tools until it is changed or disabled. Extract by Points: Extracts the cells of a raster dataset based on a set of points.
ExtractByPoints <in_raster> <points;points...> <out_raster> {INSIDE | OUTSIDE}

Cell locations that are not selected are assigned NoData. Extract by Polygon: Extracts the cells of a raster dataset based on the boundaries within a polygon feature.
ExtractByPolygon <in_raster> <polygon;polygon...> <out_raster> {INSIDE | OUTSIDE}

The center of the cell is used to determine whether a cell is within or outside a polygon. If the center is within the arcs of the polygon, the cell is considered fully inside even if portions of the cell fall outside the polygon. The polygon has a limit of 1,000 vertices. Polygon vertices must be entered in clockwise order. The rst and last vertex must be the same to close the polygon. The arcs of the polygon can cross one another, but convoluted polygons are not recommended. Cell locations that are not selected are assigned values of NoData. Extract by Rectangle: Extracts the cells of a raster dataset based on the boundaries of a rectangle.
ExtractByRectangle <in_raster> <rectangle> <out_raster> {INSIDE | OUTSIDE}

The center of the cell is used to determine whether a cell is within or outside a rectangle. If the center is within the outline of a rectangle, the cell is considered fully inside even if portions of the cell fall outside the rectangle. Cell locations that are not selected are assigned values of NoData.

Spatial Analyst toolbox

134

Extract Values to Points: Extracts the cell values from a raster at the locations of points in a feature class.
ExtractValuesToPoints <in_point_features> <in_raster> <out_point_features> {NONE | INTERPOLATE} {VALUE_ONLY | ALL}

The interpolation option determines how the values will be obtained from the raster. The default option is to use the value at the center of the cell being sampled. The interpolation option will use bilinear interpolation to interpolate a value for the cell center. The Extract Values to Points tool can be used with a oating-point input raster. In this case, the resulting output point dataset will only contain attributes from the input feature data and the value of the cell, as determined by the interpolation option. The output shapele will have at least the RASTERVALU eld added. All other items will be appended after the RASTERVALU eld. For the RASTERVALU eld of the attribute table, NoData cells in the value raster will be given a value of -9999. Sample: Creates a table that shows the values of cells from a raster, or set of rasters, for dened locations.
Sample <in_rasters;in_rasters...> <in_location_data> <out_table> {NEAREST | BILINEAR | CUBIC}

The locations are dened by raster cells or by a set of points. When the input location raster or point features are rasters, the set of location cells consists of all cells in the raster that have a value of zero or greater. Cells that have NoData values are not included in the location set. A location raster may be conveniently created using the Extract By tools.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 If the input location raster or point features are rasters, NoData cells will be listed in the output table as -9999.

Generalization toolset

Contains tools to remove or reduce erroneous or irrelevant data within a raster through aggregation, edge smoothing, intelligent noise removal, and so forth. Aggregate: Generates a reduced resolution raster dataset.
Aggregate <in_raster> <out_raster> <cell_factor> {SUM | MAXIMUM | MEAN | MEDIAN | MINIMUM} {EXPAND | TRUNCATE} {DATA | NODATA}

The geoprocessing analysis environment (Extent, Cell Size, and Mask) is recognized by the Aggregate function. To determine the output rasters resolution when an integer cell size has been specied, multiply the cell resolution of the analysis environment by the input cell factor parameter. If the cell size for the analysis environment is set to the minimum or maximum of the inputs, the resolution of the output raster will be the product of the input rasters resolution multiplied by the specied cell factor. Boundary Clean: Smooths the boundary between zones by expanding and shrinking the boundary.
BoundaryClean <in_raster> <out_raster> {NO_SORT | DESCEND | ASCEND} {TWO_WAY | ONE_WAY}

Spatial Analyst toolbox

All regions of less than three cells in the x- or y-direction will be changed. In the rst pass, for any processing cell in the expanded raster that has a neighbor of the original value of the processing cell, the original value of the processing cell will be recovered. In the second pass of TWO_WAY, any cell in the expanded raster that is not completely surrounded by eight cells of the same value will recover its original value. In the ONE_WAY or rst pass of the TWO_WAY, cells of NoData have the lowest priority. In the second pass of the TWO_WAY, cells of NoData have the highest priority. Expand: Expands the selected zones of a raster dataset by a specied number of cells.
Expand <in_raster> <out_raster> <number_cells> <zone_values;zone_values...>

The zone values must be integers. They can be in any order.

135

Majority Filter: Replaces cell values within a raster dataset based on the majority of their contiguous neighboring cells.
MajorityFilter <in_raster> <out_raster> {FOUR | EIGHT} {MAJORITY | HALF}

The use of FOUR will retain the corners of rectangular regions. The use of EIGHT will smooth the corners of rectangular regions. Contiguous is dened as sharing an edge for a kernel of EIGHT and as sharing a corner for a kernel of FOUR. If the keyword HALF is specied and two values occur as equal halves, a replacement will not occur if the value of the processing cell is the same as one of the halves. HALF allows more extensive ltering than MAJORITY. While the contiguity criterion is the same for edge and corner raster cells, they obey different MAJORITY and HALF rules. Using a kernel of FOUR, an edge or corner cell always requires two matching neighbors before replacement will occur. With a kernel of EIGHT, a corner cell must have all neighbors of the same value before it is changed, while an edge cell requires three contiguous neighbors, including one along the edge, before any change will occur. Nibble: Replaces cell values in a raster dataset corresponding to a mask with the values of the nearest neighbors.
Nibble <in_raster> <in_mask_raster> <out_raster> {ALL_VALUES | DATA_ONLY}

Spatial Analyst toolbox

Cells in the input raster containing NoData are not nibbled. To nibble away NoData, rst convert it to another value. Region Group: Records for each cell of a raster the identity of the connected region to which it belongs. A unique number is assigned to each region.
RegionGroup <in_raster> <out_raster> {FOUR | EIGHT} {WITHIN | CROSS} {ADD_LINK | NO_LINK} {excluded_value}

The rst region scanned (scan moves from left to right, top to bottom) receives the value 1, the second 2, and so forth, until all regions are assigned a value. The values assigned to the output zones are based on when they are encountered in the scanning process. The scanning process cannot be controlled by the user. By default, the Add Link option is true. This will create an item called LINK in the attribute table of the output raster, which retains the original value for each cell from the input raster.

136

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Shrink: Shrinks the selected zones by a specied number of cells.

Shrink <in_raster> <out_raster> <number_cells> <zone_values;zone_values...>

When two adjacent regions are part of the selected set to shrink, there is no change at the boundary between them. NoData has the same priority as any valid value to invade areas vacated by shrinking selected values. Therefore, if a selected value is adjacent to NoData, it may become NoData after shrinking. Thin: Thins rasterized linear features in a raster dataset by reducing the number of cells representing the width of the features.
Thin <in_raster> <out_raster> {ZERO | NODATA} {NO_FILTER | FILTER} {ROUND | SHARP} {maximum_thickness}

The FILTER option uses the same ltering algorithm as Boundary Clean to remove short linear features extending from the major branch. It may also remove features narrower than three cells. Specifying the maximum thickness of input linear features is essential for thinning rasters where the thickness of linear features may exceed or stay well below the default maximum thickness value. The best results can be expected when the maximum thickness ts the thickest linear features to be thinned.

Groundwater toolset

Spatial Analyst toolbox

Contains tools used to measure hydrodynamic movement within or along a surface. Darcy Flow: Calculates the groundwater volume balance residual and other outputs for steady ow in an aquifer.
DarcyFlow <in_head_raster> <in_porosity_raster> <in_thickness_raster> <in_transmissivity_raster> <out_volume_raster> {out_direction_raster} {out_magnitude_raster}

The only differences between Darcy Flow and Darcy Velocity are: Darcy Flow produces an output volume raster. Darcy Velocity does not. Darcy Velocity outputs only direction and magnitude rasters as required output. Darcy Flow produces these outputs optionally. The direction of the velocity vector is recorded in compass coordinates (degrees clockwise from north), the magnitude in units of length over time. No particular system of units is specied by this function. All data should be consistent, using the same unit for time (seconds, days, years) and length (feet, meters) for all data. However the head elevation raster is obtained, the head must be consistent with the transmissivity raster. That is, the head must reect the ow through the transmissivity eld. It is not sufcient to use values obtained by measurement and testing in the eldthe gridded values must be analyzed for consistency with the aid of a proper porous medium ow program. Consistency implies that the heads would actually be produced by the modeled transmissivity eld. Since the true and modeled transmissivity elds often differ in practice, the true and modeled head elds differ as well. Check the heads for consistency by examining the residual raster produced by Darcy Flow. The residual will reect the consistency of the dataset. Any analysis using Darcy Flow on inconsistent datasets will produce meaningless results.
137

 The effective porosity eld, a physical property of the aquifer, will generally be estimated from geological data. It is dened as the volume of void space that contributes to uid ow divided by the entire volume. Porosity is expressed as a number between zero and 1, with typical values around 0.35, and is dimensionless. A value of effective porosity of 0.35 means that 35 percent of the volume of the porous medium contributes to uid ow. The remaining 65 percent, consisting of solid matrix and unconnected pores, does not contribute to uid ow. The saturated thickness, measured in units of length, is interpreted from geological information. For a conned aquifer, this measure is the thickness of the formation between the upper and lower conning layers. For an unconned aquifer, the saturated thickness is the distance between the water table and the lower conning layer. Darcy Velocity: Calculates the groundwater seepage velocity vector (direction and magnitude) for steady ow in an aquifer.
DarcyVelocity <in_head_raster> <in_porosity_raster> <in_thickness_raster> <in_transmissivity_raster> <out_direction_raster> <out_magnitude_raster>

The only differences between Darcy Flow and Darcy Velocity are: Darcy Flow produces an output volume raster. Darcy Velocity does not. Darcy Velocity outputs only direction and magnitude rasters as required output. Darcy Flow produces these outputs optionally. The direction of the velocity vector is recorded in compass coordinates (degrees clockwise from north), the magnitude in units of length over time. No particular system of units is specied by this function. All data should be consistent, using the same unit for time (seconds, days, years) and length (feet, meters) for all data. However the head elevation raster is obtained, the head must be consistent with the transmissivity raster. That is, the head must reect the ow through the transmissivity eld. It is not sufcient to use values obtained by measurement and testing in the eldthe rasterized values must be analyzed for consistency with the aid of a proper porous medium ow program. Consistency implies that the heads would actually be produced by the modeled transmissivity eld. Since the true and modeled transmissivity elds often differ in practice, the true and modeled head elds differ as well. Check the heads for consistency by examining the residual raster produced by Darcy Flow. The residual will reect the consistency of the dataset. Any analysis using Darcy Velocity on inconsistent datasets will produce meaningless results. The effective porosity eld, a physical property of the aquifer, will generally be estimated from geological data. It is dened as the volume of void space that contributes to uid ow divided by the entire volume. Porosity is expressed as a number between zero and 1, with typical values around 0.35, and is dimensionless. A value of effective porosity of 0.35 means that 35 percent of the volume of the porous medium contributes to uid ow. The remaining 65 percent, consisting of solid matrix and unconnected pores, does not contribute to uid ow. The saturated thickness, measured in units of length, is interpreted from geological information. For a conned aquifer, this measure is the thickness of the formation between the upper and lower conning layers. For an unconned aquifer, the saturated thickness is the distance between the water table and the lower conning layer. Particle Track: Calculates the path of a particle through a velocity eld, returning an ASCII le of particle tracking data and, optionally, a coverage of track information.
ParticleTrack <in_direction_raster> <in_magnitude_raster> <source_point> <out_track_le> {step_length} {tracking_time} {out_track_polyline_features}

Spatial Analyst toolbox

138

The input direction and magnitude rasters should be from the same run of Darcy Flow. The path le generated by this function is an ASCII text le containing information about position, local velocity direction and magnitude, and cumulative length and time of travel along the path. This le is used for input by Porous Puff. The format of this le is as follows:

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Time
0.000000000 113.1648712 226.2741353 339.3574334 452.3447720 565.2657591 678.0514031 790.7309576

X
0.000000000 4.999804443 9.998043277 14.99315255 19.98356700 24.96772671 29.94406931 34.91104149

Y
482.8400000 482.7957786 482.6630814 482.4419855 482.1325285 481.7348453 481.2490323 480.6752838

Length
0.000000000 5.000000000 10.00000000 15.00000000 20.00000000 25.00000000 30.00000000 35.00000000

Flow direction
90.00000000 91.01366126 92.02765240 93.04094157 94.05521317 95.06807622 96.08254679 97.09488082

Flow magnitude
0.04418909563 0.04418332249 0.04421519432 0.04421519432 0.04425274599 0.04427874865 0.04433188322 0.04437362239

No particular system of units is specied by Particle Track. It is important that all data supplied be in a consistent set of units, using the same unit for time (seconds, days, years) and length (feet, meters) for all data. The two outputs from Particle Track are (1) a particle track ASCII le using the name specied as output particle track le and (2) a polyline feature class (optional). Porous Puff: Calculates the time-dependent, two-dimensional concentration distribution in mass per volume of a solute introduced instantaneously and at a discrete point into a vertically mixed aquifer.
PorousPuff <in_track_le> <in_porosity_raster> <in_thickness_raster> <out_raster> <mass> {dispersion_time} {longitudinal_dispersivity} {dispersivity_ratio} {retardation_ factor} {decay_coefcient}

No particular system of units is specied by this function. It is important that all data supplied be consistent, that is, using the same unit for time (seconds, days, years), length (feet, meters), and mass (kilograms, slugs) for all data. The effective porosity eld, a physical property of the aquifer, will generally be estimated from geological data. It is dened as the volume of void space that contributes to uid ow divided by the entire volume. Porosity is expressed as a number between 0.0 and 1.0, with typical values around 0.35, and is dimensionless. A value of effective porosity of 0.35 means that 35 percent of the volume of the porous medium contributes to uid ow. The remaining 65 percent, consisting of solid matrix and unconnected pores, does not contribute to uid ow. The saturated thickness, measured in units of length, is interpreted from geological information. For a conned aquifer, this measure is the thickness of the formation between the upper and lower conning layers. For an unconned aquifer, the saturated thickness is the distance between the water table and the lower conning layer. The decay coefcient is related to the half-life T as: For example, the half-life of carbon-14 is 5,730 years, so its decay coefcient is ln2 = 0.693. So the equation becomes 0.693/5730 = 1.21x10-4/year. A stable constituent has a decay coefcient of zero, corresponding to an innite half-life. Half-lives of radioisotopes are available from several sources, including the CRC Handbook of Chemistry and Physics.

Spatial Analyst toolbox

Hydrology toolset

Contains tools providing hydrology functions to simulate the ow of water over an elevation surface and creates either a stream network or a watershed. Basin: Creates a raster dataset delineating all drainage basins.
Basin <in_ow_direction_raster> <out_raster>

Best results will be obtained from Basin if the FORCE option was used when creating the Flow Direction raster.
139

 All cells in the raster will belong to a basin, even if that basin is only one cell. Fill: Fills sinks in a surface raster to remove small imperfections in the data.
Fill <in_surface_raster> <out_surface_raster> {z_limit}

A sink is a cell with an undened drainage direction; no cells surrounding it are lower. The pour point is the boundary cell with the lowest elevation for the contributing area of a sink. If the sink were lled with water, this is the point where water would pour out. All sinks that are less than the z-limit lower than their lowest adjacent neighbor will be lled to the height of their pour points. The Sink tool can be used to nd the number of sinks and help identify their depth. Knowing the depth of the sinks can help in determining an appropriate z-limit for Fill. Fill can also be used to remove peaks. A peak is a cell where no adjacent cells are higher. To remove peaks, the input surface raster must be inverted. Flow Accumulation: Creates a raster dataset of accumulated ow to each cell.
FlowAccumulation <in_ow_direction_raster> <out_accumulation_raster> {in_weight_raster} {FLOAT | INTEGER}

The result of Flow Accumulation is a raster of accumulated ow to each cell, as determined by accumulating the weight for all cells that ow into each downslope cell. The accumulated ow is based on the number of cells owing into each cell in the output raster. The current processing cell is not considered in this accumulation. Output cells with a high ow accumulation are areas of concentrated ow and may be used to identify stream channels. Output cells with a ow accumulation of zero are local topographic highs and may be used to identify ridges. Flow Direction: Creates a raster dataset of ow direction from each cell to its steepest downslope neighbor.
FlowDirection <in_surface_raster> <out_ow_direction_raster> {NORMAL | FORCE} {out_drop_raster}

Spatial Analyst toolbox

140

The output of the Flow Direction tool is an integer raster whose values range from 1 to 255. The values for each direction from the center are:

For example, if the direction of the steepest drop was to the left of the current processing cell, its ow direction would be coded as 16. If a cell is lower than its eight neighbors, that cell is given the value of its lowest neighbor, and ow is dened toward this cell.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 If a cell has the same change in z-value in multiple directions and that cell is part of a sink, the ow direction is referred to as undened. In such cases, the value for that cell in the output ow direction raster will be the sum of those directions. Flow Length: Calculates distance or weighted distance along a ow path.
FlowLength <in_ow_direction_raster> <out_raster> {DOWNSTREAM | UPSTREAM} {in_weight_raster}

The value type for the <out_raster> is oating point. Sink: Creates a raster dataset identifying all sinks or areas of internal drainage.
Sink <in_ow_direction_raster> <out_raster>

The output of the Sink function is an integer raster with each sink being assigned a unique value. Sinks are numbered between 1 and the number of sinks. Snap Pour Point: Snaps pour points to the cell of highest ow accumulation within a specied distance.
SnapPourPoint <in_pour_point_data> <in_accumulation_raster> <out_raster> <snap_distance> {pour_point_eld}

The Snap Pour Point tool is used to ensure the selection of points of high-accumulated ow when delineating drainage basins using the Watershed tool. Snap Pour Point will search within a snap distance around the specied pour points for the cell of highest accumulated ow and move the pour point to that location. The output is an integer raster where the original pour point locations have been snapped to locations of higher accumulated ow. Stream Link: Assigns unique values to sections of a raster linear network between intersections.
StreamLink <in_stream_raster> <in_ow_direction_raster> <out_raster>

Spatial Analyst toolbox

The input stream raster can be created by thresholding the results of Flow Accumulation. The stream raster linear network should be represented as values greater than or equal to 1 on a background of NoData. Stream Order: Assigns a numeric order to segments of a raster dataset representing branches of a linear network.
StreamOrder <in_stream_raster> <in_ow_direction_raster> <out_raster> {STRAHLER | SHREVE}

The input stream raster linear network should be represented as values greater than or equal to one on a background of NoData. The results of Flow Accumulation can be used to create a raster stream network by applying a threshold value to select cells with a high accumulated ow. For example, the cells that have more than 100 cells owing into them are used to dene the stream network. Use Con or Set Null to create a stream network raster where ow accumulation values of 100 or greater go to 1, and the remainder are put to the background (NoData). The resulting stream network can be used in Stream Link and Stream To Feature. In the STRAHLER order method, all links with no tributaries are assigned an order of 1 and are referred to as rst order. When two rst-order links intersect, the downslope link is assigned an order of 2. When two second-order links intersect, the downslope link is assigned an order of 3, and so on. Only when two links of the same order intersect will the order increase. This is the most common method of ordering.

141

The output from the Stream Order tool is an integer raster. Stream to Feature: Converts a raster dataset representing a linear network to features representing the linear network.
StreamToFeature <in_stream_raster> <in_ow_direction_raster> <out_polyline_features> {SIMPLIFY| NO_SIMPLIFY}

The input stream raster linear network should be represented as values greater than or equal to 1 on a background of NoData. The results of Flow Accumulation can be used to create a raster stream network by applying a threshold value to select cells with a high accumulated ow. For example, the cells that have more than 100 cells owing into them are used to dene the stream network. Use Con or Set Null to create a stream network raster where Flow Accumulation values of 100 or greater go to 1, and the remainder are put to the background (NoData). The resulting stream network can be used in Stream Link and Stream To Feature. There should be contiguous features with the same value, such as the results of Stream Order or Stream Link. Stream To Feature should not be used on a raster where there are few adjacent cells of the same value. The arcs of the output shapele will point downstream. Watershed: Determines the contributing area above a set of cells in a raster dataset.
Watershed <in_ow_direction_raster> <in_pour_point_data> <out_raster> {pour_point_eld}

Spatial Analyst toolbox

142

The value of each watershed will be taken from the value of the source in the input raster or feature pour point data. When the pour point is a raster dataset, the cell values will be used. When the pour point is a point feature dataset, the values will come from the specied eld. Better results will be obtained if the Snap Pour Point tool is used beforehand to help locate the pour points to cells of high-accumulated ow.

Interpolation toolset

Contains tools to create a raster surface from point features. IDW: Interpolates a surface from points using an inverse distance weighted technique.
IDW <in_point_features> <z_eld> <out_raster> {cell_size} {power} {search_radius} {in_ barrier_polyline_features}

The barriers option is used to specify the location of linear features known to interrupt the surface continuity. These features do not have z-values. Cliffs, faults, or embankments are typical examples of barriers. Barriers limit the selected set of the input sample points used to interpolate output z-values to those samples on the same side of the barrier as the current processing cell. The output value for a cell using IDW is limited to the range of the values used to interpolate. Because IDW is a weighted distance average, the average cannot be greater than the highest or less than the lowest input. Therefore, it cannot create ridges or valleys if these extremes have not already been sampled (Watson and Philip 1985). The best results from IDW are obtained when sampling is sufciently dense with regard to the local variation you are attempting to simulate. If the sampling of input points is sparse or uneven, the results may not sufciently represent the desired surface (Watson and Philip 1985).
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Kriging: Interpolates a raster dataset from a set of points using kriging.

Kriging <in_point_features> <z_eld> <out_surface_raster> <semiVariogram_props> {cell_ size} {search_radius} {out_variance_prediction_raster}

The universal kriging types (linear with linear drift and linear with quadratic drift) assume that there is a structural component present and that the local trend varies from one location to another. The advanced parameters allow control of the semivariogram used for Kriging. A default value for lag size is initially set to the default output cell size. For major range, partial sill, and nugget, a default value will be calculated internally if nothing is specied. Low values within the output variance of prediction raster indicate a high degree of condence in the predicted value. High values may indicate a need for more data points. Natural Neighbor: Interpolates a surface from points using a natural neighbor technique.
NaturalNeighbor <in_point_features> <z_eld> <out_raster> {cell_size}

The Natural Neighbor tool can efciently handle large numbers of input points. Other interpolators may have difculty with large point datasets. Spline: Interpolates a surface from points using a minimum curvature spline technique.
Spline <in_point_features> <z_eld> <out_raster> {cell_size} {REGULARIZED | TENSION} {weight} {number_points}

The resulting smooth surface from Spline passes exactly through the input points. The REGULARIZED option of Spline usually produces smoother surfaces than those created with the TENSION option. For the REGULARIZED option, higher values used for the Weight parameter produce smoother surfaces. The values entered for this parameter must be equal to or greater than zero. Typical values that are used are 0, 0.001, 0.01, 0.1, and 0.5. The Weight is the square of the parameter, referred to in the literature as tau (t). For the TENSION option, higher values entered for the Weight parameter result in somewhat coarser surfaces but with surfaces that closely conform to the control points. The values entered have to be equal to or greater than zero. Typical values are 0, 1, 5, and 10. The Weight is the square of the parameter, referred to in the literature as phi (). The greater the value of Number of Points, the smoother the surface of the output raster. Topo to Raster: Interpolates a hydrologically correct surface from point, line, and polygon data.
TopoToRaster <feature_layer{Field} {Type};feature_layer{Field} {Type}...> <out_surface_raster> {cell_size} {extent} {Margin} {minimum_z_value} {maximum_z_ value} {ENFORCE | NO_ENFORCE | ENFORCE_WITH_SINK} {CONTOUR | SPOT} {maximum_iterations} {roughness_penalty} {discrete_error_factor} {vertical_standard_error} {tolerance_1} {tolerance_2} {out_stream_features} {out_sink_features} {out_diagnostic_le} {out_parameter_le}

Spatial Analyst toolbox

Topo to Raster will only use four input data points for the interpolation of each output cell. All additional points are ignored. If too many points are encountered by the algorithm, an error may occur indicating the point dataset has too many points. The maximum number of points that can be used is nrows*ncols, where nrows is the number of rows in the output raster and ncols is the number of columns. Stream data always takes priority over point or contour data; therefore, elevation data points that conict with descent down each stream are ignored. Stream data is a powerful way of adding topographic information to the interpolation, further ensuring the quality of the output DEM. Some typical values for the Tolerance 1 and Tolerance 2 settings are: For point data at 1:100,000 scale, use 5.0 and 200.0. For less dense point data at up to 1:500,000 scale, use 10.0 and 400.0. For contour data with contour spacing of 10, use 5.0 and 100.0.
143

Topo to Raster by File: Interpolates a hydrologically correct surface from point, line, and polygon data using parameters specied in a le.
TopoToRasterByFile <in_parameter_le> <out_surface raster> {out_stream_features} {out_sink_features}

The parameter le is structured with the input datasets listed rst, followed by the various parameter settings, then the output options. The input data identies the input datasets and, where applicable, elds. There are six types of input: Contours, Points, Sinks, Streams, Lakes, and Boundaries. As many inputs can be used as desired, within reason. The order in which the inputs are entered does not have any bearing on the outcome. <Path> indicates a path to a dataset, <Item> indicates a eld name, and <#> indicates a value to be entered. ContoursContour line dataset with item containing height values. PointsPoint dataset with item containing height values. SinksPoint dataset containing sink locations. If the dataset has elevation values for the sinks, specify that eld name as the <Item>. If only the locations of the sinks are to be used, use NONE for <Item>. StreamsStream line dataset. Height values are not necessary. LakesLake polygon dataset. Height values are not necessary. BoundaryBoundary polygon dataset. Height values are not necessary. EnforceControls whether drainage enforcement is applied. DatatypePrimary type of input data. IterationsThe maximum number of iterations the algorithm performs. Roughness PenaltyThe measure of surface roughness. Discretization Error FactorThe amount to adjust the data smoothing of the input data into a raster. Vertical Standard ErrorThe amount of random error in the z-values of the input data. TolerancesThe rst reects the accuracy of elevation data in relation to surface drainage, and the other prevents drainage clearance through unrealistically high barriers. Z-LimitsLower and upper height limits. ExtentMinimum x, minimum y, maximum x, and maximum y coordinate limits. Cell SizeThe resolution of the nal output raster. MarginDistance in cells to interpolate beyond the specied output extent and boundary. Output Stream FeaturesOnly use if Output stream polyline features is set in the Topo to Raster by File dialog box. Output Sink FeaturesOnly use if Output remaining sink point features is set in the Topo to Raster by File dialog box. Output Diagnostics FileThe location and name of the diagnostics le. An example parameter le is:
Contour D:\data\contours2\arc HEIGHT Point D:\data\points2\point SPOTS Sink D:\data\sinks_200.shp Stream D:\data\streams\arc Lake D:\data\lakes\polygon Boundary D:\data\clipcov\polygon ENFORCE ON DATATYPE CONTOUR ITERATIONS 40 ROUGHNESS_PENALTY 0.00000000000 DISCRETE_ERROR_FACTOR 1.00000000000 VERTICAL_STANDARD_ERROR 0.00000000000 TOLERANCES 2.50000000000 100.00000000000 ZLIMITS -2000.00000000000 13000.00000000000 144 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Spatial Analyst toolbox

EXTENT -810480.62500000000 8321785.00000000000 810480.62500000000 10140379.00000000000 CELL_SIZE 1800.00000000000 MARGIN 20 OUT_STREAM OUT_SINK OUT_DIAGNOSTICS D:\data\ttr_diag.txt

Trend: Interpolates a surface from points using a trend technique.

Trend <in_point_features> <z_eld> <out_raster> {cell_size} {order} {LINEAR | LOGISTIC} {out_rms_le}

As the order of the polynomial is increased, the surface being tted becomes progressively more complex. A higher-order polynomial will not always generate the most accurate surface; it is dependent on the data. The optional root mean square (RMS) le output contains information on the RMS error of the interpolation. This information can be used to determine the best value to use for the polynomial order by changing the order value until you get the lowest RMS error. For the LOGISTIC option of Type of Regression, the Z value eld of input point features should have codes of zero and 1.

Local toolset

Contains tools to compute an output raster dataset where the output value at each location is a function of the value associated with that location on one or more raster datasets. Cell Statistics: Calculates a per-cell statistic from multiple raster datasets.
CellStatistics <in_rasters_or_constants;in_rasters_or_constants...> <out_raster> {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY}

Spatial Analyst toolbox

The order of input rasters is irrelevant. Combine: Combines multiple rasters so a unique output value is assigned to each unique combination of input values.
Combine <in_rasters;in_rasters...> <out_raster>

Combine is similar to Combinatorial Or. They both assign a new number to each unique combination of input values. Combine works on integer values and their associated attribute tables. If the values on the input are oating point, they will be automatically truncated, tested for uniqueness with the other input, and sent to the output attribute table. No more than 20 rasters can be used as input to Combine.

145

Equal to Frequency: Evaluates the number of times the input raster dataset values are equal to a specied value on a cell-by-cell basis.
EqualToFrequency <in_value_raster> <in_rasters;in_rasters...> <out_raster>

An arbitrary number of rasters can be specied in the input rasters list. Greater Than Frequency: Evaluates the number of times the input raster dataset values are greater than a specied value on a cell-by-cell basis.
GreaterThanFrequency <in_value_raster> <in_rasters;in_rasters...> <out_raster>

An arbitrary number of rasters can be specied in the input rasters list. Highest Position: Determines the position of a raster dataset with the maximum value in a set of raster datasets.
HighestPosition <in_rasters_or_constants;in_rasters_or_constants...> <out_raster>

Spatial Analyst toolbox

An arbitrary number of rasters can be specied in the input rasters list. The order of inputs is relevant for the Highest Position tool. If two or more input rasters contain the maximum value for a particular cell location, the position of the rst one is returned on the output raster. Less Than Frequency: Evaluates the number of times the input raster dataset values are less than a specied value on a cell-by-cell basis.
LessThanFrequency <in_value_raster> <in_rasters;in_rasters...> <out_raster>

An arbitrary number of rasters can be specied in the input rasters list. Lowest Position: Determines the position of a raster with the minimum value in a set of rasters.
LowestPosition <in_rasters_or_constants;in_rasters_or_constants...> <out_raster> 146 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 An arbitrary number of rasters can be specied in the input rasters list. The order of inputs is relevant for the Lowest Position tool. If two or more input rasters contain the minimum value for a particular cell location, the position of the rst one encountered is returned on the output raster. Popularity: Determines the value that is at a specied level of popularity on a cell-by-cell basis.
Popularity <in_popularity_raster_or_constant> <in_rasters;in_rasters...> <out_raster>

An arbitrary number of rasters can be specied in the input rasters list. The order of input rasters is irrelevant. Rank: Returns the value of a set of rasters based on a rank level specied by another raster.
Rank <in_rank_raster_or_constant> <in_rasters;in_rasters...> <out_raster>

Spatial Analyst toolbox

An arbitrary number of rasters can be specied in the input rasters list. The order of input rasters is irrelevant. If the input values are all the same for any cell location, no matter what the specied popularity is, the output value will be the same as the input for that cell location.

Map Algebra toolset

Contains the tool to create expressions using any of the Map Algebra statements. Map Algebra is the analysis language from Spatial Analyst. Multi Output Map Algebra: Runs an expression built with the Map Algebra language.
MultiOutputMapAlgebra <expression_string>

The Map Algebra expression requires that the output dataset name be identied. For example, the expression must be entered as out_slope = slope (D:\data\surf_1, percentrise, 2). Only ArcInfo grid are supported for use with Multi Output Map Algebra. Inputs must be in the same spatial reference to be used with Multi Output Map Algebra. The results from Multi Output Map Algebra are not added to the table of contents for the active ArcMap session.

147

Single Output Map Algebra: Runs a single expression built with the Map Algebra language.
SingleOutputMapAlgebra <expression_string> <out_raster> {in_data;in_data...}

The Map Algebra expression does not support the out_dataset = function (parameters) syntax of traditional Map Algebra. Simply specify the function and its parameters. For example, type slope (D:\ data\surf_1, percentrise, 2) instead of out_slope = slope (D:\data\surf_1, percentrise, 2). If the dataset is identied in the input raster or feature data list, it is not necessary to specify the path in the Map Algebra expression. Inputs with different spatial references can be used with Single Output Map Algebra. The datasets will be projected on the y to complete the analysis. The results from Single Output Map Algebra are added to the table of contents for the active ArcMap session.

Math toolset

Contains tools to implement math functions, which apply a specied mathematical operation or function to each cell location on an input raster or series of raster datasets. Abs: Calculates the absolute value of the input raster dataset on a cell-by-cell basis.
Abs <in_raster_or_constant> <out_raster>

Input values can be positive or negative and can be either integer or oating point.

Spatial Analyst toolbox

148

Divide: Divides the values of two input raster datasets on a cell-by-cell basis.
Divide <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant for Divide. When a number is divided by zero, the output result is NoData. If both inputs are integers, then Divide performs an integer division and the output result is an integer. For example, if 3 is to be divided by 2, the output is 1. If either input is of oating-point type, then Divide performs a oating-point division and the result is a oating-point value. For example, if 3 is divided by 2.0, the output is 1.5. Exp: Calculates the base e exponential of cells in a raster dataset.
Exp <in_raster_or_constant> <out_raster>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The base e exponential is the most commonly used exponential function. Exp10: Calculates the base 10 exponential of cells in a raster dataset.
Exp10 <in_raster_or_constant> <out_raster>

Exp2: Calculates the base 2 exponential of cells in a raster dataset.

Exp2 <in_raster_or_constant> <out_raster>

Float: Converts each cell value in a raster dataset to oating-point values.

Float <in_raster_or_constant> <out_raster>

Spatial Analyst toolbox

Input values are integers and can be positive or negative. Int: Converts each cell value in a raster dataset to an integer by truncation.
Int <in_raster_or_constant> <out_raster>

If rounding is preferred rather than truncating, add a 0.5 input raster prior to performing Int. The difference between the Round Down and Int functions is that Int always truncates a number:
int on 1.5 becomes 1 int on -1.5 becomes -1

while for the same two values, Round Down returns

round down on 1.5 becomes 1.0 round down on -1.5 becomes -2.0

A second difference between the two functions is that Round Down outputs oating-point values, and Int outputs integer values.

149

Ln: Calculates the natural logarithm (base e) of cells in a raster dataset.

Ln <in_raster_or_constant> <out_raster>

The natural logarithm is the most commonly used logarithmic function. The input value of a logarithmic function cannot be zero or a negative number. If it is, the output will be NoData. Log10: Calculates the base 10 logarithm of cells in a raster dataset.
Log10 <in_raster_or_constant> <out_raster>

The input value of a logarithmic function cannot be zero or a negative number. If it is, the output will be NoData. Log2: Calculates the base 2 logarithm of cells in a raster dataset.

Spatial Analyst toolbox

150

Log2 <in_raster_or_constant> <out_raster>

The input value of a logarithmic function cannot be zero or a negative number. If it is, the output will be NoData. Minus: Subtracts the values of the second input from the values of the rst input on a cell-by-cell basis.
Minus <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant in the subtraction expression. Mod: Divides the values of the rst input by the values of the second input and returns the remainder.
Mod <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The order of input is relevant in the modulus expression. Any value modulated (divided) by zero is assigned NoData on the output. Therefore, any location on the second input that is either zero or NoData will return NoData for that location on the output. Mod assumes both its inputs are integers. If any of the inputs are not integer, those inputs will be converted to integers through truncation. Output values are always integers. Negate: Changes the sign of the cell values of the input raster dataset (multiplies by -1).
Negate <in_raster_or_constant> <out_raster>

Plus: Adds the values of two raster datasets on a cell-by-cell basis.

Plus <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

The order of input is irrelevant in the addition expression. Power: Calculates the nth power of the input raster or number on a cell-by-cell basis.
Power <in_raster_or_constant> <in_raster_or_constants> <out_raster>

Round Down: Returns the next lower whole number value for each cell in a raster dataset.
RoundDown <in_raster_or_constant> <out_raster>

151

 In Round Down, if a number has any values to the right of the decimal point, the output will be assigned the next lowest whole value:
Input 5.3 4.9 3.0 6.5 -0.2 -2.8 Output 5.0 4.0 3.0 6.0 -1.0 -3.0

The difference between Round Down and Int is that Int always truncates a number:
int on 1.5 becomes 1 int on -1.5 becomes -1

while Round Down returns the next lower whole number:

Round Down on 1.5 becomes 1.0 Round Down on -1.5 becomes -2.0

A second difference is that Round Down outputs oating-point values while Int outputs integer values. Round Up: Returns the next highest whole number value that is greater than or equal to the input value for each cell in a raster dataset.
RoundUp <in_raster_or_constant> <out_raster>

Spatial Analyst toolbox

In Round Up, if a number has any values to the right of the decimal point, the output will be assigned the next highest whole value:
Input 5.3 4.9 3.0 6.5 -0.2 -2.8 Output 6.0 5.0 3.0 7.0 0.0 -2.0

Square: Calculates the square of cell values in a raster dataset.

Square <in_raster_or_constant> <out_raster>

Square Root: Calculates the square root of the input grid or number for each cell.
SquareRoot <in_raster_or_constant> <out_raster>

152

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 Input values must be greater than or equal to zero. If they are not, the output will be NoData. Times: Multiplies the values of two raster datasets on a cell-by-cell basis.
Times <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is irrelevant in the multiplication expression.

Bitwise (Math) toolset

Contains tools to implement bitwise operators, which treat the operands as bits (binary representations) and calculate the output by applying the logical operation (e.g., 3 BITWISEAND 5 = 0011 && 0101 = 0001 = 1). Bitwise And: Performs the bitwise AND operation on the binary values of two inputs on a cell-by-cell basis (e.g., 0011 && 0101 = 0001).
BitwiseAnd <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The bitwise methods work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise method is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit is zero; if negative, the bit is 1. Bitwise And treats the sign bit as it would any other bit. If one or both inputs for a cell location are positive, the output is positive; if both inputs are negative, the output is negative. Bitwise Left Shift: Shifts the bits to the left using the number specied (e.g., 1<<2 = 0001 << 2 = 0100 = 4).
BitwiseLeftShift <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

The bitwise operators work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise operation is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit position is zero; if negative, the bit position is 1.

153

Bitwise Not: Performs the bitwise COMPLEMENT operation on the binary values of two inputs on a cellby-cell basis (ips the bits; e.g., 5 = 0101 ~ 1010 = 10).
BitwiseNot <in_raster_or_constant> <out_raster>

The bitwise operators work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise operation is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit position is zero; if negative, the bit position is 1. The Bitwise Not treats the sign bit as it would any other bit. If one or both inputs for a cell location are negative, the output is negative; if both inputs are positive, the output is positive. Bitwise Or: Performs a bitwise OR operation on the binary values of two inputs on a cell-by-cell basis (e.g., 0101 || 1100 = 1101).
BitwiseOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

154

The bitwise operators work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise operation is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit position is zero; if negative, the bit position is 1. Bitwise Right Shift: Shifts the bits to the right using the number specied (e.g., 6>>1 = 0110 >> 1 = 0011 = 3).
BitwiseRightShift <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The bitwise operators work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise operation is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit position is zero; if negative, the bit position is 1. The Bitwise Right Shift operation does no wrapping of bits. The rightmost bit is dropped off. Bitwise XOr: Performs a bitwise exclusive OR operation on the binary values of two inputs on a cell-bycell basis (e.g., 0101 !! 1100 = 1001).
BitwiseXOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The bitwise operators work on 32-bit integers. If oating-point values are input, they are converted to integer values through truncation before the bitwise operation is performed. The output values are always integers. Binary values are stored in twos complement. The leftmost bit position is reserved for the sign of the value (positive or negative). If the integer is positive, the bit position is zero; if negative, the bit position is 1. The Bitwise XOr treats the sign bit as it would any other bit. If one or both inputs for a cell location are negative, the output is negative; if both inputs are positive, the output is positive.

Logical (Math) toolset

Contains tools to evaluate the values of an input raster or rasters relative to a conditional statement, the values in another raster, a constant value, or a specic value. Also contains tools that can produce an output that tracks the unique combinations of the input values between two rasters or constants. Boolean And: Performs the Boolean AND operator on the cell values of two input raster datasets.
BooleanAnd <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

If the input values are oating point, they are converted to integer values by truncation before the Boolean operation is performed. The output values are always integers. Boolean And interprets the input as Boolean values, where nonzero values are considered true and zero is considered false. The two input rasters are tested on a cell-by-cell basis. If both values are true, the output is 1. If one or both values are false, the output is zero. If one or both values are NoData, the output value is NoData. Boolean Not: Performs the Boolean COMPLEMENT operator on the cell values of two input raster datasets.
BooleanNot <in_raster_or_constant> <out_raster>

If the input values are oating point, they are converted to integers by truncation before the Boolean Not is performed. The output values are always integers. Boolean Not interprets the input as Boolean values, where nonzero values are considered true and zero is considered false. The input raster is tested on a cell-by-cell basis. If the value is true, the output is zero (the complement of true). If the value is false, the output is 1. If the value is NoData, the output value is NoData.

155

Boolean Or: Performs the Boolean OR operator on the cell values of two input raster datasets.
BooleanOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

If the input values are oating point, they are converted to integer values by truncation before the Boolean method is performed. Output values are always integers. Boolean Or interprets the input as Boolean values, where nonzero values are considered true and zero is considered false. The two input rasters are tested on a cell-by-cell basis. If one or both values are true, the output is 1. If both values are false, the output is zero. If one or both values are NoData, the output value is NoData. Boolean XOr: Performs the Boolean exclusive OR operator on the cell values of two input raster datasets.
BooleanXOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

156

If the input values are oating point, they are converted to integer values by truncation before the Boolean method is performed. The output values are always integers. Boolean XOr interprets the input as Boolean values, where nonzero values are considered true and zero is considered false. The two input rasters are tested on a cell-by-cell basis. If one value is True and one value is false, the output is 1. If both values are true or both are false, the output is zero. If one or both values are NoData, the output value is NoData. Combinatorial And: Performs a combinatorial AND operation on two input raster datasets.
CombinatorialAnd <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Both inputs must contain positive integer values. Combinatorial Or: Performs a combinatorial OR operation on the cell values of two input raster datasets.
CombinatorialOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 Both inputs must contain positive integer values. Combinatorial XOr: Performs a combinatorial exclusive OR operation on the cell values of two input raster datasets.
CombinatorialXOr <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Both inputs must contain positive integer values. Diff: Determines which values from the rst input are logically different from the values of the second input on a cell-by-cell basis.
Diff <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

If the values on the two inputs are different, the value on the rst input is output. If the values on the two inputs are the same, the output is zero. The order of input is relevant in the Diff expression. If both inputs are integer, the output raster will be integer; otherwise, it will be oating point. A number can be used as an input; however, the cell size and extent must rst be set in the environment. Equal To: Returns 1 for cells where the rst raster equals the second raster and zero if it does not.
EqualTo <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

157

 Equal To evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst and second input values are the same), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the output is NoData. Greater Than: Returns 1 for cells where the rst raster dataset is greater than the second raster dataset and returns zero where it is not.
GreaterThan <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant in the greater than expression. Greater Than evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst input value is greater than the second input value), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the output is NoData. Greater Than Equal: Returns 1 for cells where the rst raster dataset is greater than or equal to the second raster dataset and returns zero where it is not.
GreaterThanEqual <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

158

The order of input is relevant in the greater than equal expression. Greater Than Equal evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst input value is greater than or equal to the second input value), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the output is NoData. InList: Determines which values from the rst input are contained in the other inputs, on a cell-by-cell basis.
InList <in_raster_or_constant1> <in_raster_or_constant2;in_raster_or_constant2...> <out_raster>

If the rst input is a raster and the value of a cell location is not contained in the set specied by the second input, the location will receive NoData on the output raster.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 If all the inputs are integers, the output raster will be integer; otherwise, it will be oating point. A number can be used as an input; however, the cell size and extent must rst be set in the environment. Is Null: Returns 1 for cells in the input raster dataset that have a value of NoData and returns zero where they do not.
IsNull <in_raster> <out_raster>

The output value type is always integer. The values are either 1 or zero. Cells in the input that have a value are given zero on the output. Cells that are NoData in the input are given a value of 1 on the output. Less Than: Returns 1 for cells where the rst raster dataset is less than the second raster dataset and returns zero where it is not.
LessThan <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant in the less than expression. Less Than evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst input value is less than the second input value), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the output is NoData. Less Than Equal: Returns 1 for cells where the rst raster dataset is less than or equal to the second raster dataset and returns zero where it is not.
LessThanEqual <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

The order of input is relevant in the less than or equal to expression. Less Than Equal evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst input value is less than or equal to the second input value), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the output is NoData. Not Equal: Returns 1 for cells where the rst raster dataset is not equal to the second raster dataset and returns zero where it is not.
NotEqual <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

159

 Two inputs are necessary for Not Equal. The order of input is irrelevant for Not Equal. Not Equal evaluates the rst input value in relation to the second input value on a cell-by-cell basis within the Analysis window. In the relational evaluation, if the condition is true (the rst input is not equal to the second input), the output is 1; if it is false, the output is zero. When one or both input values are NoData, the relational expression outputs NoData. Over: Returns those values from the rst input that are non-zero; otherwise, returns the value from the second input on a cell-by-cell basis.
Over <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

The order of input is relevant in the Over expression. If both inputs are integer, the output raster will be integer; otherwise, it will be oating point. A number can be used as an input; however, the cell size and extent must rst be set in the environment.

Spatial Analyst toolbox

Test: Returns 1 for cells that evaluate to true based on a logical expression and returns zero for cells that evaluate to false.
Test <in_raster> <where_clause> <out_raster>

The output is either 1 (if the test evaluates to true) or zero (if the test evaluates to false). The test is specied by a SQL expression.

Trigonometric (Math) toolset

Contains tools for the trigonometric functions that are applied on a per-cell basis to an input raster dataset. ACos: Calculates the inverse cosine of the input raster dataset or number on a cell-by-cell basis.
ACos <in_raster_or_constant> <out_raster>

160

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The input values to the ACos function must be equal to or between -1 and 1. Any value outside this range will receive NoData on the output raster. The input values to the ACos function are interpreted as unitless. The output values from ACos are in radians. If degrees are desired, the resulting raster must be multiplied by the radians-to-degrees conversion factor of 180/, or approximately 57.296. ACosH: Calculates the inverse hyperbolic cosine of cells in an input raster dataset.
ACosH <in_raster_or_constant> <out_raster>

The input values to the ACosH function must be greater than or equal to 1. Any value below 1 will receive NoData on the output. The input and output values in ACosH are interpreted as unitless. ASin: Calculates the inverse sine of cells in an input raster dataset.
ASin <in_raster_or_constant> <out_raster>

Spatial Analyst toolbox

The input values to ASin must be between -1 and 1. Any value outside this range will receive NoData on the output. The input values to ASin are interpreted as unitless. The output values from ASin are in radians. If degrees are desired, the resulting raster must be multiplied by the radians-to-degrees conversion factor of 180/, or approximately 57.296. ASinH: Calculates the inverse hyperbolic sine of cells in an input raster dataset.
ASinH <in_raster_or_constant> <out_raster>

Output values are always oating point, no matter what the input values are. There is no limit on the input values to ASinH. The input and output values in ASinH are interpreted as unitless.
161

ATan: Calculates the inverse tangent of cells in an input raster dataset.

ATan <in_raster_or_constant> <out_raster>

The input values to the ATan function are interpreted as unitless. The output values from ATan are in radians. If degrees are desired, the resulting raster must be multiplied by the radians-to-degrees conversion factor of 180/, or approximately 57.296. ATan2: Calculates the inverse tangent (based on y/x) of cells in an input raster dataset.
ATan2 <in_raster_or_constant1> <in_raster_or_constant2> <out_raster>

Spatial Analyst toolbox

162

The values of the rst specied input are used as the numerator in the calculation of the tangent angle (tan@ = y/x). The values of the second specied input are used as the denominator in the calculation of the angle. The output values from the ATan2 function are between -pi and pi. The arc tangent two operation represents all quadrants in a Cartesian matrix (based on sign). ATan2 converts rectangular coordinates (x,y) to polar (r,th), where r is the distance from the origin and th is the angle from the x-axis.

The input values to ATan2 are interpreted as unitless. The output values from ATan2 are in radians. If degrees are desired, the resulting raster must be multiplied by the radians-to-degrees conversion factor of 180/, or approximately 57.296. ATanH: Calculates the inverse hyperbolic tangent of cells in an input raster dataset.
ATanH <in_raster_or_constant> <out_raster>

The input and output values in ATanH are interpreted as unitless. The input values to ATanH must be between -1 and 1. Any input value outside this range will result in NoData on the output raster.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Cos: Calculates the cosine of cells in an input raster dataset.

Cos <in_raster_or_constant> <out_raster>

The cosine of a value is between -1 and 1. The input values to Cos are interpreted as radians. If the desired input is in degrees, the values must be divided by the radians-to-degrees conversion factor of 180/, or approximately 57.296. CosH: Calculates the hyperbolic cosine of cells in an input raster dataset.
CosH <in_raster_or_constant> <out_raster>

The input and output values in CosH are interpreted as unitless. Sin: Calculates the sine of cells in an input raster dataset.
Sin <in_raster_or_constant> <out_raster>

Spatial Analyst toolbox

The sine of a value is between -1 and 1. The input values to Sin are interpreted as radians. If the desired input is in degrees, the values must be divided by the radians-to-degrees conversion factor of 180/, or approximately 57.296. SinH: Calculates the hyperbolic sine of cells in an input raster dataset.
SinH <in_raster_or_constant> <out_raster>

The input and output values in the SinH function are interpreted as unitless. Tan: Calculates the tangent of cells in an input raster dataset.
Tan <in_raster_or_constant> <out_raster>

163

 The input values to Tan are interpreted as radians. If the desired input is in degrees, the values must be divided by the radians-to-degrees conversion factor of 180/, or approximately 57.296. TanH: Calculates the hyperbolic tangent of cells in an input raster dataset.
TanH <in_raster_or_constant> <out_raster>

The input and output values of TanH are interpreted as unitless.

Multivariate toolset

Contains tools to allow the statistical analysis of a series of raster datasets (independent variables) that, based on the values within the rasters, produces a predictable result for some phenomena (the dependent variable). Band Collection Statistics: Calculates the statistics for a set of raster bands.
BandCollectionStats <in_raster_bands;in_raster_bands...> <out_stat_le> {BRIEF | DETAILED}

Spatial Analyst toolbox

The output is saved to an ASCII le named the output statistics le. Any extension can be used, but .txt is preferred. By default the minimum, maximum, mean, and standard deviation of the input raster bands is calculated. If the extents of the raster bands are not the same, the statistics will be calculated on the common spatial extent of all the input raster bands. The cell size will be that of the maximum of the input rasters, by default. Otherwise, it will depend on the Raster Analysis Setting in the environment. Class Probability: Creates probability layers for each class in a signature le.
ClassProbability <in_raster_bands;in_raster_bands...> <in_signature_le> <out_multiband_raster> {maximum_output_value} {EQUAL | SAMPLE | FILE} {in_a_priori_le}

Any signature le created by one of the Create Signature, Edit Signature, or Iso Cluster tools is a valid entry for input signature le. These will have a .gsg extension. The value entered for maximum output value sets the upper range of the values in the output probability layers. The default value of 100 creates a stack with each layer containing integer values ranging from zero to 100. The input a priori probability le must be an ASCII le consisting of two columns. The values in the left column represent class IDs. The values in the right column represent the a priori probabilities for the respective classes. Valid values for class a priori probabilities must be greater than or equal to zero. If zero is specied as a probability, the class will not appear on the output raster. The sum of the specied a priori probabilities must be smaller than or equal to 1. The format of the le is as follows:
1 2 4 5 7 .3 .1 .0 .15 .05

8 .2

The classes omitted in the le will receive the average a priori probability of the remaining portion of the value of 1.
164 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Create Signatures: Creates an ASCII signature le of classes dened by input sample data and a set of raster bands.
CreateSignatures <in_raster_bands;in_raster_bands...> <in_sample_data> <out_signature_le> {COVARIANCE | MEAN_ONLY} {sample_eld}

The minimum valid number of class samples in the sample data is 2. There is no maximum number of classes. The COVARIANCE option must be used if the signature le is to be used in further multivariate analysis functions that use covariance matrices, such as Maximum Likelihood Classication and Class Probability. This is the default. Dendrogram: Constructs a tree diagram showing attribute distances between sequentially merged classes in a signature le.
Dendrogram <in_signature_le> <out_dendrogram_le> {VARIANCE | MEAN_ONLY} {line_width}

The input signature le has to be a signature le in the prescribed ASCII format. A signature le can be created with the Iso Cluster or Create Signatures tool. The le must have a minimum of two classes. The output of Dendrogram, the output dendrogram le, is an ASCII le. The le contains a table of distances between pairs of sequentially merged classes and a graphical representation showing the relationships among classes and the hierarchy of the merging. By analyzing the graph and the associated table, a user can decide the potential merging of classes. The proximity of a pair of classes within a signature le is measured by the attribute distance. Edit Signatures: Edits and updates a signature le by merging, renumbering, and deleting class signatures.
EditSignatures <in_raster_bands;in_raster_bands...> <in_signature_le> <in_signature_remap_le> <out_signature_le> {sample_interval}

Edit Signatures allows the modication of an existing signature le by all or any of the following operations: Merging signatures of a set of classes Renumbering a signature class ID Deleting unwanted signatures The input signature le has to be an ASCII signature le. The le can be output of any Multivariate function that produces the le containing the required statistical informationfor example, Iso Cluster and Create Signatures. The le must have a minimum of two classes. Such a le can be recognized by its .gsg extension. The input signature remap le is an ASCII le consisting of two columns. In the rst column, the original class IDs are listed in ascending order. The second column has the new class IDs for updating in the signature le. When a set of classes is to be merged, a new class ID must be put in the second column for each class ID of the set. Only classes that need to be edited have to be placed in the signature remap le. Any class not present in the remap le will remain unchanged. To delete a class signature, the value of -9,999 must be entered in the second column of the remap le. A class ID can also be renumbered to a value that does not exist in the input signature le. The following is an example of the input signature remap le:
2:3 4 : 11 5 : -9999 9:3

Spatial Analyst toolbox

The example above will merge classes 2 and 9 with three, class 4 with 11, and delete class 5.

165

Iso Cluster: Uses an isodata clustering algorithm to determine the characteristics of the natural groupings of cells in multidimensional attribute space and stores the results in an output ASCII signature le.
IsoCluster <in_raster_bands;in_raster_bands...> <out_signature_le> <number_classes> {number_iterations} {min_class_size} {sample_interval}

Iso Cluster performs clustering of the multivariate data combined in a list of input rasters. The resulting signature le may be used as the input for a classication function, such as Maximum Likelihood Classication, producing an unsupervised classication raster. To provide the sufcient statistics necessary to generate a signature le for a future classication, each cluster should contain enough cells to accurately represent the cluster. The value entered for the minimum class size should be about 10 times larger than the number of layers in the input raster bands. Generally, for more cells contained in the input rasters extent, larger values for minimum class size and sample interval should be specied. Values entered for the sample interval should be small enough that the smallest desirable categories existing in the input data will be appropriately sampled. The class ID values on the output signature le start from one and sequentially increase to the number of input classes. The assignment of the class numbers is arbitrary. Better results will be obtained if all input rasters have the same data ranges. Maximum Likelihood Classication: Performs a maximum likelihood classication on a set of raster dataset bands.
MLClassify <in_raster_bands;in_raster_bands...> <in_signature_le> <out_classied_ raster> {0.0 | 0.005 | 0.01 | 0.025 | 0.05 | 0.1 | 0.25 | 0.5 | 0.75 | 0.9 | 0.95 | 0.975 | 0.99 | 0.995} {EQUAL | SAMPLE | FILE} {in_a_priori_le} {out_condence_raster}

Any signature le created by the Create Signature, Edit Signature, or Iso Cluster tools is a valid entry for the input signature le. These will have a .gsg extension. By default, all cells in the output raster will be classied, with each class having equal probability weights attached to their signatures. The input a priori probability le must be an ASCII le consisting of two columns. The values in the left column represent class IDs. The values in the right column represent the a priori probabilities for the respective classes. Valid values for class a priori probabilities must be greater than or equal to zero. If zero is specied as a probability, the class will not appear on the output raster. The sum of the specied a priori probabilities must be less than or equal to 1. The format of the le is as follows:
1 2 4 5 7 .3 .1 .0 .15 .05

Spatial Analyst toolbox

8 .2

The classes omitted in the le will receive the average a priori probability of the remaining portion of the value of 1. A specied reject fraction, which lies between any two valid values, will be assigned to the next upper valid value. For example, 0.02 will become 0.025. Principal Components: Performs principal components analysis on a set of raster bands.
PrincipalComponents <in_raster_bands;in_raster_bands...> <out_multiband_raster> {number_components} {out_data_le}

The value specied for the number of principal components determines the number of principal component layers in the output multiband raster. The number must not be larger than the total number of raster bands in the input. With the output data le name specied, the correlation and covariance matrices, as well as the eigenvalues and eigenvectors, will be stored in an ASCII le.
166 ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Neighborhood toolset

Contains tools to calculate a statistic or value based on the values at each processing cell and the values of the cells within an identied neighborhood. Block Statistics: Calculates statistics for a nonoverlapping neighborhood.
BlockStatistics <in_raster> <out_raster> {neighborhood} {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY} {DATA | NODATA}

For statistics type majority, cells where there is no single majority value (that is, two or more values within a block are tied as having the most number of cells with the value) will be assigned NoData. For statistics type minority, cells where there is no single minority value will similarly be assigned NoData. Filter: Performs a preset focal lter on a raster.
Filter <in_raster> <out_raster> {LOW | HIGH} {DATA | NODATA}

The LOW option is an averaging lter. The HIGH option is an edge enhancement lter. Focal Flow: Determines the ow of the values in the surface raster dataset within each cells immediate neighborhood.
FocalFlow <in_surface_raster> <out_raster> {threshold_value}

The resulting values of Focal Flow measure ow into, not out of, a cell. The output values of a function are derived from the binary representation of the results of the analysis. Focal Statistics: Calculates a statistic for each raster dataset cell value within a specied neighborhood.
FocalStatistics <in_raster> <out_raster> {neighborhood} {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY} {DATA | NODATA}

Spatial Analyst toolbox

When a circular, annulus-shaped, or wedge-shaped neighborhood is specied, since the center of the cell must be encompassed within the neighborhood, some of the outer diagonal cells may not be considered in the calculations. However, these cell locations will receive the resulting value from the calculations because they fall within the minimum bounding rectangle (or the output neighborhood) of the three circular neighborhoods. Line Statistics: Calculates a statistic on the attributes of lines in a circular neighborhood around each output cell in a raster dataset.
LineStatistics <in_polyline_features> <eld> <out_raster> {cell_size} {search_radius} {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY}

Only the part of a line within the neighborhood is considered for the majority, mean, median, and minority types. For the others, it does not matter whether a part or the whole line is used. If there are no lines in the neighborhood of a raster cell, then the variety statistic assigns a value of zero. For the other statistics, NoData is assigned. The statistic types majority, mean, median, and minority are weighted according to the length of the lines. If a line is twice as long as another one, its value is considered to occur twice as often. When the eld is integer, the available overlay statistic choices are: mean, majority, maximum, median, minimum, minority, range, STD, and variety. When the eld is oating point, the only allowed statistics are: mean, maximum, minimum, range, and STD.
167

Point Statistics: Calculates a statistic on the points in a neighborhood outputting a raster dataset.
PointStatistics <in_point_features> <eld> <out_raster> {cell_size} {neighborhood} {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY}

When the eld is integer, the available overlay statistic choices are: Mean, Majority, Maximum, Median, Minimum, Minority, Range, STD, Sum, Variety. When the eld is oating point, the only allowed statistics are: Mean, Maximum, Minimum, Range, STD, Sum. If there are no points in the neighborhood of a raster cell, then the variety statistic assigns a value of zero. For the other statistics, NoData is assigned.

Overlay toolset

Contains the tool to create an output surface by adding a series of weighted input raster datasets together. Weighted Overlay: Overlays several rasters using a common scale and weighing each according to its importance.
WeightedOverlay <raster{inuence} {eld} {remap};raster{inuence} {eld} {remap}...> <out_raster>

In the Illustration above, the two input rasters have been reclassied to a common measurement scale of 1 to 3. Each raster is assigned a percentage inuence. The cell values are multiplied by their percentage inuence, then added to create the output raster. For example, consider the top left cell. The values for the two inputs become (2 * .75) = 1.5 and (3 * .25) = .75. The sum of 1.5 and .75 is 2.25. Because the output raster from Weighted Overlay is integer, the nal value is rounded to 2. All input rasters need to be integers. A oating-point raster must rst be converted to an integer raster before it can be used in Weighted Overlay. The Reclassication tools provide an effective way to do the conversion. Each input raster is weighted according to its importance, or its percent inuence. The weight is a relative percentage, and the sum of the percent inuence weights must equal 100 percent. Weighted Sum: Overlays several rasters multiplying each by their given weight and summing them together.
WeightedSum <Raster {Field} {Weight};Raster {Field} {Weight}...> <out_raster>

Spatial Analyst toolbox

168

In the Illustration above, the cell values are multiplied by their weight factor, then added to create the output raster. For example, consider the top left cell. The values for the two inputs become (2.2 * .75) = 1.65 and (3 * .25) = .75. The sum of 1.5 and .75 is 2.4. Input rasters can be integer or oating point. The weight values can be any positive or negative decimal value. It is not restricted to be a relative percentage, or equal to 1.0. The weight will be applied to the specied eld for the input raster. Fields can be, short or long integer, double, or oat.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 The output raster will always be oating-point type.

Raster Creation toolset

Contains tools to create raster datasets based on a constant, random values, or a normal distribution using the existing cell size, extent, and other analysis properties. Create Constant Raster: Creates a raster dataset from a constant value.
CreateConstantRaster <out_raster> <constant_value> {INTEGER | FLOAT} {cell_size} {extent}

The constant value must be a numeric value. Scientic notation is accepted (for example, 3.048e-4). Create Normal Raster: Creates a raster dataset of random values from a normal distribution.
CreateNormalRaster <out_raster> {cell_size} {extent}

The random number generator is automatically seeded with the current value of the system clock (seconds since January 1, 1970). Reseeding the Create Random Raster tool also reseeds Create Normal Raster. The output from Create Normal Raster will have a mean of zero and a standard deviation of 1. If a different standard deviation is desired, multiply the output raster by that value. If a different mean is desired, add that value to the raster. For example, to create a raster where the values are characterized by a mean of 39 and a standard deviation of 2.5, multiply the results of Create Normal Raster by 2.5, then add 39. Create Random Raster: Creates a raster dataset of random numbers between zero and 1.
CreateRandomRaster <out_raster> {seed_value} {cell_size} {extent}

Spatial Analyst toolbox

Repeatedly using the same seed value or the default will not produce the same raster. The Random function creates numbers with up to 20 digits after the decimal point.

Reclass toolset

Contains tools to change the values assigned to cells in a thematic raster dataset. Lookup: Creates a new raster dataset by looking up values found in another eld in the table of the input raster dataset.
Lookup <in_raster> <lookup_eld> <out_raster>

If the lookup eld is a numeric type, the values of that eld will be written to the output raster attribute table as Value. Other items in the input raster attribute table will not be transferred to the output raster attribute table.

169

For example, an attribute table of input raster with numeric eld Attr1:
Value Count Attr1 1 294 1 2 345 8 3 654 3

Output attribute table from Lookup on Attr1 eld:

Value Count 1 294 3 654 8 345

Reclass by ASCII File: Reclassies (or changes) the values of the input cells of a raster dataset by using an ASCII remap le.
ReclassByASCIIFile <in_raster> <in_remap_le> <out_raster> {DATA | NODATA}

The output raster will always be of integer type. If the output assignment values in the ASCII le are oating-point values, an error message will be returned and the program will halt. Reclass by Table: Reclassies (or changes) the values of the input cells of a raster dataset by using a remap table.
ReclassByTable <in_raster> <in_remap_table> <from_value_eld> <to_value_eld> <output_value_eld> <out_raster> {DATA | NODATA}

The from value eld, to value eld, and output value eld are the eld names in the table that dene the remapping. To reclassify individual values, use a simple remap table of two items. The rst item identies the value to reclassify, and the other item the value to assign it. Set the to value eld to the same as the from value eld. The value to assign to the output is Output value eld. To reclassify ranges of values, the remap table must have items dening the start and end of each range, along with the value to assign the range. The item dening the start of the range is the from value eld, and the value dening the end of the range is the to value eld. The value to assign to the output is output value eld. The remap table can be an INFO table, a .dbf le, an Access table, or a text le. The values in the from and to elds can be any numerical item. The assignment values in the output eld must be integers. Values in the from eld of the table must be sorted in ascending order and should not overlap. Reclassify: Reclassies (or changes) the value of the cells in a raster dataset.
Reclassify <in_raster> <reclass_eld> <remap> <out_raster> {DATA | NODATA}

Spatial Analyst toolbox

170

The remap table can be stored with the Save button. The Load button allows previously created remap tables to be used. Only remap tables created by the tool should be used in Reclassify. If running the Reclassify tool as part of a model within a ModelBuilder window, run the tools before the Reclassify tool in the model rst. This will allow the values for the input raster to display properly in the Reclassication dialog box. Slice: Slices a range of values of the input cells of a raster by zones of equal interval, equal area, or by natural breaks.
Slice <in_raster> <out_raster> <number_zones> {EQUAL_INTERVAL | EQUAL_AREA | NATURAL_ BREAKS} {base_output_zone}

If a mask has been set, those cells that have been masked out will receive NoData on the output slice raster.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Solar Radiation toolset

Contains tools to perform solar radiation analysis. Area Solar Radiation: Derives incoming solar radiation from a raster surface.
AreaSolarRadiation <in_surface_raster> <out_global_radiation_raster> {latitude} {sky_ size} {time_conguration} {day_interval} {hour_interval} {NOINTERVAL | INTERVAL} {z_ factor} {FROM_DEM | FLAT_SURFACE} {calculation_directions} {zenith_divisions} {azimuth_ divisions} {UNIFORM_SKY | STANDARD_OVERCAST_SKY} {diffuse_proportion} {transmittivity} {out_direct_radiation_raster} {out_diffuse_radiation_raster} {out_direct_duration_ raster}

Because insolation calculations can be time consuming, it is important to be sure all parameters are correct. Calculation for a large digital elevation model can take hours, and a very large DEM could take days. The output radiation rasters will always be oating-point type and have units of watt hours per square meter (WH/m2). The direct duration raster output will be integer with unit hours. Points Solar Radiation: Derives incoming solar radiation for specic locations in a point feature class or location table.
PointsSolarRadiation <in_surface_raster> <in_points_feature_or_table> <out_global_ radiation_features> {height_offset} {latitude} {sky_size} {time_conguration} {day_ interval} {hour_interval} {NOINTERVAL | INTERVAL} {z_factor} {FROM_DEM | FLAT_SURFACE | FROM_POINTS_TABLE} {calculation_directions} {zenith_divisions} {azimuth_divisions} {UNIFORM_SKY | STANDARD_OVERCAST_SKY} {diffuse_proportion} {transmittivity} {out_ direct_radiation_features} {out_diffuse_radiation_features} {out_direct_duration_ features}

The input locations can be a feature class or table. The table can be an INFO table, a .dbf le, an Access table, or a text table le. When inputting locations by table, a list of locations must be specied with an x,y coordinate. For multiple-day time congurations, the maximum range of days is a total of one year (365 days, or 366 days for leap years). For within-day time congurations, the maximum range of time is one day (24 hours). Solar Radiation Graphics: Derives raster representations of a hemispherical viewshed, sunmap, and skymap, which are used in the calculation of direct, diffuse, and global solar radiation.
SolarRadiationGraphics <in_surface_raster> <out_viewshed_raster> {in_points_feature_ or_table} {sky_size} {height_offset} {calculation_directions} {latitude} {time_ conguration} {day_interval} {hour_interval} {out_sunmap_raster} {zenith_divisions} {azimuth_divisions} {out_skymap_raster}

Spatial Analyst toolbox

171

Outputs are raster representations and are not maps that correspond to the outputs from the area or point solar radiation analysis. Rather, they are representations of directions in a hemisphere of directions looking upward from a given location. In a hemispherical projection, the center is the zenith, the edge of the circular map is the horizon, and the angle relative to the zenith is proportional to the radius. Hemispherical projections do not have a geographic coordinate system and have a bottom left corner of (0,0). It would not be practical to store viewsheds for all locations in a DEM, so when input locations are not specied, a single viewshed is created for the center of the input surface raster. The input locations table can be an INFO table, a .dbf le, an Access table, or a text le. Output graphic display rasters do not honor extent or cell size environment settings. One or two sun map rasters may be generated, depending on whether the time conguration includes overlapping sun positions throughout the year.

Surface toolset

Contains tools to analyze the surface of the shapes represented by the raster values. Aspect: Identies the downslope direction of the maximum rate of change in value from each cell to its neighbors.
Aspect <in_raster> <out_raster>

Aspect is the direction of the maximum rate of change in the z-value from each cell in a raster surface. Aspect is expressed in positive degrees from zero to 359.9, measured clockwise from the north. Cells in the input raster of zero slope (for example, at) are assigned an aspect of -1. Contour: Creates contours or isolines from a raster dataset surface.
Contour <in_raster> <out_polyline_features> <contour_interval> {base_contour} {z_factor}

Smoother but less accurate contours may be obtained by rst performing a Neighborhood Focal Statistics operation with the mean option on the input raster. A base contour is used, for example, when you want to create contours every 15 meters, starting at 10 meters. Here, 10 would be used for the base contour, and 15 would be the contour interval. The values to be contoured would be 10, 25, 40, 55, and so on. Specifying a base contour does not prevent contours from being created above or below that value. Contour List: Creates contours or isolines based on a list of contour values.

Spatial Analyst toolbox

172

ContourList <in_raster> <out_polyline_features> <contour_values;contour_values...>

Smoother but less accurate contours may be obtained by rst performing a Neighborhood Focal Statistics operation with the mean option on the input raster. Curvature: Calculates the curvature of a raster surface, optionally including prole and plan curvature.
Curvature <in_raster> <out_curvature_raster> {z_factor} {out_prole_curve_raster} {out_plan_curve_raster}

The primary output is the curvature of the surface on a cell-by-cell basis, as tted through that cell and its eight surrounding neighbors. Curvature is the second derivative of the surface, or the slope of the slope. Two optional output curvature types are possible; the prole curvature is in the direction of the maximum slope, and the plan curvature is perpendicular to the direction of the maximum slope. A positive curvature indicates that the surface is upwardly convex at that cell. A negative curvature indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. In the prole output, a negative value indicates that the surface is upwardly convex at that cell. A positive prole indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. In the plan output, a positive value indicates that the surface is upwardly convex at that cell. A negative plan indicates that the surface is upwardly concave at that cell. A value of zero indicates that the surface is at. Units of the curvature output raster, as well as the units for the optional output prole curve raster and output plan curve raster, are one over 100 z units, or 1/100 (z units). The reasonably expected values of all three output rasters for a hilly area (moderate relief) may differ from about -0.5 to 0.5, while for the steep, rugged mountains (extreme relief), the values may vary between -4 and 4.
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Cut/Fill: Calculates the volume and area of cut and ll locations.

CutFill <in_before_surface> <in_after_surface> <out_raster> {z_factor}

The Cut/Fill tool enables you to create a map based on two input surfaces (before and after), displaying the areas and volumes of surface materials that have been modied by the addition or removal of surface material. Negative z-values indicate regions of the input before raster surface that have been lled; positive regions indicate cuts. To get accurate Cut/Fill results, the z units should be the same as the x,y ground units. This ensures that the resulting volumes are meaningful cubic measures (for example, cubic meters). If they are not the same, use a z-factor to convert z units to x,y units. For example, if your x,y units are meters and your z units are feet, you could specify a z-factor of 0.3048 to convert feet to meters. Hillshade: Creates a shaded relief raster by considering the illumination angle and shadows.
HillShade <in_raster> <out_raster> {azimuth} {altitude} {NO_SHADOWS | SHADOWS} {z_factor}

The Hillshade tool creates a shaded relief raster from a raster. The illumination source is considered at innity. Two types of shaded relief rasters can be output. Having model shadows unchecked outputs a raster that only considers the local illumination angle. Having model shadows checked outputs one that considers the effects of both the local illumination angle and shadow. Observer Points: Identies exactly which observer points are visible from each surface location.
ObserverPoints <in_raster> <in_observer_point_features> <out_raster> {z_factor} {FLAT_EARTH | CURVED_EARTH} {refractivity_coefcient}

Spatial Analyst toolbox

The visibility of each cell center is determined by comparing the altitude angle to the cell center with the altitude angle to the local horizon. The local horizon is computed by considering the intervening terrain between the point of observation and the current cell center. If the point lies above the local horizon, it is considered visible. Slope: Identies the rate of maximum change in z-value from each cell.
Slope <in_raster> <out_raster> {DEGREE | PERCENT_RISE} {z_factor}

Slope is the rate of maximum change in z-value from each cell. The use of a z-factor is essential for correct slope calculations when the surface z units are expressed in units different from the ground x,y units. Degree of slope is a value between zero and 90.

173

Viewshed: Derives the raster dataset surface locations visible to a set of observation points.
Viewshed <in_raster> <in_observer_features> <out_raster> {z_factor} {FLAT_EARTH | CURVED_ EARTH} {refractivity_coefcient}

The visibility of each cell center is determined by comparing the altitude angle to the cell center with the altitude angle to the local horizon. The local horizon is computed by considering the intervening terrain between the point of observation and the current cell center. If the point lies above the local horizon, it is considered visible.

Zonal toolset

Contains tools that can be applied to the zones within the raster dataset. Tabulate Area: Calculates cross-tabulated areas between two datasets.
TabulateArea <in_zone_data> <zone_eld> <in_class_data> <class_eld> <out_table> {processing_cell_size}

Zones are created by identical integer values. If the input is a raster, it must be integer. If the input is a feature class, the Zone eld must be integer. There will be a eld in the output table for each unique value of the input raster or feature zone data. There will be a record in the output table for each unique value of the input raster or feature class data. Each record in the output table will store the area of each class within each zone. If a point or line dataset is used as the class data, then the area intersected by those features will be reported. Zonal Fill: Fills zones in a dataset using the minimum cell value from another raster dataset along the zone boundary.
ZonalFill <in_zone_raster> <in_weight_raster> <out_raster>

Spatial Analyst toolbox

174

Zonal Fill can be used to ll sinks to the minimum elevation of their watershed boundary. This is a step in determining the depth of sinks before lling to create a depressionless digital elevation model. The input zone raster must be integer. Zonal Geometry: Calculates for each zone in a dataset the specied geometry measure (area, perimeter, thickness, or the characteristics of ellipse).
ZonalGeometry <in_zone_data> <zone_eld> <out_raster> {AREA | PERIMETER | THICKNESS | CENTROID} {cell_size}

Zones are created by identical integer values. If the input is a raster, it must be integer. If the input is a feature class, the zone eld must be integer. If the zone dataset is a feature dataset, it is recommended that you ensure the extent and snap rasters are set appropriately in the environment settings or raster settings. This will ensure that the results of the vector-to-raster conversion will align properly with the value raster. Zonal Geometry as Table: Calculates for each zone in a dataset the geometry measuresfor example, area, perimeter, thickness, and the characteristics of ellipseand reports the results as a table.
ZonalGeometryAsTable <in_zone_data> <zone_eld> <out_table> {processing_cell_size}

Zones are created by identical integer values. If the zone input is a raster, it must be integer. If the zone input is a feature class, the zone eld must be integer. If the input raster or feature zone data is a feature dataset, a cell size must be set in either the dialog box or the environment settings. To align the feature dataset to the value raster, it is recommended that the extent and snap rasters are set appropriately in the environment settings and raster settings.

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

 All the results in the output table are presented in map units. Only the values of the ORIENTATION item are in degrees, with a possible range of zero to 180. The ORIENTATION is dened as an angle between the x-axis and the major axis of the ellipse. The values of the orientation angle increase counterclockwise, starting from zero in the east (horizontal, to the right) and going through 90 when the major axis is vertical. An example of the Zonal Geometry As Table on the following input:

This would populate the output table as follows:

VALUE 0 1 2 4 AREA 5.0 5.0 6.0 2.0 PERIMETER 14.0 14.0 8.0 6.0 THICKNESS 0.5 0.5 0.5 0.5 XCENTROID 2.300 1.900 3.167 0.500 YCENTROID 2.100 2.100 2.167 1.000 MAJORAXIS 2.338 2.668 1.286 1.128 MINORAXIS 0.681 0.596 0.743 0.564 ORIENTATION 60.710 126.061 130.00 90.00

Zonal Statistics: Calculates a statistic on values of a raster within the zones of another dataset.
ZonalStatistics <in_zone_data> <zone_eld> <in_value_raster> <out_raster> {MEAN | MAJORITY | MAXIMUM | MEDIAN | MINIMUM | MINORITY | RANGE | STD | SUM | VARIETY} {DATA | NODATA}

The input value raster can be either integer or oating point. However, when it is of oating-point type, the zonal calculations for majority, median, minority, and variety are not available. For majority and minority, when there is a tie, the output for all cell locations in the zone are assigned the lowest of the tied values. Zonal Statistics as Table: Summarizes values of a raster dataset within the zones of another dataset and reports the results to a table.
ZonalStatisticsAsTable <in_zone_data> <zone_eld> <in_value_raster> <out_table> {DATA | NODATA}

Spatial Analyst toolbox

The input value raster can be either integer or oating point. However, when it is of oating-point type, the zonal calculations for majority, median, minority, and variety are not available. For majority and minority calculations, when there is a tie, the output for all cell locations in the zone are assigned the lowest of the tied values. The number of rows in the output table is the number of zones. An example of the output table is:
VALUE
0 1 2 4

COUNT
5 5 3 2

AREA
125.0000 125.0000 75.0000 50.0000

MEAN
0.6 1.0 1.667 3.0

MIN
0.0 0.0 1.0 3.0

MAX
0.0 3.0 2.0 3.0

...
... ... ... ...

175

176

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Tracking Analyst toolbox

This toolbox provides tools for preparing and loading temporal data into an ArcGIS application.
Concatenate Date and Time Fields: Concatenates two separate date and time elds into a new eld that is added to the same feature dataset.
ConcatenateDateAndTimeFields <feature_dataset> <date_eld> <time_eld> <output_eld>

Input values must be text type. This tool adds a new text eld to the input feature dataset. If you are working with a shapele that contains a date eld with the date only (for example, 03/09/2006), you must calculate the information into a new eld that is of type text before you can concatenate it with a time eld. Make Tracking Layer: Adds a feature dataset as a new tracking layer to your ArcMap session.
MakeTrackingLayer <feature_dataset> <date_eld> {track_eld} <output_name> {H:MM:SS TT | HH:MM:SS TT | H:MM:SS | HH:MM:SS} {M/D/YYYY | M/D/YY | MM/DD/YY | MM/DD/YYYY | YY/MM/DD | YYYY-MM-DD | DD-MMM-YY} {AM} {PM}

The feature dataset must have a date and time eld and a unique identier eld. If the date eld is string type, then you must specify the format of date and time.

Tracking Analyst toolbox

177

Index
Numbers and extensions
.e00 exporting to .................................................................. 27 importing from ............................................................. 29 3D Analyst toolbox ......................................................... 99 3D ASCII le converting to feature class............................................ 99 3D les importing ...................................................................... 99 3D layer converting to feature class............................................ 99

A
Absolute value. See Abs command Abs command ............................................................... 148 ACosH command .......................................................... 161 ACos command............................................................. 160 AddCADFields command............................................... 16 AddCodedValueToDomain command ............................ 45 AddColormap command ................................................. 66 AddFeatureClassToTerrain command........................... 113 AddFeatureClassToTopology command ......................... 73 AddFieldToAnalysisLayer command ........................... 123 AddField command......................................................... 52 AddGlobalIDs command ................................................ 44 AddIndex command ........................................................ 59 Adding. See also Plus command attribute index .............................................................. 59 CAD elds.................................................................... 16 coded value to domain ................................................. 45 color maps .................................................................... 66 elds ............................................................................. 52 indexes ......................................................................... 59 items ............................................................................. 35 joins ............................................................................. 60 rules to topology........................................................... 74 spatial indexes .............................................................. 59 subtypes ........................................................................ 71 x,y coordinates ....................................................... 37, 48 AddItem command.......................................................... 35 AddJoin command .......................................................... 60 AddLocations command ............................................... 123 AddRepresentation command ......................................... 12 Address geocoding ..................................................................... 79 locator creating ......................................................................79 deleting ......................................................................79 rebuilding ..................................................................80 rematching .................................................................... 80 standardizing ................................................................ 80

AddressBuild. See RebuildGeocodingIndex command AddressCreate. See CreateAddressLocator command AddressMatch. See GeocodeAddresses command AddressParse. See StandardizeAddresses command AddRouteMeasure. See LocateFeaturesAlongRoutes command AddRuleToTopology command ...................................... 74 AddSpatialIndex command............................................. 59 AddSubtype command .................................................... 71 AddTerrainPoints command ......................................... 113 AddTerrainPyramidLevel command ............................. 113 AddXY command ..................................................... 37, 48 Adjust. See Transform command Adjust3DZ command ...................................................... 49 ADRGGrid. See CopyRaster command Advanced Tiger Conversion. See TigerTool command Aggregate command .................................................................... 135 toolset ........................................................................... 30 AggregatePolygons command .................................. 32, 56 Aggregate Polygons. See AreaAggregate command Alias described ........................................................................ 2 list ... ............................................................................... 2 AlignMarkerToStrokeOrFill command .......................... 13 AlterVersion command ................................................... 75 Analysis toolbox ........................................................................... 5 toolset ................................................................... 23, 123 Analyze command .......................................................... 72 Analyzing clusters and outliers ................................................ 86, 87 hot spots ....................................................................... 87 Analyzing Patterns toolset .............................................. 85 And bitwise ........................................................................ 153 Boolean ...................................................................... 155 combinatorial ............................................................. 156 Annotation importing from CAD .................................................... 18 importing from coverage .............................................. 19 AppendAnnotation command ......................................... 47 Append command ..................................................... 30, 54 ArcDLG command.......................................................... 27 ArcDXF. See ExportCAD command ArcEditor licensing ......................................................................... 2 ArcIGDS. See ExportCAD command ArcInfo licensing ......................................................................... 2 ArcInfo workspace creating ......................................................................... 76 ArcRoute command ........................................................ 31 ArcS57 command............................................................ 28 ArcSDE checking in ................................................................... 43 checking out ................................................................. 43
179

Index

ArcSection. See CreateRoutes command ArcShape. See FeatureClassToShapele command ArcTiger. See TigerArc command. See TigerTool command ArcTIN. See Editing: TINs ArcView licensing ......................................................................... 2 Area calculating .................................................................... 90 creating polygon features ............................................. 50 AreaAggregate. See AggregatePolygons command AreaSolarRadiation command ...................................... 171 Arguments ......................................................................... 2 ASCII converting to raster....................................................... 15 Ascii3DToFeatureClass command.................................. 99 ASCIIGrid. See ASCII: converting to raster ASCIIToRaster command ............................................... 20 ASinH command........................................................... 161 ASin command.............................................................. 161 Aspect command................................................... 110, 172 AssignDefaultToField command .................................... 53 AssignDomainToField command ................................... 45 Assigning domain to eld ............................................................. 45 ATan2 command ........................................................... 162 ATanH command .......................................................... 162 ATan command ............................................................. 162 Attributes joining tables ................................................................ 35 Attribute tables for raster data ............................................................... 69 Autocorrelation ............................................................... 86 AutomateGeocodingIndexes command .......................... 79 AverageNearestNeighbor command ............................... 85

B
BandCollectionStats command ..................................... 164 Band Collection Statistics. See BandCollectionStats command Base 10. See Exp10 command. See Log10 command Base 2. See Exp2 command. See Log2 command Base e. See Exp command Basic Tiger Conversion. See TigerArc command Basin command............................................................. 139 Batch projecting ..................................................................... 63 BatchBuildPyramids command ...................................... 66 BatchCalculateStatistics command ................................. 66 BatchProject command ................................................... 63 Bitwise And . ........................................................................... 153 complement. See BitwiseNot command Exclusive Or ............154. See also BitwiseXOr command left shift ...................................................................... 153 Not .. ........................................................................... 154
180

Bitwise (continued) Or ............ ................................................................. .154 right shift .................................................................... 154 toolset ......................................................................... 153 BitwiseAnd command................................................... 153 BitwiseLeftShift command ........................................... 153 BitwiseNot command.................................................... 154 BitwiseOr command ..................................................... 154 BitwiseRightShift command ......................................... 154 BitwiseXOr command .................................................. 154 Bitwise Complement. See BitwiseNot command Bitwise Exclusive Or. See BitwiseXOr command BlockMajority. See BlockStatistics command BlockMax. See BlockStatistics command BlockMean. See BlockStatistics command BlockMedian. See BlockStatistics command BlockMin. See BlockStatistics command BlockMinority. See BlockStatistics command BlockRange. See BlockStatistics command BlockStatistics command .............................................. 167 BlockStd. See BlockStatistics command BlockSum. See BlockStatistics command BlockVariety. See BlockStatistics command. Boolean and 155 complement. See BooleanNot command exclusive or ................................................................ 156 not .............................................................................. 155 or ..... .......................................................................... 156 BooleanAnd command.................................................. 155 BooleanNot command .................................................. 155 BooleanOr command .................................................... 156 BooleanXOr command ................................................. 156 Boolean Complement. See BooleanNot command BoundaryClean command............................................. 135 Buffer command ........................................................................ 8 using multiple rings ........................................................ 8 Buffer command ............................................................. 25 Building pyramids ....................................................................... 66 raster attribute tables .................................................... 66 simplication ................................................................ 34 BuildNetwork command ............................................... 124 BuildPyramids command ................................................ 66 BuildRasterAttributeTable command ............................. 66 BuildSta. See CellStatistics command BuildTerrain command ................................................. 113 Build command ............................................................... 38

Index

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

C
Cache delete for GlobeServer ................................................. 93 delete for MapServer .................................................... 93 generate for GlobeServer ............................................. 93 generate for MapServer ................................................ 94 update for GlobeServer ................................................ 94 update for MapServer................................................... 95 Caching toolset ........................................................................... 93 CAD importing ..................................................................... 19 importing annotation .................................................... 18 CalculateAreas command ............................................... 90 CalculateDefaultClusterTolerance command ................. 47 CalculateDefaultGridIndex command ............................ 47 CalculateDistanceBand command .................................. 90 CalculateEndDate command........................................... 53 CalculateField command ................................................ 53 CalculateGeodesicAngle command ................................ 13 CalculateLineCaps command ......................................... 13 CalculateLocationFields command............................... 123 CalculateLocations command ....................................... 123 CalculatePolygonMainAngle command ......................... 14 CalculateRepresentationRule command ......................... 12 CalculateStatistics command .......................................... 66 CalculateValue command................................................ 55 Calculating cluster tolerance ........................................................... 47 elds ............................................................................. 53 kernel density ............................................................. 128 spatial grid index .......................................................... 59 statistics ........................................................................ 66 summary statistics .......................................................... 9 CalibrateRoutes command .............................................. 81 CAnd. See CombinatorialAnd command Cartography toolbox ....................................................... 11 CellStatistics command................................................. 145 Cell groupings using isodata clustering .............................................. 166 Centerline creating ......................................................................... 32 CentralFeature command ................................................ 88 CentroidLabels. See FeatureToPoint command ChangePrivileges command............................................ 72 ChangeTerrainReferenceScale command ..................... 113 CheckGeometry command.............................................. 49 CheckInDelta command.................................................. 43 Checking in from Delta geodatabases .............................................. 43 to ArcSDE .................................................................... 43 Checking out from ArcSDE................................................................ 43 CheckIn command .......................................................... 43 CheckOut command........................................................ 43

ClassProb. See ClassProbability command ClassProbability command ........................................... 164 ClassSig. See CreateSignatures command Cleaning boundaries .................................................................. 135 Clean command .............................................................. 38 Clip command ....................................................... 5, 23, 67 Clustering high/low ....................................................................... 85 ClustersOutliersRendered command .............................. 87 ClustersOutliers command .............................................. 86 Cluster and outlier analysis ....................................... 86, 87 Cluster tolerance calculating .................................................................... 47 setting ........................................................................... 74 CollapseDualLinesToCenterline command .................... 57 CollapseDualLineToCenterline command ...................... 32 CollectEventsRendered command .................................. 90 CollectEvents command ................................................. 90 Color maps adding ........................................................................... 66 deleting ......................................................................... 69 Combinatorial and .. ........................................................................... 156 exclusive or ................................................................ 157 or ..... .......................................................................... 156 CombinatorialAnd command ........................................ 156 CombinatorialOr command .......................................... 156 CombinatorialXOr command........................................ 157 Combine command ....................................................... 145 Combining features. See Append command Compact command ......................................................... 42 CompareReplicaSchema command ................................ 44 Comparing features ......................................................................... 41 les .. ............................................................................ 41 rasters ........................................................................... 41 tables ............................................................................ 41 TINs ............................................................................ 42 CompositeBands command ............................................ 67 Composite Features toolset ............................................. 31 CompressFileGeodatabaseData command...................... 54 Compressing data . ............................................................................. 54 Compress command ........................................................ 42 ConcatenateDateAndTimeFields command ................. 177 Conditional toolset ........................................................ 127 Conicts nding .......................................................................... 33 Contouring from a TIN.................................................................. 116 ContourList command .......................................... 111, 172 Contour command................................................. 111, 172 Conversion toolbox ......................................................................... 15 toolset ..................................................................... 27, 99

Index

181

ConvertImage. See CopyRaster command Converting to feature class .............................................................. 18 to shapele ................................................................... 18 ConvertRemap. See ReclassByASCIIFile command Con command ............................................................... 127 Coordinates adding x,y ..................................................................... 37 CopyFeatures command.................................................. 49 Copying features ......................................................................... 49 feature classes .............................................................. 55 feature datasets ............................................................. 55 raster catalog items....................................................... 68 rows in a table .............................................................. 72 tables ............................................................................ 55 CopyRasterCatalogItems command................................ 68 CopyRaster command ..................................................... 67 CopyRows command ...................................................... 72 Copy command ............................................................... 55 COr. See CombinatorialOr command Corridor command ........................................................ 129 CosH command............................................................. 163 Cost calculating least accumulative distance ..................... 130 least accumulative ...................................................... 130 least accumulative distance path ..................................................................130, 132 least accumulative path dene neighbor cell .................................................129 least accumulative source........................................... 132 CostAllocation command.............................................. 129 CostBackLink command............................................... 129 CostDistance command ................................................ 130 CostPath command ....................................................... 130 Cos command................................................................ 163 Counting table rows. See GetCount command CountRenderer command ............................................... 91 Coverages appending ..................................................................... 30 combining..................................................................... 30 creating ......................................................................... 39 erasing .......................................................................... 24 exporting as text le ..................................................... 28 exporting to DLG ......................................................... 27 generating ..................................................................... 29 generating topology...................................................... 38 importing from DLG .................................................... 29 importing from S57 ...................................................... 29 importing from SDTS .................................................. 30 importing from VPF ..................................................... 30 projecting ..................................................................... 36 setting tolerances .......................................................... 38 toolbox ......................................................................... 23 transforming ................................................................. 36

Coverages (continued) updating ........................................................................ 25 updating attribute table and topology........................... 38 CreateAddressLocator command .................................... 79 CreateArcInfoWorkspace command ............................... 76 CreateCADXData command .......................................... 17 CreateConstantRaster command ................................... 169 CreateCustomGeoTransformation command ................. 62 CreateDomain command ................................................ 46 CreateFeatureClass command ......................................... 47 CreateFeatureDataset command ..................................... 76 CreateFishnet command.................................................. 47 CreateFolder command ................................................... 76 CreateLabels command ................................................... 39 CreateNormalRaster command ..................................... 169 CreateOrthoCorrectedRasterDataset command .............. 68 CreateOverpass command .............................................. 14 CreatePansharpenedRasterDataset command ................. 68 CreatePersonalGDB command ....................................... 77 CreateRandomPoints command ...................................... 48 CreateRandomRaster command.............................. 68, 169 CreateRasterCatalog command....................................... 68 CreateRasterDataset command ....................................... 69 CreateRelationshipClass command ................................ 71 CreateReplicaFootPrints command ................................ 44 CreateReplicaFromServer command .............................. 44 CreateReplica command ................................................. 44 CreateRoutes command .................................................. 81 CreateSignatures command .......................................... 165 CreateSpatialReference command .................................. 63 CreateTable command .................................................... 72 CreateTerrain command ................................................ 113 CreateThiessenPolygons command .................................. 8 CreateTIN command..................................................... 114 CreateTopology command .............................................. 74 CreateTurnFeatureClass command ............................... 125 CreateUnderpass command ............................................ 14 CreateVersion command ................................................. 75 CreateWorkspace. See CreateArcInfoWorkspace command Create command ............................................................. 39 Creating address locators ............................................................ 79 ArcInfo workspaces ..................................................... 76 CAD x data................................................................... 17 centerlines .................................................................... 32 coverages ...................................................................... 39 custom geographic transformations ............................. 62 domains ........................................................................ 46 feature classes .............................................................. 47 feature datasets ............................................................. 76 folders........................................................................... 76 layers ............................................................................ 60 multiband raster datasets .............................................. 67 personal geodatabases .................................................. 77 raster catalogs ............................................................... 68 raster datasets ....................................................... 69, 169

Index

182

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Creating (continued) relationship classes ....................................................... 71 spatial references .......................................................... 63 tables ............................................................................ 72 tables from domains ..................................................... 46 table to relationship classes .......................................... 71 terrains ........................................................................ 113 TINs .......................................................................... 114 topology ....................................................................... 74 versions ........................................................................ 75 CuldeSacMasks command .............................................. 11 Curvature command .............................................. 111, 172 Custom tool ....................................................................... 1 CutFill command .................................................. 111, 173 CXOr. See CombinatorialXOr command

D
DarcyFlow command .................................................... 137 DarcyVelocity command............................................... 138 Data compressing ................................................................. 54 selecting ....................................................................... 56 Database toolset .............................................................. 42 Datasets copying ......................................................................... 55 deleting ......................................................................... 55 renaming....................................................................... 56 uncompressing ............................................................. 54 Data Comparison toolset ................................................. 41 Data Interoperability toolbox ........................................ 119 Data Management toolbox .............................................. 41 Data Management toolset ............................................... 30 DBaseInfo. See TableToGeodatabase command DBMSInfo. See TableToGeodatabase command DeautomateGeocodingIndexes command ...................... 79 DecimateTinNodes command ....................................... 115 DeneProjection command....................................... 36, 62 DeleteAddressLocator command .................................... 79 DeleteCodedValueFromDomain command .................... 46 DeleteColormap command ............................................. 69 DeleteDomain command ................................................ 46 DeleteFeatures command ................................................ 49 DeleteField command ..................................................... 53 DeleteGlobeServerCache command ............................... 93 DeleteMapServerCache command.................................. 93 DeleteRasterAttributeTable command ............................ 69 DeleteRasterCatalogItems command .............................. 69 DeleteRows command .................................................... 73 DeleteVersion command ................................................. 75 Delete command ............................................................. 55 Deleting address locators ............................................................ 79 coded values from domains.......................................... 46 domains ........................................................................ 46 features ......................................................................... 49 feature classes .............................................................. 55

Deleting (continued) feature datasets ............................................................. 55 elds in a table ............................................................. 53 geodatabase versions .................................................... 75 items in a raster catalog ................................................ 68 raster datasets ............................................................... 55 rows in a table .............................................................. 73 tables ............................................................................ 55 DelineateTinDataArea command .................................. 114 Delta geodatabase checking in ................................................................... 43 checking out ................................................................. 43 DEM converting to raster..................................................... 143 DEMGrid. See DEM: converting to raster DEMLattice. See DEM: converting to raster DEMToRaster command ................................................ 20 Dendrogram command.................................................. 165 Density calculating kernel ....................................................... 128 calculating using line features .................................... 128 calculating using point features.................................. 128 toolset ......................................................................... 128 DetectGraphicConict command.................................... 11 DFADArc. See Feature class: converting to coverage Diff command ............................................................... 157 DirectionalDistribution command .................................. 88 DirectionalMean command ............................................. 88 Directions command ..................................................... 123 Disconnected Editing toolset .......................................... 43 DissolveRouteEvents command ..................................... 81 Dissolve command .................................................... 33, 57 Dissolving route events .................................................................. 81 Distance toolset ............................................................. 129 Distributed Geodatabase toolset ..................................... 44 Divide command ........... 108, 148. See also Mod command DLG importing to coverage .................................................. 29 DLGArc command.......................................................... 29 Domain creating ......................................................................... 46 creating from table ....................................................... 46 deleting ......................................................................... 46 removing from eld ..................................................... 46 setting value for range .................................................. 46 Domains toolset .............................................................. 45 DomainToTable command .............................................. 46 Drainage. See Hydrology toolset DropIndex command ....... 35. See RemoveIndex command DropItem command ........................................................ 35 Dropping indexes ......................................................................... 35 items ............................................................................. 35 DropRepresentation command........................................ 12 DTEDGrid. See CopyRaster command

Index

183

DXFArc. See ImportCAD command DXFINFO. See ImportCAD command

E
Editing TINs .......................................................................... 115 EditSig. See EditSignatures command EditSignatures command .............................................. 165 EditTin command .......................................................... 115 Eliminate command .................................................. 33, 57 Ellipse .............................................................................. 2 Envelopes creating polygons from ................................................ 49 EqualityTest. See EqualTo command EqualToFrequency command ....................................... 146 EqualTo command ........................................................ 157 Erase command ........................................................... 6, 24 ESRITranslator command ............................................... 16 ESRI Metadata Translator ............................................... 16 ETAKArc. See FeatureClassToCoverage command EucAllocation command............................................... 131 EucDirection command ................................................ 131 EucDistance command.................................................. 131 Euclidean allocating ............ 131. See also EucAllocation command direction ............... 131. See also EucDirection command distance..................131. See also EucDistance command Euclidean Allocation. See EucAllocation command Euclidean Direction. See EucDirection command Euclidean Distance. See EucDistance command EventArc. See MakeRouteEventLayer command EventPoint. See MakeRouteEventLayer command Events dissolving for routes ..................................................... 81 transforming routes ...................................................... 82 EventTransform. See TransformRouteEvents command Example tool ..................................................................... 2 Exclusive arguments ......................................................... 2 Exclusive Or bitwise ........................................................................ 154 Boolean ...................................................................... 156 combinatorial ............................................................. 157 Exp10 command ........................................................... 149 Exp2 command ............................................................. 149 Expand command.......................................................... 135 Exponential. See Exp command base 10........................................................................ 149 base 2.......................................................................... 149 base e .......................................................................... 148 ExportAcknowledgementMessage command ................. 44 ExportCAD command .................................................... 17 ExportDataChangeMessage command ........................... 44 Exporting feature attribute to ASCII ............................................. 91 to CAD ......................................................................... 17 to Delta geodatabase .................................................... 43
184

Exporting (continued) to interchange le ......................................................... 27 to S57 ........................................................................... 28 to SDTS ........................................................................ 28 to VPF .......................................................................... 28 ExportReplicaSchema command .................................... 44 ExportToDelta command ................................................ 43 ExportXYv command ..................................................... 91 Export command ............................................................. 27 Exp command ............................................................... 148 ExtractByAttributes command...................................... 133 ExtractByCircle command ............................................ 133 ExtractByMask command............................................. 133 ExtractByPoints command............................................ 134 ExtractByPolygon command ........................................ 134 ExtractByRectangle command...................................... 134 Extraction toolset .......................................................... 133 ExtractValuesToPoints command ................................. 134 Extract toolset ............................................................. 5, 23 ExtrudeBetween command ........................................... 115

F
FeatureClassToCoverage command................................ 17 FeatureClassToFeatureClass command .......................... 18 FeatureclassToGeodatabase command ........................... 18 FeatureclassToShapele command ................................. 22 FeatureClassZToASCII command .................................. 99 FeatureCompare command ............................................. 41 FeatureEnvelopeToPolygon command ........................... 49 FeatureOutlineMasks command ..................................... 11 Features buffering ......................................................................... 8 center of concentration ................................................. 89 centrally located ........................................................... 88 concentration or dispersion .......................................... 89 converting to raster....................................................... 20 copying ......................................................................... 49 deleting ......................................................................... 49 dissolving ..................................................................... 57 eliminating ................................................................... 57 erasing ............................................................................ 6 extracting ........................................................................ 5 locating along routes .................................................... 81 splitting........................................................................... 5 toolset ........................................................................... 48 unioning ......................................................................... 7 FeatureToLine command ................................................ 50 FeatureToNetCDF command .......................................... 83 FeatureToPoint command ............................................... 50 FeatureToPolygon command .......................................... 50 FeatureToRaster command ............................................. 20 FeatureVerticesToPoints command ................................. 51 Feature class adding to terrain ......................................................... 113 combining..................................................................... 54 comparing..................................................................... 41
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Index

Feature class (continued) converting to coverage ................................................. 18 converting to feature class............................................ 18 converting to shapele ................................................. 18 copy to geodatabase ..................................................... 18 creating ......................................................................... 47 intersecting ..................................................................... 6 remove from topology .................................................. 74 toolset ........................................................................... 47 updating attributes and geometry ................................... 7 Feature toolset ................................................................. 63 Fields adding ........................................................................... 52 assigning default to ...................................................... 53 calculating .................................................................... 53 deleting ......................................................................... 53 toolset ........................................................................... 52 transposing time ........................................................... 53 FileCompare command ................................................... 41 Fill command ................................................................ 140 Filter command ............................................................. 167 FindConicts command .................................................. 33 Flipping raster data ..................................................................... 63 Flip command ................................................................. 63 Float command ............................................................ 108, 149 convert to raster .......................................................... 169 FloatGrid. See FloatToRaster command FloatToRaster command ................................................. 21 Flow. See DarcyFlow command FlowAccumulation command ....................................... 140 FlowDirection command .............................................. 140 FlowLength command .................................................. 141 FMod. See Mod command FocalFlow command..................................................... 167 FocalMajority. See FocalStatistics command FocalMax. See FocalStatistics command FocalMean. See FocalStatistics command FocalMedian. See FocalStatistics command FocalMin. See FocalStatistics command FocalMinority. See FocalStatistics command FocalRange. See FocalStatistics command FocalStatistics command .............................................. 167 FocalStd. See FocalStatistics command FocalSum. See FocalStatistics command FocalVariety. See FocalStatistics command Folder creating ......................................................................... 76 Frequency command ......................................................... 9 From Coverage toolset .................................................... 27 From Feature Class toolset.............................................. 99 From File toolset ............................................................. 99 From Raster toolset ................................................. 15, 100 From Terrain toolset ...................................................... 101 From TIN toolset........................................................... 101 Functional Surface toolset............................................. 103

G
GACalculateZValue command ..................................... 121 GACreateGeostatisticalLayer command ...................... 121 GAGetModelParameter command................................ 121 GALayerToContour command ..................................... 121 GALayerToGrid command ........................................... 121 GALayerToPoints command ........................................ 121 GAMovingWindowKriging command ......................... 121 GANeighborhoodSelection command .......................... 122 GASemivariogramSensitivity command ...................... 122 GASetModelParameter command ................................ 122 Generalization toolset ....................................... 32, 56, 135 Generalize. See Lines: simplifying General toolset ................................................................ 54 GenerateGlobeServerCache command ........................... 93 GenerateMapServerCacheTilingScheme command ....... 94 GenerateMapServerCache command.............................. 94 Generate command ......................................................... 29 GeocodeAddresses command ......................................... 79 Geocoding addresses ...................................................................... 79 deautomating indexes ................................................... 79 index rebuilding ..................................................................80 toolbox ......................................................................... 79 Geodatabase creating ......................................................................... 77 Geometries checking ....................................................................... 49 repairing ....................................................................... 52 Geostatistical Analyst toolbox ...................................... 121 Geostatistical layer converting to contours ................................................ 121 converting to grid ....................................................... 121 converting to points .................................................... 121 creating ....................................................................... 121 GetCount command ........................................................ 73 Getis-Ord General G ....................................................... 85 Getis-Ord Gi*.................................................................. 87 GetRasterProperties command........................................ 69 GlobeServer cache generate ........................................................................ 93 update ........................................................................... 94 Globe Server cache delete ............................................................................ 93 Graphic Quality toolset ................................................... 11 GreaterThanEqual command ........................................ 158 GreaterThanFrequency command ................................. 146 GreaterThan command.................................................. 158 GridASCII. See RasterToASCII command GridClip. See ExtractByRectangle command GridComposite. See CompositeBands command GridFlip. See Flip command GridFloat. See RasterToFloat command GridImage. See CopyRaster command GridLine. See RasterToPolyline command
185

Index

GridLineShape. See RasterToPolyline command GridMirror. See Mirror command GridPoint. See RasterToPoint command GridPointShape. See RasterToPoint command GridPoly. See RasterToPolygon command GridRotate. See Rotate command GridShape. See RasterToPolygon command GridShift. See Shift command GridWarp. See Warp command Groundwater calculating steady ow ............................................... 137 dispersion of point ...................................................... 139 toolset ......................................................................... 137

H
HighestPosition command ............................................ 146 HighLowClustering command ........................................ 85 HillShade command .............................................. 112, 173 HotSpotsRendered command.......................................... 87 HotSpot command .......................................................... 87 Hydrodynamic dispersion. See PorousPuff command Hydrology toolset.......................................................... 139

I
IDEdit command ............................................................. 37 Identity command ....................................................... 6, 24 IDs updating ...................................................................... 125 IDW command ...................................................... 105, 142 IGDSArc. See ImportCAD command IGDSInfo. See ImportCAD command ImageGrid. See CopyRaster command Import3DFiles command ................................................ 99 ImportCADAnnotation command .................................. 18 ImportCAD command .................................................... 19 ImportCoverageAnnotation command............................ 19 Importing CAD annotation ........................................................... 18 coverage annotation ..................................................... 19 from CAD .................................................................... 19 from interchange le .................................................... 29 from S57 ....................................................................... 29 from SDTS ................................................................... 30 from VPF ...................................................................... 30 ImportMessage command ............................................... 45 ImportReplicaSchema command .................................... 45 Import command ............................................................. 29 IncreaseMaximumEdges command .............................. 125 Index adding ........................................................................... 59 adding spatial index ..................................................... 59 automating geocoding index ........................................ 79 dropping ....................................................................... 35 item .............................................................................. 35 rebuilding for geocoding .............................................. 80 removing ................................................................ 59, 60
186

Indexes toolset .......................................................... 35, 59 IndexItem command ....... 35. See also AddIndex command Info joining tables ................................................................ 35 InfoDBASE. See TableToDBASE command InList command ............................................................ 158 Integer converting from. See Int command Integrate command.......................................................... 48 Interoperability tools ..................................................... 119 InterpolatePolyToPatch command ................................ 116 InterpolateShape command ........................................... 103 Interpolating a raster dataset .................................................... 105, 142 calculating the trend on a point dataset ...................... 145 raster surfaces ..................................................... 105, 142 z-values ...................................................................... 103 Interpolation toolset ...................................................... 142 Intersecting coverages ................................................................ 24, 25 IntersectingLayersMasks command................................ 12 Intersect command ...................................................... 6, 24 Int command ......................................................... 108, 149 Inverse distance weighted ..................................... 105, 142 IsNull command ............................................................ 159 IsoCluster command ..................................................... 166 Item adding ........................................................................... 35 dropping ....................................................................... 35 indexing ........................................................................ 35 Items toolset .................................................................... 35

Index

J
Joining attribute tables .............................................................. 60 info tables ..................................................................... 35 JoinItem command .......................................................... 35 Joins adding ........................................................................... 60 removing ...................................................................... 60 toolset ..................................................................... 35, 60

K
KernelDensity command .............................................. 128 Kill. See Delete command KML create from layer ........................................................ 103 create from map ......................................................... 103 creating ....................................................................... 103 le conversion ............................................................ 103 Kriging. See Krige command. See Kriging command Kriging command ................................................. 105, 143

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

L
LAS converting to multipoint ............................................. 100 LASToMultipoint command ......................................... 100 LatticeClip. See ExtractByPolygon command LatticeContour. See Contour command Layer make from feature ........................................................ 60 make from query table ................................................. 61 make from raster .......................................................... 61 make from raster catalog .............................................. 61 make from x,y events ................................................... 61 Layer3DToFeatureClass command ................................. 99 Layers and Table Views toolset....................................... 60 LayerToKML command ............................................... 103 LessThanEqual command ............................................. 159 LessThanFrequency command ..................................... 146 LessThan command ...................................................... 159 Licensing ArcEditor ........................................................................ 2 ArcInfo ........................................................................... 2 ArcView ......................................................................... 2 tools ...........................................................................A-1 Linear directional mean .................................................. 88 Linear Referencing toolbox ............................................ 81 LineDensity command .................................................. 128 LineGrid. See FeatureToRaster command LineOfSight command .................................................. 104 Lines converting coverage to region .....................................................31 coverage to route .......................................................31 creating from polygon .................................................. 50 generating for polygon ................................................. 51 simplifying ............................................................. 34, 58 smoothing ..................................................................... 59 splitting at vertices ....................................................... 52 LineStatistics command ................................................ 167 LineStats. See LineStatistics command Ln command ................................................................. 150 Local toolset .................................................................. 145 LocateFeaturesAlongRoutes command .......................... 81 Locating features along routes .................................................... 81 Log10 command ........................................................... 150 Log2 command ............................................................. 150 Logarithm. See also Ln command base 10........................................................................ 150 base 2.......................................................................... 150 base e .......................................................................... 150 natural......................................................................... 150 Logical toolset............................................................... 155 Lookup command ................................................. 109, 169 LowestPosition command ............................................. 146

M
Majority. See CellStatistics command MajorityFilter command ............................................... 136 MakeClosestFacilityLayer command ........................... 123 MakeFeatureLayer command ......................................... 60 MakeNetCDFFeatureLayer command ............................ 83 MakeNetCDFRasterLayer command.............................. 83 MakeNetCDFTableView command ................................ 83 MakeODCostMatrixLayer command ........................... 124 MakeQueryTable command ............................................ 61 MakeRasterCatalogLayer command ............................... 61 MakeRasterLayer command ........................................... 61 MakeRouteEventLayer command .................................. 82 MakeRouteLayer command .......................................... 124 MakeServiceAreaLayer command................................ 124 MakeTableView command ............................................. 61 MakeTrackingLayer command ..................................... 177 MakeXYEventLayer command ...................................... 61 Mapping Clusters toolset ................................................ 86 MapServer cache delete ............................................................................ 93 generate ........................................................................ 94 tiling scheme ................................................................ 94 update ........................................................................... 95 MapToKML command ................................................. 103 Map Algebra single output ............................................................... 148 statements ................................................................... 147 toolset ......................................................................... 147 Mask creating cul-de-sac ................................................. 11, 12 creating from feature outline ........................................ 11 Masking toolset ............................................................... 11 Masks at interecting layers ...................................................... 12 cul-de-sacs .................................................................... 11 outlining features.......................................................... 11 MasksFromFeatureOutlineMasks command .................. 11 MasksFromIntersectingLayersMasks command ............ 12 Math toolset .................................................................. 148 Max. See CellStatistics command Maximum Likelihood Classication. See MLClassify command MDPublisher command .................................................. 16 Mean. See CellStatistics command MeanCenter command .................................................... 89 MeasureRoute. See CreateRoutes command Measuring Geographic Distributions toolset .................. 88 Med. See CellStatistics command MergeBranch command .................................................. 55 Merge command ............................................................. 55 Metadata publisher ....................................................................... 16 translator....................................................................... 16 XSLT translation .......................................................... 16 Metadata toolset .............................................................. 16
187

Index

Min. See CellStatistics command Minimum curvature. See Spline command Minority. See CellStatistics command Minus command.................................................... 108, 150 Mirror command ............................................................. 64 MLClassify command................................................... 166 Model tool ......................................................................... 1 Mod command .............................................................. 150 Morans I .......................................................................... 86 MosaicToNewRaster command ...................................... 70 Mosaic command ............................................................ 69 Multiband raster dataset creating ......................................................................... 67 Multidimension toolbox .................................................. 83 MultiDistanceSpatialClustering command ..................... 85 MultiOutputMapAlgebra command.............................. 147 MultipartToSinglepart command .................................... 51 Multipart feature converting to single-part feature .................................. 51 MultiPatchFootprint command ....................................... 99 MultipleRingBuffer command .......................................... 8 Multiply. See Times command Multivariate toolset ....................................................... 164

Overlaying route events .................................................................. 82 OverlayRouteEvents command ...................................... 82 Overlay toolset .................................................... 6, 24, 168 Overpasses creating ......................................................................... 14 Over command .............................................................. 160

P
Pan-sharpening raster data ..................................................................... 68 Parameters ......................................................................... 2 optional........................................................................... 2 required .......................................................................... 2 Particle calculating path .......................................................... 138 ParticleTrack command ................................................ 138 PathAllocation command .............................................. 132 PathBackLink command ............................................... 133 PathDistance command................................................. 132 Pick command............................................................... 127 PivotTable command ...................................................... 73 Plus command ....................................................... 109, 151 Point calculating at surface. See SurfaceSpot command PointDensity command ................................................. 128 PointDistance command ............................................. 9, 26 PointGrid. See FeatureToRaster command PointNode command....................................................... 26 Points calculating at surface. See SurfaceSpot command calculating distance between .................................... 9, 26 calculating distance from ......................................... 9, 26 creating from features .................................................. 50 creating from vertices................................................... 51 transferring attributes to node features......................... 26 PointsSolarRadiation command .................................... 171 PointStatistics command ............................................... 168 PointToRaster command ................................................. 21 Polygons aggregating ................................................................... 32 converting coverages to regions ................................... 31 converting to lines ........................................................ 51 dissolving ..................................................................... 33 merging ........................................................................ 33 Thiessen ......................................................................... 8 PolygonToLine command ............................................... 51 PolygonToRaster command ............................................ 21 PolyGrid. See FeatureToRaster command PolylineToRaster command ............................................ 21 PolyRegion command ..................................................... 31 Popularity command ..................................................... 147 PopulateAlternateIDFields command ........................... 125 PorousPuff command .................................................... 139 PostVersion command..................................................... 75 Power command............................................................ 151
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

N
NaturalNeighbor command................................... 105, 143 Nearest neighbor ............................................................. 85 Near command ............................................................ 9, 26 Negate command .......................................................... 151 Neighborhood selection ................................................ 122 Neighborhood toolset .................................................... 167 NetCDF layers ............................................................................ 83 tools for ........................................................................ 83 Networks building ...................................................................... 124 Network Analyst toolbox .............................................. 123 Network Dataset toolset ................................................ 124 Nibble command ........................................................... 136 Nodes renumber ...................................................................... 37 Normal. See CreateNormalRaster command Not bitwise ........................................................................ 154 Boolean ...................................................................... 155 NotEqual command ...................................................... 159

Index

O
ObserverPoints command ..................................... 112, 173 Or bitwise ........................................................................ 154 Boolean ...................................................................... 156 combinatorial ............................................................. 156 Orthorectify raster data ..................................................................... 68 Outlier and cluster analysis ....................................... 86, 87
188

PrincipalComponents command ................................... 166 PrinComp. See PrincipalComponents command Privileges changing ....................................................................... 72 ProjectDene. See DeneProjection command ProjectGrid. See ProjectRaster command Projecting ........................................................................ 63 rasters ........................................................................... 64 Projection dening................................................................... 36, 62 Projections and Transformations toolset ......................... 62 Projections toolset ........................................................... 36 ProjectRaster command .................................................. 64 Project command ...................................................... 36, 63 Properties for raster data ............................................................... 69 Proximity toolset ......................................................... 8, 25 Pyramids adding to terrain ......................................................... 113 building for rasters ....................................................... 66 removing from terrain ................................................ 114

Q
QuickExport command ................................................. 119 QuickImport command ................................................. 119

R
Range. See CellStatistics command Rank command ............................................................. 147 RasterCompare command ............................................... 41 RasterDomain command............................................... 100 Rasters classication ............................................................... 166 RasterTIN command ..................................................... 100 RasterToASCII command ............................................... 15 RasterToFloat command ................................................. 15 RasterToGeodatabase command ..................................... 19 RasterToNetCDF command ............................................ 84 RasterToOtherFormat command ..................................... 22 RasterToPoint command ................................................. 15 RasterToPolygon command ............................................ 15 RasterToPolyline command ............................................ 15 Raster attribute tables building ........................................................................ 66 Raster catalogs copying items ............................................................... 68 creating ......................................................................... 68 deleting items ............................................................... 69 making layers ............................................................... 61 Raster Creation toolset .................................................. 169 Raster datasets calculating accumulated ow ..................................... 140 calculating aspect ......................................................... 15 calculating band statistics............................................. 66 calculating drainage basins ........................................ 139 calculating ow direction ........................................... 140

Raster datasets (continued) calculating ow distance ............................................ 141 calculating slope ................................................. 112, 173 calculating statistics ............................................. 66, 167 calculating surface length........................................... 104 calculating surface values .......................................... 103 calculating surface visibility ...................................... 104 calculating surface volume......................................... 104 calculating weighted overlay ..................................... 168 changing cell values. See Reclassify command changing scale .............................................................. 64 clipping......................................................................... 67 combining................................................................... 145 comparing..................................................................... 41 converting from TINs ................................................. 102 converting to ASCII ..................................................... 15 converting to linear network features......................... 142 converting to points ...................................................... 15 converting to polygons ................................................. 15 converting to polylines ................................................. 15 converting values to oat ..................................... 15, 149 converting values to integer. See Int command creating ................................................. 69, 105, 108, 169 creating ASCII le of selected cells ........................... 134 creating contours ................................................ 111, 172 creating surface. See Raster Interpolation toolset creating TINs .............................................................. 114 creating using elevation data .............................. 143, 144 extracting cells using attributes ........................................................133 using a mask ............................................................133 using points .............................................................134 within a circle ..........................................................133 within a polygon ......................................................134 within a rectangle ....................................................134 extracting cell values using points .............................................................134 interpolating ............................................... 105, 116, 142 majority lter.............................................................. 136 making layers ............................................................... 61 mosaicking ............................................................. 69, 70 performing a classication ......................................... 166 principal components ................................................. 166 projecting ..................................................................... 64 reclassifying ............................................... 109, 110, 170 recording least cost path ............................................. 130 reducing resolution ..................................................... 135 replacing cell values. See Nibble command resampling .................................................................... 70 rotating ......................................................................... 64 solar radiation ............................................................. 171 surface calculating viewable areas ...............................112, 174 removing sinks ........................................................140 surface ow values ..................................................... 167 transforming ................................................................. 63 viewshed............................................................. 112, 174
189

Index

Raster Interpolation toolset ........................................... 105 Raster Math toolset ....................................................... 108 Raster Reclass toolset ................................................... 109 Raster Surface toolset ................................................... 110 Raster toolset............................................................. 63, 66 RebuildAddressLocator .................................................. 80 RebuildGeocodingIndex command ................................ 80 Rebuilding geocoding indexes ........................................................ 80 Reclass. See ReclassByTable command. See also ReclassByTable command toolset ......................................................................... 169 ReclassByASCIIFile command ............................ 109, 170 ReclassByTable command .................................... 110, 170 Reclassify command ............................................. 110, 170 ReconcileVersion command............................................ 75 Reconciling versions ........................................................................ 75 Rectify. See ProjectRaster command Reducing database sizes.................................................. 42 ReExportUnacknowledgedMessages command ............. 45 Reference scale terrains ........................................................................ 113 RegionClass command.................................................... 31 RegionGroup command ................................................ 136 RegionPoly command ..................................................... 31 Regions converting to polygon coverages ................................. 31 grouping ..................................................................... 136 RegisterAsVersioned command ...................................... 76 Relationship Classes toolset............................................ 71 RematchAddresses .......................................................... 80 RemoveDomainFromField command............................. 46 RemoveFeatureClassFromTerrain command................ 114 RemoveFeatureClassFromTopology command .............. 74 RemoveIndex command ................................................. 59 RemoveJoin command .................................................... 60 RemoveOverride command ............................................ 12 RemoveRuleFromTopology command ........................... 74 RemoveSpatialIndex command ...................................... 60 RemoveSubtype command ............................................. 71 RemoveTerrainPoints command ................................... 114 RemoveTerrainPyramidLevel command ...................... 114 Removing attribute indexes ........................................................... 59 feature classes from topologies .................................... 74 joins ............................................................................. 60 rules from topologies ................................................... 74 spatial indexes .............................................................. 60 Rename command........................................................... 56 Rendering collecting events and .................................................... 90 counts ........................................................................... 91 with hot spot analysis ................................................... 87 Renode command............................................................ 37 Renumbering nodes ............................................................................ 37
190

RepairGeometry command ............................................. 52 Representations add .. ............................................................................. 12 calculate rule ................................................................ 12 creating overpasses ...................................................... 14 creating underpasses .................................................... 14 drop . ............................................................................ 12 remove overrides .......................................................... 12 select features by overrides .......................................... 13 seting control point....................................................... 14 update overrides ........................................................... 13 Representation Management toolset ............................... 12 Resample command ........................................................ 70 Rescale command ........................................................... 64 Reselect command ................23. See also Select command Rotate command ............................................................. 64 RoundDown command ................................................. 151 RoundUp command ...................................................... 152 Routes calibrating..................................................................... 81 creating ......................................................................... 81 creating from line coverages ........................................ 31 locating features along ................................................. 81 overlaying events ......................................................... 82 transforming events ...................................................... 82 Route layer create .......................................................................... 124 Rows copying ......................................................................... 72 counting ........................................................................ 73 deleting ......................................................................... 73 Rubber sheeting rasters ................................................... 65 Rules adding to topology ....................................................... 74 removing from topology .............................................. 74

Index

S
S57Arc command............................................................ 29 Sample command .......................................................... 134 SaveToLayerFile command ............................................ 61 Saving layer les ...................................................................... 61 Scale changing ....................................................................... 64 Script tool .......................................................................... 1 SDTSExport command ................................................... 28 SDTSImport command ................................................... 30 SelectBox. See ExtractByRectangle command SelectByDimension command ........................................ 84 SelectCircle. See ExtractByCircle command SelectData command ...................................................... 56 SelectFeatureByOverride command ............................... 13 Selecting by attributes .................................................................. 62 by locations .................................................................. 62 data . ............................................................................. 56
ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Selecting (continued) layers by attributes ....................................................... 62 layers by locations ........................................................ 62 SelectLayerByAttribute command.................................. 62 SelectLayerByLocation command .................................. 62 SelectMask. See ExtractByMask command SelectPoint. See ExtractByPoints command SelectPolygon. See ExtractByPolygon command SelectPolygon command. See ExtractByPolygon command Select command ................................................................ 5 Semivariogram sensitivity ............................................ 122 Server toolbox ......................................................................... 93 Service area layer create .......................................................................... 124 SetCADAlias command .................................................. 17 SetClusterTolerance command ....................................... 74 SetDefaultSubtype command.......................................... 72 SetNull command.......................................................... 127 SetRepresentationControlPointByAngle command........ 14 SetSubtypeField command ............................................. 72 Setting CAD aliases.................................................................. 17 SetValueForRangeDomain command ............................. 46 Shaded relief. See Hillshade command ShapeGrid. See FeatureToRaster command Shift command ................................................................ 65 Shrink command ........................................................... 137 Signatures les creating ....................................................................... 165 creating probability layers .......................................... 164 editing......................................................................... 165 SimplifyBuilding command ...................................... 34, 58 Simplifying buildings ....................................................................... 34 lines ............................................................................. 34 SimplifyLineOrPolygon command ................................. 34 SimplifyLine command .................................................. 58 SingleOutputMapAlgebra command ............................ 148 SinH command.............................................................. 163 Sink command .............................................................. 141 Sin command ................................................................ 163 Slice command ...................................................... 110, 170 Slope command..................................................... 112, 173 SmoothLine command .................................................... 59 SnapPour. See SnapPourPoint command SnapPourPoint command .............................................. 141 SnapPout. See SnapPourPoint command SolarRadiationGraphics command ............................... 171 Solar radiation deriving incoming ...................................................... 171 representing ................................................................ 171 toolset ......................................................................... 171 Solve command............................................................. 124 SpatialAutocorrelation command ................................... 86

SpatialJoin command ........................................................ 6 Spatial Analyst toolbox ................................................. 127 Spatial grid index calculating .................................................................... 47 Spatial reference creating ......................................................................... 63 upgrading ..................................................................... 42 Spatial Statistics toolbox ................................................. 85 Spline command.................................................... 105, 143 SplitLine command ......................................................... 52 Split command ............................................................ 5, 23 SQR. See Square command SQRT. See SquareRoot command SquareRoot command ................................................... 152 Square command........................................................... 152 StandardDistance command............................................ 89 StandardizeAddresses command .................................... 80 Standardizing addresses ...................................................................... 80 Standard deviational ellipse ............................................ 88 Statistics calculating for a block ................................................ 167 calculating for raster..................................................... 66 calculating summary ...................................................... 9 command ........................................................................ 9 frequency ........................................................................ 9 of a cell ....................................................................... 145 toolset ............................................................................. 9 StreamLink command ................................................... 141 StreamOrder command ................................................. 141 StreamShape. See StreamToFeature command StreamToFeature command .......................................... 142 Subtract. See Minus command Subtypes setting ........................................................................... 72 Subtypes toolset .............................................................. 71 Subtype elds setting ........................................................................... 72 Sum. See CellStatistics command Summary Statistics. See Statistics: command Summing two raster datasets ...................................................... 151 Surface aspect .................................................................. 110, 172 slope ................................................................... 112, 173 toolset ......................................................................... 172 SurfaceLength command .............................................. 104 SurfaceSpot command .................................................. 104 SurfaceVolume command ............................................. 104 Symbolization Renement toolset .................................. 13 SymDiff command ............................................................ 7 Symmetrical difference ..................................................... 7 SynchronizeChanges command ...................................... 45 Syntax example ................................................................. 2 System tool ....................................................................... 1

Index

191

T
TableCompare command ................................................ 41 Tables calculating frequency ..................................................... 9 comparing..................................................................... 41 converting or copying to tables .................................... 19 converting to dBASE ............................................. 18, 19 copying ......................................................................... 55 creating ......................................................................... 72 creating from domains ................................................. 46 creating pivot tables ..................................................... 73 deleting ......................................................................... 55 importing to geodatabases ............................................ 19 making table views....................................................... 61 renaming....................................................................... 56 selecting ......................................................................... 5 TableSelect command ....................................................... 5 Tables toolset .................................................................. 37 TableToDBASE command .............................................. 18 TableToDomain command .............................................. 46 TableToGeodatabase command ...................................... 19 TableToNetCDF command ............................................. 84 TableToRelationshipClass command .............................. 71 TableToTable command .................................................. 19 Table toolset .................................................................... 72 TabulateArea command ................................................ 174 TanH command ............................................................. 164 Tan command ................................................................ 163 Temporary layers making. See Layers and Table Views toolset Terrains adding feature class .................................................... 113 adding pyramid .......................................................... 113 building ...................................................................... 113 creating ....................................................................... 113 points .................................................................. 113, 114 reference scale ............................................................ 113 remove pyramid ......................................................... 114 TerrainToRaster command ............................................ 101 TerrainToTin command ................................................. 101 Terrain toolset ............................................................... 113 Test command ............................................................... 160 Thiessen polygons ......................................................................... 8 Thiessen command.......................................................... 27 Thin command .............................................................. 137 TigerArc command ......................................................... 29 TigerTool command ........................................................ 28 Tiger conversion advanced....................................................................... 28 basic ............................................................................ 29 Tiling Scheme to generate MapServer cache ....................................... 94 Times command .................................................... 109, 153 TINArc. See FeatureClassToCoverage command TinAspect command ..................................................... 116
192

TinCompare command .................................................... 42 TinContour command ................................................... 116 TinDifference command ............................................... 116 TinDomain command ................................................... 101 TinEdge command ........................................................ 101 TINHull. See TINDomain command TINLattice. See TINRaster command TINLines. See TINEdge command TinLine command ......................................................... 101 TinNode command ........................................................ 102 TinPolygonTag command ............................................. 102 TinPolygonVolume command....................................... 117 TinRaster command ...................................................... 102 TINs calculating aspect ....................................................... 116 calculating contours ................................................... 116 calculating slope ......................................................... 117 converting to raster datasets ....................................... 102 creating ....................................................................... 114 editing......................................................................... 115 extracting edges.......................................................... 101 extracting interpolation zones .................................... 101 extracting nodes ......................................................... 102 extracting polygon tag information ............................ 102 extracting triangle polygons ....................................... 103 TinSlope command ....................................................... 117 TINSpot. See SurfaceSpot command TinTriangle command ................................................... 103 TIN Creation toolset ..................................................... 114 TIN Surface toolset ....................................................... 115 Tolerance command ...................................................................... 38 setting cluster tolerances .............................................. 74 Tolerances toolset............................................................ 38 Tool licensing .....................................................................A-1 Toolbox 3D Analyst.................................................................... 99 Analysis .......................................................................... 5 Cartography .................................................................. 11 Conversion ................................................................... 15 Coverage ...................................................................... 23 Data Interoperability .................................................. 119 Data Management ........................................................ 41 described ........................................................................ 1 Geocoding .................................................................... 79 Geostatistical Analyst ................................................. 121 Linear Referencing ....................................................... 81 Multidimension ............................................................ 83 Network Analyst ........................................................ 123 Server ........................................................................... 93 Spatial Analyst ........................................................... 127 Spatial Statistics ........................................................... 85 Tracking Analyst ........................................................ 177

Index

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Tools custom ............................................................................ 1 model .............................................................................. 1 script ............................................................................... 1 system............................................................................. 1 Toolset Aggregate ..................................................................... 30 Analysis ................................................................ 23, 123 Analyzing Patterns ....................................................... 85 Bitwise ....................................................................... 153 Caching ........................................................................ 93 Composite Features ...................................................... 31 Conditional ................................................................. 127 Conversion ............................................................. 27, 99 Database ....................................................................... 42 Data Comparison.......................................................... 41 Data Management ........................................................ 30 Density ....................................................................... 128 described ........................................................................ 1 Disconnected Editing ................................................... 43 Distance ...................................................................... 129 Distributed Geodatabase .............................................. 44 Domains ....................................................................... 45 Extract ...................................................................... 5, 23 Extraction ................................................................... 133 Feature .......................................................................... 63 Features ........................................................................ 48 Feature Class ................................................................ 47 Fields ............................................................................ 52 From Coverage ............................................................. 27 From Feature Class ...................................................... 99 From File ...................................................................... 99 From Raster .......................................................... 15, 100 From Terrain............................................................... 101 From TIN ................................................................... 101 Functional Surface ..................................................... 103 General ......................................................................... 54 Generalization ................................................ 32, 56, 135 Graphic Quality ............................................................ 11 Groundwater............................................................... 137 Hydrology .................................................................. 139 Indexes ................................................................... 35, 59 Interpolation ............................................................... 142 Items ............................................................................. 35 Joins ...................................................................... 35, 60 Layers and Table Views ............................................... 60 licensing .....................................................................A-1 Local........................................................................... 145 Logical ....................................................................... 155 Mapping Clusters ......................................................... 86 Map Algebra ............................................................... 147 Masking ........................................................................ 11 Math ........................................................................... 148 Measuring Geographic Distributions ........................... 88 Metadata ....................................................................... 16 Multivariate ................................................................ 164

Toolset (continued) Neighborhood............................................................. 167 Network Dataset ......................................................... 124 Overlay ............................................................. 6, 24, 168 Projections .................................................................... 36 Projections and Transformations .................................. 62 Proximity .................................................................. 8, 25 Raster ..................................................................... 63, 66 Raster Creation ........................................................... 169 Raster Interpolation .................................................... 105 Raster Math ................................................................ 108 Raster Reclass ............................................................ 109 Raster Surface ............................................................ 110 Reclass ....................................................................... 169 Relationship Classes .................................................... 71 Representation Management ........................................ 12 Solar Radiation ........................................................... 171 Subtypes ....................................................................... 71 Surface ....................................................................... 172 Symbolization Renement ........................................... 13 Table ............................................................................. 72 Tables ........................................................................... 37 Terrain ........................................................................ 113 TIN Creation .............................................................. 114 TIN Surface ................................................................ 115 Tolerances .................................................................... 38 Topology ................................................................ 38, 73 To CAD ........................................................................ 16 To Coverage ........................................................... 17, 28 To dBASE .................................................................... 18 To Geodatabase ............................................................ 18 To KML ...................................................................... 103 To Raster ...................................................................... 20 To Shapele .................................................................. 22 Trigonometric ............................................................. 160 Turn Feature Class ..................................................... 125 Utilities ......................................................................... 90 Versions ........................................................................ 75 Workspace .................................................................... 76 Workspace Management .............................................. 39 Zonal .......................................................................... 174 Topology adding feature classes................................................... 73 adding rules .................................................................. 74 creating ......................................................................... 74 removing feature classes .............................................. 74 removing rules.............................................................. 74 toolset ..................................................................... 38, 73 validating ...................................................................... 75 TopoToRasterByFile command ............................ 106, 144 TopoToRaster command ....................................... 106, 143 To CAD toolset ............................................................... 16 To Coverage toolset .................................................. 17, 28 To dBASE toolset ........................................................... 18 To Geodatabase toolset ................................................... 18 To KML toolset ............................................................. 103

Index

193

To Raster toolset ............................................................. 20 To Shapele toolset ......................................................... 22 Tracking Analyst toolbox .............................................. 177 Transforming raster datasets ............................................................... 63 route events .................................................................. 82 TransformRouteEvents command................................... 82 Transform command ....................................................... 36 TransposeTimeFields command ..................................... 53 Trend command .................................................... 107, 145 Trigonometric toolset .................................................... 160 TurnTableToFeatureClass command ............................ 125 TurnTableToTurnFeatureClass command ..................... 125 Turn feature class create .......................................................................... 125 Turn Feature Class toolset............................................. 125

Visibility. See LineOfSight command. See also Viewshed command. Volume. See SurfaceVolume command VPF creating tile topology ................................................... 39 VPFExport command...................................................... 28 VPFImport command...................................................... 30 VPFTile command .......................................................... 39

W
Warp command ............................................................... 65 Watershed command ..................................................... 142 WeightedOverlay command.......................................... 168 WeightedSum command ............................................... 168 Workspace creating ......................................................................... 76 toolset ........................................................................... 76 WorkspaceToRasterCatalog command ........................... 70 WorkspacetoRasterDataset command ............................. 70 Workspace Management toolset ..................................... 39

U
UncompressFileGeodatabaseData command.................. 54 Uncompressing dataset........................................................................... 54 Underpasses creating ......................................................................... 14 Ungenerate command ..................................................... 28 Union command .......................................................... 7, 25 UnregisterAsVersioned command .................................. 76 Unregistering as versioned .................................................................. 76 UpdateAnnotation command .......................................... 48 UpdateByAlternateIDFields command ......................... 125 UpdateByGeometry command...................................... 125 UpdateGlobeServerCache command .............................. 94 UpdateMapServerCache command ................................ 95 UpdateOverride command .............................................. 13 Update command ........................................................ 7, 25 Updating IDs .. ............................................................................. 37 UpgradeSpatialReference command ............................... 42 USGSMPTranslator command ....................................... 16 Utilities toolset ................................................................ 90

X
XOr. See Exclusive Or XSLTransform command ................................................ 16

Index

Z
Z-value calculating .................................................................. 121 ZonalArea. See TabulateArea command ZonalCentroid. See ZonalGeometry command ZonalFill command ....................................................... 174 ZonalGeometryAsTable command ............................... 174 ZonalGeometry command .....................................174. See also ZonalGeometryAsTable command ZonalMajority. See ZonalStatistics command ZonalMax. See ZonalStatistics command ZonalMean. See ZonalStatistics command ZonalMedian. See ZonalStatistics command ZonalMin. See ZonalStatistics command ZonalMinority. See ZonalStatistics command ZonalPerimeter. See ZonalGeometry command ZonalRange. See ZonalStatistics command ZonalStatisticsAsTable command ................................. 175 ZonalStatistics command .............................................. 175 ZonalStats. See ZonalStatisticsAsTable command ZonalStd. See ZonalStatistics command ZonalSum. See ZonalStatistics command ZonalThickness. See ZonalGeometry command ZonalVariety. See ZonalStatistics command Zonal toolset.................................................................. 174 ZRenderer command....................................................... 91 Z score rendering ............................................................ 91

V
ValidateTopology command ........................................... 75 Variety. See CellStatistics command Velocity. See DarcyVelocity command Versions altering ......................................................................... 75 changing edit session ................................................... 75 creating ......................................................................... 75 deleting ......................................................................... 75 reconciling .................................................................... 75 registering..................................................................... 76 toolset ........................................................................... 75 unregistering................................................................. 76 Viewshed command .............................................. 112, 174 VisdeCode. See ObserverPoints command
194

ArcGIS 9: Geoprocessing Commands Quick Reference Guide

Appendix A: Tool licensing

The core toolboxes contain a mixture of tools available with specic license levels. These are shown in the tables below. The Coverage toolbox is only available with the ArcInfo license. All tools provided with extensions are available at any license level.

Appendix A

Analysis toolbox
Toolset/Tool
Extract toolset Clip Select Split Table Select Overlay toolset Erase Identity Intersect Spatial Join Symmetrical Difference Union Update Proximity toolset Buffer Create Thiessen Polygons Multiple Ring Buffer Near Point Distance Statistics toolset Frequency Summary Statistics

ArcView ArcEditor ArcInfo

A-1

Cartography toolbox Appendix A

Toolset/Tool
Graphic Quality toolset Detect Graphic Conict Masking Tools toolset Cul-De-Sac Masks Feature Outline Masks Intersecting Layers Masks Representation Management toolset Add Representation Calculate Representation Rule Drop Representation Remove Override Select Feature By Override Set Layer Representation Update Override Symbolization Renement toolset Align Marker To Stroke Or Fill Calculate Geodesic Angle Calculate Line Caps Calculate Polygon Main Angle Create Overpass Create Underpass Set Representation Control Point By Angle

ArcView ArcEditor ArcInfo

A-2

Conversion toolbox Appendix A

Toolset/Tool
From Raster toolset Raster To ASCII Raster To Float Raster To Point Raster To Polygon Raster To Polyline Metadata toolset ESRI Metadata Translator Metadata Publisher USGS MP Metadata Translator XSLT Translator To CAD toolset Add CAD Fields Create CAD XData Export To CAD Set CAD Alias To Coverage toolset Feature Class To Coverage To dBASE toolset Table To dBASE (multiple) To Geodatabase toolset Feature Class To Feature Class Feature Class To Geodatabase (multiple) Import CAD Annotation Import Coverage Annotation Import From CAD Raster To Geodatabase (multiple) Table To Geodatabase (multiple) Table To Table To Raster toolset ASCII To Raster DEM To Raster Feature To Raster Float To Raster Point To Raster Polygon To Raster Polyline To Raster Raster To Other Format (multiple) To Shapele toolset Feature Class To Shapele (multiple)
A-3

ArcView ArcEditor ArcInfo

Data Management toolbox Appendix A

Toolset/Tool
Data Comparison toolset Feature Compare File Compare Raster Compare Table Compare TIN Compare Database toolset Compact Compress Upgrade Spatial Reference Disconnected Editing toolset Check In Check In From Delta Check Out Export To Delta Distributed Geodatabase toolset Add Global IDs Compare Replica Schema Create Replica Create Replica Footprints Create Replica From Server Export Acknowledgment Message Export Data Change Message Export Replica Schema Import Message Import Replica Schema Re-Export Unacknowledged Messages Synchronize Changes Domains toolset Add Coded Value To Domain Assign Domain To Field Create Domain Delete Coded Value From Domain Delete Domain Domain To Table Remove Domain From Field Set Value For Range Domain Table To Domain

ArcView ArcEditor ArcInfo

A-4

Feature Class toolset Append Annotation Feature Classes Calculate Default Cluster Tolerance Calculate Default Spatial Grid Index Create Feature Class Create Fishnet Create Random Points Integrate Update Annotation Feature Class Features toolset Add XY Coordinates Adjust 3D Z Check Geometry Copy Features Delete Features Feature Envelope To Polygon Feature To Line Feature To Point Feature To Polygon Feature Vertices To Points Multipart To Singlepart Polygon To Line Repair Geometry Split Line At Vertices Fields toolset Add Field Assign Default To Field Calculate End Date Calculate Field Delete Field Transpose Time Fields File Geodatabase toolset Compress File Geodatabase Data Uncompress File Geodatabase Data General toolset Append Calculate Value Copy Delete Merge Merge Branch Rename Select Data

ArcView ArcEditor ArcInfo

Appendix A

A-5

Generalization toolset

ArcView ArcEditor ArcInfo

Appendix A

Aggregate Polygons Collapse Dual Lines To Centerline Dissolve Eliminate Simplify Building Simplify Line Simplify Polygon Smooth Line Indexes toolset Add Attribute Index Add Spatial Index Remove Attribute Index Remove Spatial Index Joins toolset Add Join Remove Join Layers and Table Views toolset Make Feature Layer Make Query Table Make Raster Catalog Layer Make Raster Layer Make Table View Make XY Event Layer Save To Layer File Select Layer By Attribute Select Layer By Location Projections and Transformations toolset Create Custom Geographic Transformation Dene Projection Feature toolset Batch Project Create Spatial Reference Project Raster toolset Flip Mirror Project Raster Rescale Rotate Shift Warp
A-6

Raster toolset Add Colormap Batch Build Pyramids Batch Calculate Statistics Build Pyramids Build Raster Attribute Table Calculate Statistics Clip Composite Bands Copy Raster Copy Raster Catalog Items Create Ortho-Corrected Raster Dataset Create Pan-Sharpened Raster Dataset Create Random Raster Create Raster Catalog Create Raster Dataset Delete Colormap Delete Raster Attribute Table Delete Raster Catalog Items Get Raster Properties Mosaic Mosaic To New Raster Resample Workspace To Raster Catalog Workspace To Raster Dataset Relationship Classes toolset Create Relationship Class Table To Relationship Class Subtypes toolset Add Subtype Remove Subtype Set Default Subtype Set Subtype Field Table toolset Analyze Change Privileges Copy Rows Create Table Delete Rows Get Count Pivot Table

ArcView ArcEditor ArcInfo

Appendix A

A-7

Topology toolset

ArcView ArcEditor ArcInfo

Appendix A

Add Feature Class To Topology Add Rule To Topology Create Topology Remove Feature Class From Topology Remove Rule From Topology Set Cluster Tolerance Validate Topology Versions toolset Alter Version Create Version Delete Version Post Version Reconcile Version Register As Versioned Unregister As Versioned Workspace toolset Create ArcInfo Workspace Create Feature Dataset Create File Geodatabase Create Folder Create Personal Geodatabase

Geocoding toolbox
Tool
Create Address Locator Geocode Addresses Rebuild Address Locator Rematch Addresses Standardize Addresses

ArcView ArcEditor ArcInfo

Linear Referencing Toolbox

Tool
Calibrate Routes Create Routes Dissolve Route Events Locate Features Along Routes Make Route Event Layer Overlay Route Events Transform Route Events

ArcView ArcEditor ArcInfo

A-8

Multidimension Toolbox Appendix A

Tool
Feature To NetCDF Make NetCDF Feature Layer Make NetCDF Raster Layer Make NetCDF Table View Raster To NetCDF Select By Dimension Table To NetCDF

ArcView ArcEditor ArcInfo

Server Toolbox
Tool
Delete Globe Server Cache Delete Map Server Cache Generate Globe Server Cache Generate Map Server Cache Generate Map Server Cache Tiling Scheme Update Globe Server Cache Table To NetCDF

ArcView ArcEditor ArcInfo

Requires 3D Analyst extension

A-9

Spatial Statistics toolbox Appendix A

Toolset/Tool
Analyzing Patterns toolset Average Nearest Neighbor High/Low Clustering (Getis-Ord General G) Multi-Distance Spatial Cluster Analysis (Ripleys K Function) Spatial Autocorrelation (Morans I) Mapping Clusters toolset Cluster And Outlier Analysis (Anselin Local Morans I) Cluster/Outlier Analysis With Rendering Hot Spot Analysis (Getis-Ord Gi*) Hot Spot Analysis With Rendering Measuring Geographic Distributions toolset Central Feature Directional Distribution (Standard Deviational Ellipse) Linear Directional Mean Mean Center Standard Distance Utilities toolset Calculate Areas Calculate Distance Band From Neighbor Count Collect Events Collect Events With Rendering Count Rendering Export Feature Attribute To ASCII Z Score Rendering

ArcView ArcEditor ArcInfo

A-10