11.07.2014 Views

treasure valley road dust study: final report - ResearchGate

treasure valley road dust study: final report - ResearchGate

treasure valley road dust study: final report - ResearchGate

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

c. Year_2010_Emissions_Inventory_By_Silt.xls<br />

i. Emissions_By_Silt_Master_Table<br />

d. Year_2015_Emissions_Inventory_By_Silt.xls<br />

i. Emissions_By_Silt_Master_Table<br />

e. Year_2020_Emissions_Inventory_By_Silt.xls<br />

i. Emissions_By_Silt_Master_Table<br />

C.1.2.2 File Contents<br />

These files contain link-level paved <strong>road</strong> <strong>dust</strong> emissions in grams per day of PM 10 for Ada and<br />

Canyon Counties. Emissions have been calculated based on silt loading measurements<br />

conducted as part of the TVRDS and silt loadings specified as default values in AP-42. AP-42<br />

does not prescribe a method for correcting paved <strong>road</strong> <strong>dust</strong> emissions for precipitation.<br />

Therefore, no corrections have been applied to the emissions in these data files. Emissions have<br />

been calculated using three different sets of values for silt loadings. “TVRDS1” uses silt loading<br />

values measured as part of the TVRDS with the assumption that silt loadings on freeways are<br />

equal to the AP-42 default value of 0.02 grams per square meter. “TVRDS2” uses the same<br />

values as “TVRDS1” except that the silt loading on freeways is assumed to be the same as for<br />

arterials (1.9 and 0.5 grams per square meter for winter and average annual conditions,<br />

respectively). “AP-42” simply uses the default values for silt loading for all <strong>road</strong> classes. ALL<br />

EMISSSIONS ARE REPORTED FOR WEEKEDAYS ONLY. The Subdirectory<br />

“Traffic_Demand_Model_Summaries” contains additional information to allow calculation of<br />

weekend emissions. The fields in the worksheets along with their descriptions are given below:<br />

C.1.2.2a Field list for worksheets a.i, b.i, c.i, and d.i<br />

PROJ: The year corresponding to the Traffic Demand Model projection<br />

FID_1: Feature ID in Traffic Demand Model Database. The feature ID and the projection year<br />

together uniquely identify a link in the traffic demand model.<br />

A: The ID number for the starting Node for the link<br />

B: The ID number for the Terminating Node for the link<br />

COUNTY: The county that the link is in. 1=Ada, 2= Canyon.<br />

TVRDS1_W_SL: Silt loading in Grams per square meter used to calculate winter conditions<br />

emissions factors as described in Equation 2-3 of the TVRDS <strong>report</strong>. Silt loadings for freeways<br />

are assumed to be equal to the AP-42 default value of 0.02 grams per meter squared.<br />

TVRDS1_Ave_SL: Silt loading in Grams per square meter used to calculate average daily<br />

conditions emissions factors as described in Equation 2-3 of the TVRDS <strong>report</strong>. Silt loadings for<br />

freeways are assumed to be equal to the AP-42 default value of 0.02 grams per meter squared.<br />

TRVDS2_W_SL: Silt loading in Grams per square meter used to calculate winter conditions<br />

emissions factors as described in Equation 2-3 of the TVRDS <strong>report</strong>. Silt loadings for freeways<br />

are assumed to be equal to those for arterials, 1.9 grams per meter squared.<br />

TVRDS2_Ave_SL: Silt loading in Grams per square meter used to calculate average daily<br />

conditions emissions factors as described in Equation 2-3 of the TVRDS <strong>report</strong>. Silt loadings for<br />

freeways are assumed to be equal to those for arterials, 0.5 grams per meter squared.<br />

AP-42_W_SL: Silt loading in Grams per square meter used to calculate winter conditions<br />

emissions factors as described in Equation 2-3 of the TVRDS <strong>report</strong>. These are the default<br />

C-4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!