Home » railML newsgroups » railML.infrastructure » ocpRef at <platformEdges> and <stopPost>
Re: ocpRef at <platformEdges> and <stopPost> [message #425 is a reply to message #424] Fri, 09 November 2012 15:48 Go to previous messageGo to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Dirk and other railML users,

> with the new <platformEdges> and <stopPost> elements, I was only now
> aware that they have no ocpRef attributes so far.
>
> I herewith plead for these ocpRef attributes because we need them to
> link the timetable information with the new infrastructure elements.
>
> [...]
>
> --> providing references from a <platformEdge> to an <ocp>:
> <platformEdge> gets an "ocpRef".
>
> --> We then also have the references from the stop posts to its ocp's
> via the platformEdges, but there may be stop posts without platforms
> (freight-only tracks), so: providing references from a <stopPost> to an
> <ocp>: <stopPost> gets an "ocpRef".

thank you for your remark. Indeed, a direct reference from the
<platformEdge> to the OCP and from the <stopPost> to the OCP has not
been implemented, yet. With the latest modification of trac tickets [1]
and [2], I considered the missing references.

[1] https://trac.assembla.com/railML/ticket/122
[2] https://trac.assembla.com/railML/ticket/167

Best regards

--
Christian Rahmig
railML.infrastructure coordinator

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Track: description vs. trackDescr
Next Topic: loading gauge
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri May 17 07:10:36 CEST 2024