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
  • #334
Closed
Open
Issue created Jun 20, 2018 by Deleted User@deleted-user

Different station tracks in one <ocpTT> for different <operatingPeriod>s (de: Saisonierte Gleisbenutzung)

Description

Discussion during the last TT development meeting: It shall be possible to specify different station tracks for one ocpTT.

Background

The topology reference is similar to the designator register for an ocp which allows the receiving system to retrieve additional information from an external register.

Please note, that the actual topology is not part of the railML file and must exist in or be accessible to the receiving system.

Links

  • Forum discussion
  • Christian Rößiger (iRFP) (de/en), January 2016: Different station tracks in one for different s
  • Dirk Bräuer, 23.09.2017: addendum to in railML2.4
  • Wiki Documentation
  • https://wiki.railml.org/index.php?title=TT:trackInfo

Changes in railML 2.4

A cancelled train or trainPart is written to the railML file including all regular attributes and elements. The `@NEWATTRIBTE` attribute with a value of 'true' allows the importing system to process this information accordingly - e.g. to inform passengers of a cancellation.

railML elements

The following new attributes are available:
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference `
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference/@register `
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference/@entry `
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference/@startDate `
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference/@endDate `
 1. ` railml/timetable/trains/train/trainPartSequence/topologyReference/@any##other `
The following XSD file(s) have been updated:
 1. timetable.xsd
 1. timetableTypes.xsd
The following codelist XML file(s) have benn updated:
 1. Registers.xml

Changesets in trunk

  • [changeset:"804/railML"] - adding changes related to topic "different station tracks in one for different s" (de: saisonierte Gleisbenutzung), see #334 (closed)

Documentation Tasks

  • Document the changes for 2.4
  • Update the wiki pages
Assignee
Assign to
Time tracking

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