On November 14, 2025, DEP API was updated to use SmarterRoads as the source of VDOT RWIS data in response to VDOT’s migration of RWIS stations described in November 6th announcement. The DEP development team switched the source interface in a way that preserved the DEP API output and prevented need for any rework from the downstream users. VDOT has confirmed that the element mappings and units are correct. As of November 14, 2025, VDOT RWIS data is once again available in the DEP API output.

On November 13, 2025 from 7pm to 7:45pm, the DEP will undergo brief maintenance to deploy additional redundancy hardware to further harden and improve the stability of the overall system. In addition to the new hardware, during this maintenance DEP will apply security patches to continue to maintain strong security posture. While it is unlikely that the maintenance will cause any down time, there is a possibility of brief connectivity interruptions as DNS changes are propagating.

Sometime earlier this year, VDOT began migrating RWIS stations from the system that DEP was using to collect RWIS data to another system and the new SmarterRoads portal. The result of this migration was that DEP was slowly losing access to RWIS stations. Once notified of this migration, the DEP team has prioritized addressing this change and using the new interface for VDOT RWIS data. While the source data format is different, the DEP will strive to maintain the existing API output and reduce or eliminate any changes needed for the downstream API users. It is anticipated that the DEP change will be in place on or around November 14, 2025, at which time all VDOT RWIS stations’ data will once again be available to the DEP API users.

On November 6, 2025, at 12pm EST the DEP API VDOT event and detector endpoints will be updated to include additional data elements (as described in October 17, 2025 post).

These enhancements include the following:

Detector Data Endpoint

1. Addition of <milemarker> element to the detector location element.
2. Addition of <lanes> element to detector zone data element.

VDOT Event Data

1. Addition of <typeFurtherInfo> element to the <agencyExtension> element
   • Just like <publicText>, this is an optional field and will be missing if the event does not have it.
2. Addition of <cause> element to the <agencyExtension> element
   • Just like <publicText>, this is an optional field and will be missing if the event does not have it.
3. Addition of <specialFacility> element to the <agencyExtension> element
   • Just like <publicText>, this is an optional field and will be missing if the event does not have it.
4. Addition of <description> element to the <onAddress> element.
   • While this element is technically optional, the start location should always be set, and the end location <onAddress> will only be set for workzone events with start and end point.

For more information, please contact the DEP Customer Support at dep-support@ritis.org.

On October 17, 2025, the DEP API event data output was updated for VDOT events to include the end mile marker values for work zones where that data is available.

In scope of these enhancements, there are additional updates that are anticipated to be deployed by early November that will include the following additions (when available) to the DEP API VDOT event data output:

• <typeFurtherInfo> freetext field for “other traffic” and “other weather” event types
• <cause> for short term weather events
• <description> for the start and end location point names and <specialFacility>  when used for special facilities

On October 7, 2025, the DEP reference documentation section 2.8 now includes supplemental information about Transurban toll rate origins and destination (OD) pairs.