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
  • #173
Closed
Open
Issue created Oct 24, 2012 by IS Coordination@coordination.ISMaintainer

Signals and Panels

The current implementation of signals is not sufficient for a practical usage. In particular, it is currently not possible to distinguish between light signals and panels/signposts showing static information. In the forum threads [http://www.railml.org/forum/ro/?group=1&id=148] and [http://www.railml.org/forum/ro/?group=1&id=149] this subject has been discussed and the following aspects are derived:

  • It is better to modify the element signal instead of introducing a new element panel, because often combinations of switcheable and non-switcheable signals/signal elements exist.

  • The element signal resembles a physical unit, which is situated (with orientation) next to the track and therefore contains the attributes pos, direction and optionally also the sub-element geoCoord as already implemented.

  • A signal may show several signal aspects, which are defined in signalAspect sub-elements.

  • A signal aspect can be identified via its parameters id, name and code, which are inherited from the type "tElementWithIDAndName".

  • A signal aspect may be fixed (panel) or switcheable (e.g. light signal), which is modelled with the boolean parameter switcheable.

  • A signal aspect may refer to a certain functionality. It is proposed to group these funcionalities into speed, etcs, levelCrossing, gsm, catenary and signalingSystem and to refer to these groups using the parameter type.

  • A signal aspect with type="speed" may refer to a certain speed change on the track. For providing this reference, the parameter elementRef of type "tGenericRef" can be used.

Further attributes for signals, signal aspects or signal frames are considered to be more related to an interlocking point of view on signals and therefore momentarily discarded.

Here is a short example of a signal showing two signal aspects:

<signal id="s01" pos="42.0" type="main">
   <signalAspect id="s01a01" switchable="true" type="block">
   </signalAspect>
   <signalAspect id="s01a02" switchable="false" type="speed" elementRef="sc01">
   </signalAspect>
</signal> 
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