Skip to content

Visum Importer

Importing a network from Visum

The Visum importer imports Visum networks (NET files) whose language is English, German or French. Currently, supported versions range from 2.8 to 9.0. A NET file can be exported from Visum. Aimsun Next can not directly read a Visum VER file.

A Visum network must be imported into a new Aimsun document created by using the File > New menu option. It is not possible to import a Visum network into a previously existing Aimsun traffic network.

To import a Visum network:

  1. Select File > Import > Visum Network Files.

  2. Find the NET file you want to import and click Open. The Visum Transport Systems dialog is displayed.

  3. Adjacent to Create Sections Accepting, select one of the two following options from the drop-down list:

  4. Any Transport System Selected to import the sections where at least one of the selected Transport Systems is permitted.

  5. All Transport Systems Selected to import the sections where all selected Transport Systems are permitted.

  6. From the Transport System list, tick one or more of the options in the Import column.


    Visum Importer Dialog

  7. Click OK to complete the import.

Relationships between Visum and Aimsun objects

Infrastructure

Visum Links are imported as Aimsun road sections using the following mapping:

  • External Id: Visum Link No is imported as the Aimsun road section External ID.
  • Name: Visum Link Name is imported as the Aimsun road section Name.
  • Origin Node: Visum Link FNode is imported as the Aimsun road section Origin Node.
  • Destination Node: Visum Link TNode is imported as the Aimsun road section Destination Node.
  • Points: If the Visum Link have Link Polygons defined, these points are used to calculate the Aimsun road section Polyline, otherwise the section is created as a simple segment (using origin and destination node points).
  • On/Off Ramp: On/Off Ramp information is imported from Visum Lanes Table to the Aimsun road sections.
  • Number of Lanes: Visum Link NLanes is imported as the Aimsun section Number of Lanes (excluding On/Off Ramps).
  • Length: Visum Link Length is imported as the Aimsun road section Length.
  • Speed: Visum Link V0prt is imported as the Aimsun road section Speed Limit.
  • Capacity: Visum Link Capprt is imported as the Aimsun road section Capacity.
  • Road Type: Visum Link Type is imported as the Aimsun road type.
  • Reserved Lanes: Visum Link BUS_LANES are imported as Aimsun transit reserved lanes.
  • Lane Capacity: Visum Link Lane Capacity is imported as an Aimsun road section attribute with external name "GKSection::Visum::LaneCapacity".

Visum Link Types are imported as Aimsun Road Types using the following mapping:

  • External Id: Visum Link Type No is imported as the Aimsun Road Type External ID.
  • Name: Visum Link Type Name is imported as the Aimsun Road Type Name.
  • Speed: Visum Link Type V0prt is imported as the Aimsun Link Type Speed Limit.
  • Capacity per Lane: Visum Link Type Capprt is imported as the Aimsun Link Type Capacity.

Visum Nodes and Aimsun Nodes

Visum Nodes are imported as Aimsun Nodes using the following mapping:

  • External Id: Visum Node No is imported as the Aimsun Node External ID.
  • Geometry: Aimsun Node Geometry is calculated adapting Section geometry to avoid Section overlaps.
  • Main Node No: Visum Main Node No is imported as the Aimsun Node attribute with external name "GKNode::Visum::MainNodeNo".
  • Node Control Type: Visum Node Control Type is imported as the Aimsun Node attribute with external name "GKNode::Visum::NodeControlType".
  • Main Node Control Type: Visum Main Node Control Type is imported as the Aimsun Node attribute with external name "GKNode::Visum::MainNodeControlType".
  • Node ICAsneakers: Visum Node ICAsneakers is imported as the Aimsun Node attribute with external name "GKNode::Visum::NodeICAsneakers".
  • Main Node ICAsneakers: Visum Main Node ICAsneakers is imported as the Aimsun Node attribute with external name "GKNode::Visum::MainNodeICAsneakers".
  • Major Flow Orientation1: Visum Major Flow Orientation1 is imported as the Aimsun Node attribute with external name "GKNode::Visum::MajorFlowOrientation1".
  • Major Flow Orientation2: Visum Major Flow Orientation2 is imported as the Aimsun Node attribute with external name "GKNode::Visum::MajorFlowOrientation2".
  • Preset Follow Up Time: Visum Roundabout Inscribed Diameter is imported as the Aimsun Node attribute with external name "GKNode::Visum::RoundaboutInscribedDiameter".
  • Preset Follow Up Time: Visum ICA Entry Width is imported as the Aimsun Node attribute with external name "GKNode::Visum::ICAEntryWidth".
  • Preset Follow Up Time: Visum ICA Approach Half Width is imported as the Aimsun Node attribute with external name "GKNode::Visum::ICAApproachHalfWidth".
  • Preset Follow Up Time: Visum ICA Flare Length is imported as the Aimsun Node attribute with external name "GKNode::Visum::ICAFlareLength.
  • Preset Follow Up Time: Visum Round About Entry Radius is imported as the Aimsun Node attribute with external name "GKNode::Visum::RoundAboutEntryRadius".
  • Preset Follow Up Time: Visum ICA Entry Angle is imported as the Aimsun Node attribute with external name "GKNode::Visum::ICAEntryAngle".

Visum Turns and Aimsun Turns

Visum Turns are imported as Aimsun Turns using the following mapping:

  • Node: Visum Turn ViaNode is imported as the Aimsun Turn Node.
  • Origin Section: Visum Turn ViaNode and FNode are used to deduce the Aimsun Turn Origin Section.
  • Destination Section: Visum Turn ViaNode and TNode are used to deduce the Aimsun Turn Destination Section.
  • User-defined Cost: Visum Turn T0prt is imported as the Aimsun Turn User-defined Cost.
  • Main Node No: Visum Main Node No is imported as the Aimsun Turn attribute with external name "GKNode::Visum::MainNodeNo".
  • Capacity: Visum Turn Capprt is imported as the Aimsun Turn specific attribute with external name "GKTurning::VISUM::Capacity".
  • Use Preset Critical Gap: Visum Use Preset Critical Gap is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::UsePresetCriticalGap".
  • Preset Critical Gap: Visum Preset Critical Gap is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::PresetCriticalGap".
  • Use Preset Follow Up Time: Visum Use Preset Follow Up Time is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::UsePresetFollowUpTime".
  • Preset Follow Up Time: Visum Preset Follow Up Time is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::PresetFollowUpTime".
  • ICA Use Preset Sat Flow Rate: Visum ICA Use Preset Sat Flow Rate is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::ICAUsePresetSatFlowRate".
  • ICA Preset Sat Flow Rate: Visum ICA Preset Sat Flow Rate is imported as the Aimsun Turn attribute with external name "GKTurning::Visum::ICAPresetSatFlowRate".

Turn Lane information is not defined in Visum for all turns. Aimsun will create turns in two different ways depending on the information that Visum provides:

Nodes with out Lane Turns defined in Visum

Aimsun Next creates all possible Turns (excluding U-Turns) with all the Section lanes connected.

Nodes with Lane Turns defined in Visum

Visum Turn Lanes are imported as Aimsun Turns using the following mapping: - Node External Id: Visum NodeNo is used to find the Aimsun Turn Node. - Origin Section: Visum FromLinkNo is imported as Origin Section. - Destination Section: Visum ToLinkNo is imported as Destination Section. - Origin Lane: Visum FromLaneNo is used to provide the Aimsun Turn Origin From Lane and Origin To Lane. - Destination Lane: Visum ToLaneNo is used to provide the Aimsun Turn Destination From Lane and Destination To Lane.

Visum Detectors, Visum Count Locations and Aimsun Detectors

Visum Detectors are imported as Aimsun Detectors using the following mapping:

  • External Id: Visum Detector No is imported as the Aimsun Detector External ID.
  • Name: Visum Detector Name is imported as the Aimsun Detector Name.
  • Lanes: Visum Detector Lane and NLanes are used to deduce the Aimsun Detector From Lane and To Lane.
  • Section: Visum Count Location LinkNo, FNode, and TNode are used to deduce the Aimsun Detector Bottom Section.
  • Position: Visum Count Location RelPos is imported as the Aimsun Detector Position.

Traffic Demand

Visum Zones and Aimsun Centroids

Visum Zones are imported as Aimsun Centroids using the following mapping:

  • External Id: Visum Zone No is imported as the Aimsun External ID.
  • Position: Visum Zone XCoord and YCoord are imported as the Aimsun Centroid Position.

Visum Connectors and Aimsun Centroid Connections

Visum Connectors are imported as Aimsun Centroid Connections using the following mapping:

  • Centroid: Visum Connector ZoneNo is imported as the Aimsun Centroid Connection Centroid.
  • NodeId: Visum Connector NodeId is imported as the Aimsun Centroid Connection Connected Object.
  • Connection Type: Visum Connector Dir is imported as the Aimsun Connection Type.

Visum Transport Systems and Aimsun Vehicle Types

Visum Transport Systems are imported as Aimsun Vehicle Types using the following mapping:

  • External Id: Visum Transport System Name is imported as the Aimsun Vehicle Type External ID.
  • Name: Visum Transport System Name and Code are imported as the Aimsun Vehicle Type Name.
  • PCU: Visum Transport System PCU is imported as the Aimsun Vehicle Type PCU.

Visum OD Matrices in *.mtx files and Aimsun OD Matrices

The importer finds all the Visum OD Matrix files in *.mtx format located in the same folder as the *.net file and creates an Aimsun OD Matrix for each *.mtx file it reads. The OD Matrix properties such as number of trips between each pair of zones, time period and scaling factor stored in Visum *.mtx files are imported and hold the same definition as OD Matrices in Aimsun Next. The exception is the Vehicle Type as in the Visum *.mtx file the Vehicle Type is not associated with OD Matrix, while the OD Matrix formulation in Aimsun Next does require selection of the associated Vehicle Type.

All the *.mtx files need to be saved as VisumTransportSystemName.mtx as Aimsun Next assigns to the vehicles type to the imported OD Matrix that has exactly the same name of the *.mtx file.

Importing OD Matrices will not automatically store the trips in the Aimsun document, they will be created as External Matrices. These OD Matrices will be stored in the Aimsun document only if specified in the matrix options.

Transit Lines

Visum Lines, Visum Line Routes, Visum Line Route Items, and Aimsun Transit Lines

Visum Lines, Line Routes, and Line Route Items are imported as Aimsun Transit Lines using the following mapping:

  • Name: Visum Line Route Name and DirectionCode are imported as the Aimsun Transit Line Name.
  • Vehicle Type: Visum Line TSysCode is imported as the Aimsun Transit Line Schedule Departure Vehicle Type.
  • Bus Stop: Visum Line Route Item StopPointNo is imported as the Aimsun Transit Line Transit Stop.
  • Section: Visum Line Route Item NodeNo is imported as the Aimsun Transit Line Section.

Visum Stop Points and Aimsun Transit Stops

Visum Transit Stops are imported as Aimsun Transit Stops using the following mapping:

  • Name: Visum Stop Point Name is imported as the Aimsun Transit Stop Name.
  • Position: Visum RelPos is imported as the Aimsun Transit Stop Position.

Note: A current limitation on the import of Transit Stops

Visum Transit Stops that are located directly on nodes are not imported as part of this process. However, all Visum Transit Stops located on links (whether a direction has been specified or not) are imported.

Control plans

Visum Signal Groups, Visum Signal Control to Node, Visum Signal Groups to Lane Turn and Aimsun Signal Groups

Visum Signal Groups, Signal Control to Node, and Signal Groups to Lane Turn are imported as Aimsun Signal Groups using the following mapping:

  • External Id: Visum Signal Group No is imported as the Aimsun Signal Group External ID.
  • Name: Visum Signal Group Name is imported as the Aimsun Signal Group Name.
  • Turn: Visum Signal Groups to Lane Turn FromLinkNo and ToLinkNo are imported as the Aimsun Signal Group Turn.
  • Node: Visum Signal Control to Node NodeNo is imported as the Aimsun Signal Group Node.

Visum Signal Control, Visum Signal Group, Visum Signal Control to Aimsun Node, Aimsun Control Node, and Aimsun Control Plan

Only Visum Signal Controls of types Fixed and Signal Group Based are imported. Visum Signal Control, Signal Group, and Signal Control to Node objects are imported as Aimsun Control Nodes and Control Plans using the following mapping:

  • Cycle: Visum Signal Control CycleTime is imported as the Aimsun Control Node Cycle Time.
  • Offset: Visum Signal Control Offset is imported as the Aimsun Control Node Offset.
  • Phase Start: Visum Signal Group GTStart is imported as the Aimsun Phase Start Time.
  • Phase Duration: Visum Signal Group GTStart and GTEnd are used to calculate Phase End Time.
  • Phase Yellow Time: Visum Signal Group Amber is imported as the Aimsun Phase Yellow Time.
  • Phase Minimum Green Time: Visum Signal Group MinGreenTime is imported as the Aimsun Phase Minimum Green Time.

Preferences

  • Rule of the Road: Visum LeftHandTraffic is imported as the Aimsun Rule of the Road.
  • Coordinate System: Visum ProjectDefinition is imported as the Aimsun Default Coordinate System

Notes

  • Tables and columns read can be found within the file attributes.vis. This file can be found in the path:
    • Installation folder of Aimsun Next/plugins/VISUMIMPORTERDATA