Difference between revisions of "Talk:CMETEO"

From Agri4castWiki
Jump to: navigation, search
Line 148: Line 148:
 
|          || day              || day                  || mdate            || mdate            || year / dekad_in_year 5)
 
|          || day              || day                  || mdate            || mdate            || year / dekad_in_year 5)
 
|-                       
 
|-                       
|          || day_offset      || - 1)                || date_offset - 1) || - 1)            || - 1)
+
|          || day_offset      || -                   || date_offset )   || -               || -
|-                      
+
|-                        
|          || member_no        || - 2)                || - 2)            || - 2)            || - 2)           
+
|          || member_no        || -                   || -               || -               || -          
 
|-                       
 
|-                       
 
|          || max_temperature  || maximum_temperature  || temperature_max  || temperature_max  || temperature_maximum
 
|          || max_temperature  || maximum_temperature  || temperature_max  || temperature_max  || temperature_maximum
Line 156: Line 156:
 
|          || min_temperature  || minimum_temperature  || temperature_min  || temperature_min  || temperature_minimum
 
|          || min_temperature  || minimum_temperature  || temperature_min  || temperature_min  || temperature_minimum
 
|-                       
 
|-                       
|          || mean_temperature || - 3)                || temperature_mean || temperature_mean || temperature_mean
+
|          || mean_temperature || -                   || temperature_mean || temperature_mean || temperature_mean
 
|-                       
 
|-                       
|          || dew_temperature  || - 4)                || temperature_dew  || temperature_dew  || - 4)
+
|          || dew_temperature  || -                   || temperature_dew  || temperature_dew  || -
 
|-                       
 
|-                       
|          || vapour_pressure  || vapour_pressure      ||vapour_pressure  || vapour_pressure  || - 6)
+
|          || vapour_pressure  || vapour_pressure      ||vapour_pressure  || vapour_pressure  || -
 
|-                       
 
|-                       
|          || wind_speed      || windspeed            || wind_speed      || wind_speed      || - 7)
+
|          || wind_speed      || windspeed            || wind_speed      || wind_speed      || -
 
|-                       
 
|-                       
 
|          || precipitation    || rainfall            || precipitation    || precipitation    || precipitation
 
|          || precipitation    || rainfall            || precipitation    || precipitation    || precipitation
 
|-                       
 
|-                       
|          || e0              || e0                  || e0              || e0              || - 8)
+
|          || e0              || e0                  || e0              || e0              || -
 
|-                       
 
|-                       
|          || es0              || es0                  || es0              || es0              || - 9)
+
|          || es0              || es0                  || es0              || es0              || -
 
|-                     
 
|-                     
 
|          || et0              || et0                  || et0              || et0              || et0
 
|          || et0              || et0                  || et0              || et0              || et0
Line 177: Line 177:
 
|}
 
|}
  
1) If an attribute for the offset of the day isn't available, the day-offset in cmeteo grid weather will be filled with a neutral value (0). This value doesn't influence the processing.<br>
+
If an attribute for the offset of the day isn't available, the day-offset in CMETEO_GRID_WEATHER will be filled with a neutral value (0). This value doesn't influence the processing. For sets that doesn't contain an attribute for members_no a '1' will be supplied in CMETEO_GRID_WEATHER. If an attribute for the mean temperature doesn't exist, this value will be estimated as the mean value of minimum and maximum temperature of the day. A dummy value '0' for the dew temperature wil be supplied to CMETEO_GRID_WEATHER for sets lacking such an attribute. Cmeteo will process this value and produces results, but these will not be written to the output table (functionality for this is located in triggers).
2) For sets that doesn't contain an attribute for members, a member_no: 1 will be supplied in cmeteo grid weather.<br>
 
3) If an attribute for the mean or daily temperature doesn't exist, this value will be estimated as the mean value of minimum and maximum temperature of the day. Cmeteo will process this value and produces a result for it.<br>
 
4) A dummy value (0) for the dew temperature wil be supplied to cmeteo grid weather for sets lacking such an attribute. Cmeteo will process this value and produces a result for it, so precautions must be taken to supply these results to the output table.<br>
 
 
|}
 
|}
  
 +
====CMETEO_REGION_WEATHER====
 +
{{Object|CMETEO_REGION_WEATHER}} is the object that contains the output weather indicators in a regional type of resolution and in a unified structure with a uniform object name. In each environment (cgms / cgfs / asia / gwsi) these weather indicators are stored in tables with different names and structures. Also the collection of the attributes may vary. Cmeteo requires that the weather indicators are stored in an object with a specific structure and specific object name. Therefore some logic is applied to transform the unified output from Cmeteo into the unique objects of various environments. This transformation is implemented by using views and/or synonyms on the target datasets while renaming the attributes and eventually skipping data for missing attributes. The unified object CMETEO_REGION_WEATHER is composed of the most wide combination of attributes of the various underlying datasets and will process results for all attributes. If some attributes are not available in the target environment it will not be written to the target table (functionality for this is located in triggers).
  
 
{|class="collapsing_table collapsible collapsed"
 
{|class="collapsing_table collapsible collapsed"
Line 188: Line 187:
 
|-
 
|-
 
|
 
|
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 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 15:41, 30 June 2011



Introduction

Cmeteo stands for CORINE-meteo. Cmeteo can be seen an application suite to aggregate weather indicators from grid resolution to a regional type of division. 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. 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

Cmeteo uses many database objects. The objects that contain the primary datasets like weather data, landcover types and aggregation areas are listed in the table below:

object name Content Environment
CMETEO_GRID_WEATHER Weather indicators per grid CGMS / CGFS / ASIA / GWSI
CMETEO_EPS_GRID_WEATHER Weather indicators per grid (ECMWF EPS model) CGFS
CMETEO_HIS_GRID_WEATHER Weather indicators per grid (ECMWF HIS model) CGFS
CMETEO_OPE_GRID_WEATHER Weather indicators per grid (ECMWF OPE model) CGFS
CMETEO_REGION_WEATHER Weather indicators per administrative region CGMS / CGFS / ASIA / GWSI
CMETEO_NUTS_WEATHER Weather indicators per NUTS region CGMS
CMETEO_EPS_NUTS_WEATHER Weather indicators per NUTS region (ECMWF EPS model) CGFS
CMETEO_HIS_NUTS_WEATHER Weather indicators per NUTS region (ECMWF HIS model) CGFS
CMETEO_OPE_NUTS_WEATHER Weather indicators per NUTS region (ECMWF OPE model) CGFS
CMETEO_ZONAL_WEATHER Weather indicators per Agri-environmental region CGMS
CMETEO_EPS_ZONAL_WEATHER Weather indicators per Agri-environmental region (ECMWF EPS model) CGFS
CMETEO_HIS_ZONAL_WEATHER Weather indicators per Agri-environmental region (ECMWF HIS model) CGFS
CMETEO_OPE_ZONAL_WEATHER Weather indicators per Agri-environmental region (ECMWF OPE model) CGFS
CMETEO_AGGREGATION_AREAS Cultivated areas per crop for Administrative region per year CGMS / CGFS / ASIA / GWSI
CMETEO_GRID_LANDCOVER_AREAS Areas for intersections of grid and administrative region CGMS / CGFS / ASIA / GWSI
CMETEO_LANDCOVERS Landcovers types or crops to be evaluated CGMS / CGFS / ASIA / GWSI
CMETEO_GRID_NUTS_LCV_AREAS Areas for intersections of grid and NUTS region CGMS
CMETEO_GRID_ZONAL_LCV_AREAS Areas for intersections of grid and Agri-environmental region CGMS
CMETEO_REJECTED_WEATHER Weather indicators per region that could not be stored via CMETEO_REGION_WEATHER CGMS / CGFS / ASIA / GWSI
CMETEO_REGION_MAPPINGS Administrative regions and their mappings (relations) CGMS / CGFS / ASIA / GWSI

Supporting objects that are required by Cmeteo:

object name Content Environment
CMETEO_PROCESS CGMS / CGFS / ASIA / GWSI
CMETEO CGMS / CGFS / ASIA / GWSI
CMETEO_HIS_NUTS_WEATHER_IO CGFS
CMETEO_HIS_ZONAL_WEATHER_IO CGFS
CMET_REGION_WTH ASIA / GWSI
CMET_NUTS_WTH CGMS
CMET_ZONAL_WTH CGMS
PRCMN_PARAMETERS CGMS / CGFS / ASIA / GWSI
PRCMN_PROCEDURES CGMS / CGFS / ASIA / GWSI
PRCMN_PROCESS_OBJECTS CGMS / CGFS / ASIA / GWSI
PRCMN_PROCESS_RUNS CGMS / CGFS / ASIA / GWSI
PRCMN_PROCESSES CGMS / CGFS / ASIA / GWSI
PROCMAN CGMS / CGFS / ASIA / GWSI

CMETEO_GRID_WEATHER

CMETEO_GRID_WEATHER is the object that contains the weather indicators in grid resolution that are needed as input for Cmeteo in a unified structure and with a uniform object name. In each environment (cgms / cgfs / asia / gwsi) the weather indicators in grid resolution are stored in tables with different names and structures. Also the collection of the attributes may vary. Cmeteo requires that the weather indicators in grid resolution are stored in an object with a specific structure and specific object name. Therefore some logic must be applied to transform the sets from various environments into a unified structure. This transformation is implemented by using views and/or synonyms on the original datasets while renaming the attributes and eventually suppliyng neutral or valuable data for missing attributes. The unified object CMETEO_GRID_WEATHER is composed of the most wide combination of attributes of the various underlying datasets.

CMETEO_REGION_WEATHER

CMETEO_REGION_WEATHER is the object that contains the output weather indicators in a regional type of resolution and in a unified structure with a uniform object name. In each environment (cgms / cgfs / asia / gwsi) these weather indicators are stored in tables with different names and structures. Also the collection of the attributes may vary. Cmeteo requires that the weather indicators are stored in an object with a specific structure and specific object name. Therefore some logic is applied to transform the unified output from Cmeteo into the unique objects of various environments. This transformation is implemented by using views and/or synonyms on the target datasets while renaming the attributes and eventually skipping data for missing attributes. The unified object CMETEO_REGION_WEATHER is composed of the most wide combination of attributes of the various underlying datasets and will process results for all attributes. If some attributes are not available in the target environment it will not be written to the target table (functionality for this is located in triggers).



Examples