GIS Importer/Exporter

The object of this feature is to load GIS files (ESRI shapefiles or MapInfo files, among others) into Aimsun Next and to extract as much information as possible from them to create a traffic network. This enables you to create networks from several sources—for example an open-source GIS, such as QGIS (www.qgis.org), or a commercial product, such as ESRI.

You can also use other transportation packages as data sources, if they can export their network data into GIS files. These include, among others, Cube, and TransCAD. The ability to export information from the network geometry to GIS shapefiles is also available.

File formats available for the import/export of GIS information:

• ESRI shapefile (SHP)
• MapInfo file (MIF)
• GML (KML)
• GeoPackage (GPKG)
• GeoJSON (GEOJSON)
• Geodatabases (GDB directories)

GIS Importer Modes

The importer can import data into Aimsun Next in two different ways:

• As objects stored in the Aimsun document (internal layer, network or a particular type of object).
• As an external layer.

Importing in the Aimsun document

When importing data from another format with this option, Aimsun objects are created that are stored in the Aimsun document. The GIS files will no longer be used.

Importing as an External Layer

For some file formats (CAD, GIS, Raster Images) it is possible to store a reference to the file rather than store the data in the Aimsun document. In this case, some part of the information will reside in the Aimsun document and some part will be in the external files in its original format. The file must therefore remain accessible to the Aimsun document.

Aimsun Next uses external layers to identify when the data in a drawing layer comes from an external source. This kind of layer, on document retrieval, reads the external data and incorporates it into the traffic network (if the Auto Retrieve is active, otherwise the user can load the data at any moment using the Retrieve command). On document save, only the location of the external file will be stored.

Data in an external layer cannot be edited in Aimsun Next.

Shapefile Introduction

The Shapefile spatial data format is open and published by ESRI. Shapefiles store non-topological geometry and attribute information for the spatial features in a data set. Shapefiles can support point, line, and area features. The shapefile concept includes as many as five file types with specific file extensions. These files should be stored in the same workspace as the Aimsun document.

Shapefile file extensions and their function:

• SHP: the feature geometry.
• SHX: an index to the feature geometry.
• DBF: the associated dBASE file of attribute information.
• SBN and SBX: a spatial index of the features.
• AIN and AIH: the attribute index of active fields in a table or a theme’s attribute table.

When shapefile is imported to create data in the Aimsun Next document, the importer will use the feature geometry (shp) to create one object for each object found in the shapefile. It will then use the attribute information to set the Aimsun object attributes.

For example: if the option to create a network from a shapefile is selected, the importer will create a section for each object in shapefile. The geometry (must be either a line or polyline) will be used as the center line of each section. The attribute information will be used to set the number of lanes, capacity, road type, etc.

GIS File Units

Aimsun Next uses the metric system internally. When importing a GIS file, its coordinates are transformed to meters if they are in feet or latitude and longitude. In the second case, a conversion to WGS84 UTM coordinates is used. For this reason, if coordinates are not in meters, it is important to set correctly the UTM zone or WKT/EPSG reference for the model coordinate system before importing. This can be done when starting a new project, or from the project properties.

Data Requirements

The amount and quality of the data found in the GIS file will determine the quality of the imported data. If no number of lanes information is present, the importer will create single lane sections, if no speed information is found a default speed will be set (using the active road type) and so on.

Network Creation

Usually GIS data does not contain detailed geometry information of a traffic network. The missing information can be:

• On ramp or off ramp information: A section contains only the main lanes or, if the on/off ramp is included, it is coded as a full lane.
• Space for the nodes: a node is coded as a point instead of as an area.
• Turn information: The section connectivity, if present, only codes “all to all” lanes turns (instead of, for example, only left most lane is used to turn to section Y from section X).

The importer will automatically create the node area based on the in and out section geometry and will do its best to create the correct turn information. No on or off ramp will be created. However, the importer can be enhanced to extract non-standard information, see Customization Services.

Customization Services

The main objective of the importer is to create a network with the highest quality and maximum amount of information. If the information is coded in a format not supported by Aimsun Next, or if extra data can be extracted from other sources of information then the Aimsun support service (support@aimsun.com) offers customization services to enhance the importer.

These services include modification of the importer logic (to add implicit rules) and the inclusion of interfaces to other data sources such as Access or Excel files, spatial databases and files in custom data formats.

Importing a GIS File

This initial dialog asks which import mode to use: create an external layer, create the network geometry and topology, create detectors or centroids or VMS, create buildings. It also requests the units and locale and the attributes in the GIS file to use as name and external IDs of the created objects.

The stages are:

1. Start Aimsun Next.
2. Create a new document using a template (setting the WKT/EPSG).
3. From the File menu, execute the Import / GIS command.
4. Locate the GIS file to import.
5. The GIS Importer dialog appears.
6. The type name is used to assign a type to each object imported. The type name must refer either to a type that doesn't exist or to the name of an already existing type that can be used by the objects that will be imported. For more information, see the point Types and Objects in Aimsun Next below.
7. If importing data in a language not covered by the ASCII character set (i.e. Chinese, Japanese…) the correct encoding must be set.
8. Set the units which will be used in the attributes of the network (for example, speed in km/h or mph).
9. Aimsun Next will look at the coordinate system of the file, which is marked in the Coordinate System Information text box. The CS will be either kept, projected or re-projected, see Imported Data and the Coordinate System.
10. Set the attribute in the shapefile to be used as the external identifier. Aimsun Next will put its own identifier on each imported object. The external identifier is also used to keep the identifier used in the shapefile.
11. Set the attribute to be used as the name of each object.
12. Set how Aimsun Next will import the file using Import as combo.

The import options are:

• As an External Layer: the file is imported as it is, no modification is carried out and no data is created in the Aimsun document. Only the path to the GIS file is stored. When the user retrieves an Aimsun document that contains an external layer it will load the data from this GIS file.
• As an Internal Layer: the file is converted into lines and points. After the conversion, the original file will no longer be used. The objects created will be stored in the Aimsun document.
• As a Network: the GIS network will be converted into an Aimsun Next network. After the conversion, the original file will no longer be used. The objects created will be stored in the Aimsun document. A dialog asking for extra information will appear.
• As Centroids, VMS, Detectors or Bus Stops: the file will be used to create the selected Aimsun objects (centroids, VMS, detectors or transit stops). After the conversion, the file will not be used. The objects created will be stored in the Aimsun document.
• As Buildings: For each polygon on the file, an extruded polygon with the selected height will be created. The height can be either random, fixed, or can come from one of the attributes of the objects.

The imported objects will be placed in a new layer whose name will be the name of the type used.

Network Importer

The network importer will extract as much information as possible from a GIS file to create an Aimsun Next network. Refer to the How the Network Importer Works section for a detailed description.

Only GIS files that contain lines or polylines can be used to create a network. The importer will not work with polygons, arcs, points or multi-patch files.

The dialog will ask for information about the Section Creation, how to connect these sections in Node Creation, whether the links include Centroid Connections and whether any attribute can be used to assign VDFs to the sections. All the settings filled in the import dialog will be stored and kept for later GIS imports of the same shapefile.

Road Types

Before importing, as many road types as needed must be already available in the Aimsun document. These will be used to initialize values in the sections as they are created.

When the network importer creates the sections on the network it is possible to use an attribute in the shapefile to specify the road type to be used. If no equivalence is defined, the new sections will have the default road type (as defined using the Set as Default command in the Road Type context menu).

If no value or attribute correspondence is specified in the network importer dialog for a particular section attribute then the importer will use, if possible, the values found in the road type.

If the values from the road type instead are to be be given priority, this can be done by setting the following values in the importer:

• Speed: Select None
• Capacity: Select None
• Lane Width: Leave the field blank.

How the Network Importer Works

The network importer will create a section for each polyline found in the GIS file. Then it will create the nodes using the From Node and To Node attributes. Each node will contain all the possible turns between all the sections in that node. Then it will process each turn to remove the U-Turns and to fine-tune the lanes used in each turn. It will expand the nodes from a point to an area (optional step). The last (optional) step will be the import of extra node information from another GIS file.

Section Creation

Each polyline or line found in the GIS file will be converted to a new section.

The attributes in the GIS file are used to specify values for the number of lanes, speed, and capacity. If no information is present for any of these attributes the following values will be used:

Attribute Value ---------------------------- ---------------------------- Number of lanes 1 Speed Speed from Road Type Capacity Capacity from Road Type

If a single link in the GSI file generates sections in both directions, the attributes number of lanes, speed, and capacity can have two values. The first is for the primary section specified in the first column and the second for the reverse direction specified in the second column. If no attribute is specified in the second column, both directions are assumed to have the same value.

Road Types

The road type can be set in the Network Importer dialog. If no road type is set then the default Road Type will be used.

It is possible to add a number of lanes by road type if no attribute for number of lanes is specified in the Section Basic area. If the number of lanes is set to Don't Import, sections from this road type will not be imported.

Note that Aimsun Next uses metric units internally. The imported GIS file will create sections in meters. If the GIS file units were meters then the geometry in the GIS file and the center line of the sections will be the same (unless some post processing is applied such as making space for the nodes).

Omitting Links

Some GIS files can include links that might not be required, for example a metro or train line, or the internal links in a car park. These links can be omitted from the import by using their Road Type Attribute as above and setting the number of lanes to zero. If this is done, the Aimsun road type is not required.

Single and Dual Direction

Usually the polyline in the GIS file codes a centerline of a single section, and the order of the points in the polyline determines the direction of flow. However, the importer also supports the following alternatives:

• Inverse sections: The direction of flow is the inverse of the point order.
• Dual directions: The polyline codes the separation line between two sections, one in each direction.

It is possible to combine both possibilities (inverse and dual) to give four options. The Direction of Flow parameters inform the importer how to assign the section in the right direction and if the polyline codes dual directions and hence two sections should be generated.

To do this, select the attribute that has the information and for each possibility, enter the number, character or text that identifies the correct setting. Use a non-valid entry if a setting is not permitted in the imported file.

Example: a GIS file has an attribute named DIR with these possible values:

• 0: Single Direction
• 1: Inverted Direction
• 2: Dual Direction
• 3: Dual Direction, Inverted

Enter 0 - 3 to enumerate the values in the file. If any other character is found in the file, it will be ignored.

Note that if a link is coded in the GIS file as Dual Direction it should be only be represented in the file once. For example, if a GIS link had an attribute TWOWAY indicating it was a part of a normal bi-directional road (i.e not a dual carriageway) but in the GIS file both ways were represented as separate links, then that attribute should be ignored and the individual links imported as single direction road sections.

Number of Lanes and Dual Direction

When a single polyline generates two sections, one in each direction, the GIS file might contain two attributes for the number of lanes or one. In the later case, the number of lanes attribute found in the GIS file can be considered as the sum of all the lanes in both directions or as the number of lanes for each direction. If the number of lanes is the same for both directions and is equal to the value in the attribute, fill in both columns for the number of lanes. Otherwise, activate the toggle button Share Lanes in Dual Direction to divide the number of lanes between both sections.

Overlapped Sections

Some shapefiles contain two overlapped centerlines for each direction of flow. The Figure below shows two links, 1 and 2, which connect two nodes, A and B. Aimsun Next can automatically move these overlapped centerlines to ensure a more representative network geometry.

This operation is activated by checking the Unoverlap Sections option. The application will look for pair of sections that connect opposite nodes (section 1 goes from A to B, section 2 from B to A) and will displace the sections from their original centerline.

The current Rule of the Road will be used (as set in Preferences ) to determine which section will be translated to the left of the centerline and which one will be translated to the right.

Node Creation

If the GIS file contains topological information (in our case how objects are connected), it can be used to create nodes where sections on the network are connected. The “From Node” and “To Node” attributes are used to create such nodes.

Activate the toggle button Make Space For Nodes to expand the nodes from a point to an area.

After a node is created, turns on the node are also created to physically connect sections, to each other. As no information is available on which section is connected with which, the importer creates a connection between all the sections in the node.

Turn Refinement

Aimsun Next can specify which sections are connected to which sections in a node and also which lanes are used in a turn. For example, in a right turn, maybe only the rightmost lane of a section allows such a turn and the rest of the lanes are used to go straight ahead.

The importer classifies the turns to determine if they are a u-turn, left, right or straight turn. This uses the angle between the sections that are connected before the node is expanded.

After the turn angles have been calculated and the turns classified the importer will assign some or all of the lanes to the turn, considering other turns that start in the section, as follows:

Turn Type Other Turns on Sections Lanes Used

---

Left Straight Left most Left None All Left Right Half (left most) Right Straight Right most Right None All Right Left Half (right most) Straight None All

Expanding the Node

The last step will convert the node from a point to an area giving space to the turns. It will compress the sections that are part of the node reducing each section. The compression will make the section shorter but neither the section will be removed, nor any point on it.

The compression size will depend of the number of lanes of the sections involved. The importer will use the maximum size of the section width (number of lanes * lane size) divided by 2 then, to that result, it will add 10%.

This space will ensure a correct node area for most of the cases but it will not try to guarantee that some sections do not overlap the node.

Adding Extra Node Information

The user can specify a second GIS file with node information. The importer creates nodes based on the “From Node” and “To Node” settings. Each node created will have as its external identifier the value of the “From Node” or “To Node” attribute.

In order to use this second GIS file the importer must match the nodes created when importing the network with the nodes found in this shapefile. The importer will ask for the attribute that contains the identifier of the node. It will also ask for the attribute that contains the name of the node.

No geometrical information will be loaded, only the attributes and its values.

Centroid Creation

Some GIS files contain centroid connections as links. In this case, Aimsun Next can automatically create the centroids and connect them to the corresponding section or node.

In the Centroid tab folder, enable the Centroid connections in Links option and then tell the importer how it can recognize connections by selecting a value in Coding combo. You can either differentiate from links using a range of identifiers or the value of an attribute.

The second option allows a list of identifiers and/or a close range of values. The IDs are separated by commas, the range by the “-“ symbol. In order to differentiate the minus symbol from a negative number, add a space after the symbol, for example: “- 9”. If the second value in the range is not present, then all the range from the lower value up will be used. Example of valid inputs are:

• Links 1,2 and 3: 1,2,3
• From 1 to 20 (inclusive): 1 – 20
• From 20 (inclusive): 20 -

Centroid, VMS, Detector and Building Importer

The centroid importer creates unconnected centroids in the network, Therefore, if possible, it’s better to create centroids using the Network Importer (see Centroid Creation).This can be used with shapefiles that contain points or areas:

• From points: each point will be used to create a centroid. The point will not be created.
• From areas: a centroid will be created in the center of each area. The area will not be created.

For VMS and detectors the importer asks for the section identifier (ID or external ID) in which the object resides and the offset to the section start.

The building importer will use the polygon in the shapefile to create an extruded polygon (with 3D information) and with the height as specified either in an attribute of the shapefile or using a random number.

Exporting Shapefiles

Using File > Export, you can export network information to shapefiles. You must specify where to generate the files and the coordinate system to use.

Note that if the designated folder contains previous files, they will be overwritten.

You must also specify the file format to saved: SHP, MIF, KML, GPKG, or GEOJSON.

The exporter will generate files for the following type of objects by default:

• Sections
• Nodes
• Turns ( In the Complex mode)
• VMSs
• Meterings
• Detectors
• Centroids
• Centroid connections
• Transit stops
• Labels
• Polygons

More control of what can be exported is available in the filters tab of the export dialog where the attributes of objects can be selected to be used or displayed in the GIS.

For MapInfo, GML, and GeoJSON there will be a file for each object type, with the appropriate filename extension. In the case of GeoPackage, only one file will be exported, containing all the exported object types.

Attributes exported are covered in the next section.

Exporting to ESRI Shapefiles

Sections file

Sections will be placed in a shapefile with multiple arc shapes with Z coordinate (SHPT_ARCZ). The generated files are:

• sections.shp
• sections.shx
• sections.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• nb_lanes: Number of lanes.
• speed: Section speed in km/h.
• capacity: Section capacity in PCUs/h.
• fnode: Origin node (using the Aimsun node identifier).
• tnode: Destination node (using the Aimsun node identifier).
• rd_type: Road Type identifier

Sections geo file

Additional files to provide the X and Y coordinates of the two extreme points on the axis of the section, and of the 4 extreme points to the edge of the section (entrance point at right, entrance point at left, exit point at left and exit point at right; left and right considering the section direction) are also created. These files are:

• sectionsgeo.shp
• sectionsgeo.shx
• sectionsgeo.dbf

The attributes written in the DBF file are the X and Y coordinates of the above mentioned 6 points:

• fx : X of the axis point at the entrance
• fy : Y of the axis point at the entrance
• tx : X of the axis point at the exit
• ty : Y of the axis point at the exit
• lfx : X of the left point at the entrance
• lfy : Y of the left point at the entrance
• rfx : X of the right point at the entrance
• rfy : Y of the right point at the entrance
• ltx : X of the left point at the exit
• lty : Y of the left point at the exit
• rtx : X of the right point at the exit
• rty : Y of the right point at the exit

Nodes file

Nodes will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• nodes.shp
• nodes.shx
• nodes.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• intersection: a 0 if it is a simple node or a 1 if it is a complex node.

Turns file

Turns will be placed in a shapefile with multiple arc shapes with Z coordinate (SHPT_ARCZ). The generated files are:

• turns.shp
• turns.shx
• turns.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• id_node: Aimsun node identifier.
• speed: Turn speed in km/h.
• sign: Warning sign. Possible values are:
  • 0: no sign
  • 1: yield
  • 2: stop
• fsection: origin section (using the Aimsun section identifier)
• tsection: destination section (using the Aimsun section identifier)
• flaneA: Origin lane, left most.
• flaneB: Origin lane, right most.
• tlaneA: Destination lane, left most.
• tlaneB: Destination lane, right most.

VMSs file

VMSs will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• vms.shp
• vms.shx
• vms.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• section_id: identifier of the section
• position: position, in meters, from the entrance of the section

Meterings file

Meterings will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• meterings.shp
• meterings.shx
• meterings.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• section_id: identifier of the section
• position: position, in meters, from the entrance of the section

Detectors file

Detectors will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• detectors.shp
• detectors.shx
• detectors.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• section_id: identifier of the section.
• position: position, in meters, from the entrance of the section.
• length: detector length in meters.
• from_lane: left most lane in where the detector is (numbered from 0 to N-1).
• to_lane: right most lane in where the detector is (numbered from 0 to N-1).

Centroids file

Centroids will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• centroids.shp
• centroids.shx
• centroids.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• type: type of the centroid connections, either from, to, from_to or none.
• percentages: percentages defined for the centroid, either nothing, origin, destination, both or same.

Centroid connections file

Centroids will be placed in a shapefile with multiple point shapes with Z coordinate (SHPT_ARCZ). The generated files are:

• centroid_connections.shp
• centroid_connections.shx
• centroid_connections.dbf

The attributes written in the DBF file are:

• id_cent: Aimsun Identifier for the centroid.
• id_object: Aimsun Identifier for the object connected (either a section or a node).
• obj_type: Whether the connection is to a section or to a node
• direction: whether the connection is a from (from the object to the centroid) or a to connection (to the object from the centroid).
• percentage: percentage defined for the connection in the centroid editor.

Transit stops file

Transit stops will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• bus_stops.shp
• bus_stops.shx
• bus_stops.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• section_id: identifier of the section
• position: position, in meters, from the entrance of the section
• length: length, in meters.
• Lane: lane where the stop is located
• stop_type: stop type, either 0 if normal, 1 if bus bay or 2 if bus terminus.

Labels file

Labels will be placed in a shapefile with one point shape with Z coordinate (SHPT_POINTZ). The generated files are:

• labels.shp
• labels.shx
• labels.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• label: ASCII version of the label (Aimsun Next uses UNICODE strings but shapefiles do not).

Polygons file

Labels will be placed in a shapefile with multiple point shapes with Z coordinate (SHPT_POINTZ). The generated files are:

• polygons.shp
• polygons.shx
• polygons.dbf

The attributes written in the DBF file are:

• id: Aimsun Identifier.
• name: Object name.
• layer: Polygon’s layer.
• fill: 1 if it is filled and 0 otherwise
• color: polygon’s brush color.

Types and Objects in Aimsun Next

A GIS file contains geometry and attribute information for spatial features. The geometry can be points, lines, and areas. The information assigned to the geometry is what makes a feature type different from another one. For example, a GIS file can contain points that represent airports or cities. The difference between one type and another is the information associated with it (number of terminals in an airport or number of inhabitants in a city).

When Aimsun Next imports a GIS file it creates objects of a type based on the geometry type used in it. The problem is how to deal with the attributes. For example, when importing airports (points) and later on cities (points too), Aimsun Next will create points for each new object.

There are two options in dealing with the attributes: one is to add all attributes to all points which means a given point will have airport and city attributes but some of them, depending of the type, will be unused. The other option is to only add the relevant attributes to each point which means the point representing an airport will have airport attributes and no city attributes which implies different instances of the same type of objects (point) will have different sets of attributes for different instances of it

The solution implemented in Aimsun Next is the extensible object model in which:

• New types can be added to the system at run time.
• New attributes can be added to any type at run time.

Following the example, Aimsun Next will create a new type, Airport, to hold all the airports. For this type, the attributes found in the GIS file will be used. In this way, Aimsun Next will know which points are airports, which are cities and which are simple points.

The new type is created as a subtype of a geometrical Aimsun Next type based on the type held in the GIS file. The GIS Importer therefore requires the name of the type to be used for the new objects.

Incompatible Types

When Aimsun Next imports a GIS file it uses the specified type name (from the GIS Importer dialog) to create a new type or to use it if it was already present. If the type was already present then it must be compatible with the information found in the GIS file. That is:

• The geometrical type must be the same. It is not possible to use the type City for points and subsequently attempt to use it for polygons.
• The attributes of the type must be the same. In this case, we cannot first import cities creating the City type and then try to import airports using the same type (an unusual operation) as the attributes of the airports GIS file will not be present in the City type.

When an types are incompatible, the importer will present an error dialog such as shown below.