Difference between revisions of "CMETEO"

From Agri4castWiki
Jump to: navigation, search
Line 131: Line 131:
 
Cmeteo_region_weather is a replacement for a variety of datasets, both for themes (e.g. cgfs-his, cgms) and for resolutions (e.g. NUTS regions, agri-environmental zones), to which cmeteo need to fill up with output. In general, datasets for NUTS-regions are pre- or postfixed with 'nuts'; datasets for agri_environmental zones are pre- or postfixed with 'zonal'.<br>
 
Cmeteo_region_weather is a replacement for a variety of datasets, both for themes (e.g. cgfs-his, cgms) and for resolutions (e.g. NUTS regions, agri-environmental zones), to which cmeteo need to fill up with output. In general, datasets for NUTS-regions are pre- or postfixed with 'nuts'; datasets for agri_environmental zones are pre- or postfixed with 'zonal'.<br>
 
In various schemas, datasets containing weather indicators do vary both in name of the set and in names of the attributes. Also the collection of the attributes may vary. However, all the sets contain the essential indicators for which cmeteo delivers output. Per theme, the structure of datasets for both resolutions are very similar. As cmeteo only can use one structure for region weather, some logic must be applied to transform the various sets into unified representations. This transformation is implemented as a view (with the possibility to insert/update values) on each of the original datasets while renaming the attributes. As the dataset cmeteo_region_weather delivers the most wide combination of attributes of the various underlying datasets, some precautions must be taken to prevent some useless attributes being placed into the final dataset. Functionality for this is located in a technical construct (trigger) which is connected to the views.<br>
 
In various schemas, datasets containing weather indicators do vary both in name of the set and in names of the attributes. Also the collection of the attributes may vary. However, all the sets contain the essential indicators for which cmeteo delivers output. Per theme, the structure of datasets for both resolutions are very similar. As cmeteo only can use one structure for region weather, some logic must be applied to transform the various sets into unified representations. This transformation is implemented as a view (with the possibility to insert/update values) on each of the original datasets while renaming the attributes. As the dataset cmeteo_region_weather delivers the most wide combination of attributes of the various underlying datasets, some precautions must be taken to prevent some useless attributes being placed into the final dataset. Functionality for this is located in a technical construct (trigger) which is connected to the views.<br>
The results of cmeteo, available via cmeteo_region_weather, must be linked to the proper dataset according to the theme and the appropriate spacial resolution.  
+
In a dynamical way cmeteo_region_weather will be linked to the proper dataset according to the theme and the appropriate spacial resolution to deliver the results of cmeteo.
  
 
Below a summary of some sets in various schemas and the definition of cmeteo_region_weather
 
Below a summary of some sets in various schemas and the definition of cmeteo_region_weather

Revision as of 16:01, 4 February 2011



Introduction

Cmeteo stands for CORINE-meteo. Cmeteo can be seen an application suite to process meteo data as found in e.g. the CGMS.grid_weather dataset. It aggregates and translates meteo indicators according to some spatial and thematic specs. Think of meteo indicators on temperature (maximum, minimum, mean or daily), windspeed, precipitation, radiation. Also indicators as potential transpiration, evaporation may be included. In the context of MARS, the weather indicators are given per grid. These indicators will be aggregated to spatial themas like NUTS or agri environmental regions, or translated/adjusted for landcovers of interest like crops, etc. Translation will be accompanied by aggregation. See ..(somewhere else in this wiki).. for more detailed description of cmeteo.

The cmeteo package is designed to operate in several environments which may differ in both input as output datasets. All these environments need to have the basic data (both input and output) 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.

tool remarks
REGLISTS supplies specific lists of regions directed by input parameters.
MRS_PROCESS contains common used functionality for processing more complex programs like cmeteo.
ADD_PROCESS_LOG procedure to send some info to a logtable.
ADD_PROCESS_METRICS procedure to send some data, retrieved during processing, to a logtable.
MRS_STATS generic tool to collect some metrics during processing.
MRS_HTTP generic tool to handle some messages.
DATE_GENERATOR generic tool to generate specific lists of dates according to the input paramaters.

Interface

Datasets used by cmeteo
dataset containing example in CGMS_EUR_08 name in cmeteo remarks
weather indicators per grid grid_weather cmeteo_grid_weather input for cmeteo, renaming some columns to a standardized naming
weather indicators per NUTS-region nuts_weather cmeteo_region_weather output for cmeteo, renaming some columns to a standardized naming
weather indicators per agri-environmental region (stratum, zone) zonal_weather cmeteo_zonal_weather output for cmeteo, renaming some columns to a standardized naming
landcovers or crops to be evaluated crop_landcover cmeteo_landcovers input for cmeteo, renaming some columns to a standardized naming
areas/surfaces for landcovers per grid and per NUTS region grid_plus_nuts_landcover cmeteo_grid_nuts_lcv_areas input for cmeteo, renaming some columns to a standardized naming
areas/surfaces for landcovers per grid and per agri-env. region grid_plus_ens_landcover cmeteo_grid_zonal_lcv_areas input for cmeteo, renaming some columns to a standardized naming
areas/surfaces for crops per NUTS region aggregation_areas cmeteo_aggregation_areas input for cmeteo, renaming some columns to a standardized naming
weather indicators per region which are rejected cmeteo_rejected_weather output for cmeteo, containing weather indicators per region that could not be stored in regular output
regions and their mappings cmeteo_region_mappings input for cmeteo





Examples