| Re: Identical signal representation [de:Gruppenausfahrsignal] [message #340 is a reply to message #335] |
Thu, 05 July 2012 13:35   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Hello Pierre and Christian,
>> 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).
> 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?
I agree with Pierre that an additional information is necessary in the
tracks for which a "group starter" [Gruppenausfahrsignal] is valid. At
another infrastructure model we also had such "group starter stopping
place" [Gruppenausfahrhalteplatz] elements.
At lest they tell a train entering the track where to stop (they are not
allowed to proceed until the main signal fouling the points).
Additionally, they tell a train which is ready to depart from the train
that the "group starter" is valid and, again, that it is not allowed to
proceed until the "group starter" is cleared for that train.
---
So, we do need a virtual element there but I would not call it
'identicalSignal'. I would also not call it "group starter stopping place"
[Gruppenausfahrhalteplatz] in RailML which sounds a little bit too
special. But from my opinion, it is more a kind of stopping place than an
additional signal.
In some cases and some countries, there a marker boards at these places
(H-Tafeln in Germany, Fahrtstellungsmelder 559 in Switzerland, marker
boards in UK). In these cases, one could say that we wouldn't need the
virtual "group starter stopping place" because it follows from the real
existing marker board which should be an element elsewhere in the RailML
file. In my opinion, it should be left to the writing program to add the
virtual element at the same place (meter) of the real marker - just to
describe the function.
If we have a possibility to describe a stopping place ("H-Tafel") in
RailML - which we should have - we could use that and add a property
"virtual". This fits to the discussion on <stopPosts> earlier that year.
So, my suggestion is:
- to define a <stopPost> as optional virtual,
- to allow an optional cross-reference from a <stopPost> to a main signal.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
