Community Multiscale Air Quality Modeling System

CMAQ

Air Quality Data Summit

February 2008

2

CMAQ System Overview & Data Flow

Chemical Transport Model

GoverningEquations

Gas PhaseChemistry

TransportAerosols

Chemistry

CloudChemistry

Emissions Processing - Data

(SMOKE)

Meteorological Data &Met Models - Data

(MM-5 / WRF)

Met-Chemistry Interface Processor - Data

(MCIP)

Emissions Data &Emis Models - Data

(Mobile / other models)

CONC

DEP

Extraction“End User”

Files

3

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” O3, NO, NO2, NH3, 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

4

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)

36km DomainLower Left Corner: -2736000, -2088000Col x Row: 148 x 112Lambert Projection: 1st std parallel: 33 2nd std parallel: 45 central meridian: -97 latitude of projection's origin: 40

12km Eastern Domainx,y: -1008000, -1620000Col x Row: 279 x 240

12km Western Domainx,y: -2412000, -972000Col x Row: 213 x 192

Spatial Coverage of 2002 CMAQ DataContinental US Domain: 36 x 36 km x 14 layers

Eastern & Western Domains: 12 x 12 km x 14 layers

6

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)

7

• 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,000GB 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

Issues w/re Access to CMAQ Data (1)

8

• 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

Issues w/re Access to CMAQ Data (2)