| Re: Signal characteristics (de: Signaleigenschaften) [message #1817 is a reply to message #1764] |
Wed, 30 May 2018 15:42   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
thank you for your feedback. So, you seem to be the first one to use the
attribute <signal>@sigSystem. Congratulations ;-)
OK, for the purpose of distinguishing between conventional signals and
ETCS marker boards, it is suggested to make use of the sub-element
<signal><etcs>. In particular, use
<signal ...>
<etcs switchable="false" .../>
</signal>
for modelling an ETCS markerboard, and use
<signal type="main" ...>
</signal>
for modelling a conventional main signal.
What do you think about that solution?
Am 14.04.2018 um 15:34 schrieb Torben Brand:
> [...]
> <signal @sight>
> We do not use this in our use cases. But I know that Bane
> NOR will need to map the sight distance towards a signal in
> railML2.3nor for the use case signal planning.
I suggest to discuss with the interlocking community whether signal
sight shall be considered as a single value in signal related
interlocking information or whether it is necessary to have this signal
sight mapped to the railway network, e.g. as an area.
Anybody else being interested in <signal>@sight or its content?
Thanks and regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
