Claims and evidence

Dataset route profile

Bidirectional
Yes
Distance basis
sum of selected USGS source-field lengthmiles values
Extent
McGee Creek trailhead corridor to the dataset corridor endpoint toward McGee Pass
Geometry snapshot
Path
geometry/v0/snapshots/usgs-mcgee-lundy-routes-20260925.geojson
Sha256
5358db1bac85e9aa2db4dca13afcdae6ffb354e305c3a76976276eb95de642fc
One way distance miles
14.25364769
Evidence and sources (1)

No claim effective interval recorded.

Spatial scope IDs: scope-route-mcgee-creek

  1. Evidence stance: supports · Evidence details

    A bounded public-domain National Digital Trails extract contains a connected 14.253-mile McGee Pass mainline from the McGee Creek trailhead corridor toward McGee Pass and a connected 2.100-mile lower Lundy Canyon component. The Lundy dataset component does not reach the separately published 20 Lakes Basin endpoint.

    Retrieval time does not establish when an event occurred.

    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
    • 5358db1bac85e9aa2db4dca13afcdae6ffb354e305c3a76976276eb95de642fc

    References are not a confirmation of current availability.

Recorded observations

Browse observations separately (1)

A bounded public-domain National Digital Trails extract contains a connected 14.253-mile McGee Pass mainline from the McGee Creek trailhead corridor toward McGee Pass and a connected 2.100-mile lower Lundy Canyon component. The Lundy dataset component does not reach the separately published 20 Lakes Basin endpoint.

Retrieval time does not establish when an event occurred.

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
  • 5358db1bac85e9aa2db4dca13afcdae6ffb354e305c3a76976276eb95de642fc

References are not a confirmation of current availability.

Published record history

History lists published operations; it does not reconstruct removed content or confirm that external media remains available.

JSON

Historical evidence is not a guarantee of current conditions.