McGee Pass dataset segment 7

Route segment

Plan with 1 source-backed fact, 3 related records, and explicit uncertainty.

Plan a visit

Routes and geography

Official dataset route segment

Recorded for: McGee Pass dataset segment 7

Dataset feature id
{F7E76514-1AD3-4846-AA9D-C28FDCCC2F86}
Dataset feature name
MCGEE PASS
Distance miles
2.8452541300000003
Distance status
known
End coordinate
Latitude
37.51637800650675
Longitude
-118.82085699964769
Geometry snapshot
Feature id
{F7E76514-1AD3-4846-AA9D-C28FDCCC2F86}
Path
geometry/v0/snapshots/usgs-mcgee-lundy-routes-20260925.geojson
Sha256
5358db1bac85e9aa2db4dca13afcdae6ffb354e305c3a76976276eb95de642fc
Route role
official mainline
Source feature id
6706
Source originator
U.S. Forest Service
Start coordinate
Latitude
37.54823178577007
Longitude
-118.81843522675094
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.

    Publisher
    U.S. Geological Survey / U.S. Forest Service
    Observer / attribution
    Not recorded
    Observed at
    Unknown
    Retrieved at
    2026-09-25T02:30:00+00:00

    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.

Explore related places

Access and approaches (1)

Land and management (1)

Routes and related places (1)

Before you go

These open questions need confirmation; Wayproof does not fill them with guesses.

Where within the retained 2.845-mile source feature does the published McGee Creek beaver-pond turnaround occur?

The official dataset now establishes a connected 0.97791982-mile prefix, but the published three-mile beaver-pond destination lies within the next unsplit source feature. Neither source publishes a pond coordinate or feature identifier, so Wayproof retains partial topology instead of manufacturing a split point.

Open question. Linked evidence does not resolve this gap.

No specific claim evidence is linked to this question.

Sources, evidence, and history

Planning facts above are readable first. Open these records when you need to audit a source or see when knowledge changed.

Evidence for 1 published claim
Published ChangeSet history

Canonical data is historical evidence, not a guarantee of current conditions. Recheck volatile facts before travel.