Year Specific Inputs

The table below lists all input files that vary across model scenario years. Users should pay special attention to the listed files to ensure accurate model run results.

Category	Files	Notes
Conrols for AOC, Airports and Crossborder parameters by year	ParametersByYears.csv	AOC parameters should be updated with year/scenario specific assumptions. Use BLS CPI for San Diego to convert VMT fee to 2010 $ and add to the aoc.fuel properties parameter. Non-standard years must be added.
Land-Use	mgra13_based_input<<SCENARIO_YEAR>>.csv	Attention should be payed to parking and mobility hub access time (MicroAccessTime) for micromobility
	mobilityHubMGRA.csv	Used for microtransit. Varies by year depending on mobility hub active year.
	mobilityHubTAPs.csv	Year specific mobility hub and transit network, which is generated from transit network build process.
Synthetic Population	households.csv
	persons.csv
Network: Highway	hwycov.e00
	turns.csv
	vehicle_class_factor.csv	Include all years. Must add non-standard years as well. If toll or ML (managed lane) facilities or year values are missing, default values will be used.
	Custom process to generate highway network	Needed for preliminary runs
Network: Transit	trcov.e00
	trlink.csv
	trrt.csv
	trstop.csv
	tapcov.dbf
	tap.ptype
	timexfer_XX.csv	Special treatment for scenarios without COASTER present
	special_fares.txt
Network: Active Transportation	SANDAG_Bike_Net.dbf	Need to generate non-standard years and create logsums
	SANDAG_Bike_Node.dbf
	bikeTazLogsum.csv
	bikeMgraLogsum.csv
Warm start vehicle trip matrix	trip_XX.omx	Copy from latest runs
Controls for external trips for all years	externalExternalTripsByYear.csv	Inputs for all forecasted years, including non-standard years, must be included
	externalInternalControlTotalsByYear.csv
	specialGenerators.csv
Truck Model	regionalIEtrips<year>.csv
	regionalEItrips<year>.csv
	regionalEEtrips<year>.csv

Go To Top