Page tree
Skip to end of metadata
Go to start of metadata

C3S Seasonal forecasts are available through two platforms:

  • From the Copernicus Climate Change Service's Climate Data Store (CDS).  The CDS provides the most commonly requested C3S seasonal forecast data in an easily accessible way. See the CDS for further information.
  • From the ECMWF WebAPI, as described below. Trough the ECMWF WebAPI all C3S Seasonal forecast data is available.

(warning)  Before proceeding with the steps below, users must be ECMWF registered and have their computer set up as described on How to download data via the ECMWF WebAPI.

1. Learn about C3S Seasonal forecast data

  1. Read about C3S Seasonal forecast service.
  2. Browse the C3S Seasonal Forecast data catalogue and make sure the data you are interested in is available. Note that for a multi-selection 'Check for availability' might confirm availability, even if Step 0 is actually not available. Hence we recommend you check availability of each parameter separately for Step 0, and if Step 0 is not available for a parameter, do not include Step 0 in your request script.
  3. C3S Seasonal forecast data documentation is currently in preparation and will be made available as soon as possible to help users with parameters (fields), values for data type, stream, level type (surface, pressure levels, model levels, etc) , forecast steps, etc... In the meantime, users may contact the Copernicus User Support team for assistance with C3S Seasonal data selection.
  4. See known issues of the C3S seasonal forecast

2. Copernicus License agreement

Read the Copernicus license agreement and accept it at the bottom of the page.

3. Run a C3S Seasonal forecast test retrieval script

This is to verify that your computer is set up correctly.

  1. Copy the Python script below to a text file and save it, for example as ""

    #!/usr/bin/env python
    from ecmwfapi import ECMWFDataServer
    server = ECMWFDataServer()           
        "dataset":   "c3s_seasonal",           
        "date":      "2017-09-01",
        "levelist":  "10",
        "levtype":   "pl",
        "number":    "0/to/50",
        "origin":    "ecmf",
        "param":     "130.128",
        "step":      "12",
        "stream":    "mmsf",
        "time":      "00:00:00",
        "type":      "fc",
        "area":      "75/-20/10/60",
        "grid":      "1.0/1.0",
        "format":    "netcdf",
        "target":    ""
  2. Run the script. On most computers you would do this by opening a command prompt and typing


The test request will download data from ECMWF and save as file "" in the directory you issued the command from. The file should be around 535 KB.

(warning) If you get an error message, most likely your computer setup is wrong, or you did not accept the data license, please go back to the previous set-up steps.

Note that the data retrieval is not designed to be instant. The test request above usually takes a few minutes to complete, but depending on demand can take longer.

4. Create your custom C3S Seasonal forecast data retrieval script

  1. Browse the C3S Seasonal Forecast data catalogue for the data you are interested in, and in the last step make a selection in all boxes and click 'View the MARS request' and make sure the Python Script tab is displayed. This shows a template Python script with your selected options.
  2. Copy the template Python script to a text file and save it, for example as ''
  3. Adapt the template Python script to your requirements, taking the following remarks into account:
    1. In most cases, you will have to add lat/lon "grid" in your script, e.g., "grid": "1.0/1.0". This will enable you to download data on a regular lat/lon grid. And this is necessary if you download the data in NetCDF format.
    2. For an output in NetCDF format, add "format": "netcdf" in your script. By default, output will be in GRIB format. Notice if you retrieve forecast data in NetCDF, please be aware of this potential issue.
    3. If you specify "grid", the horizontal resolution is in decimal degrees. For more details, see this link. If not set, the archived grid as specified in the data documentation is used.
    4. If you do not want global data, you can add "area" as N/W/S/E in lat/lon degrees. Southern latitudes and western longitudes must be given as negative numbers, e.g., "area": "75/-20/10/60". If you set "area", you should also add a lat/lon grid, e.g., "grid": "1.0/1.0", as shown in c. For more details about "area", seethis link.
    5. If you are retrieving forecast data ("type":"fc"), make sure that "steps" are specified. Note that if "type" is set to "fc", then "time" is the time of the forecast.
    6. Change the "target": "CHANGEME", to the desired output path and file name, e.g.  "" or "./data/data1.grib". The default path is the current working directory.

Please read!
(warning) Limits: There are limits of the number and size of downloads.

(lightbulb) Data tapes and retrieval efficiency:

To retrieve data efficiently (and get your data quicker!) you should retrieve all the data you need from one tape, then from the next tape, and so on. In most cases, this means retrieving all the data you need for one month, then for the next month, and so on. To find out what data is available on each tape, browse the C3S Seasonal forecast catalogue and make your way until the bottom of the tree archive (where parameters are listed). Once you will have reached that level of the archive, what you see is what you can find on one single tape. See Retrieval efficiency page for more details.

5. Run your data retrieval script

On most computers you would do this by opening a command prompt and typing


This will retrieve the data as specified and download it as a single file to your computer into the current directory (or whichever "target" directory you specified).

Note that the data retrieval is not designed to be instant. A larger request can take hours and even days to complete.

For long running processes you can check the progress of your request in your job list.

To report an issue or bug please contact Copernicus Support at ECMWF.