Difference between revisions of "CMETEO"

Introduction

CMETEO stands for CORINE-meteo. The softwaretool CMETEO can be seen an application suite to aggregate meteo data as found in e.g. the CGMS_EUR_08.GRID_WEATHER dataset or similar data sets at grid resolutions. Think of meteo indicators on temperature (maximum, minimum, mean or daily), windspeed, precipitation, radiation, potential transpiration, evaporation etc. In the context of MARS, the weather indicators are given at a regular grid. These indicators will be aggregated to spatial resolutions like administrative regions (NUTS level 3-0) or agri-environmental regions according 1) a general area weighted algorithm and 2) a landcover (or even crop) specific area weighted algorithm.

The process

The process can be described in a short way as: At the start, only once, initialise parameters to hold values that are valid for all regions and for all days in the specified interval.

• parameters according the ROI and theme: type of aggregation {plain, median -- in case of weather forecast members}, type of interval {day, dekad}, indication to include a crop specific aggregation {yes,no}, thresholds whether to include a grid cell based on its land cover or crop specific area {0, integer up to 99}
• get a list of all days to process
• get a list of all landcovers that are relevant for the ROI
• get a list of all cmeteo-members, being day-offsets (days in forecast depth) and members of meteo-ensembles. Mostly, the cmeteo-members refers to only one member and no day-offset (e.g. data sets like CGMS_EUR_08.GRID_WEATHER).

Continue to process regions of level 0 (=countries) belonging to the ROI:

• get a region (country)
• get all subregions of all levels contained in that region.
• gather input for each subregion:
  • initialise an array of weather indicators for all days, all landcovers and all members of cmeteo (day-offsets and member_no's).
  • for each day:
    • collect available weather indicators of all cmeteo-members for the grid cells contained in the subregion.
    • for each threshold:
      • if the size of area is above the threshold, summarise them per cmeteo-member and landcover. The values are weighted with the land cover specific area of the grid cell.
      • optionally, continue with a crop specific aggregation, weighted for the area of the crop in the region (note that crop area statistics are only available at administrative/region level and thus can only be used in aggregations from NUTS level 3 to higher levels).

As a result an array is filled with aggregated weather indicators per (sub)region, landcover (or even crop), day and cmeteo-member. The records of the array will be merged into the database according the rules:

• if the record does not contain any result (no aggregation), then delete it's former representation from the database if one exists
• if the record contains a result (an aggregation), then update it's former representation in the database if one exists
• if the record contains a result (an aggregation), then insert it into the database if no former representation exists

The procedure stops after processing all indicated regions of level 0 belonging to the ROI.

Environment

The CMETEO package is designed to operate in several environments which may differ in both input (different tables names, definitions, structure, time resolution, etc.) as output datasets (different type of adminstrative resolutions, agri-environmental zones etc). All these environments need to have the basic data (gridded weather, list of regions, land cover or even crop specific areas per grid cell) and a number of CMETEO database objects available for the CMETEO process.

Software tools needed by cmeteo

CMETEO uses functionality which is implemented in several other software tools. The major ones are listed in the following table.

Administration

Before the process will be executed, some checks and tasks, mainly administrative, are done.

• The module checks if no other instance of CMETEO is active in it's schema and registers itself as active. At any one moment only at most one process per schema can be active.
• After registering, it checks if all objects are available that are needed for the selected theme (including the ROI).
• It also redefines some synonyms (dynamic synonyms like CMETEO_REGION_WEATHER and CMETEO_GRID_LANDCOVER_AREAS) according to the demands of the theme.
• Before processing, it checks the availability of weather indicators for the selected interval.
• After processing, it collects counts of processed data and some other items and stores them into the metrics table (DB schema XMRSMAN).
• It signals the Project Management Board that the process has successfully ended.
• Finally it releases the lock on active processes.

Interface

The CMETEO package is designed to act in a batch file, or to start from a commandline. The interface consists of a set of parameters.

To get CMETEO working properly, you supply:

• xxx: the username (and password) of the database schema that holds the data to be processed. This user name is part of the interface
• p_theme: theme, (that implies a ROI)
• p_spc_res: spatial indicator, e.g. 'Regions', 'Agri environmental zones'

Optionally, you can supply:

• xxx: a day or an interval of days to be processed.
• xxx: an indicator whether or not to refresh the previously aggregated weather indicators.
• xxx: a set identifiers of regions to be processed.

Details of the interface [suppply list of options per theme/ROI for p_theme and p_spc_res]

• The theme must be supplied in p_theme. Possible alternatives are listed in the process table of MRSMAN.
• The spatial indicator must be supplied in p_spc_res. Possible alternatives are listed in the process table of MRSMAN.
• (Optional) An interval or day to process in the set of: p_yr2start,p_dy2start,p_yr2end,p_dy2end. CMETEO uses several possibilities to define an interval. A coarse way is to mention a year to start and a year to end. In this case all days from the first of January of the starting year to the last day of December of the ending year will be processed. A more finegrained way is to provide a date to start and a date to end in which case only the days in between will be processed, or even one day if both entered dates are the same. You may supply any combination of years and dates. If you don't supply any, the default interval will be choosen, which starts at the first of January of the current year and runs up to the day before today. In fact, no day in the future will be processed.
• (Optional) an indicator to enable replacement of previously aggregated weather indicators in p_refresh, being one of 'yes', 'no'. The default is 'yes'. This one will be used when no value for this parameter has been supplied.
• A set identifiers of regions to be processed in qry_region. You may add a query or sql statement that delivers the preferred subset of regions for which you need cmeteo. The regions must be identified by their reg_map_id as found in table REGION_MAPPINGS.

If supplied, the selected set must contain some or all reg_map_ids of level 0 (!) for the relevant ROI, e.g.: select rm.reg_map_id from region_mappings rm where rm.reg_level = 0 and rm.reg_code in ('LU', 'BE', 'NL'); You also may supply a limited list of ids of region mappings which must be comma separated. If you leave this parameter empty, all regions of the ROI will be processed.

Also several datasources belong to the interface of cmeteo. The most important ones are listed in the table below.