Data sources for the Additional Features to Compare parameter must include a global ID field.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)),Ĥ (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation. The Validation Status attribute values of both the input features and the data sources included in the Additional Features to Compare parameter are ignored during evaluation.To find connection errors with the green feature, you need to configure a check specifically for that feature.ī: Feature 1 (in orange) is not returned as a dangle. However, since feature 1 is connected to at least one of the features within the tolerance, this is not considered a dangle. This is an undershoot scenario when looking at it from the green feature. In image B, feature 1 connects to the gray feature, but not the green. This is considered a dangle with an undershoot. In image A, feature 1 does not connect to any additional features within the tolerance. The following images show feature 1 in orange, the additional features in gray and green, and the tolerance in blue. When you configure two or more feature classes as additional features to compare, and the feature class for which you configured the check connects with one feature class but not all feature classes, this is not considered a dangle.Keep the following in mind when using the check: This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest. This value indicates the importance of the error relative to other errors. The severity of the error assigned when a noncompliant feature is found. This information is used to provide guidance to facilitate corrective workflows. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.Ī description you define of the error when a noncompliant feature is found. Additional feature classes to compare must have the same datum as the input data source. When the spatial reference of the feature class is geographic (GCS), the tolerance is converted from degrees to meters.Īdditional polyline or polygon feature classes to include in the comparison. The following table identifies the supported implementation methods for this check: This check can find streets that need to be connected by setting a dangle tolerance.ĪrcGIS Data Reviewer checks support multiple methods for implementing automated review of data. In address management, it may be invalid for the street centerline feature class to have a street that is not connected to other streets.This can affect downstream and upstream tracing results.
In utility networks, you can use this check to find where pipes or wires are undershoots or overshoots and do not connect to the rest of the network.This check can be used in the following scenarios: You can run the check on an entire feature class, a subtype, or a set of features selected using an SQL query. The polyline features are compared to other features in the same feature class or across other polyline or polygon feature classes. Dangles can occur if data has been moved or a feature has been extracted incorrectly. The purpose of the Find Dangles check is to find polyline features that have nodes within a defined tolerance but are not connected to other polyline or polygon features. The Find Dangles check finds polylines that have dangles within a specified tolerance. Available with ArcGIS Pro Standard and Data Reviewer licenses.
0 kommentar(er)
