Identity

Summary

Computes a geometric intersection of the input features and identity features. The input features or portions thereof that overlap identity features will get the attributes of those identity features.

Illustration

Usage

• Input Features can be point, multipoint, line, or polygon. The inputs cannot be annotation features, dimension features, or network features.

• Identity Features must be polygons or have the same geometry type as the Input Features.

• When using this tool with point input and polygon Identity Features, points that fall directly on a polygon boundary will be added to the output twice, once for each polygon that is part of the boundary. Running the Intersect tool on the output of this scenario will identify the duplicate points so you can decide which one to keep.

• When the Input Features are lines and the Identity Features are polygons, and the Keep relationships parameter is checked (relationship set to KEEP_RELATIONSHIPS in Python), the output line feature class will have two additional fields, LEFT_poly and RIGHT_poly. These fields contain the feature ID of the Identity Features on the left and right side of the line feature.

• Attribute values from the input feature classes will be copied to the output feature class. However, if the input is a layer or layers created by the Make Feature Layer tool and a field's Use Ratio Policy is checked, then a ratio of the input attribute value is calculated for the output attribute value. When Use Ratio Policy is enabled, whenever a feature in an overlay operation is split, the attributes of the resulting features are a ratio of the attribute value of the input feature. The output value is based on the ratio in which the input feature geometry was divided. For example, If the input geometry was divided equally, each new feature's attribute value is assigned one-half of the value of the input feature's attribute value. Use Ratio Policy only applies to numeric field types.

  Caution:

  Geoprocessing tools do not honor geodatabase feature class or table field split policies.

• This tool will use a tiling process to handle very large datasets for better performance and scalability. For more details, see Geoprocessing with large datasets.

• This tool may generate multipart features in the output even if all inputs were single part. If multipart features are not desired, use the Multipart to Singlepart tool on the output feature class.

Syntax

Identity_analysis (in_features, identity_features, out_feature_class, {join_attributes}, {cluster_tolerance}, {relationship})

Parameter	Explanation	Data Type
in_features	The input feature class or layer.	Feature Layer
identity_features	The identity feature class or layer. Must be polygons or the same geometry type as the input features.	Feature Layer
out_feature_class	The feature class that will be created and to which the results will be written.	Feature Class
join_attributes (Optional)	Determines what attributes will be transferred to the output feature class. ALL —All the attributes (including FIDs) from the input features, as well as the identity features, will be transferred to the output features. If no intersection is found the identity feature values will not be transferred to the output (their values will be set to empty strings or 0) and the identity feature FID will be -1. This is the default. NO_FID —All the attributes except the FID from the input features and identity features will be transferred to the output features. If no intersection is found the identity feature values will not be transferred to the output (their values will be set to empty strings or 0). ONLY_FID —All the attributes from the input features but only the FID from the identity features will be transferred to the output features. The identity features FID attribute value in the output will be -1 if no intersection is found.	String
cluster_tolerance (Optional)	The minimum distance separating all feature coordinates (nodes and vertices) as well as the distance a coordinate can move in X or Y (or both).	Linear unit
relationship (Optional)	Determines if additional spatial relationships between the in_features and the identity_features are to be written to the output. This only applies when the in_features are lines and the identity_features are polygons. NO_RELATIONSHIPS —No additional spatial relationship will be determined. KEEP_RELATIONSHIPS —The output line features will contain two additional fields, LEFT_poly and RIGHT_poly. These fields contain the feature ID of the identity_features on the left and right side of the line feature.	Boolean

Code Sample

Identity example 1 (Python window)

The following Python window script demonstrates how to use the Identity function in immediate mode.

import arcpy
from arcpy import env
env.workspace = "c:/data/data.gdb"
arcpy.Identity_analysis("wells", "counties", "wells_w_county_info")

Identity example 2 (stand-alone Python script)

The following stand-alone Python script is a simple example of how to apply the Identity function in scripting.

# IdentityWells.py
# Description: Simple example showing use of Identity tool
 
# Import system modules
import arcpy
from arcpy import env

# Set the workspace
env.workspace = "C:/data/data.gdb"

# Set local parameters
inFeatures = "wells"
idFeatures = "counties"
outFeatures = "wells_w_county_info"

# Process: Use the Identity function
arcpy.Identity_analysis (inFeatures, idFeatures, outFeatures)

Environments

• Auto Commit
• Qualified Field Names
• Default Output Z Value
• M Resolution
• M Tolerance
• Output CONFIG Keyword
• Output M Domain
• Output XY Domain
• Output Z Domain
• Output Coordinate System
• Extent
• Output has M values
• Output has Z values
• Output Spatial Grid 1
• Output Spatial Grid 2
• Output Spatial Grid 3
• XY Resolution
• XY Tolerance
• Z Resolution
• Z Tolerance

Licensing Information

• ArcGIS for Desktop Basic: No
• ArcGIS for Desktop Standard: No
• ArcGIS for Desktop Advanced: Yes

Feedback on this topic?