Operational questions about Transport Plan datasets

[clairecarnot]

Hello,

We would like to publish our Transport Plan data (theoretical timetables, stops, and services) in NeTEx format on the French National Access Point (PAN) and we have a few practical questions.

• Is it possible to include equipment (carriages) information? If yes, which NeTEx structures should be used?

• Regarding services, is it acceptable to export only active (ie running) services, or should cancelled services also be included, tagged with an appropriate status (for example using calendar exceptions or the ServiceAlteration field)?

• Regarding stops used in services (inventory side, not topography), if a stop is cancelled for a specific service, should the stop still appear in the service definition (e.g. JourneyPattern) with an inactive/cancelled status, or simply be removed from that service instance?

• Is there a notion of status to distinguish services that are already open for commercial operation, and the ones scheduled but not yet open for booking? Should the services scheduled but not yet open appear in the Transport Plan?

• If we automate the publication of the Transport Plan dataset on the National Access Point (PAN), what would be the recommended update frequency? Should a new dataset be published each time a modification occurs, or is there a recommended periodic update cadence?

Thank you !

[thbar]

Discussed with @TuThoThai, we've "triaged" and decided to keep this one here, since most questions appear to be generic.

[williampollet]

Hello,

Regarding services, is it acceptable to export only active (ie running) services, or should cancelled services also be included, tagged with an appropriate status (for example using calendar exceptions or the ServiceAlteration field)?

Regarding stops used in services (inventory side, not topography), if a stop is cancelled for a specific service, should the stop still appear in the service definition (e.g. JourneyPattern) with an inactive/cancelled status, or simply be removed from that service instance?

More globally it is not clear for me how should we handle services that have been altered.

From what I understand from the format, we can only model days where a service operates or not. (with OperatingPeriod or Date in DayTypeAssignment.

This means that if we handle a service cancelled as "not operating" on a specific day (from an OperatingPeriod for instance), if we want to reload the transport plan from the file we just exported, we will simply not create the service in our system.

The issue here is that if we want to reload the services from the file we just exported, we will not have the same state: the altered services (Cancelled, suspended for instance) will not appear, and information is lost.

How can we handle this ? Is it out of the NeTEX responsibility & use case and we should use SIRI ? And if so, should we in the NeTEX file not take account of the alterations and still export the services ? Or should we skip them ? Or did I miss a model that allows to handle such use cases ?

We also have the issue on the cancelled stops.