Portugal - Revision history

Admin: Admin moved page Draft:Portugal to Portugal

2024-10-08T13:20:22Z

Admin moved page Draft:Portugal to Portugal

← Older revision	Revision as of 15:20, 8 October 2024
(No difference)

Anonymous at 13:45, 17 September 2024

2024-09-17T13:45:47Z

← Older revision		Revision as of 15:45, 17 September 2024
Line 7:		Line 7:

	=== Description ===		=== Description ===
	~~'''~~Metropolitan Area of Porto~~'''~~		The Metropolitan Area of Porto covers 2,041 km², with a population of 1.76 million, including 76,000 university students, which represents 20% of Portugal's university population. As a Transport Authority, responsibilities include overseeing bus services operated by private companies, which covers:

	* Area: 2,041 km²
	* Population: 1.76 million
	* 76,000 university students ~~(representing~~ 20% of Portugal's university population)

	As a Transport Authority, ~~we are responsible for~~ overseeing bus services operated by private companies~~. Our responsibilities include~~:

	* Planning (routes, interconnections, frequencies, coverage, etc.)		* Planning (routes, interconnections, frequencies, coverage, etc.)
Line 31:		Line 25:

	=== Architecture ===		=== Architecture ===
	The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx ~~forma~~.		The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
	[[File:Portugal schema.png\|thumb\|656x656px\|center\|Flux diagram of NeTEx exchange]]		[[File:Portugal schema.png\|thumb\|656x656px\|center\|Flux diagram of NeTEx exchange]]
	=== Use cases ===		=== Use cases ===
Line 37:		Line 31:

	=== Outcome ===		=== Outcome ===
	As long as ~~NeTEx~~ covers the aspects ~~required for information sharing, there is no need for~~ extensions.		Netex will be seen as the base for information sharing as long as it covers all the aspects of the organisation needs. Potential extensions might be considered.

	In the future, it is hoped that comprehensive transport information will be available through NeTEx and SIRI via collaborative sharing. This information will enable companies and individual projects to develop applications that address global needs or specific interests.		In the future, it is hoped that comprehensive transport information will be available through NeTEx and SIRI via collaborative sharing. This information will enable companies and individual projects to develop applications that address global needs or specific interests.

Anonymous at 11:24, 17 September 2024

2024-09-17T11:24:24Z

← Older revision		Revision as of 13:24, 17 September 2024
Line 31:		Line 31:

	=== Architecture ===		=== Architecture ===
	The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx ~~format~~.		The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx forma.
	[[File:Portugal schema.png\|thumb\|656x656px]]		[[File:Portugal schema.png\|thumb\|656x656px\|center\|Flux diagram of NeTEx exchange]]
	~~[[File:Flux diagram of NeTEx exchange.png~~\|center~~\|thumb\|724x724px~~\|Flux diagram of NeTEx exchange]]

	=== Use cases ===		=== Use cases ===
	PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).		PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).

Anonymous at 11:22, 17 September 2024

2024-09-17T11:22:54Z

← Older revision		Revision as of 13:22, 17 September 2024
Line 32:		Line 32:
	=== Architecture ===		=== Architecture ===
	The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.		The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
			[[File:Portugal schema.png\|thumb\|656x656px]]
	[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|724x724px\|Flux diagram of NeTEx exchange]]		[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|724x724px\|Flux diagram of NeTEx exchange]]

Anonymous at 11:18, 17 September 2024

2024-09-17T11:18:52Z

← Older revision		Revision as of 13:18, 17 September 2024
Line 1:		Line 1:
	== Overview in the National Level ==		== Overview in the National Level ==
	In Portugal, AMP (Metropolitan Area of Porto) is working with native NeTEx, and ~~we hope~~ that other PTAs will soon ~~join~~ and ~~start using~~ it as well. AMP has ~~made the most use of~~ the validator~~. However~~, TML (Metropolitan ~~Transports~~ of Lisbon) and Carris (one of the largest PTOs in Portugal) have also ~~used~~ it to validate some information ~~in NeTEx~~.		In Portugal, AMP (Metropolitan Area of Porto) is working with native NeTEx, and it is anticipated that other PTAs will soon adopt and use it as well. AMP has extensively utilized the validator, while TML (Metropolitan Transport of Lisbon) and Carris (one of the largest PTOs in Portugal) have also employed it to validate some NeTEx information.

	Regarding the use of the NAP, the number of users has been growing considerably, and the information ~~available~~ is ~~very~~ diverse. It ~~includes~~ public transportation (roadway and railway), electric charging points, Zones of Conditional Automobile Access (UVAR), loading and unloading zones, scooter parks, parking lots, ~~Taxi~~ ranks, bus lanes, passenger drop-off and pick-up zones, parking ~~for bicycles~~, motorcycle parks, cycle paths, and other information.		Regarding the use of the NAP, the number of users has been growing considerably, and the available information is highly diverse. It encompasses public transportation (both roadway and railway), electric charging points, Zones of Conditional Automobile Access (UVAR), loading and unloading zones, scooter parks, parking lots, taxi ranks, bus lanes, passenger drop-off and pick-up zones, bicycle parking, motorcycle parks, cycle paths, and other related information.

	== Use cases ==		== Use cases ==
Line 31:		Line 31:

	=== Architecture ===		=== Architecture ===
	~~Our~~ platform is ~~built~~ as a ~~group~~ of microservices, ~~where~~ information exchange between specialized applications ~~is handled via~~ NeTEx. ~~It is possible to replace an~~ application with a commercial, internal, or open-source solution, ~~as long as~~ it ~~can export~~ or ~~import~~ data in the NeTEx format.		The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
	[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|~~781x781px~~\|Flux diagram of NeTEx exchange]]		[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|724x724px\|Flux diagram of NeTEx exchange]]

	=== ~~Uses~~ cases ===		=== Use cases ===
	PLIM is the name of ~~our~~ platform where all internal information is communicated by NeTEx ~~and produce NETEX~~, GTFS, SIRI, GTFS-feed to National Access Points (NAP).		PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).

	=== Outcome ===		=== Outcome ===
	~~Until whatever aspect that we want address is cover by NETEX to be~~ the ~~base of~~ sharing ~~information~~, no need of extensions~~, on use~~.		As long as NeTEx covers the aspects required for information sharing, there is no need for extensions.

	In future ~~we hope~~ that ~~a wide cover~~ transport information be available ~~in NETEX~~ and SIRI by collaborative sharing. ~~With this~~ information ~~any company project or~~ individual projects ~~could~~ develop applications to address global needs ~~our particular~~ interests.		In the future, it is hoped that comprehensive transport information will be available through NeTEx and SIRI via collaborative sharing. This information will enable companies and individual projects to develop applications that address global needs or specific interests.

Anonymous at 09:13, 17 September 2024

2024-09-17T09:13:15Z

← Older revision		Revision as of 11:13, 17 September 2024
Line 32:		Line 32:
	=== Architecture ===		=== Architecture ===
	Our platform is built as a group of microservices, where information exchange between specialized applications is handled via NeTEx. It is possible to replace an application with a commercial, internal, or open-source solution, as long as it can export or import data in the NeTEx format.		Our platform is built as a group of microservices, where information exchange between specialized applications is handled via NeTEx. It is possible to replace an application with a commercial, internal, or open-source solution, as long as it can export or import data in the NeTEx format.
	[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|~~500x500px~~\|Flux diagram of NeTEx exchange]]		[[File:Flux diagram of NeTEx exchange.png\|center\|thumb\|781x781px\|Flux diagram of NeTEx exchange]]

	=== Uses cases ===		=== Uses cases ===

Anonymous at 12:49, 16 September 2024

2024-09-16T12:49:57Z

← Older revision		Revision as of 14:49, 16 September 2024
Line 35:		Line 35:

	=== Uses cases ===		=== Uses cases ===
	PLIM is the name of our platform where all internal information is communicated by NeTEx and produce NETEX, GTFS, SIRI, GTFS-feed to ~~nap~~.		PLIM is the name of our platform where all internal information is communicated by NeTEx and produce NETEX, GTFS, SIRI, GTFS-feed to National Access Points (NAP).

	=== Outcome ===		=== Outcome ===

Anonymous: creation of portugal page

2024-09-13T08:13:05Z

creation of portugal page

New page

== Overview in the National Level ==
In Portugal, AMP (Metropolitan Area of Porto) is working with native NeTEx, and we hope that other PTAs will soon join and start using it as well. AMP has made the most use of the validator. However, TML (Metropolitan Transports of Lisbon) and Carris (one of the largest PTOs in Portugal) have also used it to validate some information in NeTEx.

Regarding the use of the NAP, the number of users has been growing considerably, and the information available is very diverse. It includes public transportation (roadway and railway), electric charging points, Zones of Conditional Automobile Access (UVAR), loading and unloading zones, scooter parks, parking lots, Taxi ranks, bus lanes, passenger drop-off and pick-up zones, parking for bicycles, motorcycle parks, cycle paths, and other information.

== Use cases ==

=== Description ===
'''Metropolitan Area of Porto'''

* Area: 2,041 km²
* Population: 1.76 million
* 76,000 university students (representing 20% of Portugal's university population)

As a Transport Authority, we are responsible for overseeing bus services operated by private companies. Our responsibilities include:

* Planning (routes, interconnections, frequencies, coverage, etc.)
* Establishing ticketing, fees, pricing, and regulations
* Managing contracts
* Handling payments related to contractual obligations (bonuses/penalties)
* Providing public information (indirectly, to other public or private entities that are better positioned to integrate the information)

To meet these requirements, the exchange of detailed information is essential. NeTEx has been chosen for data exchange between stakeholders due to its advantages:

* Comprehensive coverage of all transport system areas
* Object-oriented data model
* Version control mechanisms
* Supports transmission as both payload and file
* Compliant with the Portuguese NAP standard (IMT)
* A fully recognized European standard since 2006

=== Architecture ===
Our platform is built as a group of microservices, where information exchange between specialized applications is handled via NeTEx. It is possible to replace an application with a commercial, internal, or open-source solution, as long as it can export or import data in the NeTEx format.
[[File:Flux diagram of NeTEx exchange.png|center|thumb|500x500px|Flux diagram of NeTEx exchange]]

=== Uses cases ===
PLIM is the name of our platform where all internal information is communicated by NeTEx and produce NETEX, GTFS, SIRI, GTFS-feed to nap.

=== Outcome ===
Until whatever aspect that we want address is cover by NETEX to be the base of sharing information, no need of extensions, on use.

In future we hope that a wide cover transport information be available in NETEX and SIRI by collaborative sharing. With this information any company project or individual projects could develop applications to address global needs our particular interests.