Service link proposal v2 #194
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Provides a simplified description of an update of a SERVICE LINK, in order to provide an updated schematic shape (not ROUTE POINTs) in case of rerouting. Only updated ServiceLink are expected to be provided here, the scheduled one being provided by a NeTEx feed. The SERVICE JOURNEY itself is knonw from hte context. Note that, The shape (LineString) is mandatory in order to be consistent with the use case, which is to update the shape. In this initial proposal, the Service Links update can be inserted either in a EstimatedVehicleJourneyStructure (to be repeated for each journey) either in a consequence of a PTSituation (can be shared accross multiple journeys). As usual, the EstimatedVehicleJourneyStructure can be linked with the PTSituation.
…o ControlAction Removal of UpdatedServiceLinks from EstimatedTimetable and addition to the ChangeOfJourneyPattern ControlAction
Closed
TuThoThai
added
ET
Collaborator
|
i would not merge it with 2.3 (as commented in PR 191) but with integration so that we don't have to resolve conflicts and do additional work when preparing 2.3 (since we decided to remove integration sooner or later) |
Contributor
Author
That was my initial intention, but when I tried, CA was not available in Integration ! |
haeckerbaer
approved these changes
Dec 19, 2025
Collaborator
|
Are CA now available in Integration? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Second proposal to include ServiceLinks updates
Takes into account the decision from the September 24th 2025 meeting (remove it from ET and add to CA)
Replaces #175
Provides a simplified description of an update of a SERVICE LINK, in order to provide an updated schematic shape (not ROUTE POINTs) in case of rerouting. Only updated ServiceLink are expected to be provided here, the scheduled one being provided by a NeTEx feed. The SERVICE JOURNEY itself is known from the context.
Note that, The shape (LineString) is mandatory in order to be consistent with the use case, which is to update the shape.
In this initial proposal, the Service Links update can be inserted either in a ChangeOfJourneyPattern ControlAction (to be repeated for each journey) either in a consequence of a PTSituation (can be shared accross multiple journeys).
Also note that an EstimatedVehicleJourneyStructure can be refer PTSituations containing the UpdatedServiceLinks information.