Polyline or Path Closes on Self

Available with Data Reviewer license.

Summary

The Polyline or Path Closes on Self check finds paths or lines in polyline features that close themselves.

Overview

The purpose of the Polyline or Path Closes on Self check is to find polyline features or their individual paths that close on themselves. This includes polylines or paths that close (start and endpoints are coincident) or those that contain multiple paths that result in a closure. Alternatively, you can identify features that do not close themselves.

When configured as a constraint rule, an error notification is returned upon creation or modification of a feature that closes (or does not close) itself.

When configured as a validation rule, an error is created during validation for each feature that closes (or does not close) itself.

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

Search Goal

Yes

The error conditions evaluated by the rule.

  • Closed—Finds polylines or paths that close on themselves.
  • Unclosed—Finds polylines or paths that do not close on themselves.

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 features that do not contain a valid geometry will not be assessed by this check.

    The Invalid Geometry check is used to find features that contain invalid geometries that require correction.

  • Z-values are ignored when evaluating whether a feature is closed.
  • The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.

Related topics