Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #308
Closed
Open
Issue created Mar 17, 2017 by Deleted User@deleted-user

Referencing of canceled trains (de: Referenzierung von ausgefallenen Zügen)

Description

For a replacement train it shall be possible to specify the train that was originally planned.

Suggested change:

  • the train shall be extended to hold the information regarding the corresponding trains that are replaced.

Background

When a train is cancelled then a replacement train might be planned and for this new train the information of the train it replaces shall be accessable.

Links

  • Forum discussion
  • Mićo Mićić (SBB) (de/en), November 2016: Wie können ausgefallene Züge referenziert werden? / How to reference cancaled trains?)
  • Wiki Documentation
  • TT:replacements (NEW)
  • TT:replacementOf (NEW)
  • TT:train (Needs to be updated when 2.4 is released)

Changes in railML 2.4

A cancelled train can be replaced by another train with a different train number. For the new train all those trains can be specified that are replaced by this new train. The reference to the replaced train can be done either by supplying the tafTapTsiTrainID (TAF/TAP TSI train ID) or a uniqueTrainKey (NEW).

railML elements

The following new elements/attributes are available:

  • railml/timetable/trains/train/replacements
  • railml/timetable/trains/train/replacements/replacementOf
  • railml/timetable/trains/train/replacements/replacementOf/operatingPeriodRef
  • railml/timetable/trains/train/replacements/replacementOf/tafTapTsiTrainID
  • railml/timetable/trains/train/replacements/replacementOf/uniqueTrainKey
  • railml/timetable/trains/train/replacements/replacementOf/uniqueTrainKey/@trainNumber
  • railml/timetable/trains/train/replacements/replacementOf/uniqueTrainKey/@additionalTrainNumber
  • railml/timetable/trains/train/replacements/replacementOf/uniqueTrainKey/@scope

The following XSD file(s) have been updated:

  1. timetable.xsd
  2. timetableTypes.xsd

Development Branch

In order to facilitate the development a branch of railML 2.3 called 'topology-reference' was created - all ongoing development work for this ticket is done in this branch:

  • railML/railML2/branches/referencing-canceled-trains referencing-canceled-trains

Changesets in branch

  • [changeset:"761/railML"] - New branch for replacement train definition.
  • [changeset:"762/railML"] - First version of the "replacements" element as described in forum post.
  • [changeset:"767/railML"] - The operating period reference is also required for replacement trains referenced by TAF/TAP TSI train id.
  • Diff 761:767

Changesets in trunk

  • [changeset:"775/railML"] - Merged changes from branches\referencing-canceled-trains: New element added to , closes #308 (closed)
### Documentation Tasks
* Document the changes for 2.4
* Update the wiki pages for `NEWELEMENT` and `NEWELEMENT`
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany