From ed5831218689b96bb16b3b823ffc7263ad0d00ea Mon Sep 17 00:00:00 2001 From: isabelle-dr Date: Thu, 11 Jul 2024 12:06:22 +0200 Subject: [PATCH 1/3] Add new statements for Alerts --- gtfs-realtime/spec/en/service-alerts.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/gtfs-realtime/spec/en/service-alerts.md b/gtfs-realtime/spec/en/service-alerts.md index 261afd977..f6270f372 100644 --- a/gtfs-realtime/spec/en/service-alerts.md +++ b/gtfs-realtime/spec/en/service-alerts.md @@ -1,4 +1,6 @@ -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). +Alerts should be used for notifying that a stop will be out of service for extended periods. +Alerts can be used by consumers to modify trip planner behavior. You have the option to provide the following: @@ -22,7 +24,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. @@ -49,7 +51,7 @@ What is the cause of this alert? You may specify one of the following: 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 conflicts with values in [Trip updates](trip-updates.md), Alerts should be considered the source of truth. * Reduced service * Significant delays (insignificant delays should only be provided through [Trip updates](trip-updates.md)). * Detour From baec1c5f4303f2229f89b106828b11afc3ad90f2 Mon Sep 17 00:00:00 2001 From: isabelle-dr Date: Wed, 17 Jul 2024 20:05:33 +0200 Subject: [PATCH 2/3] Specify that only Alerts with effect: no_service can affect trip planner behaviour --- gtfs-realtime/spec/en/service-alerts.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gtfs-realtime/spec/en/service-alerts.md b/gtfs-realtime/spec/en/service-alerts.md index f6270f372..0304813f8 100644 --- a/gtfs-realtime/spec/en/service-alerts.md +++ b/gtfs-realtime/spec/en/service-alerts.md @@ -1,6 +1,5 @@ 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). Alerts should be used for notifying that a stop will be out of service for extended periods. -Alerts can be used by consumers to modify trip planner behavior. You have the option to provide the following: @@ -51,7 +50,7 @@ What is the cause of this alert? You may specify one of the following: What effect does this problem have on the specified entity? You may specify one of the following: -* No service: If an Alert with Effect No service exists and conflicts with values in [Trip updates](trip-updates.md), Alerts should be considered the source of truth. +* No service: If an Alert with Effect No service exists and conflicts with values 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. * Reduced service * Significant delays (insignificant delays should only be provided through [Trip updates](trip-updates.md)). * Detour From f3cffab1c79c26fad813fac9d5d1fc398b09e8cd Mon Sep 17 00:00:00 2001 From: isabelle-dr Date: Wed, 17 Jul 2024 21:28:12 +0200 Subject: [PATCH 3/3] Include all new statements under the no service effect --- gtfs-realtime/spec/en/service-alerts.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/gtfs-realtime/spec/en/service-alerts.md b/gtfs-realtime/spec/en/service-alerts.md index 0304813f8..9e8783f86 100644 --- a/gtfs-realtime/spec/en/service-alerts.md +++ b/gtfs-realtime/spec/en/service-alerts.md @@ -1,5 +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). -Alerts should be used for notifying that a stop will be out of service for extended periods. You have the option to provide the following: @@ -49,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: If an Alert with Effect No service exists and conflicts with values 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. +* 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