You can import the following MaaS Modeller files into Visum:
- TripStops.net for tour plans
- TripRequests.net for trip requests
|
Note: To import a tour plan from MaaS Modeller, it is mandatory that the corresponding trip requests are available in a TripRequests.net file. |
The tour plan import file
Text files with a net file extension are required, but they are not real Visum network files. The header of the file looks like this:
$VISION
* xMaas
* [Date]
*
* Table: Version block
*
$VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
1.000;TourPlan;ENG;KM
*
* Table: TripStops
*
$TRIPSTOP:VEHID;SEATCAP;NODENO;BEGINTIME;ENDTIME;TASK;TRIPREQUESTNO;ZONENO
The rows with the actual tour plan follow. There is a row for each operation of a vehicle. The following columns exist:
|
Attribute name |
Description |
|---|---|
|
VEHID |
Identification number of the vehicle |
|
SEATCAP |
Seating capacity of the vehicle It must be identical for all TripStops of the same VEHID. |
|
NODENO |
Number of the node at which the operation takes place
|
|
BEGINTIME, ENDTIME |
Start and end of the operation for TASK = 'Pickup': Start and end of the boarding procedure. for TASK = 'Dropoff': Start and end of the alighting procedure. for TASK = 'Wait': can only occur when a vehicle arrives at a node and waits there until the first pick-up procedure begins. In this case, BEGINTIME and ENDTIME are the beginning and end of the waiting procedure at the node until the first pick-up procedure begins. Input format: hh:mm:ss, greater than or equal to 24:00:00 is allowed. |
|
TASK |
'Pickup', 'Dropoff' or 'Wait' Note The values of the tasks 'Charging' and 'Relocation' are stored in the attributes 'ChargingTime' and 'Dwell time at holding area' of the network object 'Path item'. |
|
TRIPREQUESTNO |
Number of a trip request in Visum |
|
ZONENO |
Empty in the case of ‘Wait’. Otherwise, number of zone in which the operation takes place. Then also redundant, because it is equal to the From- or To-zone (depending on the task) of the TripRequest. |
During the import of the tour plan, the following elements are created in Visum:
- A PrT path is created for each vehicle
- Pseudo PrT network volumes
- A demand matrix for the paths between pickup nodes
- A PuT path is created for each trip request serviced
- PuT network volumes
- Optionally, PuT skim matrices can be calculated
- PuT assignment statistics
Import file of trip requests
For trip requests, Visum expects a network file with trip requests listed in a single table.
The header of the file looks like this:
$VISION
* xMaas
* [Date]
*
* Table: Version block
*
$VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
10.000;Net;ENG;KM
*
* Table: TripRequests
*
$TRIPREQUEST:NO;DSEGCODE;FROMNODENO;TONODENO;PICKUPNODENO;DROPOFFNODENO;FROMZONENO;TOZONENO;NUMPASS;REQUESTCREATIONTIME;DESIREDDEPARTURETIME;MAXWAITTIME
The rows with the trips requests follow.
The following columns exist:
|
Attribute name |
Description |
|---|---|
|
NO |
Identification number of the vehicle |
|
DSEGCODE |
Code of the demand segment Is known in the MaaS Modeller (Listed with the demand description) Note: If you create trip requests in the MaaS Modeller for several demand segments, you have to remember which trip requests came from which demand segment. (However, this is not yet possible.) |
|
FROMNODENO |
Number of From-node |
|
TONODENO |
Number of To-node |
|
PICKUPNODENO |
Number of pickup node |
|
DROPOFFNODE |
Number of dropoff node |
|
FROMZONENO |
Number of From-zone |
|
TOZONENO |
Number of To-zone |
|
NUMPASS |
Number of passengers |
|
REQUESTCREATIONTIME |
Time when trip request was created Input format: hh:mm:ss, greater than 24:00:00 is allowed. |
|
DESIREDDEPARTURETIME |
Desired pick-up time Input format: hh:mm:ss, greater than 24:00:00 is allowed. |
|
MAXWAITTIME |
Maximum wait time in seconds |
