Home » railML newsgroups » railML.infrastructure » [railML3] Extensions to the Modelling of Signals (Two more options related to the physical location of signals)
Re: [railML3] Extensions to the Modelling of Signals [message #3869 is a reply to message #3750] Thu, 15 January 2026 15:33 Go to previous messageGo to previous message
Dominik Looser is currently offline  Dominik Looser
Messages: 64
Registered: March 2020
Member
Hi,

I agree with the implementation of "topic 1".

I think that "topic 2" is technically the combination of "topic 1" and "combined signals" as discussed in [1].
The attachment in [1] states that combined signals - i.e. signals on the same pole - should be exported separately but also have an additional <signalIS> used as container. The individual signals would point to the container via the @belongsToParent attribute.
This has been introduced in railML 3.3 and implemented in our export.
"Topic 2" could thus be modelled as combined signals, but the <signalIS> used as container would have two <spotLocation> elements.

Example as proposal:

sig4 and sig5 are the two signals. sig4_C is the container for both signals, containing the two spotLocations of sig4 and sig5

<signalIS id="sig4_C">
  <spotLocation applicationDirection="normal" id="sig4_C_ips01" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="87.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <spotLocation applicationDirection="normal" id="sig5_ips01" netElementRef="ne_4">
	<linearCoordinate lateralSide="left" measure="50.0" positioningSystemRef="ips01"/>
  </spotLocation>
</signalIS>
<signalIS belongsToParent="sig4_C" id="sig4" isSwitchable="false">
  <spotLocation applicationDirection="normal" id="sig4_ips01" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="87.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <typeDesignator entry="E35d" rulebook="TJN"/>
  <elementState value="conceptual"/>
  <isEtcsSignal/>
  <isTrainMovementSignal/>
</signalIS>
<signalIS belongsToParent="sig4_C" id="sig5" isSwitchable="true">
  <spotLocation applicationDirection="normal" id="sig5_ips01" netElementRef="ne_4">
	<linearCoordinate lateralSide="left" measure="50.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <typeDesignator entry="E35d" rulebook="ETCS"/>
  <elementState value="conceptual"/>
  <isEtcsSignal/>
  <isTrainMovementSignal/>
</signalIS>

Additional information like <signalConstruction> can still be added.

Looking forward to your thoughts on this.

Best regards,
Dominik Looser
trafIT solutions gmbh

[1] https://www.railml.org/forum/index.php?t=msg&goto=3202&a mp;&srch=combination#msg_3202

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Modelling serviceSections
Next Topic: [railML3] Additional Switch attributes
Goto Forum:
  

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

Current Time: Wed Sep 09 15:02:38 CEST 2026