You can export your Visum data to railML®. An *.xml file is generated according to railML® schema 2.2. It contains stop point, timetable, and vehicle data. It can also contain infrastructure data. Export your data as follows.
1. In the File menu, select the Export > RailML entry.
The Export to RailML window opens.
2. Select the Basic settings tab.
3. Next to Export to file, click the 
button.
The Save RailML file window opens.
4. Enter the file name and the path, if required.
5. Click the Save button.
The file name and directory are adopted into the entry field.
6. Make the settings of your choice.
|
Element |
Description |
|
Section Extent of exported data |
Timetable data and entire infrastructure If this option has been selected, besides the timetable data, the entire infrastructure is imported, which is traversed by the exported vehicle journey sections.
The infrastructure is imported independently the of existence of vehicle journeys in the network. Timetable data and specific infrastructure based on active links If this option has been selected, the following objects are exported besides the timetable data:
Timetable data and infrastructure used If this option has been selected, the following objects are exported besides the timetable data:
Only timetable data with complete route course yet without infrastructure If this option has been selected, vehicle journey sections are exported with all required basic data, and all stop points explicitly contained in the route course are exported as OCPs. Only timetable data with just route points as route course If this option has been selected, vehicle journey sections are exported with all required basic data, and all stop points contained in the route course are exported as OCPs. Consider only active vehicle journey sections If this option has been selected, the option previously selected in the Extent of exported data section is restricted to active vehicle journey sections. |
|
Timetable period |
You can set the timetable period if the export network has a weekly calendar or no calendar. Note This section is not available if an annual calendar has been set. Start of the exported timetable period Click this button to specify a start time for the timetable period exported. End of the timetable period The end of the timetable period depends on the start time chosen. |
You can optionally select an attribute for various network objects that is included as a suffix in the OCP ID. This facilitates the readability of the railML® export file for the user.
8. Make the desired changes.
|
Element |
Description |
|
Stop point |
Selection of a stop point attribute |
|
Node |
Selection of a node attribute |
|
Main node |
Selection of a main node attribute |
9. Select the railML attributes tab.
10. Make the desired changes.
|
Element |
Description |
|
Output permitted transport systems at track element |
If this option has been selected, permitted transport systems are output at track elements. Note This option is only provided if you have selected the option Timetable data and infrastructure used on the Basic settings tab in the section Extent of exported data. |
|
Attribute selection for data objects in export file |
Data object List of export file elements Target attribute Attribute of export file element to which information is saved. Source attribute Visum attribute used to create the element Note Here you select the attributes you want to export. Only those attributes for which you have chosen a source attribute are exported. If you do not want to use an attribute, you can select the entry No selection in the attribute selection window. |
11. Select the Variable railML attributes tab to specify origin data objects and associated attributes for the export, if necessary.
12. Where applicable, click the 
Create button.
13. Make the desired changes
|
Element |
Description |
|
Origin data object |
From the drop-down list, choose the data object of which you want to export data to railML®. |
|
Attribute ID |
The button opens the attribute selection window in which you can select an attribute. |
14. Confirm with OK.
The data is exported to an *.xml file.
