| Re: Panels in general [message #482 is a reply to message #451] |
Mon, 03 December 2012 13:56   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Susanne and other railML users,
regarding the recent aspects mentioned within this forum thread, I
updated the Trac ticket [1] with the following aspects:
- In the implementation of railML 2.2 a <signal> contains exactly one
signal information. Therefore, in case of several signals/panels on one
pole, several <signal> elements need to be defined.
- For the different types of signal information, we propose
signals/panels for speed, etcs, levelCrossing, trainRadio, catenary,
line, signpost. They are modelled as sub-elements of signal.
- All the signal information sub-elements do not inherit the
parameters "id", "name" and "code" since they are already given by the
parent signal element.
- All the signal information sub-elements contain a boolean parameter
"switcheable", which allows for distinguishing between fixed (panel) or
switcheable (e.g. light signal), signal information.
- A <speed> signal information further contains the parameters "kind"
(values: announcement, execution and end) and "speedChangeRef".
- A <etcs> signal information further contains the parameter "level"
with values '1', '2' and '3'.
- A <levelCrossing> signal information further contains the parameters
"type" (values: 'bell', 'whistle', 'announcing' and 'activating') and
"levelCrossingRef".
- A <trainRadio> signal information further contains the parameter
"trackConditionRef", which refers to a <trackCondition> where the
attribute type allows for the value 'radioHole'.
- A <catenary> signal information further contains the parameter
"trackConditionRef", which refers to a <trackCondition> where the
attribute type allows for the values 'lowerPantograph' and
'mainPowerSwitchOff'.
- A <line> signal information further contains the parameter
"lineRef", which refers to a <line> element.
- A <milepost> signal information further contains the parameters
"shownValue" and "realValue".
- A <braking> signal information further contains the parameter
"trackConditionRef", which refers to a <trackCondition> where the
attribute "type" allows for the values 'nonStoppingSection',
'noRegenerativeBraking', 'noEddyCurrentBraking', 'noMagneticShoeBraking'.
- All the signal information sub-elements contain the "any" attribute.
[1] https://trac.assembla.com/railML/ticket/173
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
