Home » railML newsgroups » railml.infrastructure » Stopping Place use cases (What is the difference, from a semantic point of view, among PlatformEdge/StoppingPlace/OperationalPoint?)
Stopping Place use cases [message #2292] Thu, 12 December 2019 08:32 Go to next message
Luca Carbone is currently offline  Luca Carbone
Messages: 2
Registered: December 2019
Junior Member
Greetings,
I am a new user working for Hitachi Rail STS, in particular I am part of the SW development pool dealing with system integration and how railML can support our workflow, nice to meet you all.

While working on the implementation of <StoppingPlace> a few questions came to mind and I was hoping that somebody may be able to help.

Coming also from a quick search on the forum for previous questions, there seems to be some possible overlap between <StoppingPlace> itself and both <PlatformEdge> (which it actually refers to via <aStoppingPlace>@PlatformEdgeRef) and an <OperationalPoint> with an <OpOperation>@operationalType=="StoppingPoint" child.

What is the difference, from a semantic point of view, among the three objects: <PlatformEdge>, <StoppingPlace>, <OperationalPoint>@operationalType=="StoppingPoint" and when do they need to be used? Are there different use cases for the above elements? Which would be the more general case?

Thanks and best regards,
Luca Carbone
Re: Stopping Place use cases [message #2302 is a reply to message #2292] Mon, 06 January 2020 11:07 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 273
Registered: January 2016
Senior Member
Dear Luca,

welcome to the railML forum and happy new year!

Since our railML 3 wiki is not yet fully operable, let me provide you the semantic definitions of the different elements here in the forum first:

<platformEdge>
A platform edge is a line or border at which the platform surface terminates.

<stoppingPlace>
A stopping place is the position on the track, where the (head of the) train stops. It is usually marked by a stop post.

<operationalPoint><opOperations><opOperation>@operationalType= "stoppingPoint"
An operational point defines a point in the railway network that is essential for railway operation and where an interaction between railway operator and train driver is possible. An operational point with (operational) type "stoppingPoint" allows trains to stop (e.g. for passengers to enter and leave), but the sequence of passing trains cannot be changed due to missing switches.

So, if you want to describe the side where passengers shall enter or leave the train, use the <platformEdge> element. If you want to model railway operations (e.g. for timetable purposes), use <operationalPoint>.


Best regards
Christian


Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: Stopping Place use cases [message #2309 is a reply to message #2302] Wed, 08 January 2020 16:12 Go to previous message
Luca Carbone is currently offline  Luca Carbone
Messages: 2
Registered: December 2019
Junior Member
Dear Christian, thank you so much and happy new year to everyone on the forum.
Previous Topic: [railML2] @dir
Next Topic: Suggested definition of <ocpVis>
Goto Forum:
  


Current Time: Wed Aug 12 13:37:51 CEST 2020