Home » railML newsgroups » railml.timetable » Infrastructure train number
Infrastructure train number [message #1338] Tue, 22 December 2015 15:24 Go to next message
Andreas Tanner is currently offline  Andreas Tanner
Messages: 51
Registered: March 2012
Member
Dear railML community,

one of our customer needs to keep track of the infrastructure train
number, aka train path number (Trasse). We model this as a property of
an operational train section.

Indeed, we cannot use an attribute of the <train> since both commercial
and operational trains are owned by the train operating company. The
infrastructure manager's view on trains differs.

As for now, we will make use of a custom attribute at
<trainPartSequence>. Now railML2.3 is already in preview mode, so
probably we should discuss this issue for 2.4 or 3.

Best regards, Andreas.
Re: Infrastructure train number [message #1342 is a reply to message #1338] Thu, 21 January 2016 16:06 Go to previous messageGo to next message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 202
Registered: August 2008
Senior Member
Dear Andreas,

> Indeed, we cannot use an attribute of the <train> since both commercial
> and operational trains are owned by the train operating company.

I do not agree with that statement. An operational train is a train from
the view of the Infrastructure Manager. Therefore, the trainNumber
attribute of an operational train can contain the train (path) number
("operational train number") of that train.

I do agree (already for a long time) that this issue should be solved
better in 3.0. In my opinion it is part of the "re-factoring".

Best regards,
Dirk.


---
Am 22.12.2015 um 15:24 schrieb Andreas Tanner:
> Dear railML community,
>
> one of our customer needs to keep track of the infrastructure train
> number, aka train path number (Trasse). We model this as a property of
> an operational train section.
>
> Indeed, we cannot use an attribute of the <train> since both commercial
> and operational trains are owned by the train operating company. The
> infrastructure manager's view on trains differs.
>
> As for now, we will make use of a custom attribute at
> <trainPartSequence>. Now railML2.3 is already in preview mode, so
> probably we should discuss this issue for 2.4 or 3.
>
> Best regards, Andreas.
Re: Infrastructure train number [message #1355 is a reply to message #1338] Thu, 02 June 2016 12:16 Go to previous message
vpkolmorgen
Messages: 29
Registered: November 2004
Junior Member
This issue was discussed in the railML's Timetable developer meeting in Berlin on June 2nd, 2016.

Conclusion: The timetable experts wants to keep the operational train number (betriebliche Zugnummer) as the primary number for the infrastructure manager and a additional attribute will reduce interoperability.

Additional for most European IM's and RU's the Unique Train Transport ID by ERA introduced in railML 2.3 (see Ticket 236) will solve the problem.

Regards,
--
Vasco Paul Kolmorgen
railML.org Coordinator
Dresden; Germany www.railml.org
Previous Topic: Protocol developer meeting 22nd January 2016 at PSI
Next Topic: Request for a new optional attribute for train coupling and sharing
Goto Forum:
  


Current Time: Thu May 25 18:11:13 CEST 2017