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
  • #190
Closed
Open
Issue created Nov 12, 2012 by Deleted User@deleted-user

Pre-Signalised speed aspects

The aspect of "pre-signalised speed changes" left from the speed profile enhancement (#41 (closed) comment:21).

One approach is to define speed signals (panels) that "announce" the speed change with a reference to the appropriate speed change. It the information about this "announcement panel" is known there would be no problems to deduce the "signalised" information.

On the other hand there may be software tools that don't know about the actual panel positions but know about the information "the speed change is pre-signalised in any way".

How may railML handle both approaches in a proper matter?

See also the forum thread for further discussion:

http://www.railml.org/forum/ro/?group=1&id=213

Assignee
Assign to
Time tracking

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