Home » railML newsgroups » railml.timetable » non-timetable blockParts with track occupancy and train coupling
non-timetable blockParts with track occupancy and train coupling [message #1359] Mon, 06 June 2016 16:05 Go to previous message
Andreas Tanner is currently offline  Andreas Tanner
Messages: 52
Registered: March 2012
Member
Dear community,
the standard currently does not allow <blockPart>s with referenced
<trainPart>s with any <mission> other than timetable. This means that
these <blockPart>s cannot have track information (as there is no
<ocpTT>, only <startOcp> and <endOcp>), nor can the fact that they come
coupled with other <blockPart>s be exported in railML.

Is there any best practice to circumvent that problem? We consider using
an <other:myShuntingMissionType> and referencing <trainPart>s, and using
the <trainPart> category to identify non-trains (that is, shunting trips
etc.)

Best regards, Andreas.
 
Read Message
Read Message
Previous Topic: stopTimes - no reference to the times element
Next Topic: Minutes on railML meeting, 2nd of June, 2016
Goto Forum:
  


Current Time: Fri Mar 29 00:24:18 CET 2024