{
  "answerability": "evidence_backed_claims_available",
  "claims": [
    {
      "claim": {
        "claim_id": "claim-route-mcgee-creek-beaver-pond-dataset-prefix",
        "evidence_ids": [
          "evidence-route-mcgee-creek-beaver-pond-dataset-prefix"
        ],
        "predicate": "dataset_route_partial_topology",
        "spatial_scope_ids": [
          "scope-route-mcgee-creek-beaver-pond"
        ],
        "subject_id": "route-mcgee-creek-beaver-pond",
        "temporal_scope": null,
        "value": {
          "bidirectional": true,
          "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": [
        {
          "claim_id": "claim-route-mcgee-creek-beaver-pond-dataset-prefix",
          "evidence_id": "evidence-route-mcgee-creek-beaver-pond-dataset-prefix",
          "notes": "",
          "observation_id": "observation-usgs-mcgee-short-route-prefix-20260925",
          "stance": "supports"
        }
      ],
      "observations": [
        {
          "artifact_refs": [
            "geometry/v0/snapshots/usgs-mcgee-lundy-routes-20260925.geojson"
          ],
          "content": "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_id": "observation-usgs-mcgee-short-route-prefix-20260925",
          "observed_at": null,
          "observer": "",
          "retrieved_at": "2026-09-25T09:00:00+00:00",
          "source_id": "source-usgs-national-digital-trails-eastern-sierra-20260924"
        }
      ],
      "sources": [
        {
          "locator": "https://partnerships.nationalmap.gov/arcgis/rest/services/USGSTrails/MapServer/0",
          "publisher": "U.S. Geological Survey / U.S. Forest Service",
          "source_id": "source-usgs-national-digital-trails-eastern-sierra-20260924"
        }
      ],
      "subject": {
        "entity_id": "route-mcgee-creek-beaver-pond",
        "kind": "route",
        "name": "McGee Creek to Beaver Pond"
      }
    },
    {
      "claim": {
        "claim_id": "claim-route-mcgee-creek-beaver-pond-profile",
        "evidence_ids": [
          "evidence-route-mcgee-creek-beaver-pond-profile"
        ],
        "predicate": "published_route_profile",
        "spatial_scope_ids": [
          "scope-route-mcgee-creek-beaver-pond"
        ],
        "subject_id": "route-mcgee-creek-beaver-pond",
        "temporal_scope": null,
        "value": {
          "destination": "active beaver pond",
          "distance_precision": "published rounded value",
          "one_way_miles": 3,
          "route_shape": "out_and_back",
          "setting": "aspen groves along McGee Creek"
        }
      },
      "evidence": [
        {
          "claim_id": "claim-route-mcgee-creek-beaver-pond-profile",
          "evidence_id": "evidence-route-mcgee-creek-beaver-pond-profile",
          "notes": "",
          "observation_id": "observation-mono-county-mcgee-beaver-pond-20260925",
          "stance": "supports"
        }
      ],
      "observations": [
        {
          "artifact_refs": [],
          "content": "The Eastern Sierra fall-color map describes a steady three-mile climb along McGee Creek through aspen groves to an active beaver pond suitable as a lunch stop.",
          "observation_id": "observation-mono-county-mcgee-beaver-pond-20260925",
          "observed_at": null,
          "observer": "",
          "retrieved_at": "2026-09-25T02:30:00+00:00",
          "source_id": "source-mono-county-mcgee-fall-color-map"
        }
      ],
      "sources": [
        {
          "locator": "https://bishopvisitor.com/wp-content/uploads/2024/10/FallColorMap2017.pdf",
          "publisher": "Eastern Sierra Visitors Council / Mono County Tourism",
          "source_id": "source-mono-county-mcgee-fall-color-map"
        }
      ],
      "subject": {
        "entity_id": "route-mcgee-creek-beaver-pond",
        "kind": "route",
        "name": "McGee Creek to Beaver Pond"
      }
    }
  ],
  "entity": {
    "entity_id": "route-mcgee-creek-beaver-pond",
    "kind": "route",
    "name": "McGee Creek to Beaver Pond"
  },
  "gap_details": [
    {
      "claims": [],
      "entities": [
        {
          "entity_id": "place-mcgee-creek-beaver-pond",
          "kind": "place",
          "name": "McGee Creek Beaver Pond"
        },
        {
          "entity_id": "route-mcgee-creek",
          "kind": "route",
          "name": "McGee Creek Trail"
        },
        {
          "entity_id": "route-mcgee-creek-beaver-pond",
          "kind": "route",
          "name": "McGee Creek to Beaver Pond"
        },
        {
          "entity_id": "route-segment-mcgee-pass-07",
          "kind": "route_segment",
          "name": "McGee Pass dataset segment 7"
        }
      ],
      "history": [
        {
          "action": "ADD",
          "change_set_id": "wp-20260923-eastern-sierra-foliage-hikes",
          "evidence_refs": [],
          "knowledge_gap_refs": [],
          "path": "canonical/v0/gaps/gap-mcgee-creek-day-hike-distance.json",
          "reason": "Publish a source-backed access and route foundation for Eastern Sierra fall-foliage day-hike alternatives near East Fork Campground.",
          "record_id": "gap-mcgee-creek-day-hike-distance",
          "record_type": "gap",
          "summary": "Add source-backed Eastern Sierra foliage-hike trailheads, managing areas, route associations, published distances and hazards, plus explicit research and pre-trip gaps."
        },
        {
          "action": "REPLACE",
          "change_set_id": "wp-20260925-eastern-sierra-turnaround-options",
          "evidence_refs": [],
          "knowledge_gap_refs": [],
          "path": "canonical/v0/gaps/gap-mcgee-creek-day-hike-distance.json",
          "reason": "Add full-corridor route depth and evidence-bounded foliage turnaround options for McGee Creek and Lundy Canyon.",
          "record_id": "gap-mcgee-creek-day-hike-distance",
          "record_type": "gap",
          "summary": "Add complete McGee corridor geometry and distinct McGee and Lundy foliage turnaround options while preserving exact-junction uncertainty."
        },
        {
          "action": "REPLACE",
          "change_set_id": "wp-20260925-lundy-mcgee-convict-depth",
          "evidence_refs": [],
          "knowledge_gap_refs": [],
          "path": "canonical/v0/gaps/gap-mcgee-creek-day-hike-distance.json",
          "reason": "Close Lundy's distance answer and add evidence-bounded McGee and Convict topology.",
          "record_id": "gap-mcgee-creek-day-hike-distance",
          "record_type": "gap",
          "summary": "Resolve Lundy's bounded distance answer, expose McGee's connected prefix, and close Convict Lake Loop topology from an official map."
        }
      ],
      "navigation": {
        "next_id": "gap-ohlone-doe-water-exact-coordinate",
        "position": 236,
        "previous_id": "gap-mammoth-lakes-basin-route-distances",
        "total": 299
      },
      "observations": [],
      "record": {
        "gap_id": "gap-mcgee-creek-day-hike-distance",
        "question": "Where within the retained 2.845-mile source feature does the published McGee Creek beaver-pond turnaround occur?",
        "reason": "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.",
        "related_ids": [
          "route-mcgee-creek",
          "route-mcgee-creek-beaver-pond",
          "place-mcgee-creek-beaver-pond",
          "route-segment-mcgee-pass-07"
        ]
      },
      "record_type": "gap",
      "related_records": [
        {
          "record": {
            "entity_id": "route-mcgee-creek",
            "kind": "route",
            "name": "McGee Creek Trail"
          },
          "record_id": "route-mcgee-creek",
          "record_type": "entity"
        },
        {
          "record": {
            "entity_id": "route-mcgee-creek-beaver-pond",
            "kind": "route",
            "name": "McGee Creek to Beaver Pond"
          },
          "record_id": "route-mcgee-creek-beaver-pond",
          "record_type": "entity"
        },
        {
          "record": {
            "entity_id": "place-mcgee-creek-beaver-pond",
            "kind": "place",
            "name": "McGee Creek Beaver Pond"
          },
          "record_id": "place-mcgee-creek-beaver-pond",
          "record_type": "entity"
        },
        {
          "record": {
            "entity_id": "route-segment-mcgee-pass-07",
            "kind": "route_segment",
            "name": "McGee Pass dataset segment 7"
          },
          "record_id": "route-segment-mcgee-pass-07",
          "record_type": "entity"
        }
      ],
      "sources": []
    }
  ],
  "history": [
    {
      "action": "ADD",
      "change_set_id": "wp-20260925-eastern-sierra-turnaround-options",
      "evidence_refs": [],
      "knowledge_gap_refs": [],
      "path": "canonical/v0/entities/route-mcgee-creek-beaver-pond.json",
      "reason": "Add full-corridor route depth and evidence-bounded foliage turnaround options for McGee Creek and Lundy Canyon.",
      "record_id": "route-mcgee-creek-beaver-pond",
      "record_type": "entity",
      "summary": "Add complete McGee corridor geometry and distinct McGee and Lundy foliage turnaround options while preserving exact-junction uncertainty."
    },
    {
      "action": "ADD",
      "change_set_id": "wp-20260925-lundy-mcgee-convict-depth",
      "evidence_refs": [],
      "knowledge_gap_refs": [],
      "path": "canonical/v0/claims/claim-route-mcgee-creek-beaver-pond-dataset-prefix.json",
      "reason": "Close Lundy's distance answer and add evidence-bounded McGee and Convict topology.",
      "record_id": "claim-route-mcgee-creek-beaver-pond-dataset-prefix",
      "record_type": "claim",
      "summary": "Resolve Lundy's bounded distance answer, expose McGee's connected prefix, and close Convict Lake Loop topology from an official map."
    },
    {
      "action": "ADD",
      "change_set_id": "wp-20260925-eastern-sierra-turnaround-options",
      "evidence_refs": [],
      "knowledge_gap_refs": [],
      "path": "canonical/v0/claims/claim-route-mcgee-creek-beaver-pond-profile.json",
      "reason": "Add full-corridor route depth and evidence-bounded foliage turnaround options for McGee Creek and Lundy Canyon.",
      "record_id": "claim-route-mcgee-creek-beaver-pond-profile",
      "record_type": "claim",
      "summary": "Add complete McGee corridor geometry and distinct McGee and Lundy foliage turnaround options while preserving exact-junction uncertainty."
    }
  ],
  "journey": [],
  "knowledge_gaps": [
    {
      "gap_id": "gap-mcgee-creek-day-hike-distance",
      "question": "Where within the retained 2.845-mile source feature does the published McGee Creek beaver-pond turnaround occur?",
      "reason": "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.",
      "related_ids": [
        "route-mcgee-creek",
        "route-mcgee-creek-beaver-pond",
        "place-mcgee-creek-beaver-pond",
        "route-segment-mcgee-pass-07"
      ]
    }
  ],
  "reference_evidence": [],
  "relationships": [
    {
      "evidence_ids": [
        "evidence-route-mcgee-creek-beaver-pond-profile"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "accesses",
      "relationship_id": "relationship-mcgee-trailhead-accesses-beaver-pond-route",
      "subject_id": "trailhead-mcgee-creek",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-mcgee-creek-beaver-pond-profile"
      ],
      "object_id": "place-mcgee-creek-beaver-pond",
      "predicate": "ends_at",
      "relationship_id": "relationship-mcgee-beaver-pond-route-ends-at",
      "subject_id": "route-mcgee-creek-beaver-pond",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-mcgee-creek-beaver-pond-profile"
      ],
      "object_id": "route-mcgee-creek",
      "predicate": "part_of",
      "relationship_id": "relationship-mcgee-beaver-pond-route-part-of-corridor",
      "subject_id": "route-mcgee-creek-beaver-pond",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-01"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-01-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-01",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-02"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-02-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-02",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-03"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-03-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-03",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-04"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-04-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-04",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-05"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-05-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-05",
      "temporal_scope": null
    },
    {
      "evidence_ids": [
        "evidence-route-segment-mcgee-pass-06"
      ],
      "object_id": "route-mcgee-creek-beaver-pond",
      "predicate": "shared_prefix_of",
      "relationship_id": "relationship-route-segment-mcgee-pass-06-shared-prefix-of-mcgee-beaver-pond",
      "subject_id": "route-segment-mcgee-pass-06",
      "temporal_scope": null
    }
  ],
  "route_geometry": null,
  "route_geometry_url": null,
  "type": "canonical_entity"
}