On May 14, 2025 at noon EDT, the DEP API VDOT event data output will be transitioned to use the VDOT SmarterRoads TMDD feeds. This transition, required by VDOT,  will mainly impact the contents of the output rather than the structure of the output. Some of the key changes and improvements will include the following:

• Exclusion of manually entered Transurban events in VDOT event output (i.e. events with “HOT OC” source type) – for Transurban Express Lanes events, users should use system=vdot_transurban parameter instead.
• Exclusion of inactive planned events (i.e. planned events that do not have status set to “active”).
• Inclusion of responder information and operator notes that were previously available, but were eliminated during the initial enhanced SmarterRoads transition.

These changes will improve the overall accuracy of VDOT event data through exclusion of events that are more accurately defined and available elsewhere (e.g. Transurban events endpoint) and events that are not active on the roadway and generally have inaccurate or uncertain information (e.g. planned events). You may notice that the overall number of available events in the VDOT event output may be significantly smaller, and that’s to be expected due to exclusion of events referenced above.

In addition to content changes, there will be two data elements that will no longer exist in the VDOT event data output since they no longer exist in the source feeds:

• created_tstamp (users should use start_tstamp instead)
• regional (this flag is no longer available)