treasure valley road dust study: final report - ResearchGate
treasure valley road dust study: final report - ResearchGate
treasure valley road dust study: final report - ResearchGate
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Figure 3-6 shows the TRAKER coefficient of variation for the left and right PM 10<br />
DustTrak signals as a function of the vehicle speed. The coefficient of variation is a measure of<br />
the relative precision and is equal to the standard deviation of the measurement divided by the<br />
average of the measurement. In the Figure, the measurement corresponds to multiple passes on<br />
the same 1-mile stretch of <strong>road</strong> in the Treasure Valley. The Figure clearly shows that the<br />
precision of the measurement improves with increasing vehicle speed. The precision is 84% at 5<br />
mps, 30% at 9 mps, and approximately 10% above 14 mps. Note that most TRAKER<br />
measurements occur at speeds greater than 9 mps (approximately 20 mph). The poor precision at<br />
low speeds is probably due to the influence of fluctuating ambient winds on the flow regime<br />
behind the front tires. As the vehicle speed increases, such fluctuations become less important<br />
compared to the speed of the vehicle (see section 3.3.4 for discussion of the relationship between<br />
the TRAKER signal and vehicle speed). The equivalent information for PM 2.5 DustTraks is<br />
shown in Figure 3-7. Note that for PM 2.5 , DustTrak data at speeds less than 50 km/hr are below<br />
the detection limits of the instruments. The trend of improved precision with higher speeds is<br />
similar to the PM 10 case.<br />
3.3.1.1 Inferring PM 10 from PM 2.5<br />
Unpaved <strong>road</strong>s are by nature much <strong>dust</strong>ier than paved <strong>road</strong>s. A dilution system was<br />
designed for the TRAKER in order to reduce the particle concentration in the TRAKER inlets<br />
and allow the DustTrak measurements to remain within the manufacturer’s specified operating<br />
range. In some cases, the PM 10 DustTrak upper limit (150 mg/m 3 ) was exceeded even with the<br />
dilution system in operation. For both the Treasure Valley Road Dust Study, and the calibration<br />
tests at Ft. Bliss (described in detail in section 3.4) PM 2.5 DustTraks were collocated with PM 10<br />
DustTraks in the sampling plena within the TRAKER. Figure 3-8 shows the relationship<br />
between collocated PM 2.5 and PM 10 DustTraks. Based on the correlation shown in the figure,<br />
when the PM 10 DustTrak was out of range, the PM 2.5 value was divided by 0.39 in order to<br />
estimate the PM 10 value. Note that while useful for correcting out of range data, the DustTrak is<br />
calibrated for PM 10 and measurements with a 2.5 ?m inlet only give a nominal value for PM 2.5 .<br />
For a few cases, both the PM 10 and PM 2.5 DustTraks were out of range. Under such<br />
circumstances, default values of 770 and 280 mg/m 3 were assumed for PM 10 and PM 2.5 ,<br />
respectively. This occurrence is rare and applies to less than 0.5% of the unpaved <strong>road</strong> data.<br />
3.3.1.2 TRAKER Validity Criteria<br />
A TRAKER data point is only considered valid if it meets all of the criteria outlined in<br />
Table 3-1. Criteria are applied to the speed, acceleration, deceleration, and the wheel angle of<br />
the TRAKER vehicle. If a data point does not meet any one of the criteria, then that data point is<br />
flagged as “Invalid” and is not used in any subsequent data processing activities. Note that the<br />
TRAKER measurement uses the difference between the particle concentration measured behind<br />
the front tire and the concentration measured through the front bumper (see equation 1 in section<br />
3.3.4). Under certain conditions, the concentration at the front bumper may be higher than it is<br />
behind the front tire resulting in a negative measurement. Negative values are NOT considered<br />
invalid and are retained in the database. It is important to retain negative values so that a<br />
systematic bias is not introduced into the dataset.<br />
3-8