...
| 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 | Loop over years | 450 MB | script |
| EFAS forecast | 1000 | loop over years, months, days | 3.7 GB | script |
| EFAS reforecast | 200 | loop over yearsyear, months, days | 2.3 GB | |
| EFAS seasonal forecast | 220 | loop over months, days | 13.1 GB | |
| EFAS seasonal reforecast | 220 | loop over months, days | 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.
...