Duplicate Vertex

Disponible avec une licence Data Reviewer.

Summary

The Duplicate Vertex check finds vertices in polyline or polygon features that are within a specified tolerance of one another.

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 very close to one another. If the tolerance specified in the check is small enough, one of the vertices will be returned as an error result.

When configured as a constraint rule, an error notification is returned when a feature that contains one or more segments with vertices that are 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.

Industry scenarios

In aviation, for airport data integrity, a single polygon should not overlap itself or contain duplicate vertices or nodes (except the start and end nodes, which must be coincident).

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:

ValidationConstraint

Reviewer batch job

Reviewer map rule

Attribute (validation) rule

Yes

(ArcGIS Pro 2.4 or later)

Yes

No

Yes

(ArcGIS Pro 2.5 or later)

Syntax

Parameter Required DescriptionWorkflow

Subtype

No

The subtype that the rule is applied to if the dataset has subtypes.

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.

Type 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.

  • Insert—Triggers the rule when a new feature is added.
  • Update—Triggers the rule when a feature is updated.
  • Delete—Triggers the rule when a feature is deleted.

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

Descriptive text of the error condition when noncompliant features are found.

This information is used to provide guidance to facilitate corrective workflows.

Constraint

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.

Constraint

Validation

Notes

  • Polyline and polygon features are supported with this check.
  • 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 if a vertex is a duplicate.
  • The Tolerance parameter value must be equal to or greater than a feature's 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 WGS 84 (WKID 4326).
  • The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.

Rubriques connexes