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.
|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.|
|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|
|Specifications of cmeteo_grid_weather|
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 indicators that are essential to process cmeteo. As cmeteo only can use one structure for grid weather, some logic must be applied to transform the various sets into unified representations. This transformation is implemented as views (standard selections) on each of the original datasets while renaming the attributes and eventually suppliyng neutral or valuable data for missing attributes. The dataset cmeteo_grid_weather is composed of the most wide combination of attributes of the various underlying datasets.
Below a summary of some sets in various schemas and the definition of cmeteo_grid_weather