Home » railML newsgroups » railML.infrastructure » Stopping Place use cases (What is the difference, from a semantic point of view, among PlatformEdge/StoppingPlace/OperationalPoint?)
Re: Stopping Place use cases [message #2302 is a reply to message #2292] Mon, 06 January 2020 11:07 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
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
 
Read Message
Read Message
Read Message
Previous Topic: [railML2] @dir
Next Topic: extension of <levelCrossing> in railML2.4nor
Goto Forum:
  


Current Time: Fri May 03 23:04:43 CEST 2024