Home » railML newsgroups » railML.infrastructure » [railML3.3] Signal combinations
Re: [railML3.3] Signal combinations [message #3225 is a reply to message #3112] Wed, 10 April 2024 17:14 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 123
Registered: March 2016
Senior Member
Dear all,

the modelling of several signals at one position (one pole) shall be as in the attached graphic.
In interlocking there is one SignalIL element for each different signal referring to an individual counterpart in infrastructure.
In infrastructure there is one SignalIS element for each different signal type. Each is referring with "belongsToParent" to a SIgnalIS element as the container for all signals at this point. The container carries the information of the mechanical construction and the position which is common for all the signals at this mount point.

As explained in https://development.railml.org/railml/version3/-/issues/533 the basic signal type is included in isTrainMovementSignal element. Whereas the interlocking function is defined in SignalIL.

There is the proposal to add attribute "withShuntingFunction" as boolean in SignalIL. This shall be used as a marker that this signal (IS type=main, IL function=entry|exit|intermediate|group|junction) can be start or end of a shunting route, i.e. shows a shunting aspect. This is especially useful for ETCS markerboards for main and shunting routes as we decided to deprecate the function "main+shunting" in SignalIL.
--
Best regards,
Joerg v. Lingen - Interlocking Coordinator

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 3.4 bèta 2] misuse of designator
Next Topic: suggestion for switchIS@type="crossingPart"
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Aug 09 18:49:17 CEST 2026