Difference between revisions of "SIRI"
(14 intermediate revisions by 4 users not shown) | |||
Line 14: | Line 14: | ||
To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://www.vdv.de/siri.aspx VdV page]. | To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://www.vdv.de/siri.aspx VdV page]. | ||
− | == SIRI National and EU minimum profiles == | + | == SIRI National and EU minimum profiles inventory == |
− | + | National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [[NeTEX#Profiles inventory|NeTEx Profiles Inventory]]. | |
{| class="wikitable sortable zebra" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "" | {| class="wikitable sortable zebra" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "" | ||
|- style="font-weight:bold;" | |- style="font-weight:bold;" | ||
− | ! colspan="2" style="text-align: | + | ! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" | SIRI Profiles |
− | ! Austria | + | ! style="width: 80px;" | Full SIRI format |
− | ! Croatia | + | ! style="width: 80px;" | EU SIRI<br>Minimum profile |
− | ! Czech Republic | + | ! style="width: 80px;" | Austria |
− | ! Denmark | + | ! style="width: 80px;" | Croatia |
− | ! France | + | ! style="width: 80px;" | Czech Republic |
− | ! Italy | + | ! style="width: 80px;" | Denmark |
− | ! Netherlands | + | ! style="width: 80px;" | France |
− | ! Nordic | + | ! style="width: 80px;" | Italy |
− | ! Portugal | + | ! style="width: 80px;" | Netherlands |
− | ! Slovenija | + | ! style="width: 80px;" | Nordic<br><small><small>Norway, Sweden, Finland, Denmark(?)</small></small> |
− | ! Switzerland | + | ! style="width: 80px;" | Portugal |
− | ! UK | + | ! style="width: 80px;" | Slovenija |
− | ! Irish | + | ! style="width: 80px;" | Switzerland |
− | ! German - VDV | + | ! style="width: 80px;" | UK |
+ | ! style="width: 80px;" | Irish | ||
+ | ! style="width: 80px;" | German - VDV | ||
|- | |- | ||
| colspan="2" | Availability of SIRI national profile | | colspan="2" | Availability of SIRI national profile | ||
− | | in | + | ! |
+ | ! under development | ||
+ | | in progress | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |In use in numerous cities and regions |
− | | in | + | | in progress |
| specified but not yet in operation | | specified but not yet in operation | ||
| Specified and in use | | Specified and in use | ||
| | | | ||
| | | | ||
− | | in | + | | in progress |
| Specified and in use | | Specified and in use | ||
| | | | ||
| | | | ||
|- | |- | ||
− | | colspan="2" | EU Minimum SIRI profile based | + | | colspan="2" | EU Minimum SIRI profile based<br>(applicable when EU SIRI minimum profile available) |
− | | | + | ! |
+ | ! | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | | |
| | | | ||
| | | | ||
Line 63: | Line 69: | ||
| | | | ||
| | | | ||
− | | | + | | |
| | | | ||
| | | | ||
|- | |- | ||
− | | colspan="2" | EU Minimum SIRI profile compatible | + | | colspan="2" | EU Minimum SIRI profile compatible<br>(applicable when EU SIRI minimum profile available) |
+ | ! | ||
+ | ! | ||
| | | | ||
| | | | ||
Line 83: | Line 91: | ||
| | | | ||
|- | |- | ||
− | | colspan="2" | Available mappings with full SIRI | + | | colspan="2" | Available mappings with full SIRI format |
+ | ! | ||
+ | ! | ||
| | | | ||
| | | | ||
Line 100: | Line 110: | ||
|- | |- | ||
| colspan="2" | Available mappings with EU Minimum SIRI profile | | colspan="2" | Available mappings with EU Minimum SIRI profile | ||
+ | ! | ||
+ | ! | ||
| | | | ||
| | | | ||
Line 115: | Line 127: | ||
| | | | ||
|- | |- | ||
− | + | ! colspan="2" | '''Functional scope based on MMTIS EU Regulation 1926/2017''' | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
+ | ! | ||
+ | ! | ||
|- | |- | ||
| style="font-weight:bold; background-color:#efefef;" | LOS 1 | | style="font-weight:bold; background-color:#efefef;" | LOS 1 | ||
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 1 | | style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 1 | ||
− | + | ! | |
− | + | ! | |
− | + | ! SIRI implementation in development by PTA | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! specified but not yet in operation | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
+ | ! | ||
+ | ! | ||
|- | |- | ||
| LOS 1-1 | | LOS 1-1 | ||
| Disruptions (all modes) | | Disruptions (all modes) | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
|[[File:compliant.png|15px|link=]] | |[[File:compliant.png|15px|link=]] | ||
Line 167: | Line 185: | ||
| LOS 1-2 | | LOS 1-2 | ||
| Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes) | | Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes) | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
|[[File:compliant.png|15px|link=]] | |[[File:compliant.png|15px|link=]] | ||
Line 184: | Line 204: | ||
| LOS 1-3 | | LOS 1-3 | ||
| Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes) | | Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes) | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
|[[File:compliant.png|15px|link=]] | |[[File:compliant.png|15px|link=]] | ||
Line 201: | Line 223: | ||
| style="font-weight:bold; background-color:#efefef;" | LOS 2 | | style="font-weight:bold; background-color:#efefef;" | LOS 2 | ||
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 2 | | style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 2 | ||
− | + | ! | |
− | + | ! | |
− | + | ! SIRI implementation in development by PTA | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
+ | ! | ||
+ | ! | ||
|- | |- | ||
| LOS 2-1 | | LOS 2-1 | ||
| Estimated departure and arrival times of services | | Estimated departure and arrival times of services | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
|[[File:compliant.png|15px|link=]] | |[[File:compliant.png|15px|link=]] | ||
Line 235: | Line 261: | ||
| LOS 2-2 | | LOS 2-2 | ||
| Current road link travel times | | Current road link travel times | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
Line 252: | Line 280: | ||
| LOS 2-3 | | LOS 2-3 | ||
| Cycling network closures/diversions | | Cycling network closures/diversions | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
Line 269: | Line 299: | ||
| LOS 2-4 | | LOS 2-4 | ||
| Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles | | Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
Line 286: | Line 318: | ||
| LOS 2-5 | | LOS 2-5 | ||
| Car-sharing availability, bike sharing availability | | Car-sharing availability, bike sharing availability | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
| | | | ||
Line 303: | Line 337: | ||
| LOS 2-6 | | LOS 2-6 | ||
| Car parking spaces available (on and off-street), parking tariffs, road toll tariffs | | Car parking spaces available (on and off-street), parking tariffs, road toll tariffs | ||
+ | |[[File:compliant.png|15px|link=]] | ||
+ | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
− | | | + | |[[File:compliant.png|15px|link=]] |
| | | | ||
| | | | ||
Line 320: | Line 356: | ||
| style="font-weight:bold; background-color:#efefef;" | LOS 3 | | style="font-weight:bold; background-color:#efefef;" | LOS 3 | ||
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 3 | | style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 3 | ||
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ![[File:compliant.png|15px|link=]] | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
− | + | ! | |
+ | ! | ||
+ | ! | ||
|} | |} | ||
Line 397: | Line 435: | ||
| | | | ||
|https://qommute.com | |https://qommute.com | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | ==Validators== | ||
+ | {| class="wikitable" | ||
+ | !colspan="1"|Name | ||
+ | !colspan="1"|Availability | ||
+ | !colspan="1"|Description | ||
+ | !colspan="1"|Profile | ||
+ | !colspan="1"|License | ||
+ | !colspan="1"|URL | ||
+ | |- | ||
+ | !style="text-align:left;" rowspan="1"|[[BODS]] | ||
+ | |Available | ||
+ | |Validator of TransXChange and SIRI-VM | ||
+ | | | ||
+ | |Open Source | ||
+ | |https://github.com/department-for-transport-BODS/bods | ||
|- | |- | ||
|} | |} | ||
Line 460: | Line 516: | ||
|- | |- | ||
|} | |} | ||
+ | |||
+ | = SIRI extension for New Modes = | ||
+ | In line with NeTEx Part 5, corresponding extensions are made in SIRI for real time data such as current number of available vehicles, current number of spaces available to bring back a vehicle or to park, etc. SIRI also provide updates of positions (typically for free floating vehicles). The SIRI Facility Monitoring (FM) service is extended to provide this counted information. Further details are available in the relevant [https://www.netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf document]. | ||
+ | |||
+ | == Mapping with GBFS for real time information == | ||
+ | In the framework of the CEN work for the extension, a canonical mapping was made between NeTEx Part 5 /SIRI and GBFS. It is available ''' [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]]'''. |
Revision as of 18:55, 16 March 2022
SIRI overview
SIRI was established as European standard in October 2006. It is a CEN (Comité Européen de Normalisation) and Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.
SIRI allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with general informational messages related to the operation of the services. The information can be used for many different purposes, for example:
- To provide real time-departure from stop information for display on stops, internet and mobile delivery systems;
- To provide real-time progress information about individual vehicles;
- To manage the movement of buses roaming between areas covered by different servers;
- To manage the synchronisation of guaranteed connections between fetcher and feeder services;
- To exchange planned and real-time timetable updates;
- To distribute status messages about the operation of the services;
- To provide performance information to operational history and other management systems.
To find out more about the SIRI data model, please visit the Transmodel page and VdV page.
SIRI National and EU minimum profiles inventory
National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the NeTEx Profiles Inventory.
SIRI Profiles | Full SIRI format | EU SIRI Minimum profile |
Austria | Croatia | Czech Republic | Denmark | France | Italy | Netherlands | Nordic Norway, Sweden, Finland, Denmark(?) |
Portugal | Slovenija | Switzerland | UK | Irish | German - VDV | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Availability of SIRI national profile | under development | in progress | In use in numerous cities and regions | in progress | specified but not yet in operation | Specified and in use | in progress | Specified and in use | |||||||||
EU Minimum SIRI profile based (applicable when EU SIRI minimum profile available) |
|||||||||||||||||
EU Minimum SIRI profile compatible (applicable when EU SIRI minimum profile available) |
? | ||||||||||||||||
Available mappings with full SIRI format | |||||||||||||||||
Available mappings with EU Minimum SIRI profile | |||||||||||||||||
Functional scope based on MMTIS EU Regulation 1926/2017 | |||||||||||||||||
LOS 1 | Dynamic travel and traffic data - Level of service 1 | SIRI implementation in development by PTA | specified but not yet in operation | ||||||||||||||
LOS 1-1 | Disruptions (all modes) | dynamic platform is included |
Bus locations for about 800 vehicles included in the integrated public passenger transport system. | ||||||||||||||
LOS 1-2 | Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes) | dynamic platform is included |
|||||||||||||||
LOS 1-3 | Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes) | dynamic platform is included |
|||||||||||||||
LOS 2 | Dynamic travel and traffic data - Level of service 2 | SIRI implementation in development by PTA | |||||||||||||||
LOS 2-1 | Estimated departure and arrival times of services | ||||||||||||||||
LOS 2-2 | Current road link travel times | ||||||||||||||||
LOS 2-3 | Cycling network closures/diversions | ||||||||||||||||
LOS 2-4 | Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles | ||||||||||||||||
LOS 2-5 | Car-sharing availability, bike sharing availability | ||||||||||||||||
LOS 2-6 | Car parking spaces available (on and off-street), parking tariffs, road toll tariffs | ||||||||||||||||
LOS 3 | Dynamic travel and traffic data - Level of service 3 |
SIRI software
The following list of software is known to support NeTEx. We distinguish between different categories that may later receive a list of key performance indicators.
Conversion and connectors to SIRI software and between other formats
Name | Availability | Description | Profile | License | URL |
---|---|---|---|---|---|
Anshar | Available | Java based tool to connect, validate and redistribute SIRI. (Act as a national aggreagation hub for all SIRI feeds in Norway) | Norwegian | EUPL | https://github.com/entur/anshar |
OneBusAway SIRI | Available | A set of tools to connect to and convert SIRI. | Apache-2.0 | https://github.com/OneBusAway/onebusaway-siri | |
ara | Available | A set of tools to connect, convert and store SIRI, SIRI-Lite. | Apache-2.0 | https://bitbucket.org/enroute-mobi/ara/src/master/ | |
irys | Available | A set of tools to connect and redistribute SIRI. | CeCILL-B | https://github.com/afimb/irys | |
Diginext/CS-Group | Available | https://mobilitx.diginext.fr/ | |||
Soridis/Lumiplan | Available | https://www.lumiplan.com/produit/mobiflux/ | |||
Qommute | Available | https://qommute.com |
Validators
Name | Availability | Description | Profile | License | URL |
---|---|---|---|---|---|
BODS | Available | Validator of TransXChange and SIRI-VM | Open Source | https://github.com/department-for-transport-BODS/bods |
Producers from CAD/AVL
Name | Availability | Description | Profile | License | URL |
---|---|---|---|---|---|
IVU.realtime | Available | Producer of realtime data. | Commercial | https://www.ivu.com/products-and-solutions/ivusuite/passenger-information.html | |
Mobile-ITCS | Available | Producer of realtime data. | Commercial | https://www.initse.com/fileadmin/user_upload/Content/3_Solutions/3_Operations/MOBILE-ITCS_us.pdf | |
INEO | Available | ||||
Navocap | Available | ||||
ZenBus | Available | Producer of realtime data. | Commercial | https://zenbus.fr/ | |
IXXI/RATP Smart System | Available | Producer of realtime data. | Commercial | https://www.ratpsmartsystems.com/hopen-go/ | |
Alstom | Available | Producer of realtime data. | Commercial |
SIRI extension for New Modes
In line with NeTEx Part 5, corresponding extensions are made in SIRI for real time data such as current number of available vehicles, current number of spaces available to bring back a vehicle or to park, etc. SIRI also provide updates of positions (typically for free floating vehicles). The SIRI Facility Monitoring (FM) service is extended to provide this counted information. Further details are available in the relevant document.
Mapping with GBFS for real time information
In the framework of the CEN work for the extension, a canonical mapping was made between NeTEx Part 5 /SIRI and GBFS. It is available here.