Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal operational properties of an OCP (railML 2.3 infrastructure extension proposal operational properties of an OCP)
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP [message #1583 is a reply to message #1466] Thu, 18 May 2017 17:51 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian and Torben,

>> The attribute @operationalType is extended with the value
>> "siding". In Norway a "siding" is an additional track on the
>> path (section of line between stations). It is not a station
>> according to Norwegian definition as it does not have a
>> main-home signal. Thus the path on the siding needs to be
>> blocked during the operation of entering and leaving the
>> siding. PS. There is a trackType under track with value
>> "sidingTrack" This is described in the Wiki as: "This is a
>> siding"
>
> Yes, railML already allows to specify a track as being a siding track by
> setting <track type="sidingTrack">. However, what is missing is an
> operational representation of the siding as you request it. Therefore,
> your suggestion to add the enumeration value "siding" for the attribute
> @operationalType seems to be valid. Is there anybody among the railML
> community who needs to model sidings outside of stations, too?

Yes, of course. In Germany (and other countries), we have the same type
of sidings. In Germany they are called Anschlussstelle und
Ausweichanschlussstelle depending on interlocking and operational rules.
It is an <ocp> but not a station. In both cases, the line track has to
be blocked between the adjacent stations during the operation of
entering and leaving the siding.

Currently we model such an <ocp> as follows:

<ocp id=...>
<propOperational orderChangeable='false'
ensuresTrainSequence='false' />
<propService goodsLoading='true'/>
<propEquipment>
<summary hasHomeSignals='false' hasStarterSignals='false'/>
</propEquipment>

We do not model the siding itself since there can be no train operation
at it (just shunting). The train begins and ends at the main track at
the <ocp>.

The intention of "sidingTrack" is to model any non-main track,
independently whether in stations or line-side. "Non-main track" means
tracks with no train operation, just shunting.

I think it's not necessary to explicitly distinguish between a siding of
a station or a line-side siding. Torben has already suggested to create
a possibility to assign track elements to <ocp>s. This implements the
solution to distinguish the two kinds of sidings.

Best regards,
Dirk.
 
Read Message
Read Message
Read Message
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: [railML 2.5] state
Next Topic: [railML2] Basic speed profile
Goto Forum:
  


Current Time: Fri Apr 26 07:58:33 CEST 2024