Available with Data Reviewer license.
Summary
The Find Disconnected Polylines check finds polyline features that are not connected to other features in the same or other data sources.
Overview
The purpose of the Find Disconnected Polylines check is to find polylines that are not spatially connected to other polyline, polygon, or point features. The Find Disconnected Polylines check searches a feature class for line features that are spatially disconnected from other features in the same feature class. You can optionally configure the check to search for points, lines, and polygon features in other feature classes.
Industry scenarios
The following are scenarios in which you can use this check:
- In hydrographic data management, you can find a dissipating or disappearing point that is not connected to a river line feature, but should be connected.
- In address management, you can find invalid street centerline features that are not connected to any other streets.
- In geological data management, you can check if the end of a fault line doesn't touch at a formation polygon boundary or another fault line feature.
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:
| Validation | Constraint | ||
|---|---|---|---|
Reviewer batch job | Reviewer map rule | Attribute (validation) rule | No |
Yes | No | Yes (ArcGIS Pro 2.9 or later) | |
Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
Subtype | No | The subtype to which the rule is applied. | Validation |
Attribute | No | A query that identifies the features to which the rule is applied. | Validation |
Additional Features to Compare | No | Additional point, polyline, or polygon feature classes to include in the comparison. Additional features to compare must have the same datum as the input data source. | 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 you define of the error when a noncompliant feature is found. This information is used to provide guidance to facilitate corrective workflows. | Validation |
Severity | Yes | 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 |
Notes
Keep the following in mind when using the check:
- The Additional Features to Compare parameter allows the check to look for disassociations to features in multiple feature classes.
- Data sources for the Additional Features to Compare parameter must include a global ID field.
- The data sources of the input features and Additional Features to Compare parameter must share a common datum.
- The Validation Status attribute value of both the input features and data sources included in the Additional Features to Compare parameter are ignored during evaluation. For example, input polyline features with a validation status of 0 (No calculation required, no validation required, no error), 1 (No calculation required, no validation required, has error(s)), 4 (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation.
- Include the data source for the Additional Features to Compare parameter when sharing web layers with the Validation capability enabled.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.