Skip to content

Add definitions to Cause and Effect values #78

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.

Sign up for GitHub

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

Draft
skalexch wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Add definitions to Cause and Effect values #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 27 additions & 24 deletions gtfs-realtime/spec/en/service-alerts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,32 +32,35 @@ If you would like to represent an alert that affects more than one entity (e.g.

What is the cause of this alert? You may specify one of the following:

* Unknown cause
* Other cause (not represented by any of these options)
* Technical problem
* Strike
* Demonstration
* Accident
* Holiday
* Weather
* Maintenance
* Construction
* Police activity
* Medical emergency
* Special Event
* **Unknown cause**: Used when the cause of the disruption is not known or has not been determined. Should be avoided if any more specific cause can be reasonably identified.
* **Other cause**: Used for causes that do not represented by any of predefined options.
* **Technical problem**: Issues related to vehicles or infrastructure malfunctioning. Examples include mechanical failure and information system bugs.
* **Strike**: Service disruptions caused by a labor strike involving the transit agency or operator.
* **Demonstration**: Service disruptions caused by public demonstration, protest, or gathering.
* **Accident**: Incidents such as collisions or derailments that disrupt services.
* **Holiday**: Any public holiday that might result in a change of service.
* **Weather**: Disruptions caused by weather conditions such as snow, storms, flooding, etc.
* **Maintenance**: Planned maintenance related to the services. Examples include track maintenance, elevator maintenance and vehicle maintenance.
* **Construction**: Any construction that affects the service, regardless whether it relates to the services or not. Examples include station construction and roadworks that affect bus routes.
* **Police activity**: Disruptions due to law enforcement activity or security incidents. Examples include investigations or security threats.
* **Medical emergency**: Incidents involving passenger or staff medical emergencies. Examples include an on-board medical problem that forces a train to stop.
* **Special Event**: A special one-time or recurring event such as a parade, festival, performance, farmers market, or sporting event.

## Effect

What effect does this problem have on the specified entity? You may specify one of the following:

* No service
* Reduced service
* Significant delays (insignificant delays should only be provided through [Trip updates](trip-updates.md)).
* Detour
* Additional service
* Modified service: Operations are different from what the rider would normally expect. An example is an alert that reminds riders of an upcoming holiday schedule that is different from normal service on that day of the week.
* Stop moved
* Other effect (not represented by any of these options)
* Unknown effect
* No effect: The alert provides information to riders but does not affect operations. Examples include advertising public meetings and soliciting feedback via surveys.
* Accessibility issue: The alert provides information about accessibility issues that affects step-free access. Examples include an out of service elevator or movable ramps.
* **No service**: No transit service to the specified entity(-ies).
* For stations or stops, the rider will not be able to board or alight.
* For routes, the route will not run.
* For trips, those specific trips are cancelled.
* **Reduced service**: The number or frequency of trips is reduced.
* **Significant delays**: The route will consistently run late (insignificant delays should only be provided through [Trip updates](trip-updates.md)).
* **Detour**: The route changes its shape, resulting in one or multiple stops being moved.
* **Additional service**: The number or frequency of trips is increased. For example, more buses are running to cover for a special event.
* **Modified service**: Operations are different from what the rider would normally expect. An example is an alert that reminds riders of an upcoming holiday schedule that is different from normal service on that day of the week.
* **Stop moved**: A stop location is changed temporarily or permanently (if known to be permanent, ensure the new location is reflected in the schedule data).
* **Other effect** (not represented by any of these options).
* **Unknown effect**: Used for alerts whose effect has not been identified yet. Do not use “Unknown effect” if the effect of the alert is known or can be deduced from the alert header or description.
* **No effect**: The alert provides information to riders but does not affect operations. Examples include advertising public meetings and soliciting feedback via surveys. Unless necessary, it is advised not to use this effect.
* **Accessibility issue**: The alert provides information about accessibility issues that affect step-free access. Examples include an out of service elevator or movable ramps, a bus that is unable to kneel, or an exceptional service with trains that have a big platform gap.
Loading