Explore NAP guidelines - Revision history

Anasfou: /* Abbreviations and Acronyms */

2025-04-28T14:27:12Z

Abbreviations and Acronyms

← Older revision		Revision as of 16:27, 28 April 2025
Line 13:		Line 13:
	Check the [https://data4pt-project.eu/ DATA4PT website] and [https://napcore.eu/ NAPCORE website] for additional information.		Check the [https://data4pt-project.eu/ DATA4PT website] and [https://napcore.eu/ NAPCORE website] for additional information.

	= ~~'''~~How to make datasets for multimodal mobility systems interoperable across the EU~~'''~~ =		= How to make datasets for multimodal mobility systems interoperable across the EU =
	~~'''~~''Legal Disclaimer~~'''~~''		''Legal Disclaimer''

	''The information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The referenced consortium members shall have no liability to third parties for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. This document is published under the CC BY-SA 4.0 license<sup>[1]</sup>.''		''The information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The referenced consortium members shall have no liability to third parties for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. This document is published under the CC BY-SA 4.0 license<sup>[1]</sup>.''
Line 76:		Line 76:
	This guidance document is developed with some principles to help the industry navigate toward our interoperable future. The principles are statements of intent that lay out the MMTIS’s positive vision for the future of mobility data. Rooted in the philosophies of public service and personal empowerment that define the transit industry, the principles also highlight the efficiency, connectivity, and flexibility that interoperability will unlock for mobility data users.		This guidance document is developed with some principles to help the industry navigate toward our interoperable future. The principles are statements of intent that lay out the MMTIS’s positive vision for the future of mobility data. Rooted in the philosophies of public service and personal empowerment that define the transit industry, the principles also highlight the efficiency, connectivity, and flexibility that interoperability will unlock for mobility data users.

	# ~~'''~~CEN-Standards~~'''~~: Interoperability should be achieved through the development, adoption, and widespread implementation of NeTEx and SIRI data that support the efficient exchange and portability of mobility data.		# CEN-Standards: Interoperability should be achieved through the development, adoption, and widespread implementation of NeTEx and SIRI data that support the efficient exchange and portability of mobility data.
	# ~~'''~~Cross-border alignment~~'''~~: We seek collaboration within the NAPs and CEN to secure easy-to-use cross-border open data from the National Access Points; we align on as few profiles as possible.		# Cross-border alignment: We seek collaboration within the NAPs and CEN to secure easy-to-use cross-border open data from the National Access Points; we align on as few profiles as possible.
	# ~~'''~~Interoperability~~'''~~: It is highly recommended that all systems creating, modifying, or consuming mobility data should be interoperable.		# Interoperability: It is highly recommended that all systems creating, modifying, or consuming mobility data should be interoperable.
	# ~~'''~~Tools~~'''~~: Transit agencies and other mobility service providers should have access to tools that present high-quality mobility data accessibly, equitably, and in real time to assist travelers in meeting their mobility needs.		# Tools: Transit agencies and other mobility service providers should have access to tools that present high-quality mobility data accessibly, equitably, and in real time to assist travelers in meeting their mobility needs.
	# ~~'''~~Open technology~~'''~~: Transit agencies, other mobility service providers, and travelers should be able to select the transportation technology components that best meet their needs.		# Open technology: Transit agencies, other mobility service providers, and travelers should be able to select the transportation technology components that best meet their needs.
	# ~~'''~~High quality~~'''~~: All individuals and the public should be empowered through high-quality, always updated, well-distributed mobility data to find, access, and utilize high-quality mobility options that meet their needs as they see fit while maintaining their privacy.		# High quality: All individuals and the public should be empowered through high-quality, always updated, well-distributed mobility data to find, access, and utilize high-quality mobility options that meet their needs as they see fit while maintaining their privacy.
	# ~~'''~~Self-utilization~~'''~~: The NAPs and data producers should, when possible, use the shared data themselves.		# Self-utilization: The NAPs and data producers should, when possible, use the shared data themselves.

	----<sup>[1]</sup> Inspired by: <nowiki>https://www.interoperablemobility.org/</nowiki>		----<sup>[1]</sup> Inspired by: <nowiki>https://www.interoperablemobility.org/</nowiki>
Line 230:		Line 230:

	==== Key recommendations for developing national profiles ====		==== Key recommendations for developing national profiles ====
	1. ~~'''Align~~ with the European profile:~~'''~~		1. Align with the European profile:

	○ National profiles must adhere to the European profile to ensure consistency and interoperability across countries.		○ National profiles must adhere to the European profile to ensure consistency and interoperability across countries.

	2. ~~'''Collaborate~~ on a joint maximum profile:~~'''~~		2. Collaborate on a joint maximum profile:

	○ National Access Points (NAPs) should work together to create a shared maximum profile for Europe.		○ National Access Points (NAPs) should work together to create a shared maximum profile for Europe.
Line 240:		Line 240:
	○ The EU profile must be fully interoperable (1:1) with this joint maximum profile.		○ The EU profile must be fully interoperable (1:1) with this joint maximum profile.

	3. ~~'''Avoid~~ profile proliferation:~~'''~~		3. Avoid profile proliferation:

	○ Check existing national profiles before creating a new one.		○ Check existing national profiles before creating a new one.
Line 246:		Line 246:
	○ Collaborate with other countries to develop a profile that meets shared needs.		○ Collaborate with other countries to develop a profile that meets shared needs.

	4. ~~'''Process~~ for developing a national profile:~~'''~~ If a new national profile is necessary, follow these steps (see Section 5.5 for details):		4. Process for developing a national profile: If a new national profile is necessary, follow these steps (see Section 5.5 for details):

	○ ~~'''~~Define the functional scope:~~'''~~ Determine the essential requirements and exclude unnecessary elements.		○ Define the functional scope: Determine the essential requirements and exclude unnecessary elements.

	○ ~~'''~~Assess existing profiles:~~'''~~ Check whether any European or national profiles already meet your needs. Contact CEN experts to explore collaboration opportunities.		○ Assess existing profiles: Check whether any European or national profiles already meet your needs. Contact CEN experts to explore collaboration opportunities.

	○ ~~'''~~Develop a new profile (if needed):~~'''~~ If no existing profiles are suitable and collaboration is not possible, use the standard to create a new profile. If additional information is required beyond the European profile		○ Develop a new profile (if needed): If no existing profiles are suitable and collaboration is not possible, use the standard to create a new profile. If additional information is required beyond the European profile

	* Check if the needed elements already exist in the full standard. If so, add them to the national profile.		* Check if the needed elements already exist in the full standard. If so, add them to the national profile.
Line 258:		Line 258:

	==== Practical considerations ====		==== Practical considerations ====
	1. ~~'''Interoperability~~:~~'''~~		1. Interoperability:

	○ Ensure European profiles enable easy information exchange.		○ Ensure European profiles enable easy information exchange.
Line 264:		Line 264:
	○ Extensions should allow seamless extraction of interoperable data.		○ Extensions should allow seamless extraction of interoperable data.

	2. ~~'''Resolve~~ ambiguities in profiles:~~'''~~		2. Resolve ambiguities in profiles:

	○ NAPs should provide clear guidance and coordinate with other NAPs to resolve ambiguities uniformly across Europe.		○ NAPs should provide clear guidance and coordinate with other NAPs to resolve ambiguities uniformly across Europe.

	3. ~~'''Expert~~ consultation:~~'''~~		3. Expert consultation:

	○ If unsure about profiles, consult expert groups responsible for the standards.		○ If unsure about profiles, consult expert groups responsible for the standards.

	4. ~~'''Roadmap~~ and documentation:~~'''~~		4. Roadmap and documentation:

	○ Maintain a roadmap for profile development and adherence.		○ Maintain a roadmap for profile development and adherence.
Line 412:		Line 412:
	● [https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf GBFS to NeTEx & SIRI v1.0- A canonical mapping produced by MobilityData and DATA4PT]		● [https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf GBFS to NeTEx & SIRI v1.0- A canonical mapping produced by MobilityData and DATA4PT]

	== ~~'''~~Abbreviations and Acronyms~~'''~~ ==		== Abbreviations and Acronyms ==
	{\| class="wikitable"		{\| class="wikitable"
	\|DR		\|DR
Line 454:		Line 454:
	\|}		\|}

	== ~~'''~~Guidelines Control Sheet~~'''~~ ==		== Guidelines Control Sheet ==
	{\| class="wikitable"		{\| class="wikitable"
	\|Type of documentation:		\|Type of documentation:

Anasfou at 14:26, 28 April 2025

2025-04-28T14:26:38Z

← Older revision		Revision as of 16:26, 28 April 2025
Line 411:		Line 411:

	● [https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf GBFS to NeTEx & SIRI v1.0- A canonical mapping produced by MobilityData and DATA4PT]		● [https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf GBFS to NeTEx & SIRI v1.0- A canonical mapping produced by MobilityData and DATA4PT]

			== '''Abbreviations and Acronyms''' ==
			{\| class="wikitable"
			\|DR
			\|Delegated Regulation
			\|-
			\|EPIAP
			\|European Passenger Information Accessibility Profile (NeTEx part 6)
			\|-
			\|EPIP
			\|European Passenger Information Profile (NeTEx part 4)
			\|-
			\|MMTIS
			\|MultiModal Travel Information Services (EU 2017/1926 and the amendment EU/2024/490)
			\|-
			\|MS
			\|Members States
			\|-
			\|NAP
			\|National Access Point
			\|-
			\|NeTEx
			\|Network Timetable Exchange
			\|-
			\|OPRA
			\|OPerating RAw data and statistics exchange
			\|-
			\|PTA
			\|Public Transport Authorities
			\|-
			\|PTO
			\|Public Transport Operators
			\|-
			\|SIRI
			\|Service interface for real-time information
			\|-
			\|Source system
			\|The system producing the data for the NAP.
			\|-
			\|TRANSMODEL
			\|Public Transport Reference Data Model
			\|}

	== '''Guidelines Control Sheet''' ==		== '''Guidelines Control Sheet''' ==

Anasfou: /* Guidelines on How to make datasets for multimodal mobility systems interoperable across the EU */

2025-04-28T13:58:24Z

Guidelines on How to make datasets for multimodal mobility systems interoperable across the EU

← Older revision		Revision as of 15:58, 28 April 2025
Line 13:		Line 13:
	Check the [https://data4pt-project.eu/ DATA4PT website] and [https://napcore.eu/ NAPCORE website] for additional information.		Check the [https://data4pt-project.eu/ DATA4PT website] and [https://napcore.eu/ NAPCORE website] for additional information.

	= ~~Guidelines on~~ '''How to make datasets for multimodal mobility systems interoperable across the EU''' =		= '''How to make datasets for multimodal mobility systems interoperable across the EU''' =
	'''''Legal Disclaimer'''''		'''''Legal Disclaimer'''''

Anasfou: Anasfou moved page National Access-Points to Explore NAP guidelines

2025-04-28T13:46:56Z

Anasfou moved page National Access-Points to Explore NAP guidelines

← Older revision	Revision as of 15:46, 28 April 2025
(No difference)

Anasfou: update of page name

2025-04-28T13:28:17Z

update of page name

← Older revision		Revision as of 15:28, 28 April 2025
Line 1:		Line 1:
			{{DISPLAYTITLE:Explore NAP Guidelines}}

	A National Access Point (NAP) is a central internet resource from which transport data for a country can be obtained by operators and third parties.		A National Access Point (NAP) is a central internet resource from which transport data for a country can be obtained by operators and third parties.

Anasfou: /* Guidelines on How to make datasets for multimodal mobility systems interoperable across the EU */

2025-04-28T12:22:40Z

Guidelines on How to make datasets for multimodal mobility systems interoperable across the EU

← Older revision		Revision as of 14:22, 28 April 2025
Line 14:		Line 14:
	'''''Legal Disclaimer'''''		'''''Legal Disclaimer'''''

	''The information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The ~~above~~ referenced consortium members shall have no liability to third parties for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. This document is published under the CC BY-SA 4.0 license<sup>[1]</sup>.''		''The information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The referenced consortium members shall have no liability to third parties for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. This document is published under the CC BY-SA 4.0 license<sup>[1]</sup>.''
	----<sup>[1]</sup> See <nowiki>https://creativecommons.org/licenses/by-sa/4.0/deed.en</nowiki>		----<sup>[1]</sup> See <nowiki>https://creativecommons.org/licenses/by-sa/4.0/deed.en</nowiki>

Anasfou: /* General Guidance for Responsibilities of a NAP[1] */

2025-04-25T16:17:10Z

General Guidance for Responsibilities of a NAP[1]

← Older revision		Revision as of 18:17, 25 April 2025
Line 206:		Line 206:
	* Links to data usage description, tools, libraries and base information should be provided with the data. The description should be written for user consumption.		* Links to data usage description, tools, libraries and base information should be provided with the data. The description should be written for user consumption.

	=== General ~~Guidance~~ for ~~Responsibilities~~ of a NAP<sup>[1]</sup> ===		=== General guidance for responsibilities of a NAP<sup>[1]</sup> ===
	The NAP is not only a simple meta data catalogue. Otherwise, it will never fulfill the needs of a European mobility data space. Some essential issues NAP needs to address:		The NAP is not only a simple meta data catalogue. Otherwise, it will never fulfill the needs of a European mobility data space. Some essential issues NAP needs to address:

Anasfou: /* Guidelines Control Sheet */

2025-04-25T16:12:39Z

Guidelines Control Sheet

← Older revision		Revision as of 18:12, 25 April 2025
Line 484:		Line 484:
	\|Matthias Günter		\|Matthias Günter
	Brede Dammen		Brede Dammen

	Anastasia Founta		Anastasia Founta
	\|}		\|}
	----		----

Anasfou: /* Guidelines Control Sheet */

2025-04-25T16:12:24Z

Guidelines Control Sheet

← Older revision		Revision as of 18:12, 25 April 2025
Line 472:		Line 472:
	\|Matthias Günter		\|Matthias Günter
	Brede Dammen		Brede Dammen

	Ulf Bjersing		Ulf Bjersing

	Christophe Duquesne		Christophe Duquesne

	Emmanuel De Verdalle		Emmanuel De Verdalle
	\|-		\|-

Anasfou: /* Guidelines Control Sheet */

2025-04-25T16:12:04Z

Guidelines Control Sheet

← Older revision		Revision as of 18:12, 25 April 2025
Line 465:		Line 465:
	\|Integration of input		\|Integration of input
	\|Matthias Günter		\|Matthias Günter

	Brede Dammen		Brede Dammen
	\|-		\|-
Line 472:		Line 471:
	\|Review		\|Review
	\|Matthias Günter		\|Matthias Günter

	Brede Dammen		Brede Dammen

	Ulf Bjersing		Ulf Bjersing
			Christophe Duquesne
	Christophe Duquesne

	Emmanuel De Verdalle		Emmanuel De Verdalle
	\|-		\|-
Line 485:		Line 480:
	\|Final editing		\|Final editing
	\|Matthias Günter		\|Matthias Günter

	Brede Dammen		Brede Dammen

	Anastasia Founta		Anastasia Founta
	\|}		\|}
	----		----