search

usdot-jpo-ode / wzdx

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

Represent accuracy of intermediate geometry points #232

Closed j-d-b closed 1 year ago

j-d-b commented 2 years ago

Background

In WZDx v4.0 (current), the WorkZoneRoadEvent has two properties for describing the accuracy of the start and end positions of the road event at a high level, beginning_accuracy and ending_accuracy. These properties can have a value of either estimated or verified, defined in the SpatialVerification enumerated type. Thus it is currently only possible to describe the accuracy of the first and last coordinates in the containing RoadEventFeature's geometry (array of coordinates).

Possible new feature

It may be beneficial to add properties or restructure how spatial accuracy is represented to allow describing the accuracy of the intermediate coordinates between the start and end in a work zone road event with a LineString geometry. Consumers could then have more information to decide how to use the intermediate coordinates in snapping the road event to their map.

Drawbacks

For the majority of current WZDx feed producing agencies, the only position that will be verified is the start. In some but fewer cases, the end will be as well. Adding the ability to represent the accuracy of the points in between adds complexity to the specification for the benefit of only a small number of users—maybe none immediately. Likely this feature should be addressed only once there are more producers who are able to provide verified the middle points in the road event.

sergebeaudry commented 2 years ago

Great suggestion. Today some vendors have GPs enabled devices that could be use to report an intermediate coordinates. EX: a smart arrow can report a left arrow with its GPS coordinate using the 4.0 SwzDeviceFeed . This could then be use to create a segment within the workzone where the road impact will be reported based on the Arrow board mode. Same apply for DSL where speed is dropped at the work zone approach or alternate one-way road using AFAD or flagger GPs devices within a larger work zone.

I think we will need it down the road. do we need it now or later? Let see data consumer opinions on the subject.

j-d-b commented 1 year ago

Closing as low priority/lack of interest. The most important positions are the start and end of the event. Most consumers snap/map the line to their base map so the accuracy of the intermediate points is not critical. This can be reopened if needs change.