Traffic simulation input data files, Reference: http://www.dynasmart.umd.edu/documents/DYNASMART-P_Users-Guide-1.0.pdf
Input File
bus.dat
control.dat
demand.dat
destination.dat
incident.dat
leftcap.dat
movement.dat
network.dat
origin.dat
output_option.dat
path.dat
pricing.dat
ramp.dat
scenario.dat
SuperZone.dat
system.dat
TrafficModel.dat
vehicle.dat
vms.dat
WorkZone.dat
StopCap2Way.dat
StopCap4Way.dat
GradeLengthPCE
Description
information regarding the buses including the trajectories, location of stops, dwell time, etc
the type of traffic control at each node and phasing information, if the intersection is signalized
temporal and spatial distribution of demand
destinations in the network
the locations of road closures (incidents/work zone applications), severity, timing, etc
left-turn capacity at signalized intersections
the allowed movements of vehicles (right turns, left turns, through, and others)
the network configuration, zoning and link characteristics
the generation links of the network
the frequency of writing to output files
the vehicle trajectory to be used in conjunction with vehicle.dat
the pricing on the HOT/HOV lanes
ramp locations, detector locations, metering rate, and its timing
the basic simulation variables
the mapping of zones to super zones
election of the solution mode, length of the planning horizon, aggregation and assignment interval
the type of speed-density models specified and their corresponding parameters
the number of vehicles to be loaded
the location, type, and time of activation for variable message signs
the number of work zone links, duration, capacity reduction, new speed limit, and discharge rate
the capacity of approaches at two-way stop-controlled intersections
the capacity of approaches at all-way stop-controlled intersections
the effect of grade length and truck percentage on Passenger Car Equivalent (PCE) factors
Graphical representation and animation (GUI) input data files
linkname.dat
names of links (i.e. street names)
linkxy.dat
links starting and ending nodes. For more accurate representation, users can specify as many
feature points as needed to create curvatures
xy.dat
the coordinates of the physical nodes to be used by the DYNASMART-P GUI
zone.dat
information that describes the zonal boundaries
Status
May be empty
Required
Required
Required
May be empty
Required
Required
Required
Required
Required
May be empty
May be empty
May be empty
Required
Optional
Required
Required
May be empty
May be empty
May be empty
Required
Required
Required
pg
83
50
60
64
77
52
44
42
62
93
68
82
76
71
66
91
46
67
73
78
54
55
47
Optional
Optional
39
38
Optional
Optional
37
59
Quarterly Report for
Decision Support System for Evacuation Route-Schedule Planning:
Determining Optimal Network Configuration
Period: 07/01/2004 ~ 09/30/2004
Shashi Shekhar (shekhar@cs.umn.edu)
Qingsong Lu (lqingsong@cs.umn.edu)
Sangho Kim (sangho@cs.umn.edu)
Task Number 2: Analysis of DYNASMART-P Data Formats
To create a project, the following data categories are needed:
 Network data
 Control data
 Demand data
 Scenario data
 System data
DYNASMART-P accounts for 7 different link types. These link types are:
1. Freeways: links with fully controlled access and high speed limits such as interstate highways
2. Freeways with detectors: to be used for ramp metering purposes
3. On-ramps: links that provide entry locations to freeways
4. Off-ramps: links that provide exit locations from freeways
5. Arterials: links with fully signalized/controlled intersections
6. HOV/HOT links: links specifically designed to model HOV/HOT links
7. Highways: links with higher speeds and more controlled access than arterials
TrafficFlowModel.dat
DYNASMART-P uses a modified Greenshield model for traffic propagation. In the current version,
two types of the modified Greenshild family models are available. Type one model is a two-regime model
in which constant free-flow speed is specified for the free-flow regime and Modified Greenshield model
is specified for the congested-flow regime. The second type applies the modified Greenshield model for
both free- and congested-flow regimes.
Intersection control types modeled in DYNASMART-P include
 no control
 stop and yield signs
 pre-timed
 actuated signals.
DYNASMART-P has two methods to load vehicles on the network,
(1) using a time-dependent OD demand matrix notation, albeit of a dynamic one
(2) using a predefined vehicle-path dataset, which is ideal to model trip chaining as well as for
providing a controlled environment for assessing the short-term impacts of several traffic management
strategies.
SuperZone.dat
DYNASMART-P also has an option that allows for the aggregation of TAZs into a single SuperZone (i.e.
destinations are linked to the same centroid). Each aggregated zone will have a centroid, which is created
internally by DYNASMART-P. The actual connections between the destination nodes and the centroids
are handled internally as well. Essentially, DYNASMART-P allows the user to specify which zones are to
be aggregated. It then creates a centroid for each super-zone and connects all the destination nodes in the
super-zone to its centroid.
Scenario.dat
User Class 1: Unresponsive
Vehicles that follow their given paths, and will not respond to any en-route information or guidance
devices such as VMS.
User Class 2: System Optimal (SO)
Vehicles following paths determined under the SO objective. This class is only recognized in the
iterative procedure
User Class 3: User Equilibrium (UE)
Vehicles following paths determined with the UE objective. This class is only recognized in the iterative
procedure
User Class 4: En-route info
Vehicles that receive real-time en-route information and are allowed to re-route at any intersection. The
re-routing is based on the boundedly rational behavior mechanism.
User Class 5: VMS Responsive
Vehicles that follow their given paths; and are responsive to external real-time information via VMS. This
user class could receive pre-trip information
vms.dat
types of VMS supported by DYNASMART-P.
Type 1 VMS is the speed advisory type
Type 2 VMS is detour type
Type 3 VMS is congestion warning
Reference: http://www.dynasmart.umd.edu/documents/DYNASMART-P_Users-Guide-1.0.pdf