Skip to content

Adding DeadRun flag to SIRI for ET and VM - #238

Open
TuThoThai wants to merge 2 commits into
v2.3-wipfrom
vm_cr_deadrun
Open

Adding DeadRun flag to SIRI for ET and VM#238
TuThoThai wants to merge 2 commits into
v2.3-wipfrom
vm_cr_deadrun

Conversation

@TuThoThai

Copy link
Copy Markdown
Collaborator

Context

Since we have the possibility to have dead runs in NeTEx, it would be interesting to be able to follow them in SIRI-VM (mostly) and in SIRI-ET. It would allow to address these use cases:

  • Have an explicit mention of a dead run that can be used for passenger information, especially when unplanned
  • Support fleet monitoring regardless of the ServiceJourney type (accepting passengers or not).

Changes made in this PR

  • In the XSD, more precisely in siri_journey.xsd in the JourneyInfoGroup, addition of an optional boolean named DeadRun7 with the default value being false`
  • One example of a payload in SIRI-ET that includes a dead run
  • One example of a payload in SIRI-VM that includes a dead run

Addition of:
- DeadRun flag as a boolean in JouneyInfoGroup
- Example in SIRI-ET
- Example in SIRI-VM
@TuThoThai TuThoThai added this to the v2.3 milestone Aug 11, 2026
@TuThoThai TuThoThai added ET For everything SIRI-ET VM For everything SIRI-VM labels Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ET For everything SIRI-ET VM For everything SIRI-VM

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant