When importing intersection data, 'Intersections’ and legs are mapped to nodes, main nodes, and zones. Afterwards their associated attributes as well as lanes, lane turns, detectors, signal groups, stages, crosswalks and their allocations are imported. Further information is stored in user-defined attributes.
Imported files
The zipped file that is read during import contains the files Detectors.csv, Intersections.csv, Legs.csv, Phases.csv, Signalgroups.csv and Streets.csv. Only the data of the Intersections.csv and Legs.csv files are mandatory. All column headers are created with the IntersectionDataImport_ prefix as user-defined attributes of the respective network object during import and the values are transferred. This also applies to columns that are not relevant for the import into Visum.
Descriptions of the data relevant to Visum follow.
Legs.csv
Each row of the file describes a node leg (NodeLeg). All values are written as user-defined attributes to the respective node leg. The file is necessary.
The following data is imported:
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
NodeLeg |
Key of the leg |
String |
Yes (mandatory) |
|
Street |
Key of the street from Streets.csv |
String |
Yes (optional) |
|
Angle |
Counterclockwise leg angle |
Double |
Yes (mandatory) |
|
ReferenceNodeLeg |
Key of the reference leg (indicates to which leg the offset refers) |
String |
Yes (optional) Specifies which leg(NodeLeg) of the intersection the offset refers to. String value that can be empty. |
|
Offset |
Offset from the center of the intersection along the reference leg in meters |
Int >= 0 |
Yes (optional) |
|
InboundLanes |
Number of inbound lanes |
Int >= 0 |
Yes (mandatory) |
|
OutboundLanes |
Number of outbound lanes |
Int >= 0 |
Yes (mandatory) |
|
SlipLanes |
Number of lanes with a separate right-hand turn (right-hand traffic) or left-hand turn (left-hand traffic) |
Int >= 0 |
Yes (optional) |
|
SlipLanePedCrossing |
Information whether there is a crosswalk at the channelized turn |
Bool. All entries are considered true (column not empty). |
Yes (optional) |
|
PedCrossingPosition |
Offset for the position of the crosswalk across the leg |
Double |
Yes (optional) |
|
LaneArrows |
Definition of turns on the lane. The number of entries must correspond to 'InboundLanes'. |
Composite string consisting of the components "l", "lr", "ltr", "t", "tr", "r", each separated by spaces. |
Yes (optional) |
|
NextIntersection |
Key of the next intersection along the leg |
|
Yes (optional) |
Intersections.csv
Each row of the file belongs to a node. All values are written as user-defined attributes to the respective node. The coordinate transformation is unknown. It must be specified during the import. The file is necessary.
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
Intersection_X |
X-coordinate of the intersection with regard to the coordinate system from the parameters |
Double |
Yes (mandatory) |
|
Intersection_Y |
Y-coordinate of the intersection with regard to the coordinate system from the parameters |
Double |
Yes (mandatory) |
Detectors.csv
Each row of the file describes a detector. All values are written as user-defined attributes to the respective detector. The file is optional.
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
Detector |
Key of the detector |
String |
Yes (mandatory) |
|
NodeLeg |
Key of the leg |
String |
Yes (mandatory) |
|
Lane |
Lane index of the lane on which the detector is located. Counting takes place from left to right on the incoming leg. Only inbound lanes count. |
Int >= 0 |
Yes (mandatory) |
|
DetectorPos |
Distance of the detector from the stop line |
Double >= 0 |
Yes (mandatory) |
Phases.csv
Each row of the file describes a signalization stage. All values are written as user-defined attributes to the respective stage. The file is optional.
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
Name |
Key of the stage |
String |
Yes (mandatory) |
|
SignalGroups |
List of signal group keys assigned to the stage separated by commas or spaces. |
String |
Yes (mandatory) |
Signalgroups.csv
Each row of the file describes a signal group. All values are written as user-defined attributes to the respective signal group. The file is optional.
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
SignalGroup |
Key (number) of the signal group |
Int |
Yes (mandatory) |
|
FromNodeLeg |
Key of the From-leg of the turn belonging to the signal group or, in the case of pedestrian signal groups, key of the leg of the crosswalk |
String |
Yes (mandatory) |
|
ToNodeLeg |
Key of the To-leg of the turn belonging to the signal group |
String |
Yes (mandatory) |
|
Type |
Turn type of the signal group, possible are: l - left, t - through,r - right,p - pedestrian. |
String |
Yes (mandatory) |
Streets.csv
Each row describes the street name or street type for a combination of node and street index (e.g. TRAM). The street name is written as a user-defined attribute to the node leg (NodeLeg) that refers to the corresponding street. The file is optional.
|
Column |
Definition |
Type |
Relevant for Visum |
|
Intersection |
Key of the intersection |
String |
Yes (mandatory) |
|
Street |
Key of the street |
String |
Yes (mandatory) |
|
Name |
Name of the street |
String |
Yes (mandatory) |
