Switzerland - Revision history

Anasfou: /* Overview in the National Level */

2026-04-17T16:22:02Z

Overview in the National Level

← Older revision		Revision as of 18:22, 17 April 2026
Line 32:		Line 32:
	\| 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/en/cookbook/open-journey-planner-ojp/ API])		\| 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/en/cookbook/open-journey-planner-ojp/ API])

	OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp~~/ojpstopeventrequest-2-0~~/ API])		OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/ API])
	\|-		\|-
	\| style="text-align: center;" \| Fares		\| style="text-align: center;" \| Fares

Anasfou: /* Use cases */

2026-04-17T14:20:31Z

Use cases

← Older revision		Revision as of 16:20, 17 April 2026
Line 35:		Line 35:
	\|-		\|-
	\| style="text-align: center;" \| Fares		\| style="text-align: center;" \| Fares
	\| OJP-Fare – ~~Swiss Profile (Documentation,~~ [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/ojp-fare/ ~~API~~])		\| OJP-Fare – [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/ojp-fare/ Swiss Profile]
	\|}		\|}

Line 63:		Line 63:
	The provided data is used for all public transport customer information systems in Switzerland.		The provided data is used for all public transport customer information systems in Switzerland.

	Furthermore, a set of showcases created with the opentransportdata.swiss data can be found [https://opentransportdata.swiss/~~en/showcases-and-actual-data-archive-have-moved/~~ here]:		Furthermore, a set of showcases created with the opentransportdata.swiss data can be found [https://data.opentransportdata.swiss/showcase here]:

	=== Outcome ===		=== 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.		The easier the standards are to use and to adapt, the more they are accepted and used by transport operators and mobility service providers.

Anasfou: /* Overview in the National Level */

2026-04-16T17:04:30Z

Overview in the National Level

← Older revision		Revision as of 19:04, 16 April 2026
Line 1:		Line 1:
	== Overview in the National Level ==		== Overview in the National Level ==
	In Switzerland the [https://www.bav.admin.ch~~/bav~~/en/~~home.html~~ Federal Office of Transportation] (FOT) ~~was tasked with the realization of~~ the National Access Point (NAP) ~~for Switzerland,~~ called ~~the~~ “[https://opentransportdata.swiss/en/ ~~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 [https://opentdatach.github.io/ojp-demo-app/search here].		In Switzerland, the [https://www.bav.admin.ch/en/the-fot Federal Office of Transportation] (FOT) provides the Swiss National Access Point (NAP) called “[https://opentransportdata.swiss/en/ opentransportdata.swiss]”. 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 [https://opentdatach.github.io/ojp-demo-app/search 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 [https://www.astra.admin.ch/astra/en/home.html Federal Roads Office in Switzerland] (FEDRO), while all geographical and topological information is gathered by the Federal Office of Topography ([https://www.swisstopo.admin.ch/en swisstopo]). ~~Here~~ we focus on the FOT related data.		It is important to note that the published data covers primarily conventional public transport. The goal is to extend to other forms of transport, too. All road related data is handled by the [https://www.astra.admin.ch/astra/en/home.html Federal Roads Office in Switzerland] (FEDRO), while all geographical and topological information is gathered by the Federal Office of Topography ([https://www.swisstopo.admin.ch/en swisstopo]). On this page we focus on the FOT related data.

	Via ~~these two channels~~, Switzerland provides the following data standards for Switzerland:		Via [https://opentransportdata.swiss/en/ opentransportdata.swiss] and OJP, Switzerland provides the following data standards for Switzerland:
	{\| class="wikitable" style="width: 50%;"		{\| class="wikitable" style="width: 50%;"
	\|-		\|-
Line 22:		Line 22:
	\| [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/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]		[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		\| style="text-align: center;" \| Events
Line 30:		Line 30:
	\|-		\|-
	\| style="text-align: center;" \| Routing		\| 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 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/en/cookbook/open-journey-planner-ojp/ API])

	OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/de/~~dataset~~/~~ojp2~~-0 API])		OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/ojpstopeventrequest-2-0/ API])
	\|-		\|-
	\| style="text-align: center;" \| Fares		\| 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])		\| OJP-Fare – Swiss Profile (Documentation, [https://opentransportdata.swiss/en/cookbook/open-journey-planner-ojp/ojp-fare/ API])
	\|}		\|}

Line 41:		Line 41:

	=== Description ===		=== 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~~).		* NeTEx is not yet broadly used by Swiss (public) transport operators. The provided export is primarily used by the neighboring 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, mainly VDV 454 and 453 are used).
	The GTFS standards are used most by small and medium-sized mobility providers.		* The GTFS standards are used most by small and medium-sized mobility providers.
			* Alongside the use of the routing service, the OJP standard is being increasingly adapted by transport operators, especially with the introduction of OJP 2.0.
	~~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 ===		=== Architecture ===
	The following ~~Figure~~ provides an overview of the public transport data being centrally provided and processed for the various previously introduced data categories.		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:		Short translation:

	* Ereignisdaten = event data		* Ereignisdaten = event data
Line 63:		Line 61:

	=== Use cases ===		=== Use cases ===
	The provided data is used for all public transport customer information systems in Switzerland.		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 [https://opentransportdata.swiss/de/~~showcase~~-5/ here]:		Furthermore, a set of showcases created with the opentransportdata.swiss data can be found [https://opentransportdata.swiss/en/showcases-and-actual-data-archive-have-moved/ here]:

	=== Outcome ===		=== 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.		The easier the standards are to use and to adapt, the more they are accepted and used by transport operators and mobility service providers.

Admin: Admin moved page Draft:Switzerland to Switzerland

2024-10-08T12:56:34Z

Admin moved page Draft:Switzerland to Switzerland

← Older revision	Revision as of 14:56, 8 October 2024
(No difference)

Anonymous at 08:57, 2 October 2024

2024-10-02T08:57:47Z

@@ Line 5: / Line 5: @@
 Via these two channels, Switzerland provides the following data standards for Switzerland:
-* '''Timetables'''
+[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS – Swiss Profile]
-* '''On-demand'''
+[https://www.oev-info.ch/sites/default/files/2023-07/hrdf_2_0_5_e.pdf HRDF – Swiss Profile]
-** [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] (as above)
+| style="text-align: center;" | On demand
-* '''Realtime data'''
+| [https://www.oev-info.ch/sites/default/files/2024-07/Fachkonzept%20On-Demand_v2.1_en.pdf NeTEx]
-== Uses cases ==
+[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Flex]
 === Description ===

Anonymous: Creation of switzerland page

2024-10-02T08:48:21Z

Creation of switzerland page

New page

== Overview in the National Level ==
In Switzerland the [https://www.bav.admin.ch/bav/en/home.html Federal Office of Transportation] (FOT) was tasked with the realization of the National Access Point (NAP) for Switzerland, called the “[https://opentransportdata.swiss/en/ 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 [https://opentdatach.github.io/ojp-demo-app/search 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 [https://www.astra.admin.ch/astra/en/home.html Federal Roads Office in Switzerland] (FEDRO), while all geographical and topological information is gathered by the Federal Office of Topography ([https://www.swisstopo.admin.ch/en swisstopo]). Here we focus on the FOT related data.

Via these two channels, Switzerland provides the following data standards for Switzerland:

* '''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]

* '''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] (as above)
* '''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] (see above)
* '''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] (see above)
* '''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]
* '''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]

== Uses 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

[[File:Swiss architecture.png|center|thumb|674x674px]]

=== 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 [https://opentransportdata.swiss/de/showcase-5/ 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.