Difference between revisions of "CMETEO"

From Agri4castWiki
Jump to: navigation, search
Line 4: Line 4:
 
Cmeteo stands for CORINE-meteo. The softwaretool Cmeteo can be seen an application suite to process meteo data as found in e.g. the CGMS_EUR_08.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.
 
Cmeteo stands for CORINE-meteo. The softwaretool Cmeteo can be seen an application suite to process meteo data as found in e.g. the CGMS_EUR_08.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 process==
+
===The process===
 
+
The process can be described in a short way as:[br]
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.
At the start, only once
+
*.1 parameters according the ROI and theme: type of aggregation {plain, median}, type of interval {day, dekade}, indication to include crops {yes,no}, thresholds for area of grid {0, integer up to 99}
1. Initialise parameters to hold values that are valid for all regions and for all days in the specified interval.
+
*.2 get a list of all days to process
-.1 parameters according the ROI and theme: type of aggregation {plain, median}, type of interval {day, dekade}, indication to include crops {yes,no}, thresholds for area of grid {0, integer up to 99}
+
*.3 get a list of all landcovers that are relevant for the ROI
-.2 get a list of all days to process
+
*.4 get a list of all cmeteo-members, being day-offsets and members of meteo-ensembles. Mostly, there is only one member and no day-offset.
-.3 get a list of all landcovers that are relevant for the ROI
 
-.4 get a list of all cmeteo-members, being day-offsets and members of meteo-ensembles. Mostly, there is only one member and no day-offset.
 
  
 
Continue to process a region of level 0:
 
Continue to process a region of level 0:

Revision as of 13:29, 30 May 2013



Introduction

Cmeteo stands for CORINE-meteo. The softwaretool Cmeteo can be seen an application suite to process meteo data as found in e.g. the CGMS_EUR_08.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 process

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

  • .1 parameters according the ROI and theme: type of aggregation {plain, median}, type of interval {day, dekade}, indication to include crops {yes,no}, thresholds for area of grid {0, integer up to 99}
  • .2 get a list of all days to process
  • .3 get a list of all landcovers that are relevant for the ROI
  • .4 get a list of all cmeteo-members, being day-offsets and members of meteo-ensembles. Mostly, there is only one member and no day-offset.

Continue to process a region of level 0: get the region get all subregions of all levels contained in that region. 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 grids 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 area in the grid of the landcover. --- optionally, add aggregated weather indicators for crops, weighted for the area of the crop in the region.

As a result you find an array of aggregated weather indicators per (sub)region, landcover, day and cmeteo-member. The members of the array will be merged into the database according the rules: - if the member does not contain any aggregation, then delete it's former representation from the database (if one exists there); - if the member contains an agregation, then update it's former representation in the database (if one exists there); - if the member contains an agregation, then insert it into the database (if no former representation exists there).

In the end stop after processing all regions of level 0.

Environment

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 with standardized attribute names
weather indicators per NUTS-region NUTS_WEATHER CMETEO_NUTS_WEATHER CMETEO_REGION_WEATHER input for cmeteo with standardized attribute names
weather indicators per agri-environmental region ZONAL_WEATHER CMETEO_ZONAL_WEATHER CMETEO_REGION_WEATHER input for cmeteo with standardized attribute names
landcovers or crops to be evaluated CROP_LANDCOVER CMETEO_LANDCOVERS input for cmeteo with standardized attribute names
landcover areas intersection of grid and NUTS region GRID_PLUS_NUTS_LANDCOVER CMETEO_GRID_NUTS_LCV_AREAS CMETEO_GRID_LANDCOVER_AREAS input for cmeteo with standardized attribute names
areas/surfaces for landcovers per grid and per agri-env. region GRID_PLUS_ENS_LANDCOVER CMETEO_GRID_ZONAL_LCV_AREAS CMETEO_GRID_LANDCOVER_AREAS input for cmeteo, renaming columns to a standardized naming
areas/surfaces for crops per NUTS region AGGREGATION_AREAS CMETEO_AGGREGATION_AREAS input for cmeteo, renaming 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 via cmeteo_region_weather
regions and their mappings CMETEO_REGION_MAPPINGS input for cmeteo