| Re: Representation of operational stations [message #1746 is a reply to message #1743] |
Wed, 28 March 2018 10:50   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Tobias,
in my understanding of the current railML schemes, a purely-operational station as you describe them is a station without any traffic service (dt: Bahnhof, der keine Zugangsstelle ist, keine verkehrlichen Eigenschaften hat).
So, to model such stations, we use an <ocp> without the sub-element <propService>.
To make it explicitly, if you fear a misunderstanding with an unknown <propService>, you can either use an empty <propService> element or set all its services to false:
<ocp id='ocp_DKT_B' name='Dresden-Klotzsche Bbf.' type='operationalName'>
<propOperational operationalType='station' orderChangeable='true' ensuresTrainSequence='true'/>
<propService/>
<designator register='RL100' entry='DKT B'/>
</ocp>
or
<ocp id='ocp_DKT_B' name='Dresden-Klotzsche Bbf.' type='operationalName'>
<propOperational operationalType='station' orderChangeable='true' ensuresTrainSequence='true'/>
<propService passenger='false' goodsLoading='false'/>
<designator register='RL100' entry='DKT B'/>
</ocp>
Please be aware that it is always good provide your interface with an own specification of which elements/attributes you used and how, complementing the railML scheme - a kind of use case documentation. Here, you can specify what a missing or an empty <propService> means.
> We propose the addition of a fifth attribute "operational" in railML 2.4...
I think that this would not be in the original sense. Even a station with "services" (dt: verkehrlichen Eigenschaften) would be operational as well. Please be also aware the possible misunderstanding with the sub-element <propOperational>.
> Btw, isn't this an OCP of type "siding" as proposed in [1]?
As far as I know, "siding" has been intended for sidings (dt: Nebengleise; hier: Anschlussstelle = Nebengleis abzweigend auf freier Strecke).
A pure station for overtakings or crossings (dt: reiner Überholungs- oder Kreuzungsbahnhof) would be a "loop". But in the operational meaning, it is still a station (dt: i. S. v. Zugmeldestelle). Since the name of the attribute is _operational_Type, the value should be 'station'.
(Dt: Im betrieblichen Sinne sind auch reine Überholungsbahnhöfe Zugmeldestellen. Da der Name des Attributs "_betrieblicher_ Typ" ist, sollte hier für alle Zugmeldestellen einheitlich 'station' verwendet werden. Die Unterscheidung der verkehrlichen Eigenschaften (Reiseverkehr, Güterverkehr oder keiner davon) sollte nicht im Element <propOperational> = "betriebliche Eigenschaften", sondern im Element <propService> = "verkehrliche Eigenschaften" erfolgen.)
With best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
