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.

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

Jump to bottom

Clarification of CANCELED/SKIPPED TripUpdates VS NO_SERVICE Alerts #482

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Clarification of CANCELED/SKIPPED TripUpdates VS NO_SERVICE Alerts #482

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ed58312
Add new statements for Alerts
isabelle-dr Jul 11, 2024
baec1c5
Specify that only Alerts with effect: no_service can affect trip plan…
isabelle-dr Jul 17, 2024
f3cffab
Include all new statements under the no service effect
isabelle-dr Jul 17, 2024
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
7 changes: 3 additions & 4 deletions gtfs-realtime/spec/en/service-alerts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Service alerts allow you to provide updates whenever there is disruption on the network. Delays and cancellations of individual trips should usually be communicated using [Trip updates](trip-updates.md).
Service alerts allow you to provide updates whenever there is disruption on the network. Delays and cancellations of individual trips should usually be communicated using [Trip updates](trip-updates.md).

You have the option to provide the following:

Expand All @@ -22,7 +22,7 @@ Entities are selected using their GTFS identifiers, and you can select any of th
* Route - affects the whole route
* Route type - affects any route of this type. e.g. all subways.
* Trip - affects a particular trip
* Stop - affects a particular stop
* Stop - affects a particular stop.

You may include more than one of the fields listed above in one `informed_entity`. When multiple fields are included in one `informed_entity`, they should be interpreted as being joined by the `AND` logical operator. In other words, the alert should only be applied in a context that meets all of the fields provided in an `informed_entity`. For example, if `route_id: "1"` and `stop_id: "5"` are both included in one `informed_entity`, then the alert should apply only to route 1 at stop 5. It should NOT be applied to any other stop on route 1, and it should NOT be applied to any other route at stop 5.

Expand All @@ -48,8 +48,7 @@ What is the cause of this alert? You may specify one of the following:
## Effect

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

* No service
* No service: If an Alert with Effect No service exists and the change is not reflected in [Trip updates](trip-updates.md), Alerts should be considered the source of truth. Alerts with Effect No service can be used by consumers to modify trip planner behavior. If a stop is out of service and it affects many trips, use Alerts instead of providing TripUpdates for all trips with the skipped stop time.
* Reduced service
* Significant delays (insignificant delays should only be provided through [Trip updates](trip-updates.md)).
* Detour
Expand Down
Loading