| Re: railML 2.3 infrastructure extension proposal operational properties of an OCP [message #1744 is a reply to message #1741] |
Tue, 27 March 2018 11:14   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
I filed the Trac ticket #327 [1] dealing with this issue.
[1] https://trac.railml.org/ticket/327
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
Am 27.03.2018 um 10:28 schrieb Christian Rahmig:
> Dear all,
>
> we were recently discussing the different types of OCP in our railML 3.x
> Schematic Track Plan use case working group. Therefore, I would like to
> come back to this forum post opened by Torben Brand from
> Jernbanedirektoratet:
>
>>>> 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>
>
> In order to complete the modelling, I suggest to follow Torben's
> proposal and add the enumeration value "siding" for attribute
> <ocp><propOperational>@operationalType.
>
> If you agree, we may bring this as last minute change into railML 2.4.
>
> Best regards
> Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
