Talk:NeTEX - Revision history

Anasfou at 14:45, 12 January 2023

2023-01-12T14:45:11Z

← Older revision		Revision as of 16:45, 12 January 2023
Line 180:		Line 180:

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 11:12, 2 November 2022 (CET)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 11:12, 2 November 2022 (CET)

			== Should "RouteLink" have a unique identifier? ==

			Each unique RouteLink should have a unique identifier (id-attribute).
			Note that a RouteLink over time may be altered and still retain its original identifier, but each modification should have a different version-attribute.

			At the same time it is OK to refer to the same RouteLink in relation to different Lines, if those Lines include a shared physical path for some part of the respective routes. This applies also if the Lines are provided in separate files.

			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 15:44, 12 January 2023 (CET)

Anasfou at 10:12, 2 November 2022

2022-11-02T10:12:49Z

← Older revision		Revision as of 12:12, 2 November 2022
Line 172:		Line 172:

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:04, 05 October 2022 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:04, 05 October 2022 (CEST)


			== How to describe two similar stops sequences when the one has a boarding and alighting information and the other has not? ==

			One ROUTE is enough, it can cover two different JOURNEY PATTERNS if the vehicle will traverse the same physical path in both cases. The relation between ROUTE POINT and SCHEDULED STOP POINT is formally through projection.


			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 11:12, 2 November 2022 (CET)

Anasfou: /* Where can I find the UML model for NeTEX? */

2022-10-21T18:23:56Z

Where can I find the UML model for NeTEX?

← Older revision		Revision as of 20:23, 21 October 2022
Line 134:		Line 134:
	== Where can I find the UML model for NeTEX? ==		== Where can I find the UML model for NeTEX? ==

	The UML of NeTEx is ~~actually~~ Transmodel UML~~. It~~ is available in Enterprise Architect file https://www.transmodel-cen.eu/model/. This version corresponds to the CEN v6.0 release c2018, with revisions from 2021. For more information regarding the data model (Transmodel) please check here https://www.transmodel-cen.eu/downloads/. Updates on the Transmodel UML are expected in the coming period.		The UML of NeTEx is available [[here\|https://www.netex-cen.eu/model/conceptual/part1/index.htm]]. NeTEx is based on data model Transmodel, of which the UML is available in Enterprise Architect file https://www.transmodel-cen.eu/model/. This version corresponds to the CEN v6.0 release c2018, with revisions from 2021. For more information regarding the data model (Transmodel) please check here https://www.transmodel-cen.eu/downloads/. Updates on the Transmodel UML are expected in the coming period.

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:08, 22 September 2022 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:08, 22 September 2022 (CEST)


	== Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==		== Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==

Anasfou at 08:04, 5 October 2022

2022-10-05T08:04:41Z

@@ Line 141: / Line 141: @@
 == Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities?  ==
-TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis. NeTEx Part 5 (CEN/TS 16614-5) is complementary to the previous parts (1/2/3/4). It is fully aligned with the new Transmodel Part 10, being the underlaying data model.
+TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis.
 Transmodel extension published as CEN TS 17413:2019. The conversion of CEN TS 17413:2019 into an EN is going to be the Transmodel -Part 10. General information about NeTEx Part 5 is available here http://netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf. The specifications are also now published by CEN.
@@ Line 150: / Line 154: @@
 --[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 16:28, 22 September 2022 (CEST)

Anasfou: /* Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? */

2022-09-22T14:33:20Z

Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities?

← Older revision		Revision as of 16:33, 22 September 2022
Line 144:		Line 144:
	Transmodel extension published as CEN TS 17413:2019. The conversion of CEN TS 17413:2019 into an EN is going to be the Transmodel -Part 10. General information about NeTEx Part 5 is available here http://netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf. The specifications are also now published by CEN.		Transmodel extension published as CEN TS 17413:2019. The conversion of CEN TS 17413:2019 into an EN is going to be the Transmodel -Part 10. General information about NeTEx Part 5 is available here http://netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf. The specifications are also now published by CEN.

	Besides the CEN documentation, the users (IT suppliers/operators, in general developers etc.) can have access to the technical artefacts (XSD) through the publicly available repository in GitHub https://~~github~~.~~com~~/~~NeTEx-CEN~~/~~NeTEx/tree/new-modes~~.		Besides the CEN documentation, the users (IT suppliers/operators, in general developers etc.) can have access to the technical artefacts (XSD) through the publicly available repository in GitHub (check https://data4pt.org/w/index.php?title=NeTEX#NeTEx_Part_5_for_New_Modes). In addition, there is an available mapping-comparison with GBFS, the bike sharing data format from Mobility Data https://data4pt.org/w/index.php?title=NeTEX#Canonical_mapping_with_GBFS.
	~~Actually~~, ~~all technical artefacts and examples regarding NeTEx are~~ available ~~there (~~ https://~~github~~.~~com~~/~~NeTEx-CEN)~~.

	Since NeTEx is about scheduled data (including location of parking places, capacity etc.), is complemented by SIRI for realtime data. Therefore, SIRI has also been extended (recently voted) to cover new modes (vehicles availability, parking places availability etc.). This extension is in SIRI Part 4 (Facility Monitoring).		Since NeTEx is about scheduled data (including location of parking places, capacity etc.), is complemented by SIRI for realtime data. Therefore, SIRI has also been extended (recently voted) to cover new modes (vehicles availability, parking places availability etc.). This extension is in SIRI Part 4 (Facility Monitoring).

Anasfou: /* Where can I find information about how and when NetEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? */

2022-09-22T14:28:43Z

Where can I find information about how and when NetEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities?

← Older revision		Revision as of 16:28, 22 September 2022
Line 139:		Line 139:


	== Where can I find information about how and when ~~NetEx~~ is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==		== Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==

	TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis. NeTEx Part 5 (CEN/TS 16614-5) is complementary to the previous parts (1/2/3/4). It is fully aligned with the new Transmodel Part 10, being the underlaying data model.		TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis. NeTEx Part 5 (CEN/TS 16614-5) is complementary to the previous parts (1/2/3/4). It is fully aligned with the new Transmodel Part 10, being the underlaying data model.

Anasfou at 14:28, 22 September 2022

2022-09-22T14:28:19Z

← Older revision		Revision as of 16:28, 22 September 2022
Line 137:		Line 137:

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:08, 22 September 2022 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:08, 22 September 2022 (CEST)


			== Where can I find information about how and when NetEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==

			TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis. NeTEx Part 5 (CEN/TS 16614-5) is complementary to the previous parts (1/2/3/4). It is fully aligned with the new Transmodel Part 10, being the underlaying data model.
			Transmodel extension published as CEN TS 17413:2019. The conversion of CEN TS 17413:2019 into an EN is going to be the Transmodel -Part 10. General information about NeTEx Part 5 is available here http://netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf. The specifications are also now published by CEN.

			Besides the CEN documentation, the users (IT suppliers/operators, in general developers etc.) can have access to the technical artefacts (XSD) through the publicly available repository in GitHub https://github.com/NeTEx-CEN/NeTEx/tree/new-modes.
			Actually, all technical artefacts and examples regarding NeTEx are available there ( https://github.com/NeTEx-CEN).

			Since NeTEx is about scheduled data (including location of parking places, capacity etc.), is complemented by SIRI for realtime data. Therefore, SIRI has also been extended (recently voted) to cover new modes (vehicles availability, parking places availability etc.). This extension is in SIRI Part 4 (Facility Monitoring).
			In particular for parking, there is a comprehensive description in NeTEx. France for example has already a dedicated profile for parking – the documentation in french is available here http://www.normes-donnees-tc.org/wp-content/uploads/2021/10/NF_Profil-NeTEx-pour-les-ParkingsF-v1.2a.pdf ).

			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:28, 22 September 2022 (CEST)

Anasfou at 14:08, 22 September 2022

2022-09-22T14:08:54Z

← Older revision		Revision as of 16:08, 22 September 2022
Line 131:		Line 131:

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 19:16, 9 September 2022 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 19:16, 9 September 2022 (CEST)

			== Where can I find the UML model for NeTEX? ==

			The UML of NeTEx is actually Transmodel UML. It is available in Enterprise Architect file https://www.transmodel-cen.eu/model/. This version corresponds to the CEN v6.0 release c2018, with revisions from 2021. For more information regarding the data model (Transmodel) please check here https://www.transmodel-cen.eu/downloads/. Updates on the Transmodel UML are expected in the coming period.

			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:08, 22 September 2022 (CEST)

Anasfou: /* How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations? */

2022-09-12T11:56:35Z

How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations?

← Older revision		Revision as of 13:56, 12 September 2022
Line 125:		Line 125:
	== How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations? ==		== How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations? ==

	For planned deviations, another version of JourneyPattern needs to be described having different validity conditions than the regular ~~JourenyPattern~~. For deviations that occur the same day of the operation, SIRI Estimated Timetable (ET) can be used, and for deviations known some days before the operational day, SIRI Production Timetable (PT) can be used.		For planned deviations, another version of JourneyPattern needs to be described having different validity conditions than the regular JourneyPattern. For deviations that occur the same day of the operation, SIRI Estimated Timetable (ET) can be used, and for deviations known some days before the operational day, SIRI Production Timetable (PT) can be used.

	Moreover, there is today no element in the XSD that states if a JourneyPattern is "normal" or "diversion".		Moreover, there is today no element in the XSD that states if a JourneyPattern is "normal" or "diversion".

Anasfou: /* How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations? */

2022-09-12T11:51:06Z

How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations?

← Older revision		Revision as of 13:51, 12 September 2022
Line 126:		Line 126:

	For planned deviations, another version of JourneyPattern needs to be described having different validity conditions than the regular JourenyPattern. For deviations that occur the same day of the operation, SIRI Estimated Timetable (ET) can be used, and for deviations known some days before the operational day, SIRI Production Timetable (PT) can be used.		For planned deviations, another version of JourneyPattern needs to be described having different validity conditions than the regular JourenyPattern. For deviations that occur the same day of the operation, SIRI Estimated Timetable (ET) can be used, and for deviations known some days before the operational day, SIRI Production Timetable (PT) can be used.

			Moreover, there is today no element in the XSD that states if a JourneyPattern is "normal" or "diversion".
			This means that you would probably need to analyse the timetable over a longer period of time and compare how often different JourneyPatterns (or versions of a certain JourneyPattern) are actually used on a certain Direction to find which is the "normal" one.

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 19:16, 9 September 2022 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 19:16, 9 September 2022 (CEST)