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
  • #116
Closed
Open
Issue created Mar 23, 2011 by Deleted User@deleted-user

Rostering restrictions for timetable data (de: Umlaufbindung)

In verschiedenen Kontexten wie folgt bezeichnet: Durchbindung, Zwangsbindung oder Wendevorgabe

Christoph Jobmann suggested enhancing timetable data with some rostering restrictions not defining a fully valid rostering schema.

see German discussion following http://www.railml.org/forum/ro/index.php?group=2&id=148

Edited Dec 13, 2021 by Administrator
Assignee
Assign to
Time tracking

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