FAQ SIRI: Difference between revisions
(Siri SX question) |
|||
| Line 16: | Line 16: | ||
the "informed_entity" of GTFS-RT a priori concerns PublishingActions in SIRI which via PublishAtScope->Affects->StopPoints makes it possible to point as well the stops concerned (with the possibility of specifying the Quay number, see StopPointType). | the "informed_entity" of GTFS-RT a priori concerns PublishingActions in SIRI which via PublishAtScope->Affects->StopPoints makes it possible to point as well the stops concerned (with the possibility of specifying the Quay number, see StopPointType). | ||
The PublishingActions are described in SIRI Situation Exchange (Part 5 - CEN/TS 15531-5:2022) and is also included in the EU profile. | |||
Revision as of 11:03, 3 November 2023
How to best model the logic "AND" of GTFS- RT in SIRI SX (Situation Exchange)?
SIRI technical standard offers to also have publications of diversified information (with the possibility of having variants depending on the communication channels and also their location), in addition to allowing the management of multiple consequences. For example when referring to a line, we do not inform the same way upstream and downstream of the disturbance.
In the following example of GTFS'RT message,
"informed_entity": [ { "route_id": "13", "stop_id": "quay11" }, { "route_id": "13", "stop_id": "quay12" } ], where for route 13 and 2 platforms 11 and 12 are impacted,
the "informed_entity" of GTFS-RT a priori concerns PublishingActions in SIRI which via PublishAtScope->Affects->StopPoints makes it possible to point as well the stops concerned (with the possibility of specifying the Quay number, see StopPointType).
The PublishingActions are described in SIRI Situation Exchange (Part 5 - CEN/TS 15531-5:2022) and is also included in the EU profile.