61070: How can shunting movements be displayed in FBS and how does this affect RailML Export?
There are two possibilities to display shunting movements in FBS:
- with path in the graphic timetable
- or without path in the graphic timetable.
The more frequent case is that shunting movements without a path are mapped, since usually also no train order and no timetable creation for shunting trips takes place. In this case, shunting movements are inserted manually as a service into the circulation plan.
To map shunting movements as a path, they would have to be shunting trips on main tracks for which you already have a timetable (for example between two station parts) or you would have to create a graphic timetable / route for the "shunting route", that means for a depot access. In this type of mapping the "shunting track" should be at least a few hundred meters long.
If shunting movements are depicted as a path in the graphic timetable, then they are hardly distinguishable from train travels in railML. In this case, the train drives would also have the same attributes for example "mission = timetable" and "trainPartRef".
In the case of an image without a route in the graphic timetable (the standard case for shunting movements), shunting trips may have during the railML export, e.g. no "mission = timetable" and "trainPartRef" anymore. The cornering times of the shunting trips are specified directly in the < blockParts >. There is also a lack of train-specific information, such as the type of train, the braking percents, etc.
Last update on 21.01.2020 by iRFP Support.