Reference · built on requestCommons signalTransit, roads & mobility

Caltrans CWWP2 Data Feeds

Lane closures, chain controls, message signs, cameras, roadside weather, and travel times per Caltrans district as CSV, JSON, TXT, and XML.

Request accessPricing ↗

About

The Commercial Wholesale Web Portal (CWWP2) at cwwp2.dot.ca.gov is where the California Department of Transportation publishes near-real-time traveler information from its 12 districts. The data comes from Intelligent Transportation Systems devices along the State Highway System, namely Changeable Message Signs, Closed Circuit Television Cameras, and Roadway Weather Information Systems, and from the central Lane Closure System and Chain Control systems. Each dataset is a file per district at a fixed HTTPS path, in four formats that carry the same fields.

On Fibric, an operator reads the closures, chain controls, and travel times on the routes your drivers or deliveries use and proposes a resequenced route, a delivery hold, or a customer ETA update for your approval.

This is a reference listing. It documents what Fibric would read from Caltrans CWWP2 Data Feeds and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • LCS (Lane Closures): approved closures planned for the next 7 days plus current lane, ramp, and road closures, per district, every 5 minutes
  • Chain Controls (CC): the location and status of each chain control point on the state highway network, once a minute
  • CMS (Changeable Message Signs): the location and current display of each sign, once a minute in most districts
  • CCTV (Closed Circuit Television Cameras): camera locations and status, updated as necessary, in all 12 districts
  • RWIS (Roadway Weather Information Systems): readings from 150 weather, visibility, and environmental units, once a minute, with a recordTimestamp per site
  • TT (Travel Times): segment travel times on selected routes in districts 3, 8, 11, and 12, every 5 minutes

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Resequence stops around a fresh closure

    Poll the district LCS files for the routes on today's runs. When a new closure lands on a segment before its stop, the operator proposes a resequenced route and cites the closure record.

    With Route Resequence

  • Hold mountain deliveries when chains go on

    Read the Chain Controls file for the passes your deliveries cross. When a control point changes status, the operator proposes holding the affected orders and drafts the customer notice.

    With Weather Hold

  • Update the customer ETA from measured travel times

    Use the TT segments on the driver's route to recompute arrival. When the estimate moves past your threshold, the operator proposes a new ETA message for your approval.

    With ETA Notice

Requirements

  • The district numbers for your routes, decoded with the District Map and County Chart
  • A file URL per district and feed, such as data/d4/lcs/lcsStatusD04.json; the same path pattern serves .csv, .txt, and .xml
  • The Field Description and the Postmile Prefix, Route Suffix, and Alignment charts to decode location fields
  • The Chain Control Status Chart and the Duration, Facility, Lane Type, and Type of Work charts to decode coded values
Authentication
None: the files are public HTTPS downloads at cwwp2.dot.ca.gov/data/d{district}/{feed}/, with no key and no charge.

Limits

  • Not every feed exists in every district: chain controls omit districts 4, 5, and 12; RWIS and travel times publish only in reporting districts
  • CCTV carries a fair use policy: viewing 10 or more streams at once needs a written agreement with Caltrans Traffic Operations
  • The TXT format uses a 0xFF delimiter and ISO 8859-1 encoding; XML is ISO-8859-1 while CSV and JSON are UTF-8
  • Caltrans states no warranty for accuracy or completeness, and posted restrictions on the road supersede the feed

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Caltrans CWWP2 Data Feeds ↗

Questions and answers

Is there an API key or a fee?
No. Each dataset page says the files are available over HTTPS for integration into your application and that there is no charge for the use of the data. You fetch a file per district and feed.
How often do the files change?
Lane closures and travel times every 5 minutes. Chain controls, message signs, and RWIS once a minute, except message signs in district 2, which are every 5 minutes. CCTV files update as necessary. RWIS pages tell you to check recordTimestamp for each site's last update.
What are the terms of use?
The Caltrans Conditions of Use state that information on its websites is in the public domain unless otherwise indicated and may be distributed or copied as permitted by law, that copyrighted items such as photographs may need permission, and that no warranty is given. CCTV adds a fair use policy for bulk streaming.
Ask about Caltrans CWWP2 Data Feeds

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by California Department of Transportation (cwwp2.dot.ca.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy