Contents
Documentation
Alerts
Last updated
Transitland enriches static schedule data with real-time alerts. Alerts are read from GTFS Realtime service alerts feeds. Alert entities that appear inside a trip updates feed are not used.
See also GTFS Realtime feed fetching and caching.
Each alert lists the entities it applies to in its informed_entity selectors. The Transitland v2 REST API matches those selectors to the most appropriate endpoint:
| Endpoint | Alerts included |
|---|---|
| Agencies and operators | Alerts for the agency as a whole, or for all routes of one route_type |
| Routes | Alerts for the route, the route at a specific stop, the route's route_type, or one of the route's trips |
| Stops | Alerts for the stop that do not name a specific trip |
| Trips | Alerts for that specific trip |
All of the above endpoints, and the departures endpoint, take the include_alerts query parameter to turn on or off the inclusion of alerts in the API response.
The GraphQL API provides an alerts field on agencies, routes, stops, and trips, with arguments to limit results to currently active alerts.