Home » railML newsgroups » railML.infrastructure » Use of <bufferStop> (<bufferStop>)
Use of <bufferStop> [message #2048] Wed, 19 December 2018 13:55
Torben Brand is currently offline  Torben Brand
Messages: 156
Registered: March 2016
Senior Member
We in the Norwegian sector understand <bufferStop> not as a track element "Buffer stop", but as the physical end of the track you could drive a trains buffer towards. This position would then be the correct placement of a @pos of a <trackEnd> or <trackBegin> with a sub element <bufferStop>. See illustration bellow. What is behind the ending track is irrelevant. This could be a buffer stop (of different types), a concrete wall, a sand trapp or "nothing"). This also makes sense as the <bufferStop> is placed under <trackTopology>. Thus the <bufferStop> also has no <state>.
If you need to map the component "Buffer Stop" I would suggest to add an extension (<any>) element in 2.4 under <trackElements>. The component is already avaliable in railML3 under <functionalInfrastrucutre>

<bufferStop> wiki: https://wiki.railml.org/index.php?title=IS:bufferStop_trackE nd
"Buffer stop" wikipedia article: https://en.wikipedia.org/wiki/Buffer_stop

https://cloud.railml.org/remote.php/webdav/Photos/bufferstop.png

My question to the comunity and the coordinator: Is this understood correct?

If yes I would suggest to rewrite the definition in IS:bufferStop somewhat. This as the current definition is vague about the component being mapped.

Previous Topic: Question towards different use of @pos and @absPos attributes
Next Topic: infrastructure "state"
Goto Forum:
  


Current Time: Thu Mar 28 18:08:05 CET 2024