Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
Re: RFE for connection, DE:Anschluss [message #958 is a reply to message #878] Mon, 02 December 2013 12:26 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hi,
in order to solve this issue we will prevent (by documentation) to have
two times the same ocpTT within one trainPart.

https://trac.assembla.com/railML/ticket/235

Kind regards,
Joachim

-------------------------------------
Joachim Rubröder
Schema Coordinator: railML.timetable

Dirk Bräuer wrote:
>
>> But the train arrives Köln-Mülheim the second time "orientation
>> reversed", doesn't it?
>
> No, it does not. The fist and the carriages are still the same. The
> orientation of a formation currently refers to its running direction but
> not to a geographic direction nor a mileage direction.
>
>> It would be interesting to
>> see it in railML without splitting into two train parts. Which problems
>> may occur regarding the timetable in general and rostering in special?
>
> So far: None. There already are these cases in practice including
> circulation plans w/o problems. There is no reference to an <ocpTT> in
> RailML so far so that's why two <ocpTT> may refer to the same <ocp> w/o
> problems.
>
> Dirk.
>
>



--
----== posted via PHP Headliner ==----
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: stop probability
Next Topic: wiki: missing attribute description for additionalTrainNumber at <train>
Goto Forum:
  


Current Time: Sun May 05 23:39:52 CEST 2024