Available with Data Reviewer license.
Summary
The Duplicate Feature check finds features of the same geometry type that are collocated and have matching attribute values.
Overview
The purpose of the Duplicate Feature check is to find features that contain duplicated geometry and attribute values. This can include the comparison of features stored in a different data source or within the same data source.
Industry scenarios
In water utility management, the Duplicate Feature check can be used to identify service points, system valves, and hydrants that contain stacked points located in the same location between two or more point features, for example, overlapping valves.
Supported workflows
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of your data. The following table identifies the supported implementation methods for this check:
| Validation | Constraint | ||
|---|---|---|---|
Reviewer batch job | Reviewer map rule | Attribute (validation) rule | No |
Yes | Yes | Yes | |
Syntax
| Parameter | Required | Description | Workflows |
|---|---|---|---|
| Input Feature Layers | Yes | The input feature layers evaluated by the rule. Valid inputs are point, polyline, and polygon features. | Validation (map rules) |
| 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 |
Features to Compare Filter | No | A query that identifies the features to include in the rule. | 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 (attribute rules) |
| Compare selected attributes | No | The attribute values to compare when evaluating for duplicate features. Only editable fields common to all feature layers configured in the Input Layers parameter are displayed. Common fields are those that share the same name and data type. | Validation (map rules) |
| Title | No | A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Validation |
| Notes | No | Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows. | Validation |
| Severity | No | Severity of the error created when noncompliant features are 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 | 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 |
Notes
Keep the following in mind when using the check:
- The data sources of the input and Features to Compare parameter must share a common datum.
- M- and z-values are ignored when evaluating the geometry of input and comparison features.
- The following conditions apply when this check is authored as an attribute (validation) rule:
- Only input features with a validation status of 2 (No calculation required, validation required, no error), 3 (No calculation required, validation required, has error(s)), 6 (Calculation required, validation required, no error) or 7 (Calculation required, validation required, has error(s)) are considered during rule evaluation. The validation status of features from the data source in the Features to Compare parameter are not considered during rule evaluation.
- When this check is authored as an attribute (validation) rule, the Attribute and Features to Compare Filter parameters are limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- Include the data source for the Features to Compare parameter when sharing web layers with the Validation capability enabled.
- When this check is authored as a map-based rule, verify that filter parameters using database-specific SQL functions are the same as from those supported in your production environment.