-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional vehicle_impact to enable real time field data #159
Comments
At the last subgroup meeting we discussed adding There was also discussion on whether the Also from the subgroup meeting was a discussion about coordinating with the worker presence subgroup related to flaggers. Since the |
@sergebeaudry - Would you be able to put a pull request together with the changes you suggested as well as adding the |
@sknick-iastate sorry I'm late on this. Yes I'll do a pull request |
@sknick-iastate Regarding your comment
I don't think AFAD or human flagger are really different from the Worker Presence perspective. In both case worker(s) are present. An AFAD has to be operated by a flagger per MUTCD. Next revision is also proposing to clarify further by precluding any sort of automation |
Completed in #196. |
Issue name: “[Clarification / New feature / Question] — Summarize topic”
Summary
Current version does not enable work zone data exchange on important real-time work zone events. EX: a lane closure just been deployed, nothing can tell if the merge is to the right or left unless lane level is provided which is not realist. The following is to add a few new road-impact enumeration to exchange such data elements.
Background
The current roadevent structure has been developed to address a very detailed level of information that could be capture during the planning phase and which can help the data user such as mapping companies and CAV/ADS to figure out the impact of the planned works on their maps. Thus could help them sending resources to digitize the road layout during and after the works.
Real time active work zones
Technologies exists that can reports some real-time field information. Smart Arrow Board can publish their GPS location and the type of merging arrow presented to the motorist (left/right). Temporary traffic light and Flagging operation can also be reported in real-time. Today WZDx cannot be used to exchange that real-time information because that level of detail is only reported inside lane-level elements. It is not realist to expect an arrow board to report such level of lane-level information.
Such level of basic real-time road impact is important for many reasons:
Some DOT already started developing their own API to receive such work zone information because WZDx can't support it today.
Proposed changes
I recommend to add to the
Vehicle Impact
enumerated type the following (current = already in the specification):all-lanes-closed
some-lanes-closed
all-lanes-open
alternating-one-way
unknown
some-lanes-closed-merge-left
some-lanes-closed-merge-right
some-lanes-closed-split
flagging
temporary-traffic-signal
The text was updated successfully, but these errors were encountered: