Release Level	5.4
	Release Date	2008 10
	Revision Level	1.0

Last modified on:   Monday, 20-Jul-09 14:03 CEST

AirWare Data requirements

1. Domain definition:
   • Definition of the geographical scope/area, background maps including the definition of the individual city/industrial areas of interest, land use, topography (DEM);

2. Monitoring data:
   • Meteorological data (minimally for one reference year) at an hourly resolution:
     • wind speed and direction
     • air temperature
     • precipitation
     • early-morning soudings, (optional) hourly mixing height,
       please note that these can be estimated from (optional) cloud cover data alternatively.
     Please note that alternatively, meteorological data can be generated by a prognostic meteorological model (MM5, WRF) driven with global GFS data from NOAA on a daily basis. These data can either be used as dynamic data fields (multi-layered) or by extracting meteorological parameters into existing or simulated meteorological monitoring stations.

   • Air quality observation data (matching the emission and meteo data sets !) including station locations.

3. Meteo forecasts: to run the model(s) in forecast mode, dynamic boundary conditions (met data for selected grid points within the domain) from an appropriate regional meteorological forecasting model are required. The meteorological forecasts can optionally be suplied by the prognostic meteorolgical model MM5 Output from MM5 is generated to a 3 km, hourly resolution, automatically interpolated further with MM5toCAMxto a 1 km resolution by use with the CAMx nested grid air quality model.

4. Emission data:
   • Point (stacks) and area source emissions, locations, source (stack) characteristics, emission rates for any or all pollutants covered. Additional (alternative) data include fuels and fuels consumption, combustion technologies, industrial classifications, etc.
   • Transportation graph/network with link specific data (frequencies) as well as global properties such as fleet composition;
   • Fugitive emission from the fuel system including parked cars, gas stations.
     Alternative: traffic emission grid;
   • Emission inventories for (industrial) point sources and fugitive emissions, and area sources (domestic heating);
   • For the ozone modelling (PBM photochemical box model; for the 3D (optional) dynamic CAMx model see below): Hydrocarbons, divided into the following eight groups: Non reactives, Ethilene, Olefines, Alkanes, Formaldehyde, Aldehyde, Aromatics and Toluene; and CO, NOx (fixed ratio between NO and NO2), data for biogenic VOC emissions.

5. Population data:
   • Population distribution (for exposure analysis) by census tracts or larger administrative entities, or gridded (1ha to 1 km2);
6. Receptor points: for the monitoring of compliance with standards, model performance (validation), and impact assessment a number of receptors should be defined. These are:
   • Air quality monitoring stations
   • Building points (user positioned arbitrary receptor points)
   • Receptor areas (user defined arbitrary polygons).

7. Economic data:
   • Cost functions for emission reduction strategies, by emission class of major (point source) object or traffic related (fleet composition).

8. Logo(s) and start-page image.