Air concentrations of nine volatile organic compounds were measured over 48-h periods at 23 locations in three communities in the Minneapolis-St. Paul metropolitan area. Concentrations at the same times and locations were modeled using a standard regulatory air dispersion model (ISCST3). The goal of the study was to evaluate model performance by comparing predictions with measurements using linear regression and estimates of bias. The modeling, done with mobile and area source emissions resolved to the census tract level and characterized as model area sources, represents an improvement over large-scale air toxics modeling analyses done to date. Despite the resolved spatial scale, the model did not fully capture the spatial resolution in concentrations in an area with a sharp gradient in emissions. In a census tract with a major highway at one end of the tract (i.e., uneven distribution of emissions within the tract), model predictions at the opposite end of the tract overestimated measured concentrations. This shortcoming was seen for pollutants emitted mainly by mobile sources (benzene, ethylbenzene, toluene, and xylenes). We suggest that major highways would be better characterized as line sources. The model also failed to fully capture the temporal variability in concentrations, which was expected since the emissions inventory comprised annual average values. Based on our evaluation metrics, model performance was best for pollutants emitted mainly from mobile sources and poorest for pollutants emitted mainly from area sources. Important sources of error appeared to be the source characterization (especially location) and emissions quantification. We expect that enhancements in the emissions inventory would give the greatest improvement in results. As anticipated for a Gaussian plume model, performance was dramatically better when compared to measurements that were not matched in space or time. Despite the limitations of our analysis, we found that the regulatory air dispersion model was generally able to predict space and time matched 48-h average ambient concentrations of VOC species within a factor of 2 on average, results that meet regulatory model acceptance criteria.
Links with this icon indicate that you are leaving the CDC website.
The Centers for Disease Control and Prevention (CDC) cannot attest to the accuracy of a non-federal website.
Linking to a non-federal website does not constitute an endorsement by CDC or any of its employees of the sponsors or the information and products presented on the website.
You will be subject to the destination website's privacy policy when you follow the link.
CDC is not responsible for Section 508 compliance (accessibility) on other federal or private website.
For more information on CDC's web notification policies, see Website Disclaimers.
CDC.gov Privacy Settings
We take your privacy seriously. You can review and change the way we collect information below.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies used to make website functionality more relevant to you. These cookies perform functions like remembering presentation options or choices and, in some cases, delivery of web content that based on self-identified area of interests.
Cookies used to track the effectiveness of CDC public health campaigns through clickthrough data.
Cookies used to enable you to share pages and content that you find interesting on CDC.gov through third party social networking and other websites. These cookies may also be used for advertising purposes by these third parties.
Thank you for taking the time to confirm your preferences. If you need to go back and make any changes, you can always do so by going to our Privacy Policy page.