| Re: Haltetafel / stop post [message #288 is a reply to message #287] |
Tue, 03 April 2012 19:20   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Christian,
sorry, but with
> although any railML user didn't reply to your questions...
I am a little bit annoyed because with my message form Monday March 26th
where I indeed thought to reply to Susanne:
> Additionally, I want to remember to Susanne's post from 2011-11-04 where
> she pleads for a stop markers (Haltetafeln) in RailML.
I also wrote a suggestion to handle stop posts both from the view of
infrastructure as well as from a train (timetable).
---
> The stop post itself is a physical element, which is a sign right next
> to the track. Therefore I would not use the crossSection element for
> specifying stop posts.
I agree with you. The crossSection is intended to specify a virtual place
not marked by any physical sign.
> Instead I would put the stop post element inside the ocsElements
> container.
I agree.
> The even more difficult question is how the stop post can be referenced
> with a certain platform (=serviceSection). Like with an ocpRef, the sign
> post may directly refer to the ID of a serviceSection via an attribute
> serviceSectionRef. What do you think?
I also agree in general. But as written in the above mentioned post I
would not create a <serviceSection> but a <platform> (splitting 'passenger
service sections' and other service sections into different elements). But
this is only a small detail which does not change the principle.
From my side, it would also be ok to add the properties of a platform
(orientation, length, height, a. s. o.) directly into the stop post
element and in that way to eliminate the <serviceSection> or <platform> at
all. But I understand that this is probably too much from the operational
view. So defining a <serviceSection> or <platform> and referencing it from
the stop post would be ok from my side.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
