Skip to article frontmatterSkip to article content

IFS (Integrated Forecasting System) Data


In our tutorials we will use the subset of free and open IFS parameters. The open data are a product of the high-resolution and ensemble as well as seasonal forecast models.

Medium-range and long-range forecast models

The medium-range forecasts consist of a high-resolution (HRES) forecast and the ensemble (ENS) which provide the information about the evolution of weather up to 15 days ahead. HRES is a single forecast which describes one possible evolution of the weather out to 10 days ahead. ENS is a probabilistic forecast system of 51 forecasts. One is a control forecast, the other 50 forecasts are produced with slightly altered initial conditions and model physics. ENS indicates the range of possible weather conditions out to 15 days ahead, including the probability of occurrence of particular weather events.

The long-range (seasonal) forecast provide information about the Earth system components (atmosphere, ocean, land) up to 7 months into the future.

These products are produced at 0.25 degrees resolution in GRIB edition 2 format and are available 1 hour after the real-time dissemination schedule. The files are named as ROOT/yyyymmdd/HHz/model/resol/stream/yyyymmdd HH0000-step U-stream-type.format.

Table 1:File-naming convention of the ECMWF IFS model outputs.

File-naming conventionValues
ROOTURL of a site hosting the open data
yyyymmddreference date
HH00, 06, 12, or 18
modelIFS
resol0p25
streamoper, enfo, waef, wave, scda, scwv, or mmsf
stepforecast time step
Uunit of the time step (h or m; m only for mmsf)
typefc, ef, ep, or tf
formatgrib2 or bufr

The valid combinations are in detail described here.

Index files

Each GRIB file has its corresponding index file which can be accessed by substituting the .grib2 extension with .index in the URL. Each line in an index file represents a GRIB field in the corresponding GRIB file. It is described using the MARS query language. The keys _offset and _length represent the byte offset and length of the corresponding field respectively. This allows us to download a single field from the GRIB file using HTTP byte-range requests, see Retrieve Data.

{"domain": "g", "date": "20250608", "time": "0000", "expver": "0001", "class": "od", "type": "fc", "stream": "oper", "step": "0", "levtype": "sfc", "param": "asn", "_offset": 0, "_length": 71895}