For data export to Vissim, you can save Visum network data as an abstract network to an *.anm file. Routes and matrices can be saved in a route file *.anmRoutes. Both types of files can be stored in XML format (Brief introduction to the *.xml data format).
1. From the File menu, choose Export > Vissim (ANM).
The ANM export window opens.
2. Make the desired changes.
|
Element |
Description |
|
ANM file |
Network data If this option has been selected, the network data of the current network can be saved in an *.anm file. Select the directory, if applicable, and enter the file name or click the |
|
ANMRoutes file |
Routes If this option has been selected, the route information is saved to a route file *.anmRoutes. Select the directory, if applicable, and enter the file name or click the Note For the import in Vissim, you can specify if you want to read in static or dynamic path information. Matrices If this option has been selected, the demand matrices of the current network are saved to an ANM route file *.anmRoutes. Select the directory, if applicable, and enter the file name or click the Round demand If the option has been checked, you can set the number of decimal places to which you want to round the demand. The values of the exported matrices are rounded consistently with the route volumes. Note The method used is “bucket rounding", which ensures that total demand is maintained as far as possible. |
button.3. Select the Vehicle categories tab.
4. From the selection list, allocate each Visum transport system you want to export to a Vissim vehicle category.
|
Note: Transport systems of type PuT Walk are not exported to Vissim and are therefore not listed. |
|
Tip: If you do not want to export a Visum transport system to Vissim, select the Do not export entry from the drop-down list. |
5. Select the Driving behavior tab.
6. In the selection lists, select a Vissim default driving behavior for each Visum link type.
|
Tip: If you click the Ctrl key and hold it down while clicking the desired rows with the left mouse key and click the Multiple button, you can specify driving behavior for multiple link types simultaneously in a separate window. |
7. Select the PuT tab.
8. In the Vissim stops section, adjust the desired settings.
|
Element |
Description |
|
Stop length from stop point attribute |
Via this button, select the attribute from which the length of the PT stop in Vissim is to be determined. Tip You can, for example, create a user-defined attribute for stop points, enter data for this attribute and select this attribute. |
|
As lay-by if stop point attribute is 'true' or not equal to 0 |
Via this button, select a stop point attribute which defines whether the exported stop points are of the street or lay-by type. Tip You can, for example, allocate an AddValue of 1 to all stop points that you want to export as lay-bys, and a 0 to all stop points that you want to export as on street stops. If you then select the attribute AddValue, the stop points are exported as desired. |
|
Node stop point before node if the stop point attribute is 'true' or not equal to 0 |
Via this button, select the stop point attribute which controls whether the stop point is located before the node or behind it. Notes This applies to node stop points only. For line routes that terminate at a node, the last stop point is always placed before the node. If no attribute is selected, the stop points will be placed behind the node. |
9. In the PT telegrams section, make the desired settings.
|
Element |
Description |
|
Line sends PuT telegrams |
Click this button and select the vehicle journey attribute which defines whether the vehicle journey (which is a line in Vissim) sends PuT telegrams. In Vissim in the PT telegrams window, this value is displayed via the check box Line sends PuT telegrams. If in Visum the attribute value is zero, the check box will be disabled. |
|
Line |
Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the PT line field. |
|
Route |
Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Route field. |
|
Priority |
Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Priority field. |
|
Tram length |
Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Tram length field. |
|
Manual direction |
Attribute of the vehicle journey. In Vissim in the PT telegrams window, the values are displayed in the Manual direction field. |
10. Select the Further settings tab.
11. Make the desired changes.
|
Element |
Description |
|
Simulation time interval From / To |
Enter the beginning and the end of a time interval for the Vissim simulation period under From and To in the time format (hh:mm:ss). Notes The beginning and the end of the time interval may fall on two consecutive days as long as the period does not exceed 24 hours. If you use a calendar, you also need to select a day of the week or a date (Selecting a calendar ). |
|
Decimal places for coordinates |
Maximum If this option has been selected, the most accurate coordinates are used. Reduced (4) If this option has been selected, the coordinates are rounded to four decimal places. |
|
Signal controls |
Signal program or daily signal program list number for Vissig controls From attribute If this option has been checked, click the button and select the desired signal controller attribute. The daily schedule number of the signal controller is selected by default. Then the currently selected daily signal program list is exported. If no daily signal program list number is available, the signal program number is selected. Due to this setting, the currently selected Vissig signal program is exported. This is useful if each signal controller has only one signal program or if you have selected the relevant signal program for each signal controller for the export. Signal programs can be selected manually (Properties and options of signal controllers and Switching off or manually changing signal programs in Visum) or are set automatically during the procedure sequence (Adding procedures to the procedure sequence). Unique number If this option has been checked, enter a number in the entry field. This is useful if the same daily signal program number is used by all signal controllers in the selected time interval. Example: Monday 101, Tuesday 102 etc. |
|
|
Attribute defining the coordination group Click this button to select a signal controller attribute for the coordination group. Note The attribute will only be used for data import into PTV Balance. |
|
Settings for other objects |
Attribute defining the reduced-speed area of lane turns Use the button to select a lane turn attribute in order to specify a speed. Note Use the button to select a lane turn attribute in order to specify a speed.
Attribute defining the saturation flow rate of links Click this button to select a link attribute. Note The attribute will only be used for data import into PTV Balance. Attribute defining the saturation flow rate of turns Click this button to select a turn attribute. Note The attribute will only be used for data import into PTV Balance. |
|
Note: In Visum, there are nodes that allow turns, but do not have a lane definition. If, after the ANM data export from Visum, you want to generate Vissim connectors for these nodes, deactivate the (main) node attribute Use lane definition. Then information on a turn level will be used for these nodes, instead of detailed geometry data (i.e. here lane turn data). |
12. Confirm with OK.
The abstract network model is saved.
|
Notes: During ANM export of a Visum network containing a projection, the projection is also written to the ANM file, so that the geographic position of the data in Vissim is known. This allows you to show background maps. To use this function, you will need a Vissim version from 5.40-11 or 6.00-09. In the ANM export a signal controller is exported if it is assigned to at least one signalized node or main node. |
