Summary
Replaces the input coverage areas with the update coverage polygons using a cut and paste operation.
Illustration
Usage
Before using UPDATE, the following conditions must be met:
- Item definitions past the User-ID must be the same for the input and update coverages. This includes redefined items.
- Annotation subclasses and their attribute definitions must be identical. Blank annotation subclasses are ignored.
- Section subclasses and their attribute definitions must be identical.
- Region subclasses with the same name must have the same attribute definitions.
The input coverage and the update coverage must have polygon topology.
The item definitions for items past the User-ID in the input coverage and update coverage feature attribute tables must match exactly, including redefined items. The input coverage and update coverage items are joined to the output coverage attribute table using the old polygon internal number as the relate item.
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.
UPDATE maintains all route system subclasses. If a Section (SEC) subclass is present on either coverage, then it must be present on both, and it must have identical item definitions. Route systems attached to update arcs are retained. Route systems attached to input arcs are retained if they survive. UPDATE manages route systems like an Erase, followed by an Append, then a Clean.
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 some output regions may not be maintained.
Annotation features are updated by identifying and deleting the set of input coverage annotation whose lower left starting points fall within an update coverage polygon. Update coverage annotation is then appended for all annotation subclasses present in the output coverage. Both coverages must have identical sets of annotation subclasses with the exception of blank annotation classes, which can be either present or absent. Where subclasses have attributes, they must have identical attribute definitions.
If the update coverage contains nodes on its border that are coincident with nodes in the input coverage, the update coverage nodes are maintained. The only exception is if the input coverage node contains data in the NAT and the update coverage node does not have an NAT.
Region subclasses are updated with both the POLY and NET options. All regions are maintained with the KEEP_BORDER option only. The DROP_BORDER option does not maintain all regions and, therefore, is not recommended when updating region coverages.
The input coverage and update coverage region subclasses may be the same or different. When the subclasses are the same, they must have the same item definitions.
The coordinate precision of the output coverage is determined by the Precision for Derived Coverages environment.
Projection files will be compared for similarity using the level of comparison specified in the Compare Projections environment.
The output coverage inherits the items from the point attribute table, tics, and the projection file data model contents from the input coverage.
When the input coverage contains linear data belonging to different planar graphs, the data will be maintained in the output coverage. For example, with coincident or colinear arcs, such as arcs representing utility cables at different levels or a road following a stream, the coincident and colinear line segments will be preserved. However, additional vertices may be inserted. In the case of intersecting arcs, such as a road passing over a stream, nodes will not be inserted at the apparent intersection.
Syntax
arcpy.arc.Update(in_cover, update_cover, out_cover, {feature_type}, {fuzzy_tolerance}, {keep_border})| Parameter | Explanation | Data Type |
in_cover | The coverage containing polygons to be updated. | Coverage |
update_cover | The coverage whose polygons will replace input coverage areas. | Coverage |
out_cover | The coverage to be created. | Coverage |
feature_type (Optional) | The set of feature classes to be updated.
| String |
fuzzy_tolerance (Optional) | The minimum distance between coordinates in the output coverage. By default, the minimum fuzzy tolerance value from the input and erase coverages is used. Learn more about how the default fuzzy tolerance is calculated | Double |
keep_border (Optional) | Specifies whether the outside border of the update coverage will be kept after it is inserted into the input coverage.
| Boolean |
Code sample
Update example (stand-alone script)
The following stand-alone script demonstrates how to use the Update tool.
# Name: Update_Example.py
# Description: Updates a coverage
# Requirements: ArcInfo Workstation
# Import system modules
import arcpy
from arcpy import env
# Set environment settings
env.workspace = "C:/data"
# Set local variables
inCover = "c3zone4"
updateCover = "newsub"
outCover = "C:/output/newc3zone4"
featureType = "POLY"
# Execute Update
arcpy.Update_arc(inCover, updateCover, outCover, featureType, "", "")
Environments
Licensing information
- Basic: No
- Standard: No
- Advanced: Requires ArcInfo Workstation installed