Home » railML newsgroups » railML.infrastructure » Something about platforms, platformEdges, serviceSections and their relation to a track
Re: Something about platforms, platformEdges, serviceSections and their relation to a track [message #458 is a reply to message #457] Wed, 21 November 2012 22:26 Go to previous messageGo to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear railML users,

>> 3. It would be usefull to implement an element like <platform> which has
>> several childs like <serviceSection> or <platformEdge> (or maybe
>> both). So
>> you can find out whether a connection will be done at the same
>> platform or
>> not. This is helpful if you do some routing for passenger information.
>> This
>> mother element can also include the link to an ocp so it can be taken
>> away
>> from the <platformEdge>. So you are also able to link a <platform> or a
>> <platformEdge> depending on the information you want to give to the
>> following systems.
>
> I absolutely agree with you that the <platformEdge> is not sufficient to
> model the complete functionality of the "operational platform" such as
> interchanges between platform edges situated at the same platform.
> Therefore, the introduction of a track-independent new element
> <platform> is a good idea. Until now, I thought about this enhancement
> as a topic for railML version 2.x with x>2 since I wanted to give it
> some time in order to see how the introduced element <platformEdge> is
> being used by the railML appliers before further extensions.

I filed a trac ticket for this aspect [1].

[1] https://trac.assembla.com/railML/ticket/209

Regards

--
Christian Rahmig
railML.infrastructure coordinator
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Tools zum Erstellen der Topologie / Tools for creating the topology
Next Topic: <crossSection>.ocpTrackID
Goto Forum:
  


Current Time: Sat May 18 19:32:25 CEST 2024