Reference · built on requestCommons signalWeather & climate

Copernicus Climate Data Store

ERA5 hourly reanalysis, monthly seasonal forecasts and CMIP6 projections from the Copernicus Climate Data Store, by API with a free token.

Request accessPricing ↗

About

The Climate Data Store (CDS) is the catalogue of the Copernicus Climate Change Service, run by ECMWF for the European Union. It holds reanalysis, seasonal forecasts, climate projections, satellite and in-situ observations, and climate indices. ERA5 gives hourly global weather back to 1940 on a 0.25 degree grid, updated daily and about 5 days behind real time. Each dataset carries its own licence, accepted once in the browser.

Through Fibric, an operator pulls the ERA5 hours a site lived through, or the month's seasonal outlook for its region, and sets them beside your own demand, energy or sales records. It proposes a plan adjustment you approve, with the retrieval request on file.

This is a reference listing. It documents what Fibric would read from Copernicus Climate Data Store and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • ERA5 hourly data on single levels from 1940 to present: 0.25 x 0.25 degree reanalysis, updated daily, about 5 days behind real time
  • ERA5T, the early release inside ERA5, which can differ from the final release published 2 to 3 months later
  • Seasonal forecast daily and subdaily data on single levels: multi-system forecasts at 1 x 1 degree, released monthly on the 6th and 10th
  • CMIP6 climate projections: monthly and daily model output for historical (1850 to 2014) and SSP (2015 to 2100) experiments as NetCDF4
  • Catalogue families: reanalysis, satellite observations, climate projections, seasonal forecasts, climate indices, in-situ observations, time-series
  • Job state on the Your Requests page while a retrieval is running; finished jobs drop off the list

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Weather-normalise site energy

    ERA5 gives the hourly 2 metre temperature and wind each site sat in. The operator sets consumption against those hours, ranks sites on a like-for-like basis, and proposes which ones to inspect first.

    With Site Benchmark, Peak Demand

  • Build the season with the seasonal outlook

    Seasonal forecasts arrive on the 6th and 10th of each month. The operator reads the outlook for your regions and proposes an adjustment to the season build before purchase orders go out.

    With Season Build, Demand Outlook

  • Explain a forecast miss with the weather that happened

    When sales or load diverge from plan, the operator pulls the ERA5 hours for that period and reports how much of the variance the weather accounts for, with the request it used.

    With Forecast Variance

Requirements

  • A CDS account registered with name, email, country and sector; the Personal Access Token shown on the profile page
  • The Terms of Use of each dataset accepted by hand at the bottom of its download form before the first API call
  • The dataset short name and request dictionary, copied from the Show API request code button on the download form
  • Python 3 with cdsapi 0.7.7 or later, or the ecmwf-datastores-client for asynchronous job submission
  • Storage for the GRIB or NetCDF file each retrieval writes to its target path
Authentication
A free CDS account and its Personal Access Token, written as url and key into $HOME/.cdsapirc or passed to the cdsapi Python client; one account per named person.

Limits

  • A retrieve is a queued job that ends in a file; there is no low-latency query for a single value
  • Each dataset caps the items per request and the retrieve size; an oversized request is refused with a limit message and must be split
  • ERA5 lags real time by about 5 days, so this is a climate archive, not a current-conditions feed
  • The REST API behind ecmwf-datastores-client is offered for advanced users and is not supported

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Copernicus Climate Data Store ↗

Questions and answers

Do I need a key for the CDS API?
Yes. Register for a free CDS account, one per person. The profile page shows a Personal Access Token. Put it and https://cds.climate.copernicus.eu/api in $HOME/.cdsapirc, then accept the dataset's Terms of Use at the bottom of its download form before the first request.
Is ERA5 current enough for today's conditions?
No. ERA5 is updated daily but runs about 5 days behind real time, and the early ERA5T release can be revised 2 to 3 months later. Seasonal forecasts arrive once a month. Pair this feed with a national service for what is happening now.
What does a request return?
A file. client.retrieve(dataset, request, target) submits a job, the CDS queues it, and GRIB or NetCDF is written to the target path when it finishes. Each dataset sets a maximum number of items per request; a larger one is rejected with a limit message and must be split.
Ask about Copernicus Climate Data Store

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Copernicus Climate Change Service (C3S), operated by ECMWF (cds.climate.copernicus.eu). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy