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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Building an Abstract Network<br />

When modeling parking lots at the borders of a network, a<br />

single node on the border can be used for correctly placing both<br />

the origin and the destination parking lot (see illustration).<br />

Parking lots must be placed on an edge between two nodes. They may<br />

also be placed inside of an internal node (a node that is not situated at the<br />

border of the network).<br />

No more than one parking lot must be placed between any two nodes or<br />

within a node.<br />

A parking lot blocks the road in terms of path search: There are no paths<br />

that include a link that leads through a parking lot (i.e. where the parking lot<br />

would be ignored).<br />

If a parking lot (for destination traffic only) is placed on an outgoing link of<br />

the network, i.e. a link from which no other parking lots can be reached,<br />

then the relative flow of the parking lot must be set to zero. Make sure that<br />

there is at least one node on both sides of the parking lot.<br />

The cost for each edge where a parking lot is placed on, is determined as<br />

the average cost of all vehicles traveling into and out of the parking lot.<br />

CTRL+SHIFT+C sets the relative volumes of all parking lots to the volume<br />

totals of their paths as contained in the current path file (*.WEG). This can<br />

be helpful, if a new volume scenario (new matrix and path file) is to be<br />

applied to a network which was originally exported from VISUM, since<br />

relative volumes of origin parking lots might fit significantly better this way.<br />

Potential traps<br />

If you get an error message similar to "The destination parking lot 10 is part<br />

of several different edges", typically at least one node is missing or placed<br />

incorrectly. That results in multiple paths being found between the two nodes<br />

where the parking lot is placed, and for each path a separate cost is<br />

evaluated. On rare occasions, this could result in multiple different link costs<br />

for the same stretch of physical road and thus would lead to a wrong<br />

distribution of vehicles.<br />

To solve this problem, locate that parking lot in the <strong>VISSIM</strong> network and<br />

ensure, that<br />

► both, the path diverge point before the parking lot as well as the path<br />

merge point after the parking lot (in direction of driving) are included in a<br />

node and<br />

► both the nodes, where the parking lot is placed in between, are modeled<br />

correctly in terms of including the path diverge/merging point<br />

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

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

Saved successfully!

Ooh no, something went wrong!