When importing result data from ActivitySim, ActivitySim objects are assigned to the corresponding objects in Visum according to their key (number or code):
|
ActivitySim key |
Visum object/attribute |
|
zone_id |
Location/number; additionally zone/number if TAZ is not defined in ActivitySim. |
|
TAZ |
Zone/Number |
|
household_id |
Household/Number |
|
home_zone_id |
Residence/Location number |
|
person_id |
Person/Number |
|
school_zone_id, workplace_zone_id |
Person/Long term choice |
|
tour_id |
Tour/Number |
|
trip_id |
Trip/Number |
|
origin, destination |
Location/Number |
The stop areas (TAP) are not assigned to Visum objects, but are stored as trip attributes. In Visum, the relevant geographic objects are locations, even if the ActivitySim model has only one geographic layer. This means that activities are performed exclusively at locations. If the Visum model has only zones, one location is added per zone.
|
Note: The Import ActivitySim output data procedure is identical to the import described above. |
