Switzerland: Difference between revisions
(Creation of switzerland page) |
m (Admin moved page Draft:Switzerland to Switzerland) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 5: | Line 5: | ||
Via these two channels, Switzerland provides the following data standards for Switzerland: | Via these two channels, Switzerland provides the following data standards for Switzerland: | ||
{| class="wikitable" style="width: 50%;" | |||
|- | |||
| style="text-align: center;" | Timetables | |||
| [https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf NeTEx – Swiss Profile] | |||
[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS – Swiss Profile] | |||
[https://www.oev-info.ch/sites/default/files/2023-07/hrdf_2_0_5_e.pdf HRDF – Swiss Profile] | |||
|- | |||
| style="text-align: center;" | On demand | |||
| [https://www.oev-info.ch/sites/default/files/2024-07/Fachkonzept%20On-Demand_v2.1_en.pdf NeTEx] | |||
== | [https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Flex] | ||
|- | |||
| style="text-align: center;" | Realtime data | |||
| [https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT – Swiss Profile] | |||
[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Realtime – Swiss Profile] | |||
|- | |||
| style="text-align: center;" | Events | |||
| [https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX – Swiss Profile] | |||
[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Service Alerts] | |||
|- | |||
| style="text-align: center;" | Routing | |||
| OJP 1.0 – Swiss Profile ([https://www.oev-info.ch/sites/default/files/2023-05/open_journey_planner_ojp_de_v1_eng.pdf Documentation], [https://opentransportdata.swiss/de/dataset/ojp2020 API]) | |||
OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/de/dataset/ojp2-0 API]) | |||
|- | |||
| style="text-align: center;" | Fares | |||
| OJP-Fare – Swiss Profile ([https://opentransportdata.swiss/en/cookbook/beta-price-information-with-ojp-fares-2/ Documentation], [https://opentransportdata.swiss/de/dataset/ojpfare API]) | |||
|} | |||
== Use cases == | |||
=== Description === | === Description === | ||
Latest revision as of 13:56, 8 October 2024
Overview in the National Level
In Switzerland the Federal Office of Transportation (FOT) was tasked with the realization of the National Access Point (NAP) for Switzerland, called the “Open data platform mobility Switzerland” (ODMCH). Additionally, a national open non-discriminatory trip planner has been made available named after its interface standard “Open Journey Planner” (OJP-System). A demo is available here.
It is important to note, that the presented data covers primarily conventional public transport of all of Switzerland. The goal is to extend to other forms of transport, too. All street related data is handled by the Federal Roads Office in Switzerland (FEDRO), while all geographical and topological information is gathered by the Federal Office of Topography (swisstopo). Here we focus on the FOT related data.
Via these two channels, Switzerland provides the following data standards for Switzerland:
| Timetables | NeTEx – Swiss Profile |
| On demand | NeTEx |
| Realtime data | SIRI-ET/PT – Swiss Profile |
| Events | SIRI-SX – Swiss Profile |
| Routing | OJP 1.0 – Swiss Profile (Documentation, API)
OJP 2.0 – Swiss Profile (Documentation: Work In Progress, API) |
| Fares | OJP-Fare – Swiss Profile (Documentation, API) |
Use cases
Description
NeTEx is not used by (public) transport operators in Switzerland. The export is primarily used by the neighbouring countries and their larger transport operators (e.g., SNCF in France). The reason being its complexity (you need experts to understand and apply it) and multiplicity (substitution classes and similar constructs make simple adaptations difficult). Data exchange for timetables is mostly done by HRDF:
SIRI-SX is being actively used to represent disruptions, while SIRI-ET and -PT have only recently been introduced and are not widely adapted (currently VDV 454 and 453 are used mainly).
The GTFS standards are used most by small and medium-sized mobility providers.
The OJP standard is being increasingly adapted by transport operators, alongside the use of the routing service. With the recent introduction of OJP 2.0 we expect another increase.
Architecture
The following Figure provides an overview of the public transport data being centrally provided and processed for the various previously introduced data categories.
Short translation:
- Ereignisdaten = event data
- Echtzeitdaten = realtime data
- Fahrplandaten = timetable data
- Stammdaten = master data
- Datendrehscheibe = data exchange hub
Use cases
The provided data is used for all public transport customer information systems in Switzerland.
Furthermore, a set of showcases created with the ODMCH data can be found here:
Outcome
The easier the standards are to use and to adapt, the more they are accepted and used by transport operators and mobility service providers.