Available with Data Reviewer license.
Summary
The Duplicate Feature check finds features of the same geometry type that contain duplicate geometry and have matching attribute values.
Supported workflows
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of data. The following table identifies the supported implementation methods for this check:
| Workflow | Supported | Licensing |
|---|---|---|
Validation attribute rule | Yes (ArcGIS Pro 2.7 and ArcGIS Enterprise 10.9 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | No | Available with ArcGIS Pro Standard and Data Reviewer license |
Run Data Checks | Yes (ArcGIS Pro 3.4 or later) | Available with Data Reviewer license |
Legacy:
Map-based Reviewer rules are deprecated and are not available for use. It is recommended that you migrate automated review workflows to Data Reviewer capabilities available in attribute rules. Opening or saving a map document (.aprx file) at ArcGIS Pro 3.0 or later removes all the existing map rules from the document.
Overview
The Duplicate Feature check identifies repeated features and attribute values. This can include the comparison of features stored in a different data source or in the same data source.
Industry scenario
In water utility management, the Duplicate Feature check can be used to identify service points, system valves, and hydrants that contain stacked points in the same location between two or more point features, for example, overlapping valves.
Attribute Rule Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype to which the rule is applied. | Validation |
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Features to Compare |
Yes | Input features are returned as errors based on their relationship to the features from this data source. Valid inputs are point, polyline, and polygon features and must match the geometry type of the input data sources. | Validation |
|
Filter |
No | A query that identifies the features to include in the rule, from the data source specified in the Features to Compare parameter. | Validation |
|
Attributes to Ignore |
No | The attribute values to ignore when evaluating for duplicate features. Only editable fields common to both the input and features to compare data sources can be ignored. Common fields are those that share the same name and data type. | Validation |
|
Name |
Yes | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Validation |
|
Description |
No | A description of the error you define when a noncompliant feature is found. This information is used to provide guidance for corrective workflows. | Validation |
|
Severity |
No | The severity of the error assigned when a noncompliant feature is found. This value indicates the importance of the error relative to other errors. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest. | Validation |
|
Tags |
No | The tag property of the rule. This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements. | Validation |
Run Data Checks Syntax
| Parameter | Required | Description |
|---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. |
Attribute | No | A query that identifies the features to which the rule is applied. |
Features to Compare | Yes | Input features are returned as errors based on their relationship to the features from this data source. Valid inputs are point, polyline, and polygon features and must match the geometry type of the input data sources. |
Filter | No | A query that identifies the features to include in the rule, from the data source specified in the Features to Compare parameter. |
Attributes to Ignore | No | The attribute values to ignore when evaluating for duplicate features. Only editable fields common to both the input and features to compare data sources can be ignored. Common fields are those that share the same name and data type. |
Name | No | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. |
Visible Extent | No | Evaluate the visible extent of the map. |
Full Extent | No | Evaluate the full extent of the data. |
Notes
Keep the following in mind when using the check:
- The data sources of the input features and the Features to Compare parameter value must share a common datum.
- M- and z-values are ignored when evaluating the geometry of input and comparison features.
- Attribute values in system-maintained fields are ignored when evaluating attribution of input and comparison features.
- The Validation Status attribute values of both the input features and the data sources included in the Features to Compare parameter are ignored during evaluation. For example, input features with a validation status of 0 (No calculation required, no validation required, no error), 1 (No calculation required, no validation required, has error(s)), 4 (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation.
- The Attribute and Filter parameters are limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- Data sources for the Features to Compare parameter must include a global ID field.
- Include the data source for the Features to Compare parameter when creating map or project packages and when sharing web layers with the Validation capability enabled.
- The Attribute, the Features to compare, and the Attributes to Ignore filter parameters do not support Big Integer, Date Only, Time Only, and Timestamp Offset field types.
- GUID and Object ID data types are ignored during evaluation.