[railML2] Extension proposal: Stopping point reference for elements not of type <stopPost> [message #2554] |
Tue, 13 October 2020 14:17 |
Janne Möller
Messages: 14 Registered: March 2019 Location: Oslo
|
Junior Member |
|
|
Dear railML-community,
The attribute @stopPostRef in element <stopDescription> refers to the associated <stopPost> element where the train will stop. In Norway we often have the case that there is no stop post at the position where a train should stop. Instead the train stops at other elements, for example a signal or a switch. That is why we need to refer to an element of a different type than <stopPost> under <stopDescription>. Therefore, we introduced the attribute @nor:stopRef in railML2.4nor. We use this attribute to refer to the associated element if it is not of type <stopPost>. Are there any railML-users who might find this useful?
Any feedback is highly appreciated.
Best regards,
Janne Möller
Jernbanedirektoratet
|
|
|
Re: [railML2] Extension proposal: Stopping point reference for elements not of type <stopPost> [message #2565 is a reply to message #2554] |
Wed, 28 October 2020 10:52 |
Christian Rößiger
Messages: 63 Registered: March 2015
|
Member |
|
|
Hello Janne,
I can understand the background to your extensions in general. I'm not
an infrastructure expert, but from my point of view I have two comments
on this:
- The element <stopPost> provides an attribute "virtual". According to
the description in the railML-Wiki, it can be used to defines stop
positions for which there is no physical stop post on the track. If your
usecase is only about specifying the stopping position of a train, this
would be possible with this attribute.
- If you want to indicate explicitly that the train stops at a certain
infrastructure element (signal / switch) and the reference to this
element is important, the above solution is probably not an alternative
for you. But I would prefer not to use a generic attribute for
references to all possible infrastructure elements, because references
to elements are (as far as I can see) always type-specific in railML2.
Instead, I would provide one separate attribute or element per element
type (signalRef, switchRef and so on). The usage of an element would
have the advantage that additional element-specific information could be
included, e.g. on which end of a switch the train should stop exactly.
Kind regards
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|
|