Versions Compared

Key

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

...

You will find two CDS catalogue entries labelled 'daily data'; these contain data at daily or subdaily frequency (6h, 12h or 24h) . The output of the different forecasting systems is available both for real-time forecasts (from 2017 onwards) and retrospective forecasts (referred to as hindcasts) for the period 1993-2016.
Note that all available individual members for each forecasting system will be provided with every request.

One dataset contains surface (or single level) parameters, the other contains variables on 11 pressure levels spanning 925 hPa to 10 hPa.

...

Expand
titleSeasonal forecast monthly statistics on single levels from 2017 to present

01. Originating Centre

Select the name of the institution the forecasting system of your interest originates from.

02. System

Select the version of the forecasting system. This is a numeric label and the available values are different for the different "originating centres". Note that for a given start date you could find more than one system available for a single "originating centre".
Please note that you must pair up your forecasts with the relevant hindcasts by using the same "system" for both of them.A full description of the use of the system keyword is available from the "Documentation" tab.

03. Variable

Select the parameter(s) you are interested in.

04. Product Type

Select the monthly product you are interested in.
Note that your retrieved data those products labelled under the category "Individual members" will consist of all available individual ensemble members, except for the products based on while those others in the category "Ensemble" will just have a single value for each forecasting system ensemble (ensemble mean and hindcast climate mean).

Image Removed

.

Image Added

05. Year

Select the year of the initialization date of the model run(s) you are interested in.
Note that there could be differences in the options available depending on your selection of forecast or hindcast years.

Please note that you must use the hindcast data in order to make a meaningful use of the forecast data. And remember you must pair forecasts and hindcasts up by using the same "system" for both of them.

06. Month

Select the month of the initialization date of the model run(s) you are interested in.
Note that in the current setup all monthly products are encoded using as nominal start date the 1st of each month, regardless of the real initialization date. You can find more information about how nominal start dates are assigned in the "Documentation" tab.

07. Leadtime Month

Select the lead time(s) you are interested in. This is the time, in months, from the initialization date.
Note that the convention used for labelling the data implies that leadtime_month=1 is the first complete calendar month after the initialization date. In the current setup of all datasets that means that for a forecast initialised on the 1st of November, leadtime_month=1 is November.

08. Format

You can select the data format for your data retrieval.
Currently, just GRIB format is available for C3S seasonal forecast datasets.
An experimental netCDF conversion can be accessed by using the CDS API. You can find some related information in the "Documentation" tab.

09. Terms of Use

You must accept the terms and conditions of the Copernicus User Licence in order to access the C3S seasonal forecast data.

...

Expand
titleSeasonal forecast monthly statistics on pressure levels from 2017 to present

01. Originating Centre

Select the name of the institution the forecasting system of your interest originates from.

02. System

Select the version of the forecasting system. This is a numeric label and the available values are different for the different "originating centres". Note that for a given start date you could find more than one system available for a single "originating centre".
Please note that you must pair up your forecasts with the relevant hindcasts by using the same "system" for both of them.A full description of the use of the system keyword is available from the "Documentation" tab.


03. Variable

Select the parameter(s) you are interested in.

04. Pressure Level

Select the pressure level(s) for the variables you are interested in.

05. Product Type

Select the monthly product you are interested in.
Note that your retrieved data those products labelled under the category "Individual members" will consist of all available individual ensemble members, except for the products based on while those others in the category "Ensemble" will just have a single value for each forecasting system ensemble (ensemble mean and hindcast climate mean).

06. Year

Select the year of the initialization date of the model run(s) you are interested in.
Note that there could be differences in the options available depending on your selection of forecast or hindcast years.

Please note that you must use the hindcast data in order to make a meaningful use of the forecast data. And remember you must pair forecasts and hindcasts up by using the same "system" for both of them.

07. Month

Select the month of the initialization date of the model run(s) you are interested in.
Note that in the current setup all monthly products are encoded using as nominal start date the 1st of each month, regardless of the real initialization date. You can find more information about how nominal start dates are assigned in the "Documentation" tab.

08. Leadtime Month

Select the lead time(s) you are interested in. This is the time, in months, from the initialization date.
Note that the convention used for labelling the data implies that leadtime_month=1 is the first complete calendar month after the initialization date. In the current setup of all datasets that means that for a forecast initialised on the 1st of November, leadtime_month=1 is November.


09. Format

You can select the data format for your data retrieval.
Currently, just GRIB format is available for C3S seasonal forecast datasets.
An experimental netCDF conversion can be accessed by using the CDS API. You can find some related information in the "Documentation" tab.

10. Terms of Use

You must accept the terms and conditions of the Copernicus User Licence in order to access the C3S seasonal forecast data.

...

Expand
titleSeasonal forecast anomalies on single levels from 2017 to present

01. Originating Centre

Select the name of the institution the forecasting system of your interest originates from.

02. System

Select the version of the forecasting system. This is a numeric label and the available values are different for the different "originating centres".
A full description of the use of the system keyword is available from the "Documentation" tab.

03. Variable

Select the parameter(s) you are interested in.

04. Product Type

Select the monthly product you are interested in.

Image Removed

Note that those products labelled under the category "Individual members" will consist of all available individual ensemble members, while those others in the category "Ensemble" will just have a single value for each forecasting system ensemble.

Image Added

05. 05. Year

Select the year of the initialization date of the model run(s) you are interested in.
Note that anomalies are just available for real-time forecasts start dates.

06. Month

Select the month of the initialization date of the model run(s) you are interested in.
Note that in the current setup all monthly products are encoded using as nominal start date the 1st of each month, regardless of the real initialization date. You can find more information about how nominal start dates are assigned in the "Documentation" tab.

07. Leadtime Month

Select the lead time(s) you are interested in. This is the time, in months, from the initialization date.
Note that the convention used for labelling the data implies that leadtime_month=1 is the first complete calendar month after the initialization date. In the current setup of all datasets that means that for a forecast initialised on the 1st of November, leadtime_month=1 is November.

08. Format

You can select the data format for your data retrieval.
Currently, just GRIB format is available for C3S seasonal forecast datasets.
An experimental netCDF conversion can be accessed by using the CDS API. You can find some related information in the "Documentation" tab.

09. Terms of Use

You must accept the terms and conditions of the Copernicus User Licence in order to access the C3S seasonal forecast data.

...

Expand
titleSeasonal forecast anomalies on pressure levels from 2017 to present

01. Originating Centre

Select the name of the institution the forecasting system of your interest originates from.

02. System

Select the version of the forecasting system. This is a numeric label and the available values are different for the different "originating centres".
A full description of the use of the system keyword is available from the "Documentation" tab.


03. Variable

Select the parameter(s) you are interested in.

04. Pressure Level

Select the pressure level(s) for the variables you are interested in.

05. Product Type

Select the monthly product you are interested in.
Note that those products labelled under the category "Individual members" will consist of all available individual ensemble members, while those others in the category "Ensemble" will just have a single value for each forecasting system ensemble.

06. Year

Select the year of the initialization date of the model run(s) you are interested in.
Note that anomalies are just available for real-time forecasts start dates.

07. Month

Select the month of the initialization date of the model run(s) you are interested in.
Note that in the current setup all monthly products are encoded using as nominal start date the 1st of each month, regardless of the real initialization date. You can find more information about how nominal start dates are assigned in the "Documentation" tab.

08. Leadtime Month

Select the lead time(s) you are interested in. This is the time, in months, from the initialization date.
Note that the convention used for labelling the data implies that leadtime_month=1 is the first complete calendar month after the initialization date. In the current setup of all datasets that means that for a forecast initialised on the 1st of November, leadtime_month=1 is November.

09. Format

You can select the data format for your data retrieval.
Currently, just GRIB format is available for C3S seasonal forecast datasets.
An experimental netCDF conversion can be accessed by using the CDS API. You can find some related information in the "Documentation" tab.

10. Terms of Use

You must accept the terms and conditions of the Copernicus User Licence in order to access the C3S seasonal forecast data.

...