Features Not Split at Polygon
|
Potential issues in consuming applications arise when a linear feature (e.g., road centerline) starts in one polygon feature and continues into another polygon feature. The Features Not Split at Polygon quality control (QC Quality Control) check identifies where line features cross a polygon feature in defined layers without being split at the intersection point. Note: By default, this QC check accounts for snapping tolerance. Individual polygon features with over 1 million vertices are simplified to ensure performance. Projection-Based Unit is used in this check. Projection-Based Unit indicates the unit of measurement is pulled from the Spatial QC Projection this data target uses. If no Spatial QC Projection is used in this data target, the unit is pulled from the Data Target's projection. |
Note: By default, Features Not Split at Polygon accounts for snapping tolerance within GIS Geographic Information System. A computer application that involves storing and manipulating electronic maps and related data. Also, mapping software combining spatial information about where places and events are located with data attributes describing those places and events. editing applications. The following are applied automatically when the Tolerance parameter is configured.
- Feet: When configured to 0, the check runs with built-in tolerance of 0.0087 feet for all spatial reference systems measured in feet like most state plane projections.
- Meters: When configured to 0, the check runs with built-in tolerance of 0.0027 meters for all spatial reference systems measured in meters.
Required QC Prerequisites
To run this check, the following feature classes are required.
- Line feature class
- Polygon feature class
Configure QC Parameters
Configurations for QC check parameters contain filters to prevent selecting incompatible field types.
The following parameters can be specifically configured for the Features Not Split at Polygon QC check.
- Run On: Non-configurable. This QC check inspects the target dataset.
-
Severity: Sets the importance level of this QC check’s fallouts. Critical fallouts prevent export package outputs but will still provide fallouts.
-
Line Layer Name: The name of the line layer this QC check should inspect. For example: Road Centerline or Railroad.
-
Line Reporting Unique ID: A unique identifier in the line layer that can be used to uniquely identify a singular feature. If not configured, the source object ID is used instead.
-
Polygon Layer Name: The name of the polygon layer this QC check should inspect. For example: County_Boundary or PSAP Public Safety Answering Point. A set of call takers authorized by a governing body and operating under common management which receives 9-1-1 calls and asynchronous event notifications for a defined geographic area and processes those calls and events according to a specified operational policy._Boundary.
-
Polygon Reporting Unique ID: A unique identifier in the polygon layer that can be used to uniquely identify a singular feature.
-
Tolerance (Projection-Based Unit): Choose how far a line can extend beyond a boundary edge before it is flagged. Distance is projection based. 0 requires the line to be split at the intersection. 5 would allow a line to cross a boundary up to 5 meters pass the intersection without creating a fallout, assuming your projection is in meters.
What Does Features Not Split at Polygon QC Check Output Include?
The following information is included for this QC check's fallout output.
- QC check name
- Description of the QC check
- Feature class where the fallout appears
- Unique Feature ID used to identify and associate a fallout to a specific record in the dataset
- Extended information providing more details about the fallout
- Latitude and Longitude of the fallout's location
Examples - Fallout Report Records
The example below shows a possible error message you may receive when a record fails the Features Not Split at Polygon QC check. The extended information provides the layer and/or field names, and a unique identifier to associate a fallout to a specific record in the dataset.
Examples - Issues Reported
The example below uses the roads against county boundaries to identify the road features that intersect edge of the county boundary and removes all other features from the roads layer that do not meet this condition. Those roads are then inspected to ensure they are split at the boundary location.
