Home » railML newsgroups » railML.infrastructure » Question towards use of @passable attribute (2.4) (@passable)
Question towards use of @passable attribute (2.4) [message #2038] Thu, 13 December 2018 10:15 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 165
Registered: March 2016
Senior Member
The attribute @passable under IS:connection switch and IS:connection crossing (v2.4) is not documented in the wiki at all! I found a very short (and old) topic in the forum.

Does anyone in the community use @passable and if yes, how do you use it?

IS:connection switch wiki page: https://wiki.railml.org/index.php?title=IS:connection_switch
IS:connection crossing wiki page: https://wiki.railml.org/index.php?title=IS:connection_crossi ng
Forum topic "passable connections": https://www.railml.org/forum/index.php?t=msg&th=54&g oto=120&#msg_120

[Updated on: Thu, 13 December 2018 10:16]

Report message to a moderator

Re: Question towards use of @passable attribute (2.4) [message #2045 is a reply to message #2038] Wed, 19 December 2018 10:05 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 165
Registered: March 2016
Senior Member
As we have not received a reply to the question, I would suggest to build upon the solution suggestion described in the forum posting from 2004 and extend it with the following:

@passable: Denotes if you can pass between the track the switch/crossing is placed on (the principal track; usually straight) and the track connecting to the switch/crossing (the diverging track).
As the movement possibilities are given for a fully functional switch ("true"), a simple crossing ("false" and "false") and a double switch crossing ("true" and "true) the passable does not need to be defined there.
For fully functional switches/crossings only use @passable for each of the IS:crossing connection of a crossing@type="simpleSwitchCrossing" (single slip switch) with either the value combination "true" and "false" or "false" and "true".
 
Furthermore I suggest to be able to set a switch/crossing inn a reduced state in railML.
The use case for this is, when you pad(lock) a switch/switch crossing, you can still run over it in the set direction.
It would be useful to know if the switch/crossing is (pad)locked and in which position it is locked.
For this scenario we suggest to use the combination of state@disabled=true and passable=true/false under the switch/crossing element.
As there is no passable defined in railML for passing over the switch/crossing on the track the switch is placed on (the principal/straight track). But as the switch (or switches in the crossing) can only have one position, this is implicit given through the @passable="true"/"false" of the switch connection (the diverging track) .

[Updated on: Wed, 19 December 2018 10:14]

Report message to a moderator

Re: Question towards use of @passable attribute (2.4) [message #2046 is a reply to message #2045] Wed, 19 December 2018 13:34 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 165
Registered: March 2016
Senior Member
I have posted the suggested changes to be made in the discussion page of the relevant wiki pages:
https://wiki.railml.org/index.php?title=Talk:IS:connection_s witch
https://wiki.railml.org/index.php?title=Talk:IS:connection_c rossing
Re: Question towards use of @passable attribute (2.4) [message #2085 is a reply to message #2046] Fri, 11 January 2019 12:08 Go to previous message
Ferri Leberl is currently offline  Ferri Leberl
Messages: 24
Registered: September 2016
Junior Member
Dear Mr. Brand,
I have added the suggested content to IS:connection_switch and IS:connection_crossing.
As to avoid misconceptions, I have deleted the texts on the discussion pages.
I hope, the changes are to your satisfaction.
Yours, Ferri Leberl
Previous Topic: How to model ETCS BL2 speed restrictions and gradients, in railML v2.x
Next Topic: Redefine the use of signal@ocpStationRef (railML2.4)
Goto Forum:
  


Current Time: Thu Oct 31 23:46:17 CET 2024