24.08.2013 Views

VISSIM 5.30-05 User Manual

VISSIM 5.30-05 User Manual

VISSIM 5.30-05 User Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Results<br />

Node Evaluation<br />

The results of a Node Evaluation are grouped by turning movements and<br />

saved to a file with the extension *.KNA. Each turning relation is named<br />

using the approximate compass directions (N / NE / E / SE / S / SW / W /<br />

NW) of its first and last link (at the node boundary) with “North” direction<br />

facing to the top of the <strong>VISSIM</strong> network. If a compass with a user-defined<br />

North direction is active, any output direction data will refer to these settings,<br />

cf. section 4.1.1. Example: "NE-S" is a movement entering from the North-<br />

East and leaving to the South.<br />

The two link numbers can be written to the evaluation file as well to avoid<br />

ambiguity (two "parallel" turning relations with identical first and last links do<br />

look identical). All results are aggregated over a user-defined time period for<br />

time intervals with a user defined length.<br />

The node evaluation file *.KNA contains the following data:<br />

► File title<br />

► Path and name of the input file (File)<br />

► Simulation comment (Comment)<br />

► Date and time of the evaluation (Date)<br />

► Version no. with Service pack no. and Build no. (<strong>VISSIM</strong>)<br />

► List of selected parameters with brief description<br />

► Data block with a column for each selected parameter.<br />

The data section contains for every time interval:<br />

- one row per turning relation of each active node and<br />

- an additional row for the node total (turning relation "All").<br />

- an additional row per time interval with node number 0 containing the<br />

system total.<br />

The volume, average delay and standing time values as well as the number<br />

of stops are determined by a delay segment created automatically as a<br />

combination of new travel time measurements from all possible upstream<br />

starting points (with user-defined distance, but not extending across an<br />

upstream node boundary – unless there are more than four branches to side<br />

roads between the two nodes) to the node exit point of the respective turning<br />

relation. Also available is the number of passengers and the person delay by<br />

vehicle class.<br />

The queue length values are collected by a queue counter created automatically<br />

and placed at the first signal head or priority rule stop line on the<br />

link sequence of the turning relation. If there is no such cross section, the<br />

queue counter is placed at the node entry point. The node evaluation places<br />

a queue counter on every edge (movement) found inside the node. It is<br />

placed at the position of the signal head or priority rule stop line that is the<br />

closest one upstream to the node boundary on the respective edge.<br />

Neither scheduled stops at PT stops nor stops in parking lots are counted as<br />

stops. Neither passenger transfer times nor dwell times at STOP signs or the<br />

time spent in parking lots are counted as delays (though time losses due to<br />

<strong>User</strong> <strong>Manual</strong> © PTV AG 2011 541

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!