Roads

Road conditions come from three live layers the Grid projects for a place — each one RFC 7946 GeoJSON from GET /api/v1/places/{place}/map/{layer}.geojson. road_segment carries travel time, delay, congestion and open/restricted/closed status (Google Routes + Caltrans); chain_control the active R1/R2/R3 controls; road_incident the AI-enhanced CHP/Caltrans incidents. Each layer's metadata.source_status is rendered honestly: an UNAVAILABLE layer is shown loud — and an empty layer is a clean report, not an all-clear.

no key required CORS-open

Place — GET /api/v1/places?kind=AREA

Road segments

GET …/map/road_segment.geojson

status · congestion · travel time · delay

One row per monitored road, drawn live from Google Routes travel times and Caltrans status. Delay is against the road's free-flow duration; status is AI-determined (open / restricted / closed) with the explanation shown when a road isn't fully open.

Chain control

GET …/map/chain_control.geojson

level · highway · direction

Active chain requirements from Caltrans (R1 chains or 4WD · R2 chains except 4WD · R3 chains required, all vehicles). Empty here means the source reported no controls — not a failed feed.

Road incidents

GET …/map/road_incident.geojson

severity · headline · log #

CHP and Caltrans incidents on these corridors, each AI-enhanced into a readable summary with an impact-driven severity. These are stored events — the same records GET /api/v1/events?layer=road_incident returns.