Navigation: Operating the Interface > Select trains to be processed

 

Select trains to be processed

 

Zurück

 

 

 

 

 

 

 

This window gives a final overview of the trains to be imported, divided into new trains (1), trains to be adjusted / replaced (2) and trains that are obsolete (3).

It offers the possibility to decide for each individual train that was read from the railML file whether it should really be transferred to the FBS network. If a train has been selected, its route and arrival / departure times can be seen on the right, for railML, the status quo of the FBS network (original train) and the status after import. It depends on the selected mode (see General options) which of these columns are filled (for example, the column Source train FBS only shows contents if synchronization of trains is to take place. The font colour of the lines in this overview indicates how the train is handled in FBS at this point:

•Train has errors → train will not be imported

•Operation point / train route will be added

•Operation point cannot be added (e.g., due to not being in the FBS network)

•Time at operation point differs between railML and FBS

•No change = railML and FBS are equal

Double-click on a train or the button Report… display further information on the selected train. This includes information, warnings and errors.

 

Only the trains selected by the checkbox in the left list are taken into account during the import. If obsolete trains are to be deleted in the FBS network, the corresponding option must have been activated in synchronisation mode (the trains concerned are then listed here for information in the Obsolete tab). For trains marked in red, the selection checkbox cannot be activated.

Via a context menu in the overview list on the left it is also possible to change the train number or train number index for the marked train, e.g. in case of train number conflicts.

The process is completed by pressing the button Import, which will trigger a report to appear which can optionally be saved as a protocol (text) file.

 

 

 

 

 

Copyright © 2022 iRFP • Institut für Regional- und Fernverkehrsplanung