Parameters of the Generate trip requests procedure
Element |
Description |
Delete existing trip requests of the demand segment before running the procedure |
Select this option to delete existing trip requests when the procedure is executed. |
OD demand section |
Generate trip requests only for demand between active zones Select this option to generate trip requests between active zones only. From-time To-time Use these input fields to specify the time period for which trip requests are generated from the demand. The time period refers to the beginning of the walk link that belongs to the trip request to the pickup node. This time may lie before the desired departure time of the trip request. Scale demand with the following factor In the input field, specify the factor with which the demand is to be scaled. Note Two possible use cases for the factor:
|
Distribution of the number of passengers traveling together per trip request section |
Enter numbers in the Weight column to determine how the number of passengers traveling together is distributed per trip. The percentage in the Share column is calculated automatically from the entries in the Weight column. |
Section Distribution of the pre-booking time of trip requests |
In the table, you can create a distribution for the pre-booking period when generating trip requests. The pre-booking period is the time between the arising of the trip request and the desired departure time. In the columns Lower limit, Upper limit, and Weight, enter values that define a pre-booking time interval. Values from 1 minute to 2880 minutes (48 hours) are permitted for the interval limits. The values of the individual intervals must not overlap. Use the Create and Delete buttons to insert new rows or delete existing ones. Maximum wait time Indication of the maximum time that passengers of the trip request have to wait. |
Miscellaneous section |
Random seed The value initializes the random number generator. Two procedure sequences with the same version file and identical seed random numbers are executed in the same way. If the random seed is varied, the stochastic functions are assigned to a different value sequence in Visum, so that the result of distributing the trip requests to the nodes changes. This can lead to different distribution results. Note Vary the random seed several times and then execute the procedures Generate trip requests and Tour planning in pairs, with an averaging of the skim values. |
Access and egress tab
Element |
Description |
Allocation of nodes to zones section |
A zone can be assigned the following From- and To-nodes:
Select this option to assign only nodes with an active connector to the zone.
Select this option to assign the node to the zone in whose polygon it is located. If there are several zones, the zone is assigned whose centroid is closest to the node. The value in the Buffer box specifies the minimum distance at which the node must be located to the centroid.
Select a node attribute whose value corresponds to the number of the zone that is assigned. You can also assign a node to multiple zones by selecting a string attribute whose list of zones is a comma-separated list. Example: An attribute with a value of 3, 5, 7 causes the node to be assigned to zones 3, 5, and 7.
Select a node attribute that determines the share of demand received by each node assigned to the zone. Note The attribute acts as a weight. If, for example, three nodes with the weights 1, 2, 3 are assigned to a zone, then the first node is assigned 1/6, the second node 2/6, and the third node 3/6 of the demand at the zone. |
PUDO scheme section |
Permit only active nodes as PUDO points Select this option to assign only active nodes as pickup and dropoff points. |