-
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
New event types #139
Comments
in WI, we use event types as follows: |
To add to this, "snow and Ice" was recently brought up at a meeting with MassDOT. |
The spec extension subgroup generated the idea for a I believe @DeraldDudley is going to create a new issue for the |
Created issue #178 to address restriction-notices directly. |
Closing as the spec has changed significantly since the issue was created and new event types have been partially resolved in #205. |
Background
The WZDx specification and design goals allow it to be general in use and evolve as needed.
The v2.0 release changed the naming from "work zone activity" to "road event" to begin to open the specification's usage to events on a roadway regardless of if they are a work zone.
The v3.0 release added an
event_type
field to the RoadEvent object and created an EventType enumerated type. TheEventType
enumeration contains only two values,work-zone
for representing a typical work zone road event, anddetour
for indicating that a road event is a detour for a work zone.Detour was just the initial use case for the
event_type
field. The intention is for this enumerated type to be expanded with more road event types.Next steps
Discussion of what event types should be added needs to occur—this issue is the place for those discussions.
If a proposed road event type has similar information and impact to travelers as a work zone road event, it is a good candidate to be added. If all the fields on a current
RoadEvent
object apply to the new event, adding an event type is as simple as adding a new value to theEventType
enumerated type.Example event types
The list of example event types below is taken from MassDOT's legacy event reporting system for inspiration:
Caveats and other potential changes
A road event was intended to be generic, however it has a few fields which are largely only relevant to a work zone:
workers_present
type_of_work
Both of these could be made generic by changing to
personnel_present
(or something similar) andsub_type
.Another option is to create specific objects for each event type which extend the base
RoadEvent
object with properties that are only relevant to the event type.workers_present
andtype_of_work
would move to theWorkZone
object in this case. This allows adding event type specific fields. It is backward compatible as thework-zone
RoadEvent
details would not change.The text was updated successfully, but these errors were encountered: