General Options

Navigation: Operating the Interface > General Options

General Options

The RailML import offers more differentiated options than simple one-to-one transfer of trains from the import file to FBS. The main question is how to handle trains that already exist in the network file. They can be compared and synchronised with the trains to be imported (if necessary, with regard to individual criteria) or be completely replaced or be deleted without replacement.

The above window allows essential settings on how to proceed with the trains to be imported. First you have to determine which layer in FBS the import should affect (target layer), whereby a new layer can also be created. There are three different import modes: Import, Synchronise and Synchronise with copy.

Import all railML trains

When importing, all trains imported from the railML file are transferred to the FBS network without changing the trains already there. If the checkbox If the train numbers are ambiguous, assign new train number indexes is not selected, train number conflicts may prevent the import. If it is selected, a new train number index is added to the imported train if its train number already occurs in the target layer.

Synchronization of the FBS network with the railML file

The main difference between synchronisation and import is that existing trains in the network can be changed when synchronizing. There is the possibility to replace the already existing trains with those from the railML file or to adjust them. When adjusting, the data of the train already existing in the network is overwritten (based on the Adjustment options); when replacing, a new train is created that only contains data from railML. All data not present in the railML file (e.g., individual line colours) are lost in the process.

Optionally, existing trains in the FBS that do not appear in the railML file can be deleted. Trains that only exist in the railML-file are newly created. Therefore, this option can be used to display the exact proposed schedules of the railML file in the target layer of the FBS network.

Synchronize existing trains with a copy of the trains from the following reference layer

This import method is a kind of mixture of the other two modes. Again, no existing trains are changed or deleted, but no trains are added either. Instead, copies of the existing trains from one selected layer are created and synchronized with the trains from the railML file. This option is particularly useful if the train schedules of the trains loaded from the railML-file are to be compared with those already existing in iPLAN before the import.

Adjustment options

Here you can set which data will be taken over from the railML file when synchronizing a train. At least one option must be selected. All options not selected remain unchanged in the original FBS train.

The adjustment options are only available if the selected import mode also includes adjustments, i.e. when synchronizing and adjusting existing trains or when synchronising with copies from a reference layer.

Options for new trains to be created

When trains are newly created, all train data that is not stored in the railML file (e.g., interval group information, line colours, etc.) is lost. The selected FBS standard stop time list is assigned to all newly created trains. The values of the stops for the respective train are provided by the railML file; if required, it can be chosen under More options to Copy planned stops from FBS stop list which will replace the stop times of the railML-file. If the newly created trains are to be assigned to different stop time lists, the corresponding trains must be imported in separate processes. The same applies to the assigned train groupings.