Home » railML newsgroups » railML.infrastructure » [railml3] Signal types and functions
Re: [railml3] Signal types and functions [message #2147 is a reply to message #2146] Mon, 18 February 2019 14:36 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 474
Registered: January 2016
Senior Member
Dear Torben,

Am 18.02.2019 um 11:26 schrieb Torben Brand:
> [...] I would suggest grouping all signal in
> standard sub elements. These can of course be extended.

Sounds good, let's have a look at the issue in detail and combine it
with a proposal:

> [...]
> Suggested signal sub elements (groups of signals):
> •    Announcement:  Announcement by the train of its
> presence. Can be with different signals. Usually blowing the
> whistle (boolean value). Can be defined for one or multiple
> purpose (boolean: levelCrossing, halt, etc.)

<isAnnouncementSignal>
@type = {"whistle", "horn", ...}
@refersToElement = {reference to level crossing, halt, etc.}

> •    Border:  Indicating a level transition. Type start/end.
> The system attribute defines the type of level transition
> (ATC,CTC, ETCS, Conventional/optical).

<isSystemBorderSignal>?

> •    catanary

<isCatenarySignal>
.... have it already

> •    danger:  grouping all types of warning signals:
> avalanche, wind, frost gate, bridge, etc.

<isDangerSignal>
Is a fouling point (clearance post) also a danger signal?

> •    gradient:  indicating falling/rising gradient and other
> info.
> •    Info:  general design info. Like arrows, invalid boards,
> and info panels.

summarize both in <isInformationSignal>

> •    level crossing

<isLevelCrossingSignal>
.... have it already

> •    main:  all route related signals
> •    movement:  all signals giving an indication of the
> movement that are not main or shunting signals (line
> signals, derailers, switch and crossing indicators)

<isTrainMovementSignal>
This includes main signals, distant signals, repeaters...

> •    plow:  orders for handling the equipment on the train.
> Here the plow.

<isVehicleEquipmentSignal>?
@type = {snowplowUp, snowplowDown, ...}

> •    Position:  mileposts and distance signals (f.i. to level
> crossings)

<isPositionSignal>
@refersToPositioningSystem
@isMilepost

> •    Shunting:  shunting related signals

integrate in <isTrainMovementSignal>
Some countries don't distinguish between shunting and train movements.

> •    Speed

<isSpeedSignal>
.... have it already

•    stop post

<isStopPost>
.... have it already

Best 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
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Embedded methods in objects
Next Topic: ]railMLv3]: switch referece point
Goto Forum:
  


Current Time: Thu Dec 05 13:18:04 CET 2024