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
92
stars
62
forks
source link
Require restriction type for a lane restriction #81
Currently, none of the fields on lane_restriction entity that are present in the output data feed are required. That means it's possible for the lane_restrictions field on the lane object to contain an array of empty objects, that is
{
"lanes": [
{
"lane_restrictions: [{},{}],
}
]
}
Requiring restriction type on the lane_restriction entity would solve this issue and is a simple fix. I don't see a downside to having this required as a lane restriction is useless without the type.
Chris Brookes MDOT: so how would working outside the roadway be added? Tree Clearing Surveying operations? We want to show the workers on the side of the road. as this is a common work type. I just wanted to make sure that was an option as if you cant leave it blank, but sounds like it is. Chris is already part of the Worker Presence subgroup.
Currently, none of the fields on
lane_restriction
entity that are present in the output data feed are required. That means it's possible for thelane_restrictions
field on thelane
object to contain an array of empty objects, that isRequiring restriction type on the lane_restriction entity would solve this issue and is a simple fix. I don't see a downside to having this required as a lane restriction is useless without the type.