Dataset route partial topology
- Bidirectional
- Yes
- Connected prefix distance miles
- 0.97791982
- Connected prefix segment ids
- route-segment-mcgee-pass-01
- route-segment-mcgee-pass-02
- route-segment-mcgee-pass-03
- route-segment-mcgee-pass-04
- route-segment-mcgee-pass-05
- route-segment-mcgee-pass-06
- Destination distance one way miles
- 3
- Destination distance precision
- published rounded value
- Remaining distance after connected prefix miles
- 2.02208018
- Topology status
- partial destination within unsplit source feature
- Unresolved source feature id
- {F7E76514-1AD3-4846-AA9D-C28FDCCC2F86}
Evidence and sources (1)
Evidence stance: supports · Evidence details
The first six connected MCGEE PASS features form a 0.97791982-mile prefix from the McGee Creek trailhead. The county-published three-mile beaver-pond destination falls within the following 2.84525413-mile source feature, so the official feature cannot be assigned wholly to the short route and is not split without a source-backed pond coordinate.
Observation details · Source details · Original source: U.S. Geological Survey / U.S. Forest Service
Recorded artifact references
geometry/v0/snapshots/usgs-mcgee-lundy-routes-20260925.geojson
References are not a confirmation of current availability.