-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add Incident EventType #13
Comments
Some complexity is regarding what road event object the It seems like what closure is trying to solve could be done using the VehicleImpact, as proposed in #12. For example if a RestrictionRoadEvent has a |
The Extension Subgroup’s interest is the ability to identify an event as a closure. It seems the EventType or the RestrictionType enumerations are the best fits in the model. VehicleImpact doesn’t really work because it describes how an event affects road traffic. How do you feel about adding a |
@DeraldDudley I think what Jacob was getting at is that adding |
@mark-mockett Sorry I didn't catch that. Thank you for clarifying. Adding |
I would like to recommend that the new EeventType object be called IncidentRoadEvent. The word 'closure' can be bit confusing given that WorkZoneRoadEvent can also have closures. Also, IncidentRoadEvent name would allow for roadway impacts more than just closure. |
Attached is a list of incident/event causes we use in the Bay Area 511 system. |
Updated the Issue #13 with latest thoughts of the Extension Subgroup |
FYI, very few agencies use the word "accident". Most prefer "crash" or "incident". I would suggest we do the same. |
Agree its a bit outdated but we're trying to stick with the TMDD so we don't create competing enumerations... |
Will the IncidentRoadEvent occur in a the RoadRestrictionFeed or will a new feed be created for this new event type? Would you be open to implementing these changes in a forked version of the repo? I feel that the extension-related issues and content that has no relation to work zones are making it hard to follow what WZDx is, harder to find issues, PRs, and objects that are relevant to the primary goal of WZDx, to standardize representing work zone data. I'd suggest we create a new |
I'll post an issue proposing a new feed type for incidents today. Just haven't gotten to it yet. Open to Discuss - The WZ spec obviously adds value to the Extension but the Extension adds value (increased accessibility) to the WZ too. I'm concerned about divergent specs. Lets find a way to compliment each other... |
To limit the potential for divergence, instead of a fork, the extensions (non-work zone) could go in a |
Version 2 - Add Incident EventType
Summary
Add an
incident
value to the EventType EnumerationMotivation
Adding an
incident
value to the EventType enumeration enables publishers to inform drivers about events that close or restricts the use of road segments. This is valuable because it reduces driver uncertainty and increases the probability of driver success. It also fulfills use cases identified by WZDx working group members and state transportation officials. These use cases include informing citizens about road closures after a hurricane and informing transportation management centers about road status during emergencies.Adding 'closures' will bolster the specifications usefulness. A more useful specification is more likely to be implemented. More implementations inform more drivers about hazards to navigation. Better informed drivers avoid hazards resulting in safer, cleaner, and more efficient transportation.
IncidentRoadEvents vs WorkZoneRoadEvents
IncidentRoadEvents are very similar to WorkZoneRoadEvent. They are different in the following ways:
type_of_work
is dropped from the IncidentRoadEvent object.end_date
is optional in IncidentRoadEvent object.type_of_incident
is created for the IncidentRoadEvent object. Incident types are described using event_cause from the Transportation Management Data Dictionary 3.1 (TMDD)Proposed changes
EventType Enumeration
work-zone
Inclusions:
- Long-term stationary highway construction such as building a new bridge, adding travel lanes to the roadway, and extending an existing trafficway.
- Mobile highway maintenance such as striping the roadway, median, and roadside grass mowing/landscaping, and pothole repair.
- Short-term stationary utility work such as repairing electric, gas, or water lines within the trafficway.
Exclusions:- Private construction, maintenance, or utility work outside the trafficway.
*The AASHTO term equivalent to roadway is traveled way.*The AASHTO term equivalent to trafficway is highway, street, or road.
Source: https://www.fhwa.dot.gov/publications/publicroads/99mayjun/workzone.cfm
detour
Source: https://mutcd.fhwa.dot.gov/htm/2009/part6/part6c.htm
restriction
incident
IncidentRoadEvent Object
The
IncidentRoadEvent
object locates and describes incidents or events that close or restrict the use of a road segment.The
IncidentRoadEvent
is a type of road event; it has acore_details
property which contains the RoadEventCoreDetails and exists within a RoadEventFeature.Properties
core_details
types_of_incident
start_date
2016-11-03T19:37:00Z
.end_date
2016-11-03T19:37:00Z
.start_date_accuracy
end_date_accuracy
beginning_accuracy
ending_accuracy
location_method
vehicle_impact
lanes
beginning_cross_street
ending_cross_street
beginning_milepost
ending_milepost
event_status
worker_presence
reduced_speed_limit_kph
restrictions
Used By
properties
Version 1 - Superseded by version 2 Above
Summary
Add a
closure
value to the EventType EnumerationMotivation
Adding a
closure
value to the EventType enumeration enables publishers to inform drivers about road closures. This adds value to road event feeds by reducing driver uncertainty and increasing the probability of driver success. It also fulfills use cases identified by WZDx working group members. These use cases include informing citizens about road closures after a hurricane and informing transportation management centers about road status during emergencies.Adding 'closures' will bolster the usefulness of RoadRestrictionFeeds and hopefully increase its uptake. It might also server Work Zone Data feeds.
Proposed changes
After
work-zone
Inclusions:
- Long-term stationary highway construction such as building a new bridge, adding travel lanes to the roadway, and extending an existing trafficway.
- Mobile highway maintenance such as striping the roadway, median, and roadside grass mowing/landscaping, and pothole repair.
- Short-term stationary utility work such as repairing electric, gas, or water lines within the trafficway.
Exclusions:- Private construction, maintenance, or utility work outside the trafficway.
*The AASHTO term equivalent to roadway is traveled way.*The AASHTO term equivalent to trafficway is highway, street, or road.
Source: https://www.fhwa.dot.gov/publications/publicroads/99mayjun/workzone.cfm
detour
Source: https://mutcd.fhwa.dot.gov/htm/2009/part6/part6c.htm
restriction
closure
ClosureRoadEvent
Adding a
closure
EventType creates a ClosureRoadEvent Object. The ClosureRoadEvent is modeled after the RestrictionRoadEvent Object but with two additional properties. Thevehicle_impact
enumeration is added (see issue 264 ) to describe the event's affect.event_cause
is added (see Issue 269 to inform drivers why an event occurred.The
event_cause
property emulates the cause element found in the eventDescription property described in section 3.3.8.14 of the Transportation Management Data Dictionary 3.1 (TMDD). Theevent_cause
property will be populated using the Disasters (issue 276), Special Events (issue 277), and Winds issue coming enumerations described in sections 3.6.5.8, 3.6.5.23, 3.6.5.37 respectively.An example:
ClosureRoadEvent Object
The
ClosureRoadEvent
object is a linear road event that locates and describes roadways that may not be used.The
ClosureRoadEvent
is a type of road event; it has acore_details
property which contains the RoadEventCoreDetails and exists within a RoadEventFeature.For representing closures due to road work, see the WorkZoneRoadEvent.
Properties
core_details
restrictions
lanes
property is not provided.lanes
restrictions
property is not provided.vehicle_impact
event_cause
Winds Type,
Special Events Type
Used By
properties
The text was updated successfully, but these errors were encountered: