Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Duplicate Vertex check finds vertices in polyline or polygon features that are within a specified tolerance of one another.
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.5 and ArcGIS Enterprise10.8 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | Yes (ArcGIS Pro 2.4 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Run Data Checks | Yes ArcGIS Pro 3.5 or later) | Available with Data Reviewer license |
Overview
Duplicate vertices are created in a variety of ways, including digitizing errors, using data at a smaller scale than that for which it was collected, and loading data from a database with one precision to another. For example, you may have vertices on a line or polygon that are either collocated or are close to one another. If the tolerance specified in the check is small enough, one of the vertices is returned as an error result.
When configured as a constraint rule, an error is returned if a feature with segments containing vertices within the specified tolerance is created or modified.
When configured as a validation rule, an error is created during validation for each feature that contains vertices that are within the specified tolerance. Vertices that fall within the x and y tolerance of a feature will not be detected. Use the Check Geometry check to identify this error condition.
Industry scenario
In aviation, airport data integrity requires that a single polygon should not overlap itself or contain duplicate vertices or nodes. The exceptions are the start and end nodes, which must be coincident.
Attribute Rule syntax
The following table describes the validation and constraint attribute rule parameters:
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype(s) to which the rule is applied. |
Constraint |
|
Validation | |||
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Tolerance |
Yes | The allowable space between two vertices. Provide a value in the Tolerance text box and click the Tolerance drop-down arrow to choose a unit of measure. |
Constraint |
Validation | |||
|
Triggers |
Yes | The editing events that trigger the rule to take effect.
|
Constraint |
|
Name |
Yes | A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. |
Constraint |
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. |
Constraint |
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. |
Constraint |
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. Layer definition queries that include a spatial clause are not supported. |
Attribute Filter | No | A query that identifies the features to which the rule is applied. |
Tolerance | Yes | The allowable space between two vertices. Provide a value in the Tolerance text box and click the Tolerance drop-down arrow to choose a unit of measure. |
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:
- This check supports polyline and polygon features.
- A vertex is considered a duplicate when it's within the specified horizontal distance of an adjacent vertex.
- For multipart features, each part is evaluated independently when determining whether a vertex is a duplicate.
- The Tolerance parameter value must be equal to or greater than a feature's x,y tolerance.
- This check does not detect duplicate vertices that are closer than the x, y tolerance of the Input Feature class's spatial reference. Use the Check Geometry check to find this error condition when vertices fall within the x, y tolerance.
- When this check is authored as an attribute (constraint) rule, support for geographic coordinate system-based datasets is limited to those using Web Mercator (WKID 3857) or WGS84 (WKID 4326).
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Attribute filter parameter does not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset. If selected, the row header is marked in red and does not allow the rule to be saved.
- Multipoint error results are supported for this Run Data Check.