Home » railML newsgroups » railml.timetable » Blockparts: emptyRuns, depotRuns
Blockparts: emptyRuns, depotRuns [message #949] Fri, 25 October 2013 17:28 Go to previous message
Andreas Tanner is currently offline  Andreas Tanner
Messages: 52
Registered: March 2012
Member
Dear all,
the wiki page on <blockPart>s is inconsistent.
- It says that for missions fullRun, emptyRun, <trainpartref> must not
be used, but a "note" on the bottom of the page says the opposite for
emptyRun
- The English text says that depotRun is "not a run", in the German
text this mission type is missing.

Is a depotRun a trip to a depot? Then I would think that it _is_ a run,
and start and end will be different.

Also, shouldn't, instead of start and end ocps, rather <ocptts> be used
for those missions that are runs? Referencing a trainPart I think is not
optimal, because so far they are always used in connection with a train,
and we don't have a train for those runs.

Finally, it would be nice if we could clarify the semantics of shunting,
emptyRun, fullRun and depotRun.

Best, Andreas.
 
Read Message
Read Message
Previous Topic: planned passenger capacities
Next Topic: stop probability
Goto Forum:
  


Current Time: Thu Mar 28 17:40:24 CET 2024