Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Find Disconnected Polylines check finds polyline features that are not connected to other features in the same or other data sources.
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.9 and ArcGIS Enterprise10.9.1 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | No | N/A |
Run Data Checks | Yes (ArcGIS Pro 3.5 or later) | Available with Data Reviewer license |
Overview
The Find Disconnected Polylines check identifies polylines that are not spatially connected to other polyline, polygon, or point features. This check searches a feature class for line features that are spatially disconnected from other features in the same feature class. You can also configure the check to search for points, lines, and polygon features in other feature classes.
Industry scenarios
This check can be used in the following scenarios:
- 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 whether the end of a fault line doesn't touch at a formation polygon boundary or another fault line feature.
Attribute Rule syntax
The following table describes the validation attribute rule parameters:
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype(s) 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 polyline or polygon feature classes to include in the comparison. Added feature classes 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 of the error you define when a noncompliant feature is found. This information is used to provide guidance for 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 |
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. |
Additional Features to Compare | No | Additional polyline or polygon feature classes to include in the comparison. Added feature classes to compare must have the same datum as the input data source. |
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:
- The Additional Features to Compare parameter checks for disconnections 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 the 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 creating map or project packages, and sharing web layers with the Validation capability enabled.
- 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.