Database Inputs

A new input management system is being designed to control input files. The working list of inputs within a scenario-specific database is as follows:

Table Name	Original Input File
daily_parking_costs	parking\daily_parking_costs.csv
distribute_jblm_jobs	landuse\distribute_jblm_jobs.csv
gq_prod_att	supplemental\generation\gq_prod_att.csv
hourly_parking_costs	parking\hourly_parking_costs.csv
node_index_2014	short_distance_files\node_index_2014.txt
node_to_node_distance	short_distance_files\node_to_node_distance_2014.txt
parcel_nodes_2014	short_distance_files\parcel_nodes_2014.txt
parcels_military	landuse\parcels_military.csv
parcels_urbansim	landuse\parcels_urbansim.txt
prod_att	supplemental\generation\prod_att.csv
special_generators	supplemental\generation\special_generators.csv
synth_hh	landuse\hh_and_persons.h5
synth_person	landuse\hh_and_persons.h5
transit_stops	landuse\transit_stops.csv
taz_data	inputs/trucks/tazdata.in
pums_data_loc	inputs/supplemental/generation/pums/
externals_loc	inputs/supplemental/generation/externals.csv

Some inputs do not change much from one scenario to the next so probably should be on GitHub instead. Here are these files:

Table Name	Original Input File
hh_trip_loc	inputs/supplemental/generation/rates/hh_triprates.in
nonhh_trip_loc	inputs/supplemental/generation/rates/nonhh_triprates.in
puma_taz_loc	inputs/supplemental/generation/ensembles/puma00.ens