||air quality management information system |
for urban and industrial applications
AirWare Data Requirements
AirWare is a fully data driven system, i.e., no data
are "hardwired" in the application, everything is, in priciple, user defined
and configurable: a number of data bases and configuration files
are used to define and drive the system operations.
Several changes in the navigation style to reduce the use of pop-up windows.
Please consult the On-line MANUAL PAGES for details.
The main data repositories are based on SQL RDBMS, MySQL or ORACLE,
depending on the application. These data bases are either part of
the main application, or can be remote, distributed information
resources e.g., from monitoring networks, or the daily
global meteorological (model) data for the computation of the local,
detailed weather forecasts.
- Model domains: Any AirWare installation is configured
for a specific set of nested (geographic)
They are defined in terms of location (LAT/LONG) and extent.
A typical master domain is around 100 to 300 km, and square;
alternative layout (landscape or portrait) can also be
configured if necessary.
- Around the master domain for the air quality models, two more layers of
larger meteorological domains are constructed for the
MM5 prognostic meteorologiocal model runs.
- Within the master domain, currently up
to nine nested sub-domains of higher resolution can be defined,
e.g., for areas of special interests (cities, industrial districts);
- GIS data
For GIS data, a common projection (usually UTM) and coordinate system
must be defined; basic GIS data include:
- DEM (can be extracted form public domain data at 1 km resolution)
- background map for orientation (can be derived from satellite imagery, e.g., LANDSAT, SPOT, IKONOS)
- basic administrative data: national, provincial, municipal boundaries;
- land use and land cover (LULC) data, preferrable based on
CORINE classification, used for
roughness and albedo estimates;
- Location of emission sources (see also: emission inventory)
- Location of monitoring stations
- Location of receptor points (building points) or areas.
- Emission data
Emission data for the pollutants to be addressed
(or their pre-cursors in the case of ozone) are the key data sets in AirWare.
The data are organised in Emission inventories
of different spatial coverage (related to the model domains)
- Monitoring data
Organized around monitoring stations
they manage time-series data from emission, air quality or meteorological observations,
including the linkage to external, distributed data bases for real-time data.