Append (Coverage)

Summary

Combines an unlimited number of coverages into a single coverage.

Append checks for the existence of the coverage, verifies that the list of feature attribute table items matches the items in previously entered coverages (unless the FEATURES_ONLY option is used), and calculates Tic-ID and feature User-ID offsets according to the specified offset option.

Learn more about how Append works

Illustration

Usage

• 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 TOL file with single precision coverages and the PAR file with double precision coverages will not be transformed or retained in the Output Coverage files.

• The fuzzy tolerance of the Output Coverage will default to 0.002 if the width of the BND is between 1 and 100; otherwise, the tolerance is 1/10,000 of the width or height of the BND, whichever is greater.

• The item definitions 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).

• Using the ROUTE.subclass option is the same as using the ROUTE.subclass and SECTION.subclass options together; that is, both the routes and sections of the specified subclass are appended. If the User-ID of any route is not unique across the coverages being appended, that route will be merged with other routes of the same User-ID. The Output Coverage may, therefore, contain less routes than the total number of routes in the Input Coverages. Append never modifies route measures.

• All polygons in the Input Coverages are appended with the REGION.subclass option, not just those pertaining to the regions being appended. Region subclasses are not maintained with the POLY option; you must also specify REGION.subclass. After combining region subclasses with Append, the new topological relationships between features must be calculated using Build or Clean. Another way to combine region subclasses is to use Union. Union calculates topology when combining region subclasses.

• Annotation for each coverage is appended to the Output Coverage. As with all other feature classes, all TATs within a subclass must have identical item definitions.

• The projection file (PRJ) will be copied to the Output Coverage. The first coverage entered will provide the projection information for the Output Coverage.

• The coordinate precision of the Output Coverage is determined by the current processing rule as set by the Derived Precision environment setting. If the processing rule has not been established, then the processing rule will be HIGHEST. This means that Append will create an Output Coverage in the highest precision of the Input Coverages.

• Projection files will be compared for similarity using the level of comparison specified with the Compare Projections environment setting.

• The Feature Type parameter's 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 Feature Type parameter may not be populated with values. The Add Value button allows you to add expected value(s) so you can complete the Append dialog and continue to build your model.

Syntax

Append_arc (in_covers, out_cover, {append_method}, {feature_classes}, {number_method})

Parameter	Explanation	Data Type
in_covers [in_covers,...]	The input coverages to be appended. There is no limit to the number of coverages that can be entered.	Coverage
out_cover	The output coverage to be created. The output coverage cannot already exist.	Coverage
append_method (Optional)	Determines whether only coordinates will be appended (FEATURES_ONLY) or if features will also be appended. FEATURES_ONLY —Location information for all feature classes that are appended. Feature attribute tables are not appended. FEATURES_ATTRIBUTES —The features in the specified coverage define the set of features to be appended.	String
feature_classes (Optional)	The feature class of the input coverage or coverages. POLY —Polygon feature coordinates and attributes are appended, including label points. LINE —Arc feature coordinates and attributes are appended. POINT —Point feature coordinates and attributes are appended. NODE —Arc and node feature coordinates and their attributes are appended. NET —Arc and polygon feature coordinates and their attributes are appended. LINK —Arc and point feature coordinates and their attributes are appended. ANNO.subclass —Annotation features and attributes of the subclass are appended. SECTION.subclass —Section feature coordinates and attributes of the subclass are appended. ROUTE.subclass —Route and section feature coordinates and attributes of the subclass are appended. REGION.subclass —Region feature coordinates and attributes of the subclass are appended. Polygon feature coordinates and attributes are also appended. The Add Value button, which is used only in ModelBuilder, allows you to add expected value(s) so you can complete the dialog and continue to build your model.	String
number_method (Optional)	Specifies how tics and coverage features will be numbered in the Output Coverage. IDs can be offset to ensure unique ID values for Output Coverage features. The ID offset is equal to 1 plus the highest ID value in the previously appended coverages. Offsets can be calculated for the following types of IDs: NO —Neither Tic-IDs nor feature User-IDs will be modified. This is the default option. TICS_ONLY —ID offsets will be calculated for tics. FEATURES_ONLY —User-ID offsets will be calculated for the feature class(es) specified by the feature classes argument. Tic-IDs are not modified. FEATURES_TICS —ID offsets will be calculated for both tics and features.	String

Code Sample

Buffer example (stand-alone script)

The following stand-alone script demonstrates how to append several coverage into one output coverage.

# Name: Append_Example.py
# Description: Appends several coverages into one output
# Requirements: ArcInfo Workstation
# Author: ESRI

# Import system modules
import arcpy
from arcpy import env

# Set environment settings
env.workspace = "C:/data"

# Set local variables
inCovers = ["tongzone1", "tongzone2", "tongzone3", "tongzone4"]
outCover = "C:/output/tongass"
appendMethod = "FEATURES_ONLY"
featureClasses = "LINE"
numberMethod = "TICS_ONLY"

# Execute Append
arcpy.Append_arc(inCovers, outCover, appendMethod, featureClasses, 
                 numberMethod)

Environments

Current Workspace, Level Of Comparison Between Projection Files, Precision For Derived Coverages, Precision For New Coverages, Scratch Workspace

Licensing Information

ArcView: No

ArcEditor: No

ArcInfo: Requires ArcInfo Workstation installed