| Re: Something about platforms, platformEdges, serviceSections and their relation to a track [message #460 is a reply to message #459] |
Thu, 22 November 2012 09:46  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Good morning Susanne,
> I'm sorry I don't really understand the difference between this aspect
> (Trac ticket #122, comment #8, [1]) and the one written in Trac ticket
> #209 [2].
The Trac ticket #209 was created, because I closed the ticket #122,
which belongs to railML 2.2 while the topic of a track-independent
<platform> element belongs to railML 2.x or higher.
> The grouping of platform edges offers the possibility to refer only one
> platform from the ocpTT (from the train part). That's is already an
> important step into the direction of modelling "real" platforms.
>
> The "parentPlatformEdgeRef" should only refer to platform edges that are
> "in sequence" not "parallel", shouldn't it? If you may group "parallel
> platform edges" that would mean to model a "platform" and should not be
> defined with the same "parentPlatformEdgeRef".
The parameter "parentPlatformEdge" is only used for grouping platform
edges "in sequence" e.g. platform edges with different heights that
still form one physical PLATFORM EDGE. As you correctly mentioned, the
grouping of platform edges at one PLATFORM will be only possible with
the <platform> element suggested in Trac ticket #209.
> [1] http://trac.assembla.com/railML/ticket/122#comment:8
> [2] http://trac.assembla.com/railML/ticket/209
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
