|
Note: You can import files of the *.xml type, realizing the railML® scheme in version 2.0, 2.1, or 2.2. For the import, you select only one file, which can refer to others via an "include" statement. These have to be in the same directory as the selected file. |
1. In the File menu, select the Import > RailML entry.
The RailML import window opens.
2. Select the Basic settings tab.
3. Click the 
button next to Import from file.
The Open RailML file window opens.
4. Select the desired file.
5. Click the Open button.
File name and directory are adopted into the entry field.
6. Specify any further settings you need.
|
Element |
Description |
|
Extend of import |
Specify the data to be imported. Only timetable data If the option has been selected, only timetable data will be imported. Timetable data and line blocks If the option has been selected, timetable and line block data will be imported. The line blocks are inserted into the block version specified on the Line block import tab (Line block import tab). Note The line blocking time interval of the selected block version must at least contain the import period. You should thus check the line blocking time interval before the import. Only line blocks If the option has been selected, only line block data will be imported. The line block information is assigned to existing vehicle journey sections during import. Note The prerequisite for the option is that the required timetable data already exists in the target network and the trainPartIDs are formed according to the following naming convention: tp_<Vehicle journey number>_<Vehicle journey section number>_<From-time profile index> The timetable data should therefore be exported from Visum, extended externally by line blocks and imported back into Visum. Import vehicle data If the option is selected, vehicle information is read from the railML® data 'vehicle' and 'formation' and assigned in Visum. ‘Vehicles’ become vehicle units and ‘formations’ become vehicle combinations. The vehicle combination corresponding to the railML® attribute ‘formationRef’ is set at the vehicle journey sections or line blocks created during the import. If the option is selected, vehicle information is read from the railML® data 'vehicle' and 'formation' and allocated in Visum. ‘Vehicles’ become vehicle units and ‘formations’ become vehicle combinations. The vehicle combination corresponding to the railML® attribute ‘formationRef’ is set at the vehicle journey sections or line blocks created during the import. For the allocation of the data, you can make further settings: Only "Code" attribute only If this option is selected, a check is made to see if objects with the same "code" already exist before a new vehicle or vehicle combination is created. Use all attributes If this option is selected, a check is made to see if objects with the same attribute values already exist before inserting a new vehicle or vehicle combination. |
|
Directions |
The directions of the line routes created in Visum are determined by the train number. If no train number is specified, the outward direction is assumed. If a number is specified, you can use the option to determine whether even numbers are allocated to outward directions and uneven numbers to the opposite direction or vice versa. |
|
Line route |
As route information, a series of stop points is available in Visum. In addition, there is information on arrival and departure times as well as boarding and alighting. In Visum, a route point on the line route is created for each stop point with a stop. It is irrelevant whether it is a traffic stop or an operational stop. The following options allow you to keep the number of route points constant or insert additional route points for stop points (OCP) without a stop (ocpType != pass). None If this option has been selected, route points are only created for stop points with a stop, no additional ones. for OCPs with time data If this option has been selected, route points are created for all stop points with time data contained in the railML® file and found in the target network. for OCPs with time or To-length data If this option has been selected, route points are also generated for all stop points that are provided with a time or 'to' length data (distance) in the railML® file. for OCPs in the route course If this option has been selected, route points are created for all stop points contained in the railML® file and found in the target network, even those without times and lengths. |
|
Do not show warnings during the import |
If this option has been selected, the output of warnings can be suppressed. |
|
Show statistics of modifications |
Select this option to have Visum create a model transfer file while reading in a new file. The model transfer file contains all changes that are made according to the new file. The file is located in the project directory defined for model transfer files. It is automatically opened when it is read in. |
7. Make your changes in the other tabs.
Transfer to target network tab
|
Element |
Description |
|
Point location information (stop points) |
Equivalents in the target network can be found using different levels of detail. You can select either a primary Visum attribute only to model OCPs on one stop point each or additionally select a secondary Visum attribute for track information within the OCP. Furthermore, you can compare link information. Identify blank and underscore in primary stop point matching attribute If this option has been selected, before the search for correspondences blanks are replaced by an underscore in the railML® file and in Visum. Notes This option makes sense if in the file to be read blanks are used instead of underscores. Since in Visum the codes required have to be unique, the import will fail if two stop points differ only by this sign in the identification attribute. Primary matching attribute (course-independent) Selection of an attribute in the target network that maps each operating point to a stop point. Secondary matching attribute (track information, course-dependent) Optional selection of an additional attribute to store track information within an operating point ('trackinfo') in a Visum attribute. |
|
Linear location information (links) |
Besides stop point information, you can select one or two matching attributes for link information to import the exact route course. If you do not select any course-dependent attributes, line routes are determined using the shortest path search. |
|
Note: Missing or unclear information for the course of line routes is always determined via shortest path searches during the railML® import in Visum. |
Routing tab
|
Element |
Description |
|
Parameters: Shortest path search |
You can specify the following options for routing during import. Search criterion In the list, click the criterion you want to use for the shortest path search.
Detour factor If the length of the found route course is greater than the specified detour factor x the direct distance, the search is repeated and the routing also considers closed turns and links. Enter the desired factor in the input field. Also use closed links for routing Select this option to also include links closed for the transport system selected for routing. Also use closed turns for routing Select this option to also include turns closed for the transport system selected for routing. Note The routing has two stages. The options regarding closed objects should not be selected at first as there might be a route via closed objects which can be used without opening closed objects. |
|
|
If no shortest path is found or the length is > [detour factor] x direct distance, repeat search and route via closed links and turns If this option is selected, the program does not initially route via closed objects. If no shortest path is found in this way, a new search is carried out also for closed links and turns. |
|
|
If no shortest path is found or length is > [detour factor] x direct distance Do not insert line route If this option has been selected, line routes and system routes are not read from network file. Insert line only if a direct link can be opened If this option has been selected, line routes and system routes are only read from network file if those links can be permitted for the selected transport system. Always insert; direct link is opened if possible, otherwise it is inserted If this option has been selected, line routes and system routes are read from network file. Missing links in a route course will be created. In the list, click the link type you want to use for links newly inserted links (Specifying link types). Link type of newly created links Here you specify the link type for newly inserted links. Click the Set the link type of opened links to Here you can specify a link type for opened links. This way you can tell later which links were opened during the read in process. Click the |
symbol to add another link type. It receives the next free number and is then selected.Transport systems tab
|
Note: To access the settings in the Transport systems tab, in the Basic settings tab, select a railML® file. |
|
Element |
Description |
|
Do import |
In this column, you can specify per transport type, whether you want to import it as a Visum transport system. If the check box is disabled, the train type will not be imported. |
|
Train type code Train type name |
Display of the 'abbreviation' and 'name' attributes from the railML® file. Note If you move the mouse over the columns, a tooltip additionally displays the value of the 'description' and 'trainUsage' railML® attributes. This is useful, for example, if you want to avoid the import of empty trips. Those have the 'deadrun = true' characteristic. |
|
TSys code TSys name |
Short and long name of the imported transport system Notes Use the drop-down list in the TSys code column to select the desired transport system. It contains all PuT line TSys of the network. You can aggregate several train types to one Visum transport system using the same TSys code and TSys name for all train types. |
|
Empty trip |
Display of the 'deadRun' property from the railML® file Note The display indicates empty trips that you can exclude from the import if required using the Do import option. |
|
Check all |
Via this button, you may select all train types for the import. |
|
Uncheck all |
Via this button, you may uncheck all train types for the import. |
Calendar and times tab
|
Element |
Description |
|
Target network calendar |
Calendar type Here the calendar type of the loaded Visum network is displayed. Notes If no calendar is set, the valid day daily will always be selected. An import in a weekly calendar is not possible. If you need a different calendar type, set it in Visum before importing. Import all vehicle journey sections as ‘daily’ If this option is selected, daily is set for all vehicle journey sections of all valid days at the end of the import process. |
|
Filters |
Source network calendar Here the range of dates of the source file is displayed. The imported range of dates is intersected with the calendar set in Visum. Using the filter, you can select days from the range of dates. Then only journeys operating on the days you have specified are imported. Click the Click the Add button to add a key date to the list. Click the Delete button to delete the key dates selected in the list. Use the Delete all button to delete all key dates simultaneously. Note If there is no overlap between the calendar of the source network and the calendar of the target network, the import is performed as follows:
|
|
Time shifts |
Time shift in target network with respect to UTC Here the arrival and departure times of trips in Visum can be shifted with respect to the Universal Time Coordinated. A shift of one hour corresponds to the Central European Time (CET). |
|
Time data at ocpTT element |
List of values of the railML© attribute ‘scope‘ in the railML© element ‘times‘. The departure and arrival times for Visum are based on these values. The entry in first position has the highest priority during import, the last entry has the lowest. Use the two arrows to move the selected time data up or down in the list. |
button to open a calendar. To select a key date, click the date of your choice.Names for timetable data tab
|
Notes: Here you define from which data the names of the lines and vehicle journeys will be generated in Visum. The lists on the right contain the data used to create the names in the order specified. The list to the left stores the data which is available for the naming process. If in Visum there is a line with the set name components, they will be used if the transport system fits. If there is no line with set name components, a new one is created. If there is a line with the same name but a different transport system than the one required, the import for this line will fail. This situation can be avoided if the transport system code is selected as a component of the line name. |
8. In the Line route name section, make the desired settings.
|
Element |
Description |
|
Line route name like vehicle journey name |
If this option has been selected, the name of the vehicle journey is also used for the line route and the time profile. Note If there is already a line route or time profile with this name, it will be suffixed (by 1, 2, etc.). |
|
Name of the line route from first OCP and last OCP of the course |
If this option has been selected, the combination first OCP_last OCP is used for naming the line route, if necessary, complemented by a consecutive number. |
9. In the Line name section, make the required settings for the composition of the line names.
10. In the Available items section in the list to the left, select the entry which you would like to add to the line name.
11. Click the 
symbol.
The entry is inserted into the right list above the currently selected entry.
12. Add further entries, if required.
|
Note: You can delete an entry from the right list by selecting the desired entry and clicking the |
button.13. If necessary, change the order of the items using the arrows 
and 
.
14. If required, change the character in the Separator input field to separate several name components.
|
Notes: A semicolon is not permitted as a separator. A preview shows the current composition of the line names. |
15. In the Vehicle journey name section, specify the naming conventions accordingly.
16. Enter the desired character strings in the entry fields Fixed name component for line and Fixed name component for vehicle journey.
|
Note: For the name generation, the appropriate string is provided as the Mandatory name component. |
Attributes for timetable data tab
|
Element |
Description |
|
Flagging of imported vehicle journeys |
Flag Enter the desired name for the import. in attribute Selection of the vehicle journey attribute that stores the specified flag (name) Store vehicle information in attribute The vehicle information read is saved as text in the selected vehicle journey section attribute (Identification of vehicles (from RollingStock)). |
|
Attribute selection for further information |
Save information not listed here in user-defined attributes
|
|
Table |
Information List of information that can be additionally transferred to Visum during import. ‘Information’ is usually a railML© attribute of a railML© element, which is stored at the given network object type in the selected target attribute in Visum. For timetable data, there is also the following system information:
These have no equivalent in the railML© file. Visum defines a lot of information that is not available in every railML© file. Information is transferred to Visum if a target attribute is selected in the table. For this purpose, you can insert user-defined attributes for all source attributes and allocate them in the table. RailML element Display of the source of the attribute Notes Only attributes from 'commercial trains' are saved to vehicle journeys. Attributes from 'operational trains' are saved to vehicle journey sections. RailML attribute Name of the railML® attribute Network object type Visum object storing the information TargetAttID Attribute storing the information |
|
Show important additional information |
Note When importing or saving a *.puti file, the visible entries are taken into account. Depending on the setting of the Save information not listed here in user-defined attributes option, displayed attributes are either imported and allocated to automatically generated user-defined attributes or not. |
|
Create user-defined attributes |
Use this button to generate automatically user-defined attributes for all non-allocated source attributes. These are attributes of the import file with assignments to attributes that do not exist in the target network. |
If the option is selected, user-defined attributes are automatically generated during import for railML© attributes of the selected railML© file for which no entry is contained in the table (or in the 
If the option is not selected, railML© attributes of the selected railML© file for which no entry is listed in the table will not be taken into account during import.
|
Notes: You can sort the columns alphabetically. Right-click the column name and select the option from the shortcut menu. If you do not want to use an attribute, you can select the entry No selection in the attribute selection window. The respective railML® information is then not read in. The same applies to the optional Flag and the Vehicle information. |
Line block import tab
|
Element |
Description |
|
Import in block version:tab |
The button allows you to select the block version into which you want to import the data. Editing a block version If required, click the button to change the properties of the selected block version. (Editing a block version) Create new block version Alternatively, click this button to insert a new block version (Creating a line block version) Line blocking time interval Specifies the possible line blocking time interval. The possible line blocking time interval is determined from the calendar period specified in Visum (Selecting a calendar ) and the timetable period defined in the railML® file. The line blocking time interval set in the block version must be within the possible line blocking time interval. Import empty trips The option is activated if the block version you want to import into has the 'Interlining permissible' property. RailML® elements of type 'blockpart' with the railML® attribute 'mission=emptyRun' are then imported. |
|
Code and name for block |
Here you can make settings for the composition of the codes and names of line blocks, similar to the line and trip names in the Names for timetable data tab. |
|
Properties for imported blocks |
Empty trip transport system: Selection of a transport system for empty trips (Fundamentals: Empty trips) The transport system is required for the block check. Regard running direction If the option is selected, the direction of travel is taken into account during the block check. (Fundamentals: Regard running direction). |
|
Performing the line block check |
If the option is selected, a block check is performed after data import. (Performing the line block check). |
|
Run coverage check |
If the option is selected, a coverage check is performed after data import. (Checking the coverage). |
Attributes for blocks tab
|
Element |
Description |
| Save information not listed here in user-defined attributes |
|
|
Table |
Here you can select data from the railML® file that is not automatically imported into Visum for import. All data for which a target attribute is selected.is imported into Visum. Information List of possible railML® attributes of the elements 'Rostering', 'Block' and 'BlockPart’ that can be imported. The part after the underscore corresponds to the name of the railML® attribute. 'BlockPart_VehicleJourneySection_MismatchMessage' contains the warning that occurs when importing with the option Only line blocks if a vehicle journey section that already exists in the Visum network and the data specified in the railML line block data (blockPart, different times, different stop points) do not match. RailML element Name of the railML® element that provides the information. Only populated if the information originates from a railML® attribute of a railML® element. RailML attribute Name of the railML® attribute that provides the information. Only populated if the information originates from a railML® attribute. Network object type Visum object at which the information is stored as a user-defined attribute TargetAttID Name of the attribute of the network object type that stores the information Notes You can select the attributes individually or generate user-defined target attributes for all source attributes. You can sort the columns alphabetically. Right-click the column name and select the option from the shortcut menu. |
|
Show important additional information |
|
|
Create user-defined attributes |
Via this button, you can generate automatically user-defined attributes for all non-allocated source attributes. |
If the option is selected, user-defined attributes are automatically generated during import for railML© attributes of the selected railML© file for which no entry is contained in the table (or in the Attributes for vehicle units tab
|
Note: The tab is displayed only if you have selected the Import vehicle data option. |
|
Element |
Description |
| Save information not listed here in user-defined attributes |
|
|
Table |
Here you can select data from the railML® file that is not automatically imported into Visum for import. All data for which a target attribute is selected.is imported into Visum. Information List of possible railML® attributes of the element 'Vehicle’ that can be imported. The part after the underscore corresponds to the name of the railML® attribute. Network object type Visum object at which the information is stored as a user-defined attribute TargetAttID Name of the attribute of the network object type that stores the information Notes You can select the attributes individually or generate user-defined target attributes for all source attributes. You can sort the columns alphabetically. Right-click the column name and select the option from the shortcut menu. |
|
Show important additional information |
|
|
Create user-defined attributes |
Via this button, you can generate automatically user-defined attributes for all non-allocated source attributes. |
Attributes for vehicle combinations tab
|
Note: The tab is displayed only if you have selected the Import vehicle data option. |
|
Element |
Description |
| Save information not listed here in user-defined attributes |
|
|
Table |
Here you can select data from the railML® file that is not automatically imported into Visum for import. All data for which a target attribute is selected.is imported into Visum. Information List of possible railML® attributes of the element 'Formation’ that can be imported. The part after the underscore corresponds to the name of the railML® attribute. Network object type Visum object at which the information is stored as a user-defined attribute TargetAttID Name of the attribute of the network object type that stores the information Notes You can select the attributes individually or generate user-defined target attributes for all source attributes. You can sort the columns alphabetically. Right-click the column name and select the option from the shortcut menu. |
|
Show important additional information |
|
|
Create user-defined attributes |
Use this button to generate automatically user-defined attributes for all non-allocated source attributes. |
17. Confirm with OK.
The railML® data is imported.
|
Note: Data which cannot be imported is written to the log file and output in the message window (Notes on imported railML® data). |
