| Re: Double switch crossing: 'crossingRef' attribute for the fictive switches [message #337 is a reply to message #332] |
Thu, 05 July 2012 06:12   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Pierre,
> With the current standard (railML 2.1), the way of modelling a double
> switch crossing implies to create fictives elements (4 switches and 2
> tracks).
the way of modelling a simple or double switch crossing using railML,
which you describe, is not the only one. The other - more macroscopic
view - specifies a <crossing> element with the type attribute
"simpleSwitchCrossing" or "doubleSwitchCrossing". In that case, there is
only one element and a referencing is not necessary.
However, your approach of defining several switches and a crossing for a
simple/double switch crossing as a combined element is much closer to a
real node-edge model.
> For post-processing purpose, we suggest to add a 'crossingRef' attribute
> to the fictives switches, so that after parsing it could be considered as
> one single element.
Until now, it is not possible to explicitly group elements like switches
being parts of a simple/double switch crossing. The proposed attribute
"crossingRef" may close this gap and if we define this attribute being
optional, it is possible to implement it with railML version 2.2.
Before creating a trac ticket dealing with that issue, I would like to
ask the other users of railML infrastructure schema for their opinion
about the "crossingRef" attribute. Any comments appreciated....
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
