...
The data within the files were not individually checked, therefore it is important to note that passing of these quality control tests should not be confused with validity: for example, it will be possible for a file to be fully CF compliant and have fully compliant metadata but contain gross errors in the data that have not been revealed.
Known issues
HERE WE HAVE TO SPEAK ABOUT THE ERRATA AND WE HAVE TO POPULATE THE ERRATA INFORMATION TOO!!
All know issues about CORDEX data are documented through the ES-DOC Errata Service : https://errata.es-doc.org/. The Errata Service also includes a command-line interface and an API to request the issue database for a specific dataset or file.
In addition:
- Please have a look on the Errata Service to be warned about deprecated CORDEX runs that will be retracted in the future.
- Please not that not all combinations of models and domains exists. This feature is due to the different CORDEX initiatives/consortiums that do not involved the same data producers using the same RCMs.
- Please note that not all the combinations of models and variables exist. This feature is inherited from the ESGF system, where the main target is to publish as much as possible data and even publish incomplete datasets, which might be of use. This allows to have more data available with the price that not everything is fully complete.
- Please not that not all combinations of models and domains exists. This feature is due to the different CORDEX initiatives/consortiums that do not involved the same data producers using the same RCMs.
- Please note that not all the combinations of models and variables exist. This feature is inherited from the ESGF system, where the main target is to publish as much as possible data and even publish incomplete datasets, which might be of use. This allows to have more data available with the price that not everything is fully complete.
Sometimes there are some inconsistencies in the NetCDF files, for instance the header information is not in agreement with the content. An example is the case of ALADIN Regional Climate Model, where in the file header it is indicated that the 2m temperature data units are Kelvin, though instead the data are listed in Celsius. This kind of discrepancies come from the data producers and they are very difficult to rectify, since the producers are usually reluctant to update datasets, which were provided quite some time ago. Such kind of issue should be documented through the errata service.
Background documents and user guides
...