Duplicate Row
Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Duplicate Row check identifies rows in the attribute table of a feature class or table that have identical 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 3.7 and ArcGIS Enterprise 12.1 or later) |
Available with ArcGIS Pro Standard and Data Reviewer licenses |
|
Constraint attribute rule |
No |
N/A |
|
Run Data Checks |
Yes (ArcGIS Pro 3.7 or later) |
Available with a Data Reviewer license |
Overview
The Duplicate Row check compares attribute values across the rows of an attribute table to identify duplicates. When the check is configured to find duplicate values, the check flags features that have identical values in every attribute as an error. Null attribute values are considered errors if multiple rows contain null in the same selected attribute.
The following is an example of a table with a duplicate row error:
| Row | Address | City | State |
|---|---|---|---|
| Row 1 | 380 New York Street | Redlands | CA |
| Row 2 | 35 Cajon St | Redlands | CA |
| Row 3 | 380 New York Street | Redlands | CA |
In this example, Row 1 is a duplicate of Row 3, because they have identical values for the Address, City, and State columns. Row 2 is not a duplicate, as the address value is different.
Industry scenarios
This check can be used in the following scenarios:
In address data management, site address features that share duplicate attribute values located in the same or different places, can impact vehicle routing and place finding operations.
In the public safety industry, duplicate road centerlines with identical attributes in the same or different locations can impact first responders’ response times and may lead to misrouted 911 calls when these road centerlines are used in Next Generation 911 geospatial call routing systems.
Attribute Rule syntax
The following table describes the validation attribute rule parameters:
|
Parameter |
Required |
Description |
Workflow |
|---|---|---|---|
|
Subtype |
No |
The subtype or subtypes to which the rule is applied. |
Validation |
|
Attribute |
No |
A query that identifies the features to which the rule is applied. |
Validation |
|
Attributes to Compare |
Yes |
Select all attributes or select a subset of attributes to check for duplicate values. |
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
The following table describes the Run Data Checks parameters:
|
Parameter |
Required |
Description |
|---|---|---|
|
Input Feature |
Yes |
The input feature layer that is evaluated by the rule. Note:You can disable a map selection or layer definition query using the toggle button that honors the selection or filter before evaluation. |
|
Subtypes |
No |
The subtype or subtypes to which the rule is applied. |
|
Attribute Filter |
No |
A query that identifies the features to which the rule is applied. |
|
Attributes to Compare |
Yes |
Select all attributes or select a subset of attributes to check for duplicate values. |
|
Name |
Yes |
A unique name for the rule. This information is used to support data quality requirement traceability. |
|
Extent |
Yes |
|
Notes
Keep the following in mind when using the check:
- Features with null or invalid geometries are not evaluated by this check. Use the Check Geometry check to find invalid geometry features and correct them before using this check.
The Attribute filter parameter is limited to comparison (
=,<>,>,<,>=, and<=) and logical (AND/OR,IN/NOT IN,LIKE/NOT LIKE, andIS NULL) operators.The Attribute filter parameter does not support the following field types:
Big Integer,Date Only,Time Only, andTimestamp Offset. If selected, the row header is marked in red and does not allow the rule to be saved.When this check is authored as a Run Data Check, subtype group layers are not supported.