Append (Data Management)

Usage tips

• Use Append when you have an existing dataset into which you want to append new data. Input datasets can be point, line or polygon feature classes, tables, rasters or raster catalogs.

• When the inputs are features, all input features must be of the same feature type as the features of the target dataset. For example, if the target feature class contains polygon features, the input features types must be polygon as well.

• Input datasets may overlap one another and/or the target dataset.

• Input datasets in a different coordinate system from the target featureclass will be projected into the coordinate system of the target featureclass.

• Unlike the Union function, Append does not planarize the input features into a single output. Input features from all the input feature classes remain intact in the target feature class.

• If the TEST option is specified, the field definitions of the feature classes must be the same and in the same order for all appended features.

• If the NO TEST option is selected, input features schemas do not have to match the target feature classes's schema. However, information in the input feature class's fields which do not match the target feature class's schema will not be carried into the target unless the FieldMap parameter is used.

• The Field Map parameter can only be issued if the NO TEST option is selected in the schema type parameter.

• When NO TEST is selected, the Field Map parameter can be used to control the output attribute content of input features. For example, consider the case where both the input and target feature classes have fields containing population information but the name of the fields are different (e.g. pop vs population). If you do not manipulate the FieldMap control features from the input featureclass will get a null value for the population field. Using the FieldMap, you can set the it such that the input features will get their values for the population field from the input pop field. For more information please see the How to Perform Field Mapping help page.

• Current map layers may be used to define input features. When using layers, only the currently selected features are used in the Append operation.

• Append cannot use multiple input layers of the same name. Although ArcMap allows for the display of layers with the same name (from different directories) these may not be used in the Append tool. For example, although c:\roads and d:\redlands\roads are two distinct datasets

• Append does not perform edge matching. There will be no adjustment to the boundaries of features. Edge matching can be performed through ArcMap (or ArcINFO Workstation) only.

• Learn more about working with layers and table views

• Learn more about using the field map control.

• Learn more about mapping fields in scripts.

• Learn more about ArcGIS data types.

• The following environment affects this tool: Extent and workspace.

Command line syntax
An overview of the Command Line window
Append_management <inputs; inputs...> <target> {TEST | NO_TEST} {field_mapping}

Command line example

workspace d:\project93\data
CreateFeatureclass d:\project93\data multitown.shp POLYGON amherst.shp
Append_management "amherst.shp;hadley.shp;pelham.shp;coldspring.shp" multitown.shp TEST

Scripting syntax
About getting started with writing geoprocessing scripts
Append_management (inputs, target, schema_type, field_mapping)

Script example

# Purpose: Append several feature classes together

# Create the Geoprocessor object
import arcgisscripting
gp = arcgisscripting.create()

try:
    # Set the workspace (to avoid having to type in the full path to the data every time)
    gp.Workspace =  "d:/project93/data"

    # Set a variable to store the updated feature class
    out_feat_class = "mass_towns.shp"

    # Process:  Create a feature class to update
    gp.CreateFeatureclass(gp.workspace, out_feat_class, "POLYGON",  "amherst.shp")

    # Process: Append the feature classes into the feature class
    gp.Append_management("amherst.shp;hadley.shp;pelham.shp;coldspring.shp", out_feat_class, "NO_TEST")

except:
    # If an error occurred while running a tool print the messages
    print gp.GetMessages()