Disponible avec une licence Data Reviewer.
Summary
The Duplicate Feature check finds features of the same geometry type that are collocated and optionally share attributes.
Overview
The purpose of the Duplicate Feature check is to find features that share the same geometry and are located in the same place. This can include features stored in a different layer or within the same layer. Optionally, you can compare the attribute values of features that have duplicate geometries to determine if these features represent a duplicate.
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 | No | |
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 |
| Features to Compare | Yes | The feature layer evaluated by the rule. Only feature layers that contain a feature type that matches those configured in the Input Layers parameter are displayed. Click the Forward button | Validation |
| Compare selected attributes | No | The attribute values to compare when a duplicate feature is found. Only fields common to all feature layers configured in the Input Layers parameter are displayed. Common fields are fields that share the same field name and data type. | Validation |
| 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 |
to apply filtering to specific features in the feature layer.Notes
- Input and comparison feature layers must share a common datum to be compared.
- M- and z-values are ignored when evaluating the geometry of input and comparison features.
- When this check is authored as a map-based rule, care should be taken when configuring filter parameters using database-specific SQL functions that differ from those supported in your production environment.
Rubriques connexes
Vous avez un commentaire à formuler concernant cette rubrique ?