{
  "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"
        }
      ]
    }
  ],
  "entities": [
    {
      "entity_id": "route-mcgee-creek-beaver-pond",
      "kind": "route",
      "name": "McGee Creek to Beaver Pond"
    }
  ],
  "history": [
    {
      "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."
    }
  ],
  "navigation": {
    "next_id": "claim-route-mcgee-creek-beaver-pond-profile",
    "position": 3111,
    "previous_id": "claim-route-lundy-canyon-waterfall-beaver-dam-profile",
    "total": 3965
  },
  "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"
    }
  ],
  "record": {
    "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}"
    }
  },
  "record_type": "claim",
  "related_records": [],
  "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"
    }
  ]
}