Walk through Big Bear

This is the primary CTA flow from the Introduction page. Start with discovery, ask for the destination answer, then drill into one route or the detailed conditions feed only when the caller needs more context.

1. Discover the destination

Find Big Bear in the complete consumer-place catalog, capture the canonical big-bear slug, and verify endpoints.access is true before you request access.

GET /v1/destinations

{
  "data": [
    {
      "destination": "big-bear",
      "label": "Big Bear Lake",
      "kind": "mountain-community",
      "area": "southern-california-mountains",
      "jurisdiction": "US-CA",
      "jurisdiction_slug": "ca",
      "routes": ["SR-18", "SR-38", "SR-138", "SR-330"],
      "communities": [],
      "facets": ["mountain-biking", "boating", "fishing", "hiking", "off-roading"],
      "contained_by": null,
      "endpoints": {
        "access": true,
        "weather": true,
        "map_geometry": true,
        "route_summary": true
      }
    }
  ],
  "_meta": {
    "request_id": "req_big_bear_discovery",
    "response_generated_at": "2026-04-15T15:00:00.000Z",
    "pagination": null
  }
}

2. Ask for access

Destination access is the answer surface. It tells you whether Big Bear is reachable and which access paths are open, restricted, or unconfirmed.

GET /v1/destinations/big-bear/access

{
  "data": {
    "destination": "big-bear",
    "coverage": "full",
    "access_state": "restricted",
    "reason_excerpt": "Chain controls are reported on one or more Big Bear access paths.",
    "paths": [
      {
        "id": "ca:big-bear:west_via_sr18",
        "label": "West approach via SR-18",
        "coverage": "full",
        "access_state": "restricted"
      },
      {
        "id": "ca:big-bear:north_via_sr38",
        "label": "North approach via SR-38",
        "coverage": "full",
        "access_state": "open"
      }
    ]
  },
  "_meta": {
    "request_id": "req_big_bear_access",
    "query_coverage": "full"
  }
}

3. Optional route summary

When the caller needs to inspect one road in the Big Bear corridor, use route summary as a route-specific drilldown rather than as the first destination call.

GET /v1/routes/SR-18/summary

{
  "data": {
    "route": "SR-18",
    "jurisdictions_covered": ["US-CA"],
    "worst_status": "restricted",
    "worst_chain_control_severity": 3,
    "worst_chain_control_code": "chains_awd_exempt",
    "worst_chain_control_raw": "R-2",
    "summary": "Chain or traction restrictions are reported on SR-18.",
    "active_restrictions": 1,
    "total_segments": 1,
    "sections": []
  },
  "_meta": {
    "request_id": "req_big_bear_route_summary",
    "query_coverage": "full"
  }
}

4. Detailed conditions

Conditions stays last. Use it when you need the underlying segment rows for filtering, support workflows, or debugging one restriction in more detail.

GET /v1/conditions?jurisdiction=US-CA&route=SR-18

{
  "data": [
    {
      "id": "ca-d8-chain-controls:sr-18-example",
      "route": "SR-18",
      "overall_status": "restricted",
      "segment_description": "Big Bear Lake to Running Springs",
      "chain_control_raw": "R-2",
      "status_description": "Chains required"
    }
  ],
  "_meta": {
    "request_id": "req_big_bear_conditions",
    "query_coverage": "full"
  }
}

PLAN YOUR TRIP

ABOUT THIS SITE