-
Notifications
You must be signed in to change notification settings - Fork 109
DaySim PNR Lot Choice
DaySim can be setup to support 1, 2, or 3 zone systems. See the users guide for more information. A 1 zone system uses only TAZs, a 2 zone system uses MAZs and TAZs, and a 3 zone system uses MAZs, TAZs, and Stop Areas. Stop Areas are essentially the same as transit access points (TAPs) in CT-RAMP and ActivitySim. In addition to the zone system setup, DaySim also has a park and ride (PNR) lot choice feature, where the user inputs a list of PNR lots/zones for DaySim to calculate drive transit path cost through the best lot for each OD pair. DaySim calculates the best lot for access and looks up the zone walk transit access time for egress. This feature is essentially a version of transit virtual path building (TVPB) as constructed for ActivitySim.
I believe the following configuration for TVPB can be used to model DaySim PNR lot choice.
zone_system: 3
taz_skims:
- HWYSKMAM_taz.omx
- HWYSKMEA_taz.omx
- HWYSKMEV_taz.omx
- HWYSKMMD_taz.omx
- HWYSKMPM_taz.omx
tap_skims:
- HWYSKMAM_taz.omx
- HWYSKMEA_taz.omx
- HWYSKMEV_taz.omx
- HWYSKMMD_taz.omx
- HWYSKMPM_taz.omx
maz: maz_taz.csv
tap: taz_data.csv
maz_to_tap:
walk:
table: maz_tap_walk.csv
# Provide one maz for each tap since DaySim just gets the transit access time from the zone file
drive:
table: maz_taz_tap_drive.csv
# Provide a pre-processed accessible PNR lots/zones/TAPs for each origin zone
TRANSIT_VIRTUAL_PATH_SETTINGS:
tour_mode_choice:
units: utility
path_types:
DTW:
access: drive
egress: walk
max_paths_across_tap_sets: 1 # only best
max_paths_per_tap_set: 1
WTD:
access: walk
egress: drive
max_paths_across_tap_sets: 1 # only best
max_paths_per_tap_set: 1
tap_tap_expressions:
SPEC: tvpb_utility_tap_tap.csv
PREPROCESSOR:
SPEC: tvpb_utility_tap_tap_annotate_choosers_preprocessor.csv
DF: df
maz_tap_expressions:
drive:
SPEC: tvpb_utility_drive_maz_tap.csv
CHOOSER_COLUMNS:
#- demographic_segment
- DDIST
- DTIME
- WDIST