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.
Creative Commons Zero v1.0 Universal
89
stars
62
forks
source link
Question - Responsibility for RoadEvent Objects and Lane Objects #214
Issue name: “Question — How to handle responsibility for RoadEvent Objects and Lane Objects
Summary
Currently, the specification says that for RoadEvent Objects "A change in the lane configuration or roadway should result in creating a new road event, separating the work zone into multiple road events." This appears to make a RoadEvent much more complicated than just a roadway name and direction. If that is the case, if changes in the lane configuration or roadway trigger a new road event, who is responsible for maintaining that data?
Similarly, when it comes to LaneObjects for a particular road event, it does not seem like each individual vendor should be defining the roadway geometry. This seems like a task for the DOT or other agency. Again, it is not clear who is responsible for this data, and for altering it when there are roadway changes during construction.
Motivation
When lane configurations are changed during construction, typically the DOT and contractor will be the ones tracking this, not the smart work zone vendor providing the feed. So, how can this be properly maintained and communicated? My experience is that in major highway construction projects, lane configurations change all the time. So how can this be managed properly? This appears to create a great deal of complexity, and also confusion about who will own and be responsible for maintaining this data.
Proposed changes
The simplest solution for this issue could be to simplify the definition of the RoadEvent Object. If all that is needed is a roadway and direction, and not a different object for every different road or lane configuration, then lane changes etc, do not need to be tracked at all. So no one needs to maintain this data.
However, if there need to be a bunch of different RoadEvent Objects and lane configurations, there should be some clarity on who is intended to handle this data for a work zone and how? Does the DOT define the roadway configuration and hand that to the contractor as part of a JSON schema when they start a project there? And does the smart work zone company or other data vendor provide an interface where the DOT can update the data? Or something else? If WZDX involves defining roadways, it should be clear who is the responsible party for doing so.
Issue name: “Question — How to handle responsibility for RoadEvent Objects and Lane Objects
Summary
Currently, the specification says that for RoadEvent Objects "A change in the lane configuration or roadway should result in creating a new road event, separating the work zone into multiple road events." This appears to make a RoadEvent much more complicated than just a roadway name and direction. If that is the case, if changes in the lane configuration or roadway trigger a new road event, who is responsible for maintaining that data?
Similarly, when it comes to LaneObjects for a particular road event, it does not seem like each individual vendor should be defining the roadway geometry. This seems like a task for the DOT or other agency. Again, it is not clear who is responsible for this data, and for altering it when there are roadway changes during construction.
Motivation
When lane configurations are changed during construction, typically the DOT and contractor will be the ones tracking this, not the smart work zone vendor providing the feed. So, how can this be properly maintained and communicated? My experience is that in major highway construction projects, lane configurations change all the time. So how can this be managed properly? This appears to create a great deal of complexity, and also confusion about who will own and be responsible for maintaining this data.
Proposed changes
The simplest solution for this issue could be to simplify the definition of the RoadEvent Object. If all that is needed is a roadway and direction, and not a different object for every different road or lane configuration, then lane changes etc, do not need to be tracked at all. So no one needs to maintain this data.
However, if there need to be a bunch of different RoadEvent Objects and lane configurations, there should be some clarity on who is intended to handle this data for a work zone and how? Does the DOT define the roadway configuration and hand that to the contractor as part of a JSON schema when they start a project there? And does the smart work zone company or other data vendor provide an interface where the DOT can update the data? Or something else? If WZDX involves defining roadways, it should be clear who is the responsible party for doing so.