| Re: Speed Panels: types and reference to <speedChange> [message #398 is a reply to message #346] |
Wed, 24 October 2012 15:29   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Pierre and other railML users,
> the <speedPanel> element within its container <speedPanels> is a special
> type of a panel and therefore implemented within the <panels> container
> in <ocsElements> with railML 2.2 as described in the post [1].
in the meantime the ongoing discussion in thread [1] agreed on combining
signals and panels in the <signal> element. For distinguishing between
(static) panels and (switcheable) signals the boolean parameter
"switcheable" has been introduced.
> The definition of various speed panel types is a good extension to the
> panel concept. It can be either realized by defining a new parameter
> "speedPanelType" having the values 'announcement', 'execution' and
> 'reminder' or by setting up boolean parameters for each type, i.e.
> "announcementPanel",
> "executionPanel" and
> "reminderPanel".
With the definition of <signalAspect> sub-elements within <signal>,
which may also include panel information, it is useful to rename the
boolean parameters into "announcement", "execution" and "reminder" and
put them in the <signalAspect> element.
>> In order to make the connection with the speed profile on the tracks, a
>> reference from the <speedPanel> to the <speedChange> is needed.
>>
> As you correctly mentioned, speed panels may refer to actual speed
> changes, e.g. at a speed restriction section. I suggest a parameter
> "speedChangeRef" within the element <speedPanel>, which refers to the ID
> of a <speedChange> element.
>
> However, this concept of referencing other elements may be applied to
> other types of panels as well. In particular, catenary panels may refer
> to <electrificationChange> elements or levelcrossing panels can link to
> <levelCrossing> objects.
In the proposed implementation, which is described in trac ticket [2],
the parameter "elementRef" is introduced for the <signalAspect> element.
Depending on the above mentioned boolean parameters defining the type of
the signal aspect, the appropriate infrastructure element can be
referenced, e.g. a <speedChange>.
[1] http://www.railml.org/forum/ro/?group=1&id=148
[2] https://trac.assembla.com/railML/ticket/173
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
