The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.
Add a new Marked Location to the DeviceFeed that represents any MUTCD standard temporary Traffic Control zone signs as defined per the MUTCD standard. Ref: Table 6F-1
Motivation
Currently the DeviceFeed includes many Location Markers and the list keeps growing over the feed iterations. The ultimate goal of the feed is to become a real-time digital representation of the physical work zone. A typical work zone has many standardized temporary traffic control signs and each represents critically important information such as location of the work zone, lower work zone speed changes, closure, shift, etc... Each of those sign has a specific MUTCD code that is standardize such as the following.
By adding a few more elements to the current LocationMarkerobject this would allow future solutions to potentially fully digitize a job layout and transmit it using WZDx DeviceFeed. Applications are multiple including quality control, job conformity, inventory management, real-time road impacts to connected car or digital map, etc....
MUTCD_Sign_Designation: String, required only if MarkerLocationTypeis mutcd-sign. Represent the official MUTCD code as per current standard. EX: G20-05aP for a work zone sign, R11-2 for Road Closed
MUTCD_Sign_Name: String, optional. Represents the official MUTCD sign name. To make the feed easier to read.
MUTCD_Sign_speed: Integer, optional. Every speed sign has the same MUTCD Designation which is R2-1.
to differentiate a 40, 55, 65 MPH this field would be offered to complement the sign designation info
MUTCD_sign_direction. Choice: Left, Right. Optional. Some MUTCD signs such as W1-6
are used for both directions. They simply flip it over at the installation. This field will provide a way to specify in which direction those are pointing if known.
Summary
Add a new Marked Location to the DeviceFeed that represents any MUTCD standard temporary Traffic Control zone signs as defined per the MUTCD standard. Ref: Table 6F-1
Motivation
Currently the DeviceFeed includes many Location Markers and the list keeps growing over the feed iterations. The ultimate goal of the feed is to become a real-time digital representation of the physical work zone. A typical work zone has many standardized temporary traffic control signs and each represents critically important information such as location of the work zone, lower work zone speed changes, closure, shift, etc... Each of those sign has a specific MUTCD code that is standardize such as the following.
By adding a few more elements to the current
LocationMarker
object this would allow future solutions to potentially fully digitize a job layout and transmit it using WZDx DeviceFeed. Applications are multiple including quality control, job conformity, inventory management, real-time road impacts to connected car or digital map, etc....Proposed changes
Add mutcd-sign to the MarkerLocationType enumerated type, which is part of the LocationMarker - MarketLocation object
Add the following properties to the LocationMarker Object: Others ideas welcome
MUTCD_Sign_Designation:
String, required only ifMarkerLocationType
ismutcd-sign
. Represent the official MUTCD code as per current standard. EX: G20-05aP for a work zone sign, R11-2 for Road ClosedMUTCD_Sign_Name
: String, optional. Represents the official MUTCD sign name. To make the feed easier to read.MUTCD_Sign_speed
: Integer, optional. Every speed sign has the same MUTCD Designation which is R2-1. to differentiate a 40, 55, 65 MPH this field would be offered to complement the sign designation infoMUTCD_sign_direction
. Choice: Left, Right. Optional. Some MUTCD signs such as W1-6are used for both directions. They simply flip it over at the installation. This field will provide a way to specify in which direction those are pointing if known.