Skip to content
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

Closed
j-d-b opened this issue Nov 10, 2020 · 5 comments
Closed

New event types #139

j-d-b opened this issue Nov 10, 2020 · 5 comments
Labels
New Functionality This item relates to adding new functionality to the specification Specification Extension This issue/PR is related to the Specification Extension Subgroup

Comments

@j-d-b
Copy link
Collaborator

j-d-b commented Nov 10, 2020

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. The EventType enumeration contains only two values, work-zone for representing a typical work zone road event, and detour 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 the EventType enumerated type.

Example event types

The list of example event types below is taken from MassDOT's legacy event reporting system for inspiration:

Weather
Chemical spill
Special (Road race, parade, VIP visit)

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) and sub_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 and type_of_work would move to the WorkZone object in this case. This allows adding event type specific fields. It is backward compatible as the work-zone RoadEvent details would not change.

@j-d-b j-d-b added Needs discussion This issue needs clarification/additional discussion or is inactive Data-content labels Nov 10, 2020
@j-d-b j-d-b changed the title New Event Types New event types Nov 10, 2020
@yc-uw
Copy link

yc-uw commented Dec 17, 2020

in WI, we use event types as follows:
a. Construction
b. Maintenance
c. Permit
d. Special Event
e. Emergency Closure
Among them, a., b., and c. are work zone related, and d. Special Event is for lane closures due to parades, festivals, etc., that close the roadway to traffic and e. Emergency Closure is for road closures due to flooding, pavement repairs, etc., since they have similar impacts to travelers.

@j-d-b
Copy link
Collaborator Author

j-d-b commented Jan 27, 2021

To add to this, "snow and Ice" was recently brought up at a meeting with MassDOT.

@j-d-b
Copy link
Collaborator Author

j-d-b commented Jul 4, 2021

The spec extension subgroup generated the idea for a restriction-notice road event type. This event type would be used for road events that are intended to represent a section of a roadway with with a specific restriction. A restriction-notice road event can represent a permanent restriction unrelated to road work or a work zone, such as reduced height due to an overhead structure, reduced width on a bridge, etc.

I believe @DeraldDudley is going to create a new issue for the restriction-notice type specifically, which will be referenced here once it is created.

@DeraldDudley
Copy link
Collaborator

Created issue #178 to address restriction-notices directly.

@j-d-b j-d-b removed the Needs discussion This issue needs clarification/additional discussion or is inactive label Jul 16, 2021
@mark-mockett mark-mockett added the Specification Extension This issue/PR is related to the Specification Extension Subgroup label Jul 23, 2021
@j-d-b j-d-b added New Functionality This item relates to adding new functionality to the specification and removed Data-content labels Feb 28, 2022
@j-d-b
Copy link
Collaborator Author

j-d-b commented Mar 23, 2022

Closing as the spec has changed significantly since the issue was created and new event types have been partially resolved in #205.

@j-d-b j-d-b closed this as completed Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Functionality This item relates to adding new functionality to the specification Specification Extension This issue/PR is related to the Specification Extension Subgroup
Projects
None yet
Development

No branches or pull requests

4 participants