Difference between revisions of "CMETEO"

Introduction

CMETEO stands for CORINE-meteo. The softwaretool CMETEO can be seen as an application suite to aggregate data of meteo indicators as found in e.g. the CGMS12EU.WEATHER_OBS_GRID data set or similar data sets at grid resolutions (meteo grid). 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 to:

• a general area weighted algorithm
• a landcover (or even crop) specific area weighted algorithm.

The process

The process can be described in a short way as:

After starting, use the supplied interface to initialise some more parameters holding values that are valid during the execution of the process.

• parameters according the user name, theme and spatial type: ROI, 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 landcover or crop specific area {a comma seperated list of integer for each threshold needed, integers are in the range of: 0 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 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 landcover specific area of the grid cell.
      • optionally, add 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)
      • add this collection of data to the region that contains this subregion to facilitate the aggregation of the regions at 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 (i.e. database schemas) which may differ in both input (different tables names, definitions, structure, interval of time, etc.) as output datasets (different type of spatial 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

The essential functionality of the process is implemented in the packages: CMETEO_admin and CMETEO_process. 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.
DATE_GENERATOR	generic tool to generate lists of dates and some additional attributed based on the input parameters.
PROCMAN	package serving configurations for processing executed by complex programs like CMETEO.
PROCESS LOGGING	set of procedures to send info to the user interface (you may extend these to send to log tables).
UPDATE_EVENTS_ARCHIVE	procedure to signal the PMB (Project Management Board) that the processing ended successfully.

Installation of CMETEO

To install CMETEO you need to follow steps as

• check the environment, if the objects needed by the CMETEO package are available
• install the objects of the CMETEO package
• add configurations to PROCMAN for any schema you wish to process CMETEO on

In the next paragraphs these steps will be detailed.

CMETEO will be installed in the database. So you need to decide in which schema you wish to install. Currently, CMETEO is installed in the MRSMAN schema, which is intended to be the base of applications to process on datasets that are in other schemas. As CMETEO is such an application, it is a good choice to install it in the MRSMAN schema. However, it should not be installed in a schema that is to be processed by CMETEO.

Tools or objects needed by CMETEO do't be installed necessarily in the same schema as CMETEO. It is sufficient to grant access to these objects to the owner/schema in which CMETEO will be installed.

Installation of CMETEO, check the environment

Check that the following tools or objects are valid and available:

Tools, currently installed in the FORALL schema:

• REGLISTS
• REGION_MAPPINGS
• REGION_MAPPINGS_PER_ROI
• DATE_GENERATOR

Tools, currently installed in the MRSMAN schema:

• PROCMAN
• PROCESS LOGGING
• TD_NUMBER
• TD_ERRORS

Tool, currently installed in the PMB schema:

• UPDATE_EVENTS_ARCHIVE

Installation of CMETEO, install the package

CMETEO is delivered as a package containing scripts for the application software and accompanying objects. They must be installed in this order:

• threshold_value_tp.sql
• all: cmeteo_...._tbl.sql
• cmeteo_region_mappings_vw.sql
• cmeteo_process_pks.sql
• cmeteo_process_pkb.sql
• cmeteo_admin_pks.sql
• cmeteo_admin_pkb.sql

Installation of CMETEO, configure for schema

CMETEO uses configurations in the PROCMAN tool to do the processing of weather indicators in a proper way. Configuration in PROCMAN guides CMETEO to:

• check the availability of datasets (tables, views) needed for the processing
• create standardized entries for these datasets (tables, views)
• get settings for some details to take in account while processing

Of course, the datasets and the settings must be in accordance with each other. Thus, for each set to be processed you need to define a 'process' which declares the datasets involved and the specification of the details. You may declare several processes to be executed per schema. E.g. in schema CGMS12EU two processes are declared, named cmeteo-cgms12eu-regions and cmeteo-cgms12eu-zones.

For the details you need to specify values for:

• aggregation method
• etc. (specify a table here.

To find the availability of datasets (for the process of cmeteo-cgms12eu-regions) you need to supply PROCMAN, table prcmn_process_objects with

• CMETEO_AGGREGATION_AREAS
• CMETEO_REGION_GRID_LANDCOVERS
• CMETEO_WEATHER_OBS_GRID
• CMETEO_WEATHER_OBS_REGION
• CMETEO_WEATHER_OBS_REGION_IO

To make CMETEO run the process cmeteo_weather_obs_region, you need to supply PROCMAN, table prcmn_process_objects with info to create (dynamic) synonyms:

• CMETEO_CROPS
• CMETEO_GRID_LANDCOVER_AREAS
• CMETEO_GRID_WEATHER
• CMETEO_LANDCOVERS
• CMETEO_PROCESS
• CMETEO_REGIONS
• CMETEO_REGION_MAPPINGS
• CMETEO_REGION_WEATHER
• CMETEO_REJECTED_WEATHER

Also you need to set some parameters (in PRCMN_CONFIGURATIONS). The PROCMAN system is able to use default settings for all parameters needed. So you only should specify values for some parameters that are specific for process to run.

The list below contains parameters for the CMETEO procedure, their default value and values for processing weather indicators for Regions in CGMS12EU.

PARAMETER_GROUP	PARAMETER	ARGUMENT_TYPE	VALUE_TEXT	TEXT_MASK
	aggregation method	text	plain
	day in interval	text	day1
	destination	text	name of (view/table) for weather
	event id	number	-1	9999
	group indicator	text	std
	include crops	text	no
	interval dates	text	day
	numeric fractions	set of strings	NIL
	roi	text	replace with a non-virtual roi
	thresholds grid	set of integer	0,5
NIL	format fraction number	text	9.99
NIL	operator	text	ne
NIL	source	text	zero
NIL	thresholds	set of number	0
NIL	unit type	text	unit

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. Both methods use the same procedure, CMETEO_ADMIN.DO_AGGREGATION to start with. This procedure defines the interface consisting of parameters, both obligatory or optional.

To get CMETEO working properly, you supply:

• the name of the database schema that holds the data to be processed. Although the schema name is not defined as a parameter, this name is part of the interface. You supply this name as the user name when you login to the database to process CMETEO.
• p_theme: theme, an indication of the group of meteo indicators you wish to process. See the list below for possible themes.
• p_spatial: spatial indicator, e.g. 'Regions', 'agri-environmental zones'. See the list below for possible alternatives.

N.B. you must supply the parameters for theme and spatial indicators exactly as they are defined.

Optionally, you can supply:

• qry_region: a set identifiers of regions to be processed.
• p_yr2start,p_yr2end,p_dy2start,p_dy2end: a day or an interval of days to be processed.
• p_refresh: an indicator whether or not to refresh the previously aggregated weather indicators.

Details of the interface

Themes and spatial indicators as used by CMETEO to perform the process in schema:

schema:	process:	theme:	spatial indicator:
cgfs_eur_09	cmeteo-cgfs-eps-nuts	weather(simulated) eps	NUTS
cgfs_eur_09	cmeteo-cgfs-eps-zones	weather(simulated) eps	agri-environmental zones
cgfs14eu	cmeteo-cgfs14eu-his-regions	weather(simulated) his	Regions
cgfs14eu	cmeteo-cgfs14eu-his-zones	weather(simulated) his	agri-environmental zones
cgfs_eur_09	cmeteo-cgfs-ope-nuts	weather(simulated) ope	NUTS
cgfs_eur_09	cmeteo-cgfs-ope-zones	weather(simulated) ope	agri-environmental zones
cgms12eu	cmeteo-cgms12eu-regions	weather(observed)	Regions
cgms12eu	cmeteo-cgms12eu-zones	weather(observed)	agri-environmental zones
cgms_asia_08	cmeteo-cgms-asia	Weather - CGMS - Analysis	Regions
gwsi_e_12	cmeteo-gwsi_e	Weather - GWSI - Analysis	Regions
gwsi_t_12	cmeteo-gwsi_t	Weather - GWSI - Analysis	Regions

• The theme must be supplied in p_theme. See the table above for possible alternatives. It is an extraction of the process table in MRSMAN.
• The spatial indicator must be supplied in p_spc_res. See the table above for possible alternatives. It is an extraction of the process table in 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 fine grained 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 chosen, 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.
• (Optional) A set identifiers of regions to be processed in the parameter 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.

Several datasources work with the generic interface of CMETEO. The most important ones are listed in the table below.

Datasets (in CGMS12EU) used by cmeteo:

dataset containing:	base set	adapted set for cmeteo	name in cmeteo	remarks
weather indicators per gridcell for meteodata	WEATHER_OBS_GRID	CMETEO_WEATHER_OBS_GRID (view)	CMETEO_GRID_WEATHER	input for cmeteo; intermediate set contains standardized attribute names
weather indicators per administrative (NUTS) region	WEATHER_OBS_REGION	CMETEO_WEATHER_OBS_REGION (view)	CMETEO_REGION_WEATHER	output of cmeteo; intermediate set contains standardized attribute names
weather indicators per agri-environmental region	WEATHER_OBS_AEZ	CMETEO_WEATHER_OBS_AEZ (view)	CMETEO_REGION_WEATHER	output of cmeteo; intermediate set contains standardized attribute names
landcovers or crops to be evaluated	CMETEO_LANDCOVER_EU (in schema FORALL)	CMETEO_LANDCOVERS (synonym)	CMETEO_LANDCOVERS	input for cmeteo; intermediate set contains standardized attribute names
areas/surfaces for landcovers per grid and per admin. region	LINK_REGION_GRID_LANDCOVER	CMETEO_REGION_GRID_LANDCOVERS (view)	CMETEO_GRID_LANDCOVER_AREAS	input for cmeteo; intermediate set contains standardized attribute names
areas/surfaces for landcovers per grid and per agri-env. region	LINK_AEZ_GRID_LANDCOVER	CMETEO_AEZ_GRID_LANDCOVERS (view)	CMETEO_GRID_LANDCOVER_AREAS	input for cmeteo; intermediate set contains standardized attribute names
areas/surfaces for crops per administrative region	AGGREGATION_AREAS	CMETEO_AGGREGATION_AREAS (view)	CMETEO_AGGREGATION_AREAS	input for cmeteo
weather indicators per region which are rejected			CMETEO_REJECTED_WEATHER	output of cmeteo, containing weather indicators per region and date that could not be stored in regular output dataset via cmeteo_region_weather
regions and their mappings	CMETEO_REGION_MAPPINGS (in schema MRSMAN)	CMETEO_REGION_MAPPINGS (synonym)	CMETEO_REGION_MAPPINGS	input for cmeteo
regions to process	CMETEO_REGIONS (in schema MRSMAN)	CMETEO_REGIONS (synonym)	CMETEO_REGIONS	input/output for cmeteo

In various schemas datasets are available that contain weather indicators, e.g. for meteo gridcells or regions of some type. However, they do vary both in name of the set and in names of the attributes. Also the collection of the attributes may vary (with or without day_offsets, with or without members of the meteo ensemble). In fact, all the sets contain the indicators that are essential for the processing of CMETEO. To prevent adaption of the CMETEO application every time another dataset in a schema must be processed or a new schema will be included into the processing scheme of CMETEO, some attention must be paid to the standardisation of the structure of datasets both as input and as output. The standardized dataset for input will be called CMETEO_GRID_WEATHER. For each variant of a dataset containing grid weather a view will be created that presents all attributes needed for the CMETEO process, either as data selected from the dataset or a dummy value. CMETEO just reads this data; there is no need to update this data.

For the output of CMETEO also a view will be created for each variant of output. In some schemas several of such views can exist. The name of a view hints, in most cases, to the name of the dataset on which it is based. CMETEO uses a synonym CMETEO_REGION_WEATHER, denoting the proper view, to access the data and to write the results. At the start of the processing, CMETEO is able to create the synonym to point to the right view.

Specifications of CMETEO_GRID_WEATHER

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 a view on the original dataset containing meteo data of grid cells while renaming attributes and eventually supplying neutral data values for missing attributes (e.g. members and offset days). 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 domain schema: CGMS12EU CGFS14EU CGFS14EU CGFS14EU CGMS_ASIA_08 GWSI dataset: weather_obs_grid weather_his_grid weather_eps_grid weather_ope_grid ecmwf_downscaled_data grid_weather_model_10 cmeteo_grid_weather attributes: grid_no grid_no grid_no grid_no ecmwf_grid_no grid_id grid_no NN number(10) day day day day mdate year, dekade_in_year day NN date - 1) - 1) day_offset day_offset - 1) - 1) day_offset NN number(10) - 2) - 2) member_no member_no - 2) - 2) member_no NN number(10) temperature_max temperature_max temperature_max temperature_max temperature_max temperature_maximum max_temperature NN number(3,1) temperature_min temperature_min temperature_min temperature_min temperature_min temperature_minimum min_temperature NN number(3,1) temperature_avg temperature_avg temperature_avg temperature_avg temperature_mean temperature_mean mean_temperature NN number(3,1) - 3) temperature_dew temperature_dew temperature_dew temperature_dew - 3) dew_temperature NN number(3,1) humidity_06h - 4) - 4) - 4) - 4) - 4) - 4) humidity_09h - 4) - 4) - 4) - 4) - 4) - 4) humidity_12h - 4) - 4) - 4) - 4) - 4) - 4) humidity_15h - 4) - 4) - 4) - 4) - 4) - 4) humidity_18h - 4) - 4) - 4) - 4) - 4) - 4) vapourpressure vapourpressure vapourpressure vapourpressure vapour_pressure - 3) vapour_pressure NN number(4,2) windspeed windspeed windspeed windspeed wind_speed - 3) wind_speed NN number(5,1) precipitation precipitation precipitation precipitation precipitation precipitation precipitation NN number(4,1) e0 e0 e0 e0 e0 - 3) e0 NN number(4,2) es0 es0 es0 es0 es0 - 3) es0 NN number(4,2) et0 et0 et0 et0 et0 et0 et0 NN number(4,2) radiation radiation radiation radiation radiation_global global_radiation global_radiation NN number(6) snowdepth snowdepth - 3) snowdepth snow_depth snow_depth snow_depth number(6,2) - 3) snowweq snowweq snowweq - 3) - 3) snow_weq number(6,2) NN stands for: "not null" i.e. the attribute in this domain may not be filled with null, so must contain a value. 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. 2) For sets that doesn't contain an attribute for members, a member_no: 1 will be supplied in CMETEO_GRID_WEATHER. 3) A dummy value (0) for this weather indicator will be supplied to CMETEO_GRID_WEATHER for sets lacking such an attribute. CMETEO will process this value and produces a result for it. However these results will not be inserted into the output table. 4) This attribute, as included in some dataset, is not processed in CMETEO.

Specifications of CMETEO_REGION_WEATHER

CMETEO_REGION_WEATHER is a replacement for a variety of datasets, both for themes (e.g. CGFS-HIS, CGMS) and for spatial indications (e.g. NUTS regions, agri-environmental zones), to which CMETEO need to write the aggregated results. In general, datasets for NUTS-regions are pre- or postfixed with 'NUTS'; datasets for agri_environmental zones are pre- or postfixed with 'ZONAL'. 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 weather indicators may vary. However, all the sets contain the essential indicators for which CMETEO delivers output. Per theme, the structure of datasets for both spatial indications 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 via specific triggers) 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. In a dynamical way CMETEO_REGION_WEATHER will be linked to the proper dataset according to the theme and the appropriate spatial indication to deliver the results of CMETEO. Below a summary of some sets in various schemas and the definition of CMETEO_REGION_WEATHER domain schema: CGMS12EU CGFS14EU CGFS14EU CGFS14EU CGMS_ASIA_08 GWSI datasets: weather_obs_region weather_his_region weather_eps_region weather_ope_region ecmwf_downscaled_region region_weather_model_10 cmeteo_region_weather weather_obs_aez weather_his_aez weather_eps_aez weather_ope_aez attributes: reg_map_id reg_map_id reg_map_id reg_map_id reg_map_id reg_map_id reg_map_id NN number(10) landcover_id landcover_id landcover_id landcover_id landcover_id landcover_id landcover_id NN number(10) threshold threshold threshold threshold threshold threshold threshold NN number(3) day day day day mdate year, dekad_in_year day NN date - 1) - 1) day_offset day_offset - 1) - 1) day_offset NN number(10) - 2) - 2) member_no member_no - 2) - 2) member_no NN number(10) temperature_max temperature_max temperature_max temperature_max temperature_max temperature_maximum max_temperature NN number(3,1) temperature_min temperature_min temperature_min temperature_min temperature_min temperature_minimum min_temperature NN number(3,1) temperature_avg temperature_avg temperature_avg temperature_avg temperature_mean temperature_mean mean_temperature NN number(3,1) - 3) temperature_dew temperature_dew temperature_dew temperature_dew - 3) dew_temperature NN number(3,1) vapourpressure vapourpressure vapourpressure vapourpressure vapour_pressure - 3) vapour_pressure NN number(4,2) windspeed windspeed windspeed windspeed wind_speed - 3) wind_speed NN number(5,1) precipitation precipitation precipitation precipitation precipitation precipitation precipitation NN number(4,1) e0 e0 e0 e0 e0 - 3) e0 NN number(4,2) es0 es0 es0 es0 es0 - 3) es0 NN number(4,2) et0 et0 et0 et0 et0 et0 et0 NN number(4,2) radiation radiation radiation radiation radiation_global global_radiation global_radiation NN number(6) snowdepth snowdepth - 3) snowdepth snow_depth snow_depth snow_depth number(6,2) - 3) snowweq snowweq snowweq snowweq - 3) snow_weq number(6,2) fractions 4) fractions 4) fractions 4) fractions 4) nil-fractions 5) nil-fractions 5) fractions 4) td_threshold_values NN stands for: "not null" i.e. the attribute in this domain may not be filled with null, so must contain a value. 1) The value for the offset of the day as produced by CMETEO will not be inserted into indicated sets. 2) The value for the member as produced by CMETEO will not be inserted into indicated sets. 3) As input for this attribute was lacking, the dummy value (0) produced by CMETEO will be omitted. 4) This dataset also contains attributes that can be regarded as fractions. These are derived from meteo indicators in the input set in a well defined way. All these fractions are collected in a structure of varying length in the view based on this dataset. 5) This dataset does not contain attributes to be regarded as fractions. The nil-fractions delivers a dummy in the view based on this dataset.

Specifications of CMETEO_AGGREGATION_AREAS

CMETEO_AGGREGATION_AREAS is a replacement for some of datasets of which CMETEO needs to gather input concerning crop and region specific areas. Note this is only used if the user chooses to have an additional crop specific aggregation from lower to higher administrative regions. Below a summary of some sets in various schemas and the definition of CMETEO_AGGREGATION_AREAS domain schema: CGMS12EU CGFS14EU CGMS_ASIA_08 GWSI dataset: aggregation_areas 1) - 2) aggregation_areas 1) - 3) cmeteo_aggregation_areas attributes: crop_no crop_no crop_no NN number(10) reg_map_id > reg_code 4) nuts_code reg_code NN varchar2(10) year year year NN number(4) area_cultivated area_cultivated area_cultivated number source source source NN varchar2(40) 1) not every attribute of the dataset will be used in CMETEO. 2) CGFS14EU uses the dataset of CGMS12EU. 3) For GWSI no aggregation for crops is planned. It uses the dummy dataset of MRSMAN. 4) As a remains of a former version of CMETEO, here the region code (NUTS_code) is needed in stead of the reg_map_id

Specifications of CMETEO_GRID_LANDCOVER_AREAS

CMETEO_GRID_LANDCOVER_AREAS is a replacement for a some of datasets of which CMETEO needs to gather input concerning land cover and grid cell specific areas. Below a summary of some sets in various schemas and the definition of CMETEO_GRID_LANDCOVER_AREAS domain schema: CGMS12EU CGFS14EU CGMS_ASIA_08 GWSI datasets: link_region_grid_landcover - 1) - 2) - 2) cmeteo_grid_landcover_areas link_aez_grid_landcover - 1) attributes: grid_no grid_no 3) grid_no grid_no NN number(10) reg_map_id reg_map_id reg_map_id reg_map_id NN number(10) landcover_id landcover_id landcover_id landcover_id NN number(3) area area area area NN number(10) 1) CGFS14EU uses the dataset of CGMS12EU. 2) In this schema the dataset is defined as a view on table FORALL.GRID_REGION_LANDCOVERS. 3) Some conversion on grid_no is done in order to get the right range of grid cells as used in the ROI ASIA.