diff --git a/gtfs-realtime/spec/en/service-alerts.md b/gtfs-realtime/spec/en/service-alerts.md index 261afd97..9e8783f8 100644 --- a/gtfs-realtime/spec/en/service-alerts.md +++ b/gtfs-realtime/spec/en/service-alerts.md @@ -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: @@ -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. @@ -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