Home » railML newsgroups » railML.infrastructure » [railML2] Single and double derailer (Proposal for modeling of single and double derailers in railML2)
[railML2] Single and double derailer [message #2983] Thu, 31 March 2022 10:27 Go to next message
Georg Boasson is currently offline  Georg Boasson
Messages: 18
Registered: October 2020
Junior Member
We suggest using the @kind to describe this:

- derailerConnectedToInterlocking
- doublerDerailerConnectedToInterlocking
- derailerWithLock
- doubleDerailerWithLock

Further we also need to define the preferred position of the derailer, we suggest:

derailer@nor:preferredPosition: "passablePosition" and "derailingPosition"


See #2906 for railML3 modelling of double derailer ( https://www.railml.org/forum/index.php?t=msg&th=855& start=0&)

Report message to a moderator

Re: [railML2] Single and double derailer [message #3011 is a reply to message #2983] Fri, 10 June 2022 12:16 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Georg,

thank you very much for your input related to requirements for a more detailed model of derailers in railML 2. As you know, we enhanced the derailer in railML 3.2. This includes the differentiation between single and double derailers via <derailerIS>@type and the default/preferred position of the derailer via <derailerIL>@preferredPosition.

For railML 2 I appreciate a solution that is very close to the modelling approach in railML 3.2. Therefore, I suggest not to use the already existing attribute <derailer>@kind as its values are defined according to the Railway Compendium "Railway Signaling and Interlocking" by Gregor Theeg: "blockDerail", "singleCatchPoints" and "doubleCatchPoints". In particular, I suggest the following approach:

* add new attribute @type with values "singleDerailer" and "doubleDerailer"
* use existing attribute @lockRef to link the derailer with a lock
* add new attribute @preferredPosition with values "derailingPosition" and "passablePosition"
* add new attribute @controllerRef to link the derailer with a controller element (interlocking)

Does this approach cover all your needs?
What does the community think about the need for a more detailed derailer model in railML 2?
Or is it sufficient to have a detailed derailer model implemented in railML 3?

Any comments are highly appreciated...

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: [railML2] bridge type
Next Topic: [railML3]crossesElement/[railML2.5]crossedElement
Goto Forum:
  

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

Current Time: Thu Apr 25 22:18:55 CEST 2024