Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory stop at level crossing (Still a topic for railML 3?)
[railML3] Mandatory stop at level crossing [message #3330] Fri, 04 October 2024 17:09
christian.rahmig is currently offline  christian.rahmig
Messages: 474
Registered: January 2016
Senior Member
Dear all,

in Gitlab ticket #100 [1] we discussed how to model the mandatory stop at a level crossing. For railML 2.4 we based the solution on the element <speedChange>. For details, please see [1].

For railML 3.x, we said that it would be better to have an independent object for a railway vehicle stopping place to be referenced. Well, this element exists in terms of <stoppingPlace> being part of the functional infrastructure [2]. It is possible to specify the stopping place being relevant only for certain trains (e.g. axle count, wagon count or train length) and it can be linked with a platform edge. Additionally, you can specify that the stopping place is being signalized. A specific linking with a level crossing is missing so far.

If there is any urgent need for having this link being modelled with upcoming railML 3.3, please answer asap on this forum posting. Otherwise, I will postpone the ticket for version 3.4 (or later depending on your needs).

Any feedback is highly appreciated...

[1] https://development.railml.org/railml/version3/-/issues/100
[2] https://wiki3.railml.org/wiki/IS:stoppingPlace

Best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Proposal of a semantic constraint for <baliseGroup>
Next Topic: [railML 3.2] extending the <balise> element
Goto Forum:
  


Current Time: Thu Dec 05 15:29:21 CET 2024