Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Find out how to access ECMWF real-time open data
Note | ||
---|---|---|
ECMWF has recently deployed an updated version of the IFS Open Data at 0.25 degrees, with additional parameters to enable limited area model and machine-learning initialisation.
|
Note |
---|
See important licence and attribution information regarding open data on our datasets page. |
Where to find the real-time open data
This page documents the access to ECMWF IFS open data and the AIFS Machine Learning Data.
You can use the ECMWF link to browse the list of files.
Currently, ECMWF open real-time data are available from these locations:
- Amazon's AWS: "https://ecmwf-forecasts.s3.eu-central-1.amazonaws.com"
- ECMWF: https://data.ecmwf.int/forecasts
- Google Cloud: "https://console.cloud.google.com/marketplace/product/bigquery-public-data/open-data-ecmwf"
- Microsoft's Azure: "https://ai4edataeuwest.blob.core.windows.net/ecmwf"
- Open-meteo.com: "https://open-meteo.com/en/docs/ecmwf-api"
See file-naming convention below for an explanation of ROOT.
If you are interested in hosting our open data, please contact us via the support portal.
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Sign up for an open data mailing list, a joint project with EUMETSAT, Met Norway and DWD to share new and updated open datasets, and relevant resources, conferences and articles.
|
File format
The files are in GRIB edition 2 format, except for trajectories which are in BUFR edition 4 format. We recommend using ecCodes version 2.24.2 or newer to manipulate the GRIB and BUFR files.
File-naming convention
The files are provided with the following naming convention:
No Format |
---|
[ROOT]/[yyyymmdd]/[HH]z/[model]/[resol]/[stream]/[yyyymmdd][HH]0000-[step][U]-[stream]-[type].[format] |
where:
[ROOT]
is the top-level URL of one of the sites hosting the data. See the above for possible values.[yyyymmdd]
is the reference date of the forecasts (base date).[HH]
is the reference time of the forecasts. Values are00
,06
,12
and18
.[model]
is the production model (IFS or AIFS). Note: IFS and AIFS have different options, so please be review dataset pages to see what is available.[resol]
is the horizontal resolution of the data. Options include: 0p25 or 0p4-beta[stream]
is the forecasting system that produces the data. Values are:oper
- high-resolution forecast, atmospheric fieldsenfo
- ensemble forecast, atmospheric fields (not applicable for AIFS model)
From January 2022, ECMWF made a wide range of ensemble and high-resolution forecast data openly available
Note |
---|
Open data parameters are free of charge when accessed via the public ECMWF website. They can also be delivered via the ECPDS platform to your nominated FTP server, in this case they may be subject to service charges. For additional data, including higher resolutions and more parameters, charges apply and the ECMWF Standard Licence Agreement applies. Data can be obtained from the ECMWF Product Requirements Catalogue or by contacting a Catalogue Contact Point for more information. |
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Sign up for an open data mailing list, a joint project with EUMETSAT, Met Norway and DWD to share new and updated open datasets, and relevant resources, conferences and articles.
|
Info |
---|
AttributionThe following wording should be attached to the use of this ECMWF dataset:
The following wording shall be attached to services created with this ECMWF dataset:
|
About this dataset
ECMWF Open Data (real-time) is provided with an open licence (CC-BY-4.0). Data accessed via the public ECMWF web site are free of charge.
This page describes how the data are organised and how they can be downloaded.
A Python package called ecmwf-opendata is available from PyPi that greatly facilitates the access to this dataset. In addition, a series of Jupyter Notebooks have been developed to demonstrate the use of this package.
Availability
The data are released 1 hour after the real-time dissemination schedule.
File format
The files are in GRIB edition 2 format, except for trajectories which are in BUFR edition 4 format. We recommend using ecCodes version 2.24.2 or newer to manipulate the GRIB and BUFR files.
File-naming convention
The files are provided with the following naming convention:
No Format |
---|
[ROOT]/[yyyymmdd]/[HH]z/[resol]/[stream]/[yyyymmdd][HH]0000-[step][U]-[stream]-[type].[format] |
where:
[ROOT]
is the top-level URL of one of the sites hosting the data. See the ECMWF open data: real-time forecasts below for possible values.[yyyymmdd]
is the reference date of the forecasts (base date).[HH]
is the reference time of the forecasts. Values are00
,06
,12
and18
.[resol]
is the horizontal resolution of the data. This is currently set to0p4-beta
and will be changed to0p4
when the beta-testing period is over.[stream]
is the forecasting system that produces the data. Values are:oper
- high-resolution forecast, atmospheric fieldsenfo
- ensemble forecast, atmospheric fields- waef - ensemble forecast, ocean wave fields, (not applicable for AIFS model)
wave
- wave model, (not applicable for AIFS model)scda
- short cut-off high-resolution forecast, atmospheric fields (also known as "high-frequency products") (not applicable for AIFS model)scwv
- short cut-off high-resolution forecast, ocean wave fields (also known as "high-frequency products") and) (not applicable for AIFS model) andmmsf
- multi-model seasonal forecasts fields from the ECMWF model only (not applicable for AIFS model).
[step]
is the forecast time step expressed in unitsU
[U]
is the unit used for the time step. Values areh
for hours andm
for month. The latter is only valid for seasonal forecasts (mmsf).[type]
is once offc
(forecast),ef
(ensemble forecast),ep
(ensemble probabilities) ortf
(trajectory forecast for tropical cyclone tracks).[format]
isgrib2
for all fields, andbufr
for the trajectories.
The valid combinations of the above are:
No Format |
---|
format=bufr, type=tf
HH=00/12
stream=enfo/oper, step=240h
HH=06/18
stream=enfo, step=144h
stream=scda, step=90h
format=grib2
HH=00/12
stream=enfo/waef
type=ef, step=0h to 144h by 3h, 144h to 360h by 6h
type=ep, step=240h/360h
stream=oper, wave
type=fc, step=0h to 144h by 3h, 144h to 240h by 6h
HH=06/18
stream=enfo/waef
type=ef, step=0h to 144h by 3h
stream= scda /scwv
type=fc, step=0h to 90h by 3h
HH=00
stream=mmsf, type=fc, u=m, step=1m to 7m |
Accessing this dataset
7m |
Access real-time open data with Python package ecmwf-opendata
A Python package called ecmwf-opendata is available from PyPi that greatly facilitates the access to this dataset. In addition, a series of Jupyter Notebooks have been developed to demonstrate the use of this package.
Examples of how to access real-time open data with wget or curl
In the following examples, [ROOT]
should be replaced by one of the locations specified above.
Although all of the examples provided here use wget, curl can similarly be used to download the products
Currently, these data are available from two different locations:
- ECMWF, with
ROOT
set to https://data.ecmwf.int/forecasts - Microsoft's Azure, with
ROOT
set to "https://ai4edataeuwest.blob.core.windows.net/ecmwf" - Amazon's AWS, with ROOT set to "https://ecmwf-forecasts.s3.eu-central-1.amazonaws.com"
You can use the ECMWF link to browse the list of files.
Panel | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Examples using wget for products based on the Atmospheric Model high-resolution (HRES) forecastsIn the following examples, Although all of the examples provided here use wget, curl can similarly be used to download the products. HRES direct model output
HRES Tropical Cyclone track products
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Examples using wget for products based on the Wave Model high-resolution (HRES-WAM) forecastsHRES-WAM direct model output
|
Panel | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||
Examples using wget for products based on the Atmospheric Model ensemble (ENS) forecastsENS direct model output products
ENS Tropical Cyclone track products
ENS Probability productsFor the probability products from the Atmospheric model ensemble (ENS) forecast at all times 00, 06, 12 and 18 UTC, stream=enfo and type=ep should be used. Products are available at time=00 and time=12 only.
The steps available are 0h to 144h by 3h and 150h to 360h by 6h. The file format is grib2.
|
Panel | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
Examples using wget for products based on the Wave Model ensemble (ENS-WAM) forecasts
ENS-WAM Probability productsFor the probability products from the wave model ensemble (ENS) forecast at all times 00, 06, 12 and 18 UTC, stream=waef and type=ep should be used. Products are available at time=00 and time=12 only.
The steps available are 0h to 144h by 3h and 150h to 360h by 6. The file format is grib2.
|
Panel | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
All of the examples above download a single file containing all of the parameters for that dataset at the specific forecast step or steps. It is also possible to download of a single field using the HTTP Byte-Range request feature.
|
Anchor IndexFiles IndexFiles
Index files
IndexFiles | |
IndexFiles |
Each GRIB file is associated with a corresponding index file, accessible by substituting the '.grib2'
extension with '.index'
in the URL. Index files are text files where each line is a JSON record (JSON details here). Each record represents a GRIB field in the corresponding GRIB file, described using the MARS query language, for example:
No Format |
---|
{"domain": "g", "date": "2022010420240301", "time": "1200", "expver": "0001", "class": "od", "type": "fc", "stream": "oper", "step": "6", "levelist": "1000", "levtype": "pl", "param": "q", "_offset": 3857250, "_length": 609046} |
In addition, the keys _offset
and _length
represent the byte offset and length of the corresponding field. This allows the download of a single field using the HTTP Byte-Range request. An example is provided in Download a single field with wget above.
Differences between MARS language and file naming convention
There are some minor differences between the normal MARS request language and the open data file naming.
These are summarised in the table for information.
MARS | File names | ||||
Stream | Type | Step | Stream | Type | Step |
oper/wave | fc | nnn | oper/wave | fc | nnn |
enfo/waef | cf | nnn | enfo/waef | ef | nnn |
enfo/waef | pf | nnn | enfo/waef | ef | nnn |
enfo/waef | em | nnn | enfo/waef | ep | 240 if nnn <= 240 else 360 |
enfo/waef | es | nnn | enfo/waef | ep | 240 if nnn <= 240 else 360 |
enfo/waef | ep | nnn | enfo/waef | ep | 240 if nnn <= 240 else 360 |
msmm | fcmean/em | nnn | mmsf | fc | nnn |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Support level forthis datasetthese datasetsBoth datasets are This data is provided as a 'self-serve' dataset - documentation is provided, but no support service. However, if the data seems broken or corrupt, please report it via our support portal and we will respond during normal office hours.
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|