Skip to main content

ECMWF Software EnginE Maturity Level Licence Latest Release

Quick Start • Installation • Documentation

ecmwf-datastores-client

ECMWF Data Stores Service (DSS) API Python client.

[!IMPORTANT] This software is Graduated and subject to ECMWF's guidelines on Software Maturity.

Technical documentation: https://ecmwf.github.io/ecmwf-datastores-client/

Installation

Install with conda:

$ conda install -c conda-forge ecmwf-datastores-client

Install with pip:

$ pip install ecmwf-datastores-client

Configuration

The Client requires the url to the API root and a valid API key. These can be provided in three ways, in order of precedence:

  1. As keyword arguments when instantiating the Client.
  2. Via the ECMWF_DATASTORES_URL and ECMWF_DATASTORES_KEY environment variables.
  3. From a configuration file, which must be located at ~/.ecmwfdatastoresrc or at the path specified by the ECMWF_DATASTORES_RC_FILE environment variable.
$ cat $HOME/.ecmwfdatastoresrc
url: https://cds.climate.copernicus.eu/api
key: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Quick Start

Configure the logging level to display INFO messages:

>>> import logging
>>> logging.basicConfig(level="INFO")

[!NOTE] All Python code examples in this README are automatically tested as part of the unit test suite.

Instantiate the API client and optionally verify authentication:

>>> from ecmwf.datastores import Client
>>> client = Client()
>>> client.check_authentication()  # optional check
{...}

Retrieve data:

>>> collection_id = "reanalysis-era5-pressure-levels"
>>> request = {
...     "product_type": ["reanalysis"],
...     "variable": ["temperature"],
...     "year": ["2022"],
...     "month": ["01"],
...     "day": ["01"],
...     "time": ["00:00"],
...     "pressure_level": ["1000"],
...     "data_format": "grib",
...     "download_format": "unarchived",
... }

>>> client.retrieve(collection_id, request, target="target_1.grib")  # blocks
'target_1.grib'

Alternative methods to retrieve data:

>>> remote = client.submit(collection_id, request)  # doesn't block
>>> remote
Remote(...)
>>> remote.download("target_2.grib")  # blocks
'target_2.grib'

>>> results = client.submit_and_wait_on_results(collection_id, request)  # blocks
>>> results
Results(...)
>>> results.download("target_3.grib")
'target_3.grib'

>>> client.download_results(remote.request_id, "target_4.grib")  # blocks
'target_4.grib'

List all collection IDs sorted by last update:

>>> collections = client.get_collections(sortby="update")

>>> collection_ids = []
>>> while collections is not None:  # Loop over pages
...     collection_ids.extend(collections.collection_ids)
...     collections = collections.next  # Move to the next page
...

>>> collection_ids
[...]
>>> collection_id in collection_ids
True

Explore a collection:

>>> collection = client.get_collection(collection_id)

>>> collection.id == collection_id
True
>>> collection.title
'...'
>>> collection.description
'...'

>>> collection.published_at
datetime.datetime(...)
>>> collection.updated_at
datetime.datetime(...)

>>> collection.begin_datetime
datetime.datetime(...)
>>> collection.end_datetime
datetime.datetime(...)
>>> collection.bbox
(...)

>>> collection.submit(request)
Remote(...)

>>> collection.apply_constraints(request)
{...}

Interact with results:

>>> results = client.get_results(remote.request_id)

>>> results.content_length > 0
True
>>> results.content_type
'application/x-grib'
>>> results.location
'...'

>>> results.download("target_5.grib")
'target_5.grib'

List all successful jobs, sorted by newest first:

>>> jobs = client.get_jobs(sortby="-created", status="successful")

>>> request_ids = []
>>> while jobs is not None:  # Loop over pages
...     request_ids.extend(jobs.request_ids)
...     jobs = jobs.next  # Move to the next page
...

>>> request_ids
[...]
>>> remote.request_id in request_ids
True

Interact with a previously submitted job:

>>> remote = client.get_remote(remote.request_id)

>>> remote.collection_id == collection_id
True
>>> remote.request
{...}

>>> remote.status
'successful'
>>> remote.results_ready
True

>>> remote.created_at  # See also started_at, finished_at, updated_at
datetime.datetime(...)

>>> remote.download("target_6.grib")
'target_6.grib'

>>> remote.get_receipt()
{...}

>>> remote.get_results()
Results(...)

>>> remote.delete()
{...}

Apply constraints and find the number of available days in a given month:

>>> month = {"year": "2000", "month": "02"}
>>> constrained_request = client.apply_constraints(collection_id, month)

>>> len(constrained_request["day"])
29

Developer Workflow

1. Set Up the Environment

Configure your virtual environment and pre-commit hooks:

make install

[!NOTE] This project uses uv for dependency management. Commit the generated uv.lock file to version control.

2. Run Quality Assurance

Check formatting, linting, and lockfile consistency:

make qa

3. Commit and Push

Save and push any automatically formatted changes:

git add .
git commit -m "format codebase and sync lockfile"
git push origin HEAD

The CI/CD pipeline triggers on pull requests, merges to main/upstream, and new releases.

Using the Makefile

All development tasks are exposed as self-documenting targets in the Makefile. To see a complete list of available targets and their descriptions, run:

make help

This displays all available utility commands, including:

  • Environment setup: make install
  • Quality assurance: make qa
  • Unit tests: make unit-tests
  • Type checking: make type-check

To run the full set of quality checks, tests, and build steps in a single command, use:

make all

License

Copyright 2022, European Union.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Metadata

Release files for ecmwf-datastores-client 0.5.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ecmwf-datastores-client 0.5.3
File Size Uploaded
ecmwf_datastores_client-0.5.3.tar.gz 138.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ecmwf-datastores-client 0.5.3
File Interpreter ABI Platform
ecmwf_datastores_client-0.5.3-py3-none-any.whl Python 3 none any Details

Total release size: 164.5 kB

Release files / ecmwf_datastores_client-0.5.3.tar.gz

Download URL ecmwf_datastores_client-0.5.3.tar.gz
Size 138.4 kB
Tags Source
SHA-256 checksum
How to use checksums
15bd614a138c88fc8f6556aefdb4f2e3a5107ad1fc8b7ba18fab06dd69e3ec52
BLAKE2b-256 checksum
How to use checksums
32fc5d5175b3e8ad38a4839e2dc0ed6b607f7eddc6aac6a835379213fc6129c2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.

Transparency log

Release files / ecmwf_datastores_client-0.5.3-py3-none-any.whl

Download URL ecmwf_datastores_client-0.5.3-py3-none-any.whl
Size 26.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c840fdfd5ddfac07ba4f536b4b79c870096371d3f3e33acf74a8f791c64497dd
BLAKE2b-256 checksum
How to use checksums
d534b1e57d5e2c4095c6e10db834c6fa48c17682d4395c01b5557d42f9b3c3fd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.3 This release

2 release files

0.5.2

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page