...
The CDS enforces constraints to the number of field fields per request that are retrievable for each dataset. The reason is to keep the system responsive for as many users as possible. The consequence is that you cannot download the whole dataset in one go, but you will need to device a retrieve strategy to, for example, loop over certain fields and retrieve the dataset in chunks.
...
In Table 2, we list the maximum fields that you can retrieve for each dataset and the corresponding downloaded data size, assuming GRIB2 file format and that no cropping has been performed. Also, we provide a short description of the request strategy and the link to a script that you can use to perform the request.
...
Table 2 - Request strategy
| Dataset |
|---|
| N. of fields per request | Request strategy | Corresponding file size per request (loop) | Link to example script |
|---|---|---|---|
| GloFAS climatology | 500 |
| Loop over years | 2 GB | script |
| GloFAS forecast | 60 |
| loop over years, months, days | 8.1 GB | script |
GloFAS reforecast | 950 |
loop over months, days |
Consider cropping to ROI | 32 GB | |
| GloFAS seasonal forecast | 125 |
Loop over years, months |
Consider cropping to ROI | 31.5 GB | |
| GloFAS seasonal reforecast | 125 |
Loop over years, months |
Consider cropping to ROI | 31.5 GB | |||
| EFAS climatology | 1000 | script | ||
| EFAS forecast | 1000 | script | ||
| EFAS reforecast | 200 | loop over years, months, days | 2.3 GB | |
| EFAS seasonal forecast | 220 | loop over months, days | 13.1 GB | |
| EFAS seasonal reforecast | 220 | 13.1 GB |
Whilst submitting multiple requests can improve download time, overloading the system with too many requests will eventually slow down the overall system performance.
...