On July 10, 2025, one of the database servers supporting the DEP is scheduled for an upgrade from 7:30 PM to approximately 9:00 PM EDT. During this maintenance window, access to certain data and related services may be temporarily unavailable.

On June 24, 2025, the DEP reference documentation section 2.3 now includes supplemental information about VDOT event types and subtypes and their translations to the DEP output TMDD standard types and subtypes and DEP custom types and attributes.

Starting on May 16, 2025, the Arlington Bike/Ped Counter data source went offline. As a result of coordinated outreach to the source, it was discovered that the Arlington Bike/Ped Counter data is no longer available via previously integrated data source. The data still exists, but it is now housed on a different set of URLs and feeds. The DEP will address this change in the future when resources are available. Until then, the Arlington County Bike/Ped Counter data will not be available in the DEP beyond May 16, 2025.

On June 23, 2025, the DEP API VDOT event data output will be amended to include the 511 additional text element from the SmarterRoads TMDD data feed for events that have this information. Since this is a non-standard data element, it will be included within <agencyExtensions> data structure.

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)

On April 29, 2025, INRIX released their 25.1 map update. Based on the DEP team’s assessment, the update included roughly 4,226 new XD segments, and roughly 2,014 modified XD segments in Virginia. The DEP API real-time output using INRIX segments accounts for any newly added, removed, or modified segments. For users with access to the PDA API, data after April 29 will be reported using the new map. We expect to update the historical data to reflect the new map as much as possible by June.