Home » railML newsgroups » railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5
Re: @categoryPriority of <category> in version 2.5 / Extension of train part [message #2414 is a reply to message #2348] Mon, 06 April 2020 11:44 Go to previous messageGo to previous message
huerlimann(at)opentrackch is currently offline  huerlimann(at)opentrackch
Messages: 1
Registered: January 2016
Junior Member
Dear Community

I also recommend to keep an information about the priority of a train category in a way. I do not remember why it was defined as a string, but an integer value would also make sense. And as a not so elegant solution an integer in string format (e.g. "3") can be used. I also recommend to use the rule that the lower value means a higher priority.

Best regards

Dani

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Continuation: different stop types / Mehrere Betriebshalt-Haltegründe usw.
Next Topic: [railML2] Usage of //ocpTT/times/@scope
Goto Forum:
  

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

Current Time: Thu Dec 05 14:35:45 CET 2024