Import

Importing timetables from external sources is possible via RailML standard. For transfers of timetables between scenarios in trenoLive, see the scenario management page. If you have old TRENO3 databases to import in trenoLive please contact TRENOlab.

At the moment the process of importing a RailML file in a trenoLive scenario, especially an empty one without prior setup of scenario settings (train categories, TOCs, Operating calendars, etc.) is a task that can not be performed in a second. We advise not to perform any actions in the scenario the RailML gets imported during the import process. We advise a complete logout after the import has been completed to "reactivate" the scenario settings, too. Further, we inform about the necessity to create corridors before the opening of the graphic timetable is possible.

Import railML

railML import options section contains the read-only indication of the current project and scenario in which the timetable will be imported. It is possible to upload a configuration file in .json format to auto-fill the Mappers and Options parameters. Upload the railML file in the dedicated area.

Mappers are needed to define the correspondence between the name used on the railML file and that used in trenoLive.

Mappers Section

This section maps registers from the uploaded files to corresponding registers present in trenoLive. More information on Registers is provided in the projects section of this manual or on the RailML wiki. Apart from the OCP mapper, which needs to be set manually, an automatic matching can be attempted, if no ambiguities are present in the registers - "Try any match". We usually recommend to use this function.

OCP from File: Maps the data related to Operational Control Points (OCP) from the uploaded RailML file.

OCP from trenoLive: Maps OCP from a the current scenario database registers.

Category from File: Maps train categories (such as types of service, e.g., express, cargo) from the uploaded RailML file.

Category from trenoLive: Maps train category information from the current scenario database.

Trainset from File (i.e. formations in the railML file): Maps trainset information from the from the uploaded RailML file.

Trainset from trenoLive: Maps trainset data from the current scenario database.

TOC from File (i.e. railwayUndertaking in the railML file): Maps data related to Train Operating Companies (TOC) from the uploaded RailML file.

TOC from trenoLive: Maps TOC data from the current scenario database.

Op Cal from File (i.e. operatingPeriod in the railML file): Refers to Operational Calendar, mapping calendar data from the uploaded RailML file.

Op Cal from trenoLive: Maps the operational calendar data from the current scenario database.

The third column ("name from file") indicates the field (code/name/description) of the railML file that will be used to fill any empty name of the entity.

Options Section

This section enables specific processing options and custom behaviors.

Allow not found categories insertions: If a category is not found during the process, this option allows its insertion automatically.

Allow not found trainsets insertions: If a trainset is not found, this option allows adding it to the dataset.

Process op. period as embedded train bitmask: Likely processes the operational period information as part of the binary representation (bitmask) associated with the train's operation period.

Allow not found Op Cals insertions: If an operational calendar is not found, it will be added or inserted automatically.

Allow using default Op Cal: Allows the system to use a default operational calendar when necessary, such as when no other calendar is found.

Replace missing Op Cal dates with timetable period: Replaces missing dates in the operational calendar with the corresponding dates from the timetable period.

Replace missing Op Cal dates with scenario dates: Uses scenario dates instead of timetable dates when the operational calendar dates are missing.

Force trains to begin and end with stops only: Ensures that all trains start and end their journeys at OCP with stop, avoiding non-stop start/ending train trips.

Force train departure to day 0 (offset 0): Forces the train's departure to be set to the first day of operation, likely offsetting any previously scheduled start times.

Force train as variants if already existing: If a train (same train number) already exists in the system, this option allows it to be considered as a variant rather than creating a new entry.

Import train groups: Imports predefined groups of trains, which may be based on shared characteristics or services.

Print logs to file in Download area: Enables logging of the process into a file that can later be downloaded for review or troubleshooting.

Click Start import button.

A log of total trains, trains imported and discarded will be shown. This log can also be downloaded as a file from the Organisation -> Downloads area.

Not supported functions in RailML 2.5 Timetabling use case

• Split and join operation (portion working) and coupling of units.
• Commercial Trains and connections between trainParts
• annotations contains texts and messages dedicated for a passenger information system.
• announcement defines announcements for passenger information systems.
• stopActivities describes the activity carried out at a stop, e.g. crew change, reverse, attach engine power system change, etc.
• line This is the code or number of the train service that this train part belongs to. It corresponds to the Service Code in TRENO, but this information is not imported.
• cancellations a cancellation indicates, that this train is no longer valid and should be cancelled out of a previously delivered set. Trains with the attribute cancellation=”true” are not imported.
• import of bus replacement services.
• A pattern train is a template for other trains. Pattern trains are not imported.
• pathStatus This is an attribute of trainPartSequence and describes the status in a train paths allocation process between IM and RU/TOC.

Import CSV

not yet available