Home » railML newsgroups » railML.infrastructure » Modeling LevelTransitions
Modeling LevelTransitions [message #3698] Fri, 15 August 2025 18:31
Silvan Gruber is currently offline  Silvan Gruber
Messages: 11
Registered: July 2024
Junior Member
Dear railML-experts,

From the SBB perspective, the following information is relevant for modeling level transitions:

Location of the levelTransition and its applicationDirection
  • Can be mapped with etcsLevelTransition.spotlocation... => OK
switch to ETCS Level
  • Can be mapped with etcsLevelTransition.switchToLevel... => OK
Length of the acknowledgment area for the level transition
  • Can be mapped with "etcsLevelTransition.switchToLevel@lengthOfAcknowledgement". If no acknowledgment window is to be configured, the attribute is not listed.
  • Question: Is it necessary to specify different lenghts of acknowledgment areas depending on "switchToLevel"? Otherwise, "lengthOfAcknowledgement" could be specified as an attribute of "etcsLevelTransition."
Level Change Announcement Distance
  • The announcement distance is the distance before the level transition, from which the RBC transmits P41 (levelTransitionOrder) with "D_LEVELTR=x" metres (as soon as a vehicle sends a TPR within this distance to the level transition and the route is set over the level transition). This distance cannot be mapped with railML3.3. In Switzerland, the announcement distance is chosen so that the levelTransitionOrder only takes effect 50 meters behind the levelTransition. This measure prevents a vehicle from changing levels before the leveltransition due to odometry inaccuracies. Therefore, an offset value must also be available for the announcement distance.
  • Question: What do you think about introducing an attribute such as "lengthOfAnnouncementByRBC" [metres] for the "etcsLevelTransition" element?
TransmittedBy
Packet 41 is sent at the following locations:
  • RBC sends P41 when a vehicle sends a TPR within the level transition announcement distance and the route across the levelTransition is set
  • Balise with L0 announcement
  • Border balise at levelTransition (with D_LEVELTR="now")
Notice: It is unclear how the "isTransmittedBy" attribute should be understood in this context, since P41 is sent by different elements depending on the situation. Thus, if a balise group sends P41, it is mapped using baliseGroup.functionalType@value="announcementLevelTransition ". The information in "isTransmittedBy" would be redundant in this situation.


Best regards

Silvan


/forum/index.php?t=getfile&id=179&private=0






/forum/index.php?t=getfile&id=178&private=0








[Updated on: Fri, 15 August 2025 18:34]

Report message to a moderator

Previous Topic: [railML3] Proposal of a semantic constraint for <baliseGroup>
Next Topic: Not navigable netrelations and crossings
Goto Forum:
  


Current Time: Wed Jun 17 06:11:54 CEST 2026