Home » railML newsgroups » railML.infrastructure » [railML3.3] Signal combinations
Re: [railML3.3] Signal combinations [message #4110 is a reply to message #4107] Wed, 19 August 2026 08:18 Go to previous messageGo to previous message
Dominik Looser is currently offline  Dominik Looser
Messages: 66
Registered: March 2020
Member
Hi Thomas,

This is an example of how we export a combination of two signals (an ETCS marker board and a shunting signal) in railML 3.3, in accordance with [1]. 

<signalIS id="sig4_C">
  <spotLocation applicationDirection="normal" id="sig4_C_ips01" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <spotLocation applicationDirection="normal" id="sig4_C_sloc01_km" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="lps01"/>
  </spotLocation>
</signalIS>
<signalIS belongsToParent="sig4_C" id="sig4" isSwitchable="false">
  <name language="no" name="mb"/>
  <spotLocation applicationDirection="normal" id="sig4_ips01" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <spotLocation applicationDirection="normal" id="sig4_sloc01_km" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="lps01"/>
  </spotLocation>
  <typeDesignator entry="E35a" rulebook="TJN"/>
  <elementState value="planned"/>
  <isEtcsSignal/>
  <isTrainMovementSignal/>
</signalIS>
<signalIS belongsToParent="sig4_C" id="sig5" isSwitchable="true">
  <name language="no" name="sh"/>
  <spotLocation applicationDirection="normal" id="sig5_ips01" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="ips01"/>
  </spotLocation>
  <spotLocation applicationDirection="normal" id="sig5_sloc01_km" netElementRef="ne_3">
	<linearCoordinate lateralSide="right" measure="143.0" positioningSystemRef="lps01"/>
  </spotLocation>
  <typeDesignator entry="skift" rulebook="_ETCS"/>
  <elementState value="planned"/>
  <isEtcsSignal/>
  <isTrainMovementSignal/>
</signalIS>

Having a @sequence on <linearLocation>, or having one on <spotLocation>, is not very helpful, since all signals of a combination have the same <spotLocation>.
I think we need something like @sequenceInCombination or @mountingOrder, which could be an attribute of <signalIS> or <signalIS>/<signalConstruction>


Best regards,
Dominik Looser, trafIT solutions gmbh

[1] https://www.railml.org/forum/index.php?t=getfile&id=147& amp;

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
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How do you model operational points inside operational points in mesoscopic topology?
Next Topic: [railML3] @lateralSide and @verticalSide and distances
Goto Forum:
  

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

Current Time: Fri Oct 16 17:10:20 GMT+2 2026