Versions Compared

Old Version 5

changes.mady.by.user Unknown User (maif)

Saved on

compared with

New Version 6

changes.mady.by.user Unknown User (maif)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

page under construction ------------------------------

Table of Contents


The GRIB sub-setting service of the CDS currently rely on MIR. 

It is important to define correctly the coordinates of the bounding box. 

The coordinates have to be multiple of 0.05 otherwise MIR will interpolate the data and likely corrupt the river network.




General

Why my requests are in a 'running' state for a long time?

The Climate Data Store is used daily by thousands of users requesting and processing data. It is possible that sometime the system goes under stress.

More information in 

Why my requests are in a 'pending' state for a long time?

The Climate Data Store is a distributed data system that facilitates data retrieval from different sources and data providers.

CEMS-flood datasets are archived in MARS (Meteorological Archival and Retrieval System). Every Wednesday there is a MARS system session, that can affect request queuing time.

You can check the status of the system  hereMore information in CDS - Best Practices.

GloFAS

How do I spatially subset the dataset?

Warning

It is possible to subset GloFAS datasets using the 'area' keyword in the CDS API request,


Code Block
languagepy
titleexample request
collapsetrue
import cdsapi

c = cdsapi.Client()

c.retrieve(
    'cems-glofas-reforecast',
    {
        'system_version': 'version_2_2',
        'variable': 'river_discharge_in_the_last_24_hours',
        'format': 'grib',
        'hydrological_model': 'htessel_lisflood',
        'product_type': 'control_reforecast',
        'hyear': '2016',
        'hmonth': 'january',
        'hday': '10',
        'leadtime_hour': '24',
        'area': [
            10.95, -30.95, -15.75, 30.05, # North West South East
        ],
    },
    'download.grib')



or from the Web catalogue using the "Geographical area" widget. 



Why latitude and longitude coordinates are multiple of 0.05?

In the GRIB format the data field is represented by a grid of points. 

GloFAS datasets have a spatial resolution of 0.1x0.1 degrees.

The points coordinates, multiple of 0.05 and spaced by 0.1 degree, represent the centre of a cell of 0.1x0.1 degree.

Why the GRIB format has longitude range between 180 and 540?

GRIB format does not allow negative longitude values, therefore the range is computed adding 360 to the longitude range (180 = -180 + 360, 540 = 180 + 360).

When reading GRIB with the Python Xarray/CFGRIB converter, the tool automatically converts the range back to -180 to 180. 

EFAS

How do I spatially subset the dataset?

Currently there is no service to subset EFAS data.




...