Available with Advanced license.
Summary
Computes the geometric intersection of two coverages. Only those features in the area common to both coverages will be preserved in the output coverage.
Illustration
Usage
The intersect coverage must have polygon topology.
The input coverage, intersect coverage, and output coverage must have different names, even when in different workspaces.
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.
Route systems in the input coverage will be maintained in the output coverage when using the LINE option. However, INTERSECT on routes and sections themselves is not permitted.
Region subclasses from both input coverage and intersect coverage are maintained with the POLY option. Subclasses with identical names and attribute schemas are appended. Output regions are clipped by the extent of the output coverage.
Annotation is copied from the input coverage and saved in the output coverage.
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
Intersect_arc (in_cover, intersect_cover, out_cover, {feature_type}, {fuzzy_tolerance}, {join_attributes})| Parameter | Explanation | Data Type |
in_cover | The coverage whose polygon, line, or point features will be intersected with the intersect coverage. | Coverage |
intersect_cover | The intersect coverage. This coverage must contain polygon features. | Coverage |
out_cover | The coverage that will be created to contain the results. | Coverage |
feature_type (Optional) | The input coverage feature class to be overlaid and preserved in the output coverage.
| 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 |
join_attributes (Optional) | Specifies whether all items in both the input coverage feature attribute and identity coverage will be joined to the output coverage feature attribute table.
| Boolean |
Code Sample
Intersect example (stand-alone script)
The following stand-alone script demonstrates how to intersect two coverages.
# Name: Intersect_Example.py
# Description: Intersects two coverages
# Requirements: ArcInfo Workstation
# Import system modules
import arcpy
from arcpy import env
# Set environment settings
env.workspace = "C:/data"
# Set local variables
inCover = "stream"
intersectCover = "citylim"
outCover = "C:/output/citystreams"
featureType = "LINE"
joinAttributes = "NO_JOIN"
# Execute Intersect
arcpy.Intersect_arc(inCover, intersectCover, outCover, featureType, "",
joinAttributes)
Environments
Licensing Information
- ArcGIS for Desktop Basic: No
- ArcGIS for Desktop Standard: No
- ArcGIS for Desktop Advanced: Requires ArcInfo Workstation installed