Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal signal types and functions (railML 2.3 infrastructure extension proposal signal types and functions)
railML 2.3 infrastructure extension proposal signal types and functions [message #1461] Tue, 20 December 2016 18:34 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 157
Registered: March 2016
Senior Member
Dear railML infrastructure forum,
This posting contains the discussion to an extension towards the
signal
We need to model all relevant signals to the use case according to Norwegian law ( https://lovdata.no/dokument/SF/forskrift/2008-02-29-240/KAPI TTEL_9#KAPITTEL_9Wink.
This is done through extending the type (5 new values) and function (2 new values) attributes. The defined combination of type and function form the specific signals in Norway, but are considered universal. So the terms are in English.
There are two Norwegian specific signals that are part of a type main signal and are thus defined in new sub elements under signal in Norwegian.
The new values for the attribute @type under element <signal> are:
• "danger"
Used in Norway for signals that indicate that an avalanche fence has been broken. We chose a more generic description for warning signs in general. Other examples that fit the specification could be: cross wind signals. If there is a need to further distinguishes a type of danger signal I suggest using a later added sub element or extended value range of function.
• "derailer"
Indicates if the derailer has blocked the track.
• "switch"
Indicates the position of the switch.
• "trackIndicator"
Repeats (only) to the conductor the state of the main-exit signal. This is a different signal than a type repeater signal (that is valid for the train driver).
• "road"
Road side signals not valid for the train driver. But contained in schematic drawings.
The new values for the attribute @function under element <signal> are:
• "area"
Signals that are valid for a (undisclosed) area and not a signal route.
• "levelCrossing"
Defines either a type main/distant/road. Further attributes to be found in existing sub element <levelCrossing>
The new sub elements under element <signal> are:
• <NO:forsiktigKjøring>
Sub signal under type main and function home or intermediate. Used for shortened signal routes or dead end tracks.
• <NO:middelkontrolllampe>
Sub signal under type main and function exit or intermediate to indicate that the train is within the clearance point.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML 3.x - NTSM use case organisational/contact data
Next Topic: railML 2.3 infrastructure extension proposal - locks
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Apr 25 18:23:48 CEST 2024