• Regional subselection and horizontal grid interpolation

Currently the interactive CDS forms don't allow users to perform a regional subselection or an interpolation of the selected data. However, both actions can be performed using the CDS API keywords area and grid with the same syntax used by ECMWF MARS and Web API.

import cdsapi

c = cdsapi.Client()

c.retrieve(
    'seasonal-monthly-single-levels',
    {
        'format':'grib',
        'originating_centre':'cmcc',
        'system':'3',
        'variable':'2m_temperature',
        'product_type':'monthly_mean',
        'year':'2007',
        'month':'11',
        'leadtime_month':['1','2','3','4','5','6'],
		'area' : '75/-25/10/60',
		'grid' : '2.5/2.5'
    },
    'download.grib')

Users must be aware of the following:

• • Use of area for regional subselection is safe.
  • Use of grid for horizontal interpolation is currently NOT recommended:
    • It can lead to errors when trying to download MetOffice data. More information about what causes this error can be found in Known issue D2.
    • It can lead to failing data retrievals if more than one model version (system) is requested. Note that if system is not explicitly specified it defaults to all available systems.
    • Data previously downloaded using Web API may have used a different interpolation method; you would need to assess whether such differences are relevant for your choice of data. This issue is relevant in the context of the required consistency between interpolation of real-time forecasts and the associated hindcasts.

• Conversion to NetCDF

Currently the interactive CDS forms don't allow users to select NetCDF as data format for their retrievals. However, the value of the format keyword in CDS API scripts can be set to "netcdf" to obtain a netCDF version of the archived GRIB data.

Users must be aware that conversion to NetCDF is considered experimental and it is not guaranteed to work in all situations.

In this context,

• • It is NOT recommended to include in a single request more than one model version (system). Note that for hindcasts, data from more than one system may exist in the archive and that, if system is not explicitly specified in the request, the default is to return all available systems.
  • It is NOT recommended to include in a single request data related to more than one start time.

• Efficiency tips

The C3S seasonal forecast dataset is currently based on GRIB files archived at ECMWF's MARS archive. This implies, in some situations, accessing data not available online (on disk) but archived in the tape library.

The way the user selects the items to include in a single request can make a huge difference in the performance of the retrieval. To improve performance:

• • Users are encouraged to explore the C3S catalogue using the former Web API catalogue tool here: https://apps.ecmwf.int/data-catalogues/c3s-seasonal/?class=c3
    The guidance given in section 2a of the guidance for migration from Web API to CDS API explains the mapping of syntax between that Web API catalogue and the CDS forms.
    All the data shown at the same time in a window like the picture below, constitutes a "leaf" in the MARS "tree". This is usually guaranteed to be in a single archived file, and hence in one single tape.
    Users are encouraged to

    • combine in one single request all the data they are interested in which is contained in the same MARS "leaf"

    • avoid combining data from two different "leaves".

      
      

  • Users are encouraged to devise their requests as follows:
    • Do NOT ask for different start months in the same request when retrieving data from the "daily" datasets.
      It is much more efficient to request one single month (e.g. November) for all the hindcast years (1993 to 2016) than requesting all 12 months from a single year
    • Combine in one single request all variables of interest, all levels (for pressure level fields), all product types and all leadtimes (hours or months, depending on the CDS product). However, note that there are some limitations in the size of a request. If you are using the CDS forms directly, you will be informed when you request is too big before submitting it. If you are using CDS API you can use the forms to discover whether the request you are trying to submit is affordable or not.