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
Refactor and clarify event status and start/end date verification #294
Add new boolean properties is_start_date_verified and is_end_date_verified to the WorkZoneRoadEvent and DetourRoadEvent to indicate if the work zone or detour has been confirmed to have started/ended by a person or device in the field or report from a TMC, or similar.
Require either start_date_accuracy or is_start_date_verified.
Require eitherend_date_accuracy or is_end_date_verified.
Update example feeds to use is_start_date_verified and is_end_date_verified and not use event_status, start_date_accuracy, or end_date_accuracy.
See #281 for a similar approach of using booleans that this PR is consistent with.
@j-d-b I thought we discussed at one point but were we planning on still updating the object and enumeration lists in the spec-content README? Or will we just do this when everything is merged?
This PR resolves #189. Specifically, it proposes the following changes:
event_status
property on the WorkZoneRoadEvent and DetourRoadEvent.start_date_accuracy
andend_date_accuracy
properties on the WorkZoneRoadEvent and DetourRoadEvent.is_start_date_verified
andis_end_date_verified
to the WorkZoneRoadEvent and DetourRoadEvent to indicate if the work zone or detour has been confirmed to have started/ended by a person or device in the field or report from a TMC, or similar.start_date_accuracy
oris_start_date_verified
.end_date_accuracy
oris_end_date_verified
.is_start_date_verified
andis_end_date_verified
and not useevent_status
,start_date_accuracy
, orend_date_accuracy
.See #281 for a similar approach of using booleans that this PR is consistent with.