Re: Identical signal representation [de:Gruppenausfahrsignal] [message #335 is a reply to message #327] |
Wed, 04 July 2012 20:33 |
Christian Rahmig
Messages: 151 Registered: January 2011
|
Senior Member |
|
|
Hello Pierre,
> Hello, I'm Pierre Simon and I work for Infrabel which is responsible of
> the railway infrastructure in Belgium. We are developping a software for
> helping in the installation of the ETCS1 on the belgian railway. That's
> why we are now joining the railML community.
welcome to the railML infrastructure forum. It would be interesting to
hear more about your application of the railML schema at the next railML
meeting in Zurich, Switzerland, on November 14.
> The first subject is : The representation of the identical signal
>
> Usually, identical signals are installed at the exit of a grill
> (de:GleisHarfe). They are visible for the driver if the train is in the
> grill or even if it is on the main track.
> We suggest to duplicate this signal for all the tracks where the driver
> will see the signal and add an attribute ('identicalSignal') to refer
> signals between each other. (Apparently this kind of signal is at least
> used in Belgium, Germany and Czech Republic).
If we have a look at the real (installed) infrastructure, only one
signal (common signal) exists whereas the "signal duplicates" can be
classified as virtual signals: They repeat the common signal's
information, but cannot be found in the real infrastructure. So, one
option would be to allow for such virtual signals and define an
attribute "virtual" of type boolean. As you proposed, another attribute
"identicalSignal" or "signalRef" may be used to refer to an existing signal.
But since there are quite a few objections regarding virtual
infrastructure objects I would like to ask the other users: What do you
think about virtual signals?
Regards
---
Christian Rahmig
railML.infrastructure coordinator
|
|
|