Difference between revisions of "SIRI"

From DATA4PT WIKI
Jump to navigation Jump to search
 
Line 43: Line 43:
 
ℹ️ To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://siri-cen.eu/ SIRI page].
 
ℹ️ To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://siri-cen.eu/ SIRI 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 https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].
 
−
== SIRI national profile ==
 
−
 
−
{| class="wikitable" style="width : 50%"
 
−
|-
 
−
! Profile Name !! Availability
 
−
!EU Minimum profile based*!! EU Minimum SIRI profile compatible** !! Documentation
 
−
|-
 
−
| Nordic (Norway, Sweden, Finland, Denmark) ||  Specified and in use
 
−
| || style="text-align:center;" | ✅ || [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
 
−
|-
 
−
| UK (GB) || Specified and in use
 
−
| || style="text-align:center;" | ✅ ||
 
−
|-
 
−
| France (FR) ||In use in numerous cities and regions
 
−
| || style="text-align:center;" | ✅ ||
 
−
|-
 
−
| Netherlands (NL) || Specified but not yet in operation
 
−
| || style="text-align:center;" | ✅ ||
 
−
|-
 
−
|Italy (IT)
 
−
|Specified and currently in use by Piedmont Region and Bolzano Province. More regions by the end of 2024
 
−
|✅
 
−
|
 
−
|[https://www.siri-cen.eu/Page.aspx?CAT=STANDARD&IdPage=12114713-483f-49e5-9cf1-1c6101a0808a Italian SIRI profile]
 
−
|-
 
−
|}
 
−
<nowiki>*</nowiki>Profiles of this category have been specified after the specification of the EU Minimum profile and are based on it.
 
−
 
−
<nowiki>**</nowiki> Profiles of this category are specified before the specification of the EU Minimum profile and they have been formed the basis for the EU Minimum profile definition.
 
−
 
−
== Data categories ==
 
−
 
−
''Data categories are identified based on [https://eur-lex.europa.eu/eli/reg_del/2017/1926/oj MMTIS EU Regulation 1926/2017]''
 
−
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
 
−
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
 
−
|-
 
−
! Level of service (LOS)  !! Types of the dynamic travel and traffic data
 
−
|-
 
−
| colspan="2" style="text-align:center |'''Dynamic data - Level of service 1 (LOS 1 )'''
 
−
|-
 
−
| LOS 1-1 || Disruptions (all modes)
 
−
|-
 
−
| LOS 1-2 || Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes)
 
−
|-
 
−
| LOS 1-3 || Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes)
 
−
|-
 
−
| colspan="2" style="text-align:center |'''Dynamic data - Level of service 2 (LOS 2)'''
 
−
|-
 
−
| 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
 
−
|-
 
−
| colspan="2" style="text-align:center |'''Dynamic data - Level of service 3 (LOS 3''')
 
−
|-
 
−
|
 
−
|Future predicted road link travel times
 
−
|-
 
−
|}
 
−
 
−
== Dynamic data - Level of service 1 (LOS 1) ==
 
−
 
−
{| class="wikitable" style="width : 30%"
 
−
|-
 
−
! Data Categories 
 
−
! width="80px"|FR
 
−
! width="80px"|NL
 
−
! width="300px" | Nordic (SE, NOR, DK, FIN)
 
−
! width="80px"|GB
 
−
|-
 
−
| [[#Data categories|LOS 1-1]] ||style="text-align:center |✅ || style="text-align:center |✅  || style="text-align:center | ✅ <br>dynamic platform is included  || style="text-align:center | ✅   
 
−
|-
 
−
|[[#Data categories|LOS 1-2]]  ||style="text-align:center |✅ || style="text-align:center |✅  || style="text-align:center | ✅ <br>dynamic platform is included  || style="text-align:center | ✅   
 
−
|-
 
−
|[[#Data categories|LOS 1-3]]  ||style="text-align:center |✅ || style="text-align:center |✅  || style="text-align:center | ✅ <br>dynamic platform is included  || style="text-align:center |     
 
−
|-
 
−
|}
 
−
 
−
== Dynamic data - Level of service 2 (LOS 2) ==
 
−
 
−
{| class="wikitable" style="width : 30%"
 
−
|-
 
−
! Data Categories 
 
−
! width="80px"|FR
 
−
! width="80px"|NL
 
−
! width="300px" | Nordic (SE, NOR, DK, FIN)
 
−
! width="80px"|GB
 
−
|-
 
−
|[[#Data categories|LOS 2-1]] ||style="text-align:center |✅ || style="text-align:center |✅  || style="text-align:center | ✅  || style="text-align:center | ✅     
 
−
|-
 
−
|[[#Data categories|LOS 2-2]] || || || style="text-align:center | ✅  ||     
 
−
|-
 
−
|[[#Data categories|LOS 2-3]]|| || || ||
 
−
|-
 
−
|[[#Data categories|LOS 2-4]]|| || ||  || 
 
−
|-
 
−
|[[#Data categories|LOS 2-5]]||  style="text-align:center |✅  || || style="text-align:center | ✅ ||
 
−
|-
 
−
|[[#Data categories|LOS 2-6]]||  style="text-align:center |✅  || || style="text-align:center | ✅ || 
 
−
|-
 
−
|}
 
−
 
−
== Dynamic data - Level of service 3 (LOS 3) ==
 
−
 
−
{| class="wikitable" style="width : 30%"
 
−
|-
 
−
! Data Categories 
 
−
! width="80px"|FR
 
−
! width="80px"|NL
 
−
! width="300px" | Nordic (SE, NOR, DK, FIN)
 
−
! width="80px"|GB
 
−
|-
 
−
|}
 
−
 
−
⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution'''and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.
 
−
 
−
📄 You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].
 
  
 
= Software & tools 🧰 =
 
= Software & tools 🧰 =

Latest revision as of 15:21, 29 March 2024

SIRI overview 🔍

What is SIRI?

SIRI is a European standard that enables real-time information about public transportation to be shared between different computer systems. It is used by many different organizations, including public transportation operators, traffic management agencies, and travel information providers.

SIRI was established as European standard in October 2006. It is a CEN (Comité Européen de Normalisation) and Technical Standard

SIRI formats

SIRI is a protocol for data exchange between two IT systems for real-time information. Data can be exchanged via:

  • XML files (over TCP/IP or via SOAP/WSDL)
  • REST/JSON (over HTTP) using SIRI-Lite interface

Note: SIRI-Lite is a subset of SIRI focusing on the most frequently requested information for open data feeds.

What can SIRI be used for?

SIRI can be used for a variety of purposes, such as:

  • Providing real-time arrival information at bus stops and train stations
  • Tracking the progress of individual vehicles
  • Managing the movement of buses between different areas
  • Synchronizing connections between different services
  • Exchanging planned and real-time timetable updates
  • Distributing status messages about the operation of services
  • Providing performance information to operational history and other management systems

Benefits of SIRI

SIRI has made a significant contribution to improving the efficiency and reliability of public transportation across Europe. It is now used by millions of people every day to plan their journeys and get real-time information about the services they are using.

For example, SIRI can help you to:

  • Avoid missing a bus or train
  • Plan your journey more efficiently
  • Get real-time information about disruptions to services
  • Find the best way to travel between different locations


ℹ️ To find out more about the SIRI data model, please visit the Transmodel page and SIRI page.


Software & tools 🧰

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.

XML tools

General purpose XML tools can be used to work with the SIRI XML schema and XML documents that conform to it.

XML tools Description
XML SPY commercial
Oxygen commercial
List of tools open-source

Conversion and connectors tools

Name Availability Description Profile License
Anshar ✅ Java based tool to connect, validate and redistribute SIRI. (Act as a national aggreagation hub for all SIRI feeds in Norway) Norwegian EUPL
OneBusAway SIRI ✅ A set of tools to connect to and convert SIRI. Apache-2.0
ara ✅ A set of tools to connect, convert and store SIRI, SIRI-Lite. Apache-2.0
irys ✅ A set of tools to connect and redistribute SIRI. CeCILL-B
Diginext/CS-Group ✅
Soridis/Lumiplan ✅
Qommute ✅

Data validation tools

Name Availability Description Profile License
BODS ✅ Validator of TransXChange and SIRI-VM All Open Source

Producers from CAD/AVL

Name Availability Description Profile License
IVU.realtime ✅ Producer of realtime data. Commercial
Mobile-ITCS ✅ Producer of realtime data. Commercial
INEO ✅
Navocap ✅
ZenBus ✅ Producer of realtime data. Commercial
IXXI/RATP Smart System ✅ Producer of realtime data. Commercial
Alstom ✅ Producer of realtime data. Commercial

SIRI extension for 🆕 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

Description
NeTEx extension for New Modes Scope and overview
Canonical mapping with GBFS The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.

References

Name Description
SIRI-CEN GitHub Find xsd, examples and relevant documentation on SIRI schema
Transmodel website European data model for public transport information
SIRI website Official SIRI website
Retrieved from "https://data4pt.org/w/index.php?title=SIRI&oldid=492"