...
- Go to the C3S climate data store (CDS).
- Type 'ERA5' in the search box.
- Follow the ERA5 dataset title link of interest (there will be many more hits).
Currently there are eight six online ERA5 and two three ERA5-Land catalogue entries catalogue entries. There is an additional catalogue entry for Complete ERA5 global atmospheric reanalysis (reanalysis-era5-complete) but this data cannot be downloaded from the CDS web interface (see section 4 below).
- Each of these dataset catalogue entries includes the following tabs:
- Overview . This gives a description of the selected dataset and metadata information (e.g. spatial details, file format, variables, etc).
- Documentation . This provides links to detailed documentation about the dataset.
- Download data . This is a download web form.
- Go to the Download data tab to make your selection for ERA5 data retrieval. Using this web interface, you can:
- make selections as per your requirements. For your convenience only valid combinations will show; invalid combinations are greyed out interactively.
accept the data licence in the Terms of use section (in case you had not yet accepted it). You will only see this section after you have logged in.
Note You will need to do this regardless whether you are accessing data through the web interface or through the CDS API (see below).
Click on the button Submit Form at the bottom right to submit your data request (you must be logged in and have accepted the terms and conditions before submitting your request).
- You will now be redirected to the Your requests page.
Once your request has been processed you can download the data by clicking the green Download button. You can check the Live status of your request .
4 - Download ERA5 family data through the CDS API
...
Build a basic CDS API request.
You can use the CDS web interface to help you build your CDS API download script.
In the Download data tab, make some selections, then click the button Show API request code at the bottom left and you will be presented with the script.
Copy and paste this to your preferred text editor.
Expand title Basic CDS API script example (for ERA5 1940-present) to download geopotential at a given pressure level, 1000 hPa is shown HERE. Code Block language py import cdsapi client = cdsapi.Client() dataset = 'reanalysis-era5-pressure-levels' request = { 'product_type': ['reanalysis'], 'variable': ['geopotential'], 'year': ['2024'], 'month': ['03'], 'day': ['01'], 'time': ['13:00'], 'pressure_level': ['1000'], 'data_format': 'grib', # Supported format: grib and netcdf. Default: grib } target = 'download.grib' # Output file. Adapt as you wish. client.retrieve(dataset, request, target)
- Refine your CDS API script for ERA5 data listed in CDS for optional post-processing.
- For a different grid resolution, use the key 'grid'.
- Please note that the ERA5 native grid of online CDS is 0.25°x0.25° (atmosphere), 0.5°x0.5° (ocean waves), mean, spread and members: 0.5°x0.5° (atmosphere), 1°x1° (ocean waves). ERA5-Land: 0.1°x0.1°. So this will be returned by default.
Expand title Click here for a sample script (for ERA5 1940-present) that downloads temperature at a given pressure level at 1000 hPa for a geographical subset of the data and specified grid Code Block language py import cdsapi client = cdsapi.Client() dataset = 'reanalysis-era5-pressure-levels' request = { 'product_type': ['reanalysis'], 'variable': ['geopotential'], 'year': ['2024'], 'month': ['03'], 'day': ['01'], 'time': ['13:00'], 'pressure_level': ['1000'], 'data_format': 'grib', # Supported format: grib and netcdf. Default: grib 'area': [60, -10, 50, 2], # North, West, South, East. Default: global 'grid': [1.0, 1.0], # Latitude/longitude grid. Default: 0.25 x 0.25 } target = 'download.grib' # Output file. Adapt as you wish. client.retrieve(dataset, request, target)
...
Note | ||
---|---|---|
| ||
When requesting ERA5 data from the CDS in NetCDF (web or CDS API), users should not request ERA5 reanalysis atmospheric atmospheric data, wave data, and ensemble and ensemble data in one request. This is because the because the data has different spatial grids, which can cause issues for the current grib to NetCDF converter and produce incorrect results. |
...