| Panels in general (was: Speed Panels: types and reference to <speedChange>) [message #451 is a reply to message #432] |
Tue, 13 November 2012 10:37   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
>>> In the trac ticket [2] I proposed the
>>> following categories and ask for your approval/denial/addition:
>>>
>>> - speed,
>
> As you mentioned in your example, it may look like this:
> <speedSignal kind="announcement" switchable="false" speedChangeRef="sc1" />
Quite fine. I would name it only 'speed' because it's some child element
of a 'signal' element. That hint could be rolled out for all of the
following examples.
>>> - etcs,
>>
>> * Fixed marker boards
>>
>> * light signals indicating a new movement authority (for ETCS level 1)
>>
>> * (level crossing signals), likely don't exist
>>
>> * no balises or balise groups, but they may transfer the "traditional
>> signal aspect" as "speed restriction for a certain range".
>
> Example:
> <etcsSignal kind="execution" switchable="false" level="1" />
Sorry, if you tried to describe the marker boards, a marker board is not
ETCS-level-specific.
>>> - levelCrossing,
>>
>> several kinds of signals for ringing the bell, whistle, announcing,
>> activating the level crossing ...
>
> Example:
> <levelCrossingSignal type="whistle" />
How about the 'levelCrossingRef'?
>>> - gsm,
>>
>> more general: trainRadio
>>
>> * fixed train radio signals indicating a channel
>>
>> * fixed GSM signals indicating an GSM-R-equipped area, also the
>> negation indicating a non-GSM-R-equipped area, maybe with an
>> attribute to "enter"/"leave", also used for a "radio hole"
>
> Example:
> <trainRadioSignal switchable="false" type="enter" />
How about a "trainRadioRef'?
Yes, we need such an element in 'trackElements' for indicating GSM-R
and/or analogue train radio with specified channels/frequencies. [1]
>>> - catenary
>>
>> * no catenary section
>>
>> * no current section / main power switch off
>>
>> * lower pantograph section
>>
>> * additional signal (de: ICE-Schaltmerkhilfe)
>
> Example:
> <catenarySignal type="lowerPantograph" />
How about a 'trackConditionRef' instead of the 'type' attribute in order
to reduce redundancy?
>> - line
>>
>> * indicating the line number
>
> Example:
> <lineSignal lineNumber="1234" />
Please don't repeat the elements name in the attribute: 'code' would be
fine. Maybe some country uses combinations of numbers and letters for
their lines.
>> - milepost (de:Hektometertafel)
>>
>> * indicating the mileage of a track, often fixed at a pole
>
> Example:
> <milepostSignal value="42.0" />
The mile post needs at minimum two values, one is printed large and one
(the correction) is printed in small letters.
>> - braking
>>
>> * non-stopping section
>>
>> * no regenerative braking
>>
>> * no eddy-current braking
>>
>> * no magnetic-shoe braking
>
> Example:
> <brakingSignal type="nonStoppingSection" />
How about a 'trackConditionRef' instead of the 'type' attribute in order
to reduce redundancy?
Christian, would you please summarize this thread and update the Trac
ticket? [2]
[1] http://trac.assembla.com/railML/ticket/43
[2] http://trac.assembla.com/railML/ticket/173
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
