Integrate (Data Management) |
|
Release 9.3
Last modified March 8, 2012 |
![]() ![]() ![]() Print all topics in : "Tools" |
NOTE: This topic was updated for 9.3.1.
Integrates features and feature layers by inserting vertices where line segments cross or where segment endpoints are too close to other segments. Clusters vertices to guarantee a minimum separation between vertices, points, and line segments.
Illustration
Usage tips
Integrate permanently changes the inputs. Integrate does not create new data but, instead, modifies the original input features. If experimenting with this tool, it is recommended to make a backup copy of the inputs.
If there are any input features selected, Integrate will execute only on those selected features.
The value for xy tolerance is critical for Integrate. A tolerance that is too large may collapse and delete polygons or lines or move vertices that should not be moved. To minimize error, the value you choose for xy tolerance should be as small as possible.
Integrate supports personal, file, and ArcSDE geodatabase feature classes and shapefiles.
Integrate accepts only simple feature classes as input (point, multipoint, line, or polygon). The input features cannot include annotation features, dimension features, or network features.
To undo changes to the input features, use Integrate in an edit session to undo Integrate operations.
When processing datasets that contain any individual feature with a very large number of vertices (e.g., hundreds of thousands to millions of vertices within a single feature), some geometric processing operations may run out of memory. For more details, see Geoprocessing with large datasets.
Integrate's output data element is a derived multivalue output. To use Integrate's output(s) with another tool, use Integrate's input(s) directly and set Integrate's output as a precondition of the other tool. Learn more about setting a precondition.
The following environments affect this tool: clusterTolerance, scratch workspace, and workspace.
Command line syntax
An overview of the Command Line window
Integrate_management <Features {Ranks};Features {Ranks}...> {cluster_tolerance}
Parameter | Explanation | Data Type |
<Features {Ranks};Features {Ranks}...> |
The feature datasets to be integrated. When the distance between features is small in comparison to the tolerance, the vertices or points will be clustered (moved to be coincident). The feature class or layer with the lower rank will snap to the feature from the feature class or layer with the higher rank (with 1 being a higher rank than 2). This is not to say the features in the feature class with a rank of 1 will not move, since a large tolerance will likely cause clustering of vertices within the feature class. |
(Feature Layer Long; Feature Layer Long;...) |
{cluster_tolerance} |
The distance that determines the range in which feature vertices are made coincident. To minimize undesired movement of vertices, the xy tolerance should be fairly small. If no value is specified, the xy tolerance from the first dataset in the list of inputs will be used. |
Linear unit |
Integrate_management "C:\temp\parcels.mdb\boundary 1;C:\temp\parcels.mdb\parcels 2" 0.2
Scripting syntax
About getting started with writing geoprocessing scripts
Integrate_management (in_features, cluster_tolerance)
Parameter | Explanation | Data Type |
in_features (Required) |
The feature datasets to be integrated. When the distance between features is small in comparison to the tolerance, the vertices or points will be clustered (moved to be coincident). The feature class or layer with the lower rank will snap to the feature from the feature class or layer with the higher rank (with 1 being a higher rank than 2). This is not to say the features in the feature class with a rank of 1 will not move, since a large tolerance will likely cause clustering of vertices within the feature class. |
(Feature Layer Long; Feature Layer Long;...) |
cluster_tolerance (Optional) |
The distance that determines the range in which feature vertices are made coincident. To minimize undesired movement of vertices, the xy tolerance should be fairly small. If no value is specified, the xy tolerance from the first dataset in the list of inputs will be used. |
Linear unit |
import arcgisscripting gp = arcgisscripting.create() gp.toolbox = "management" gp.integrate("c:/city/admin.mdb/boundary 1;c:/city/parcels.shp 2", "0.2")