Changes between Version 33 and Version 34 of udg/ecoms/dataserver/catalog


Ignore:
Timestamp:
Jun 5, 2014 6:16:11 PM (7 years ago)
Author:
gutierjm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • udg/ecoms/dataserver/catalog

    v33 v34  
    1 The '''​ECOMS UDG''' provides a homogeneous access (through a single controlled vocabulary) to the different available [wiki:../Datasets datasets]. However, only a reduced number of [https://meteo.unican.es/trac/wiki/EcomsUdg/EndUserNeeds/ListOfVariables variables required] by the different ECOMS activities (impact applications and downscaling studies) is provided by the portal. The following list of variables has been identified (and is periodically updated) according to the user's needs, receiving feedback from EUPORIAS WP22 (climate information indices, CIIs), WP23 (impact models), WP21 (calibration and downscaling) and SPECS WP61 (pilot applications) and WP52 (calibration and downscaling). See  the section on the [wiki:../../EndUserNeeds assessment of user's needs] for more details.
     1The '''​ECOMS UDG''' provides access to a reduced  number of variables for the available [wiki:../Datasets datasets]. The following list of variables has been identified (and is periodically updated) according to the user's needs, receiving feedback from EUPORIAS WP22 (climate information indices, CIIs), WP23 (impact models), WP21 (calibration and downscaling) and SPECS WP61 (pilot applications) and WP52 (calibration and downscaling). See  the section on the [wiki:../../EndUserNeeds assessment of user's needs] for more details.
    22
    33The following labels are used in the table below ('''Available''': The variable is available and ready to use through the ECOMS UDG; '''e''': The variable exists in the original dataset; '''P''': The variable exists in the original dataset and work is in progress to incorporate it to the UDG; blanks indicate lack of data).
    44
    5 Note that the short names shown in boldface correspond to standard variables according to the [http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.html/ NetCDF Climate and Forecast Metadata Convention] and to the naming convention within SPECS.
     5Note that the short names shown in boldface correspond to standard variables according to the [http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.html/ NetCDF Climate and Forecast Metadata Convention] and to the naming convention within SPECS, but do not correspond to the original source name for the different datasets.
    66
    77|| || || || ||||||||||  '''Availability for the following datasets:'''  ||
     
    4040
    4141(*) These variables do NOT exist in the corresponding dataset, but they will be derived/approximated from other available variables.  More information in the table of [http://meteo.unican.es/trac/wiki/EcomsUdg/EndUserNeeds/ListOfVariables variables-datasets mapping].
     42
     43'''Data Homogeneization:''' The different nature of the datasets, and the idiosyncratic naming and storage conventions often applied by the modelling centres, makes necessary an homogeneization across datasets in order to implement a truly user-friendly toolbox for data access.  To this aim, the [wiki:RPackage R package for data access] has been developed. Data homogeneization is achieved through the creation of a common vocabulary. The particular variables of each dataset are then translated -and transformed if necessary- into the common vocabulary by means of a ''dictionary''. Both features -vocabulary and dictionary- are described [wiki:RPackage/Homogeneization here].