Starting with one of the next feeds (probably September or later), we are planning some new features in GTFS RT Service Alerts.
Separate feeds
In order to better meet the needs of our users and to reduce the volume of data, we will introduce four separate feeds for the event data:
| Feed | Category (Planned) | Perspective
(Perspective) | Type
(Progress) |
|---|---|---|---|
| Feed 1 | planned | Timetable information (whileplanningtrip) | Main messages (published) |
| Feed 2 | unplanned | Timetable information (whileplanningtrip) | Main messages (published) |
| Feed 3 | planned | Stop display (atStopPoint) | Main & final messages (published|closing) |
| Feed 4 | unplanned | Stop display (atStopPoint) | Main & final messages (published|closing) |
An event is published as soon as it is available, i.e. regardless of whether it is already active (StartTime is in the future).
Replacement of active_period by impact_period and communication_period
At the same time, we plan to: active_period by impact_period and communication_period to clarify the temporal reference of reports:
communication_period
In this time interval, the message is visible. The values correspond to the SIRI-SX structure PublicationWindow.
communication_period we only use the Perspective stop display board (atStopPoint) and is used to control the publication. The data producer can, for example, define that an event should be displayed at the stop before the start of the event.
impact_period
Within this time interval the reported event is active. The values correspond to the SIRI-SX structure ValidityPeriod.
informedEntity: Trip-related messages restricted to specific stops
Trip-related messages can now be set to Stops (stop_id) can be limited. This can be specified in the field informedEntity as in the following example:
"informedEntity": [
{
"agencyId": "11",
"stopId": "ch:1:sloid:3000",
"trip": {
"tripId": "115.TA.91-2G-Y-j26-1.28.R",
"startTime": "19:32:00",
"startDate": "20250310",
"originalTripId": "ch:1:sjyid:100001:719-001"
},
},
{
"agencyId": "11",
"stopId": "8102336",
"trip": {
"tripId": "115.TA.91-2G-Y-j26-1.28.R",
"startTime": "19:32:00",
"startDate": "20250310",
"originalTripId": "ch:1:sjyid:100001:719-001"
}
}
]informedEntity: stopId now matches the GTFS stopId of the stop
The field is now stopId within informedEntity with the stopId the stop (according to GTFS static) instead of with the SLOID of the stop. In the field originalStopId the SLOID of the stop is also provided.
For a line or journey reference, the stopId or originalStopId the stops used.
URLs are no longer output
The URLs in the field url will no longer be output. The URLs will continue to be output as part of the descriptionText.
Priority
The priority of messages is represented by the order in JSON. Messages with a higher priority appear further up the list.
Priority is determined on the basis of the following criteria:
| Rank | Criterion | Description |
|---|---|---|
| 1 | Priority from source system | Priority or ActionPriority from SIRI-SX (ActionPriority has priority) |
| 2 | Status (‘Progress’ in the source system) | Published before closing |
| 3 | Start date (impact_period or communication_period) | Smallest ‘start’ value from impact_period or communication_period |