Community Multiscale Air Quality Modeling System CMAQ Air

Community Multiscale Air Quality Modeling System CMAQ Air Quality Data Summit February 2008

CMAQ System Overview & Data Flow Meteorological Data & Met Models - Data (MM-5 / WRF) Emissions Data & Emis Models - Data (Mobile / other models) Met-Chemistry Interface Processor - Data (MCIP) Emissions Processing - Data (SMOKE) Chemical Transport Model Governing Equations Gas Phase Chemistry Transport Cloud Chemistry Aerosols Chemistry CONC Extraction “End User” Files DEP 2

CMAQ Data Types and Attributes • CMAQ Input Data Ø Meteorology: gridded (x, y, z), hourly data for more than 50 parameters Ø Emissions: gridded (x, y, z), hourly data for 30 gas and particle species • CMAQ Output Data Ø Concentration: gridded hourly average § CONC file: All species all layers § Extraction files: “ground level” O 3, NO 2, NH 3, OH, other gases, and fine and course particle species Ø Deposition: gridded, hourly total wet and dry § Oxidized and reduced nitrogen species, sulfur, ozone, and other species 3

CMAQ Data for 2002 • Supplier Ø EPA OAQPS and ORD § Data developed as part of 2002 Multi-Pollutant Air Quality Modeling Platform • Usage Ø CMAQ Evaluation & Improvement Ø EPA Policy Analyses and Regulatory Applications • Connections to Other Systems Ø Data currently stored inside EPA “firewall” at NCC Ø Data are “loosely” coupled to: § § Visualization (PAVE/VERDI) Model evaluation (AMET) Decision support (BENMap) Other analyses (e. g. , Data Fusion, Accountability) 4

Spatial Coverage of 2002 CMAQ Data Continental US Domain: 36 x 36 km x 14 layers Eastern & Western Domains: 12 x 12 km x 14 layers 12 km Western Domain x, y: -2412000, -972000 Col x Row: 213 x 192 36 km Domain Lower Left Corner: -2736000, -2088000 Col x Row: 148 x 112 Lambert Projection: 1 st std parallel: 33 2 nd std parallel: 45 central meridian: -97 latitude of projection's origin: 40 12 km Eastern Domain x, y: -1008000, -1620000 Col x Row: 279 x 240 5

CMAQ Data Enhancements • Implementing improved internal data base management procedures • Possible development of a CMAQ Applications Management Framework with attributes and functionality similar to the Emissions Modeling Framework • Exploring public access to 2002 data via Community Modeling & Analysis System (CMAS) 6

Issues w/re Access to CMAQ Data (1) • What are the specific user needs (internal/external)? Ø How will these be defined? • What is the most IT-efficient way to provide access to users inside/outside EPA? Ø Data volume issues § Outputs from 12 km Eastern Domain annual run ~ 3, 000 GB Ø Firewall issues (external users) • Should EPA provide data for all species in all layers? Ø If so, what procedures will be available to users to subset data in space and time (leverage existing procedures, e. g. , RSIG)? • How will user questions/access problems be addressed? Ø Questions: Technical issues beyond what metadata can address Ø Access: IT issues 7

Issues w/re Access to CMAQ Data (2) • CMAQ applications are often “evolutionary” Ø Specific scenarios may be updated as new inputs and science become available Ø Potential for consistency/comparability issues across different CMAQ applications Ø So. . § Increased emphasis on metadata, version tracking, and other documentation § How will the user community be notified of updates to CMAQ data? • CMAQ outputs from regulatory / research applications must be kept internal until rules / journal articles are published…. . this results in potentially large time-lag between completion of model application and public release of data 8