The Effective Integration of Analysis, Modeling, and Simulation Tools

units=MI

The original network describes distances in units of miles

direction_field=1

"1" indicates that NeXTA uses a direction field to interpret the link shape file

control_type_field=0

"0" indicates that NeXTA does not read any control type information from the node shape file

reserve_direction_field=1

"1" indicates that NeXTA will read direction-specific information for some non-directed links (two-way links)

offset_link=1

"1" indicates that NeXTA will add space between directional links to aid visualization

link_capacity_flag=0

"0" indicates that the link capacity is described on a per-lane basis

number_of_lanes_for_two_way_links=0

"0" indicates that lanes on two-way links are described using the number of lanes in each direction

use_optional_centroid_layer=0

"0" indicates that there is no additional shape file to read which only contains zone centroids

use_optional_connector_layer=0

"0" indicates that there is no additional shapefile to read which only contains zonal connector links

reference_file_name=Node_WGS84_202ft.shp

Identifies "Node_WGS84_202ft.shp" as the shape file that describes the nodes in the network

node_id=ID

Identifies "ID" as the name of the field that contains unique node numbers

TAZ=TAZID

Identifies "TAZID" as the name of the field that contains zone numbers mapped to the associated node numbers

reference_file_name=Roadway_WGS84_202ft.shp

Identifies "'Roadway_WGS84_202ft.shp" as the shape file that describes the links in the network

from_node_id=FROM_NODE

Identifies "FROM_NODE" as the name of the field that describes the starting node number for one direction on a link

to_node_id=TO_NODE

Identifies "FROM_NODE" as the name of the field that describes the ending node number for one direction on a link

link_id=ID

Identifies "ID" as the name of the field that contains unique link numbers

name=ST_NAME

Identifies "ST_NAME" as the name of the field that contains a street name for each link

length_in_mile=LENGTH

Identifies "LENGTH" as the name of the field describing the length (in miles) of each link

direction=DIR

Identifies "DIR" as the name of the field that describes each link’s directional properties (0 or 2 = two-way, 1 = one-way,
-1 = opposite direction from FROM/TO notation)

link_type =FT

Identifies "FT" as the name of the field that describes the functional classification (equivalent to link type in NeXTA/DTALite) for the directional link in FROM/TO notation

number_of_lanes=AB_LANES

Identifies "AB_LANES" as the name of the field that describes the number of lanes on the directional link in FROM/TO notation

lane_capacity_in_vhc_per_hour AB_CAPACIT

Identifies "AB_CAPACIT" as the name of the field that describes the lane capacity on the directional link in FROM/TO notation

speed_limit_in_mph=AB_SPEED1

Identifies "AB_SPEED1" as the name of the field that describes the free-flow speed on the directional link in FROM/TO notation

r_link_type =FT

Identifies "FT" as the name of the field that describes the functional classification (equivalent to link type in NeXTA/ DTALite) for the directional link in TO/FROM notation. There was no separate field for functional class in the reverse direction, so the same functional class was used for both directions

r_number_of_lanes =BA_LANES

Identifies "BA_LANES" as the name of the field that describes the number of lanes on the directional link in TO/FROM notation

r_lane_capacity_in_vhc_per_hour=BA_CAPACIT

Identifies "BA_CAPACIT" as the name of the field that describes the lane capacity on the directional link in TO/FROM notation

r_speed_limit_in_mph=BA_SPEED1

Identifies "BA_SPEED1" as the name of the field that describes the free-flow speed on the directional link in TO/FROM notation