Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Polyline or Path Closes on Self check finds paths or lines in polyline features that close on themselves.
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 Enterprise 10.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
The Polyline or Path Closes on Self check finds polyline features or their individual paths that close on themselves. This includes polylines or paths that close (start points 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 when a feature that closes (or does not close) itself is created or modified.
When configured as a validation rule, an error is created during validation for each feature that closes (or does not close) itself.
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 |
Search Goal |
Yes | The error conditions evaluated by the rule.
|
Constraint |
Validation | |||
Triggers |
Yes | The editing events that trigger the rule to take effect.
|
Constraint |
Name |
Yes | A unique 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. |
Search Goal | Yes | The error conditions evaluated by the rule.
|
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:
- Polyline features that do not contain a valid geometry cannot be assessed by this check.
The Check 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 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.