Summary
Clips portions of the input coverage into multiple coverages.
Each new output coverage contains only those portions of the input coverage features overlapped by the split coverage polygons. The unique values in the Split Item are used to name the output coverages. The number of output coverages is determined by the number of unique values in the Split Item.
Illustration
Usage
Values in the Split Item must be unique.
The Split Item data type must be character.
The output coverages will be named for Split Item values; therefore, they must start with a valid character.
Split Item values must be 13 characters or less.
The split coverage must have polygon topology.
Topology is maintained in the output coverages.
The number of output coverages is dictated by the Split Item of the split coverage. The maximum number of output coverages equals the total number of unique values in the Split Item.
The Output Workspace in which each output coverage is created must contain an INFO directory before running Split. Split will stop if it cannot find the INFO directory.
Annotation is copied when its lower left starting point falls within a new output coverage.
Polygon topology is rebuilt for each output coverage. Each polygon User-ID is set equal to the old input coverage polygon User-ID. New label point positions are only generated when the original input coverage label point position is clipped by the split coverage.
Empty output coverages can be created by Split for split coverage areas in which no input coverage features are located.
If the input coverage contains a node feature class with attributes, then each of the output coverages will contain nodes that fall within the appropriate split coverage. New NAT records will be created as required by the Split operation.
Attributes for new nodes are set to zero.
Region subclasses in the input coverage are maintained.
Empty region subclasses are created if the regions that make up the subclass are not in the output coverage.
Region subclasses are maintained as empty subclasses when all the regions are removed.
Route systems will be maintained. Route systems will be duplicated for arcs split into multiple pieces. Each resultant coverage will have a complete set of route system subclasses containing only those route systems attached to arcs within that coverage (empty route system files will be created if necessary).
Route systems are copied when their arcs are split into multiple pieces and dropped for arcs that are removed.
Routes and sections on the arcs will be carried over and maintained. Route systems will be split at their intersections. Split maintains all route system subclasses.
Split treats route systems as if it were performing repeated Clips. Each output coverage from Split contains the route systems within that particular split polygon and the parts of those that pass through that polygon. Routes retain their User-IDs across split coverages so that Append can reassemble them. Split sections will have new section measures interpolated at their split ends.
Four new tic locations are generated for each output coverage at the corners of the split coverage BND. No existing tics are retained.
The feature attribute table for each output coverage contains the same items as the input coverage feature attribute table.
Split will distribute all annotation subclasses present in the input coverage to all of the output coverages based on the split coverage polygon in which the lower left starting point falls for each annotation string. If a particular subclass has no actual annotation within a particular output coverage, it is still created.
The input coverages projection file (PRJ) will be copied to each output coverage.
The coordinate precision of each 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 during the current session, then the output coverages will be in the same precision as 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
Split_arc (in_cover, split_cover, split_item, {path}, {feature_type}, {fuzzy_tolerance})| Parameter | Explanation | Data Type |
in_cover | The coverage to be split. | Coverage |
split_cover | The coverage used to split the input coverage. | Coverage |
split_item | The item in the split coverage that will be used to split the input coverage. The unique values in the Split Item are used to name the output coverages. The number of output coverages is determined by the number of unique values in the Split Item. | INFO Item |
path (Optional) | The workspace in which the output coverage will be maintained. | Folder |
feature_type (Optional) | The feature classes to be split:
| String |
fuzzy_tolerance (Optional) | The minimum distance between coordinates in each output coverage. By default, the minimum fuzzy tolerance value from the input coverage and split coverage is used. Learn more about how the default fuzzy tolerance is calculated | Double |
Code sample
Split example (stand-alone script)
The following stand-alone script demonstrates how to split one coverage into multiple output coverages.
# Name: Split_Example.py
# Description: Splits one coverage into multiple output coverages.
# Requirements: ArcInfo Workstation
# Import system modules
import arcpy
from arcpy import env
# Set environment settings
env.workspace = "C:/data"
# Set local variables
inCover = "county"
splitCover = "citylim"
splitItem = "citycode"
path = "C:/output/city"
featureType = "LINE"
# Execute split
arcpy.Split_arc(inCover, splitCover, splitItem, path, featureType, "")
Environments
Licensing information
- ArcGIS Desktop Basic: No
- ArcGIS Desktop Standard: No
- ArcGIS Desktop Advanced: Requires ArcInfo Workstation installed