Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Recommendations for Safe Lossy Compression of weather and climate data

image image image image image image

What lossy compression is safe when using lossy compression on weather and climate data?

This repository contains community-provided recommendations that are automatically compiled into one machine-readable recommendations.yaml file. These recommendations can then be used by external tools to automatically recommend appropriate safety requirements for compressing various weather and climate data.

This repository also provides the compression-recommendations Python package for loading these recommendations and inspecting them in the strongly typed Recommendations data structure.

Furthermore, we provide the following integrations:

  • compression-requirement-checks checks whether safety requirements are upheld by a lossy-decompressed reconstruction of the original data.
  • compression-requirement-safeguards translates safety requirements into compression safeguards that can be wrapped around any compressor to guarantee that the requirements are fulfilled.

That is up to you, the community, to decide!

  • You can add comments to any recommendation to elaborate or discuss different requirements.
  • You can propose edits to any recommendation, which we accept once a new consensus has been reached.
  • You can create new recommendations for new variables or to specialise existing requirements for specific cases.
  • You can merge multiple recommendations to generalise them.
  • You can propose new filters to select which recommendations should apply, or new kinds of requirements.

Glossary

Compression : Reducing the number of bits needed to store some data.

Lossy Compression : Compression that may only produce an approximation of the original data during decompression.

Filter : Criteria, or a composition of multiple criteria, that select which requirements should apply.

Safety Requirement : A property, e.g. an error bound, or a composition of multiple properties, that the lossy-compressed data must fulfil with respect to the original uncompressed data.

Citation

Please refer to the CITATION.cff file and refer to https://citation-file-format.github.io to extract the citation in a format of your choice.

License

Licensed under the Mozilla Public License, Version 2.0 (LICENSE or https://www.mozilla.org/en-US/MPL/2.0/).

Funding

The outline for the recommendations have been developed as part of ESiWACE3, the third phase of the Centre of Excellence in Simulation of Weather and Climate in Europe.

Funded by the European Union. This work has received funding from the European High Performance Computing Joint Undertaking (JU) under grant agreement No 101093054.

Metadata

Release files for compression-requirement-checks 0.1.0a2

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

Source distribution (sdist)

Source distribution for compression-requirement-checks 0.1.0a2
File Size Uploaded Provenance Actions
compression_requirement_checks-0.1.0a2.tar.gz 14.5 kB With provenance Details for compression_requirement_checks-0.1.0a2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for compression-requirement-checks 0.1.0a2
File Interpreter ABI Platform Actions
compression_requirement_checks-0.1.0a2-py3-none-any.whl Python 3 none any Details for compression_requirement_checks-0.1.0a2-py3-none-any.whl

Total release size: 34.7 kB

Release files / compression_requirement_checks-0.1.0a2.tar.gz

Download URL compression_requirement_checks-0.1.0a2.tar.gz
Size 14.5 kB
Tags Source
SHA-256 checksum
How to use checksums
72d33922126ec5726f94cfaf161f1b9037136347ee10a279fbcbe502a4235419
BLAKE2b-256 checksum
How to use checksums
2970ea86c75c3b29e80424f8344fa52311293447145298dd5e24fec21158e223
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 17, 2026.

Transparency log

Release files / compression_requirement_checks-0.1.0a2-py3-none-any.whl

Download URL compression_requirement_checks-0.1.0a2-py3-none-any.whl
Size 20.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c01fb4f3e14a63f067a3fd2352afaa78a61f36040819c71489b9dab31e532999
BLAKE2b-256 checksum
How to use checksums
4d0fced9ea184fbbf86c8737e1f9c7252efe93935a5f439dd130ffce4583e7c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 17, 2026.

Transparency log

Security for compression-requirement-checks 0.1.0a2

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for compression_requirement_checks-0.1.0a2.tar.gz

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 Sep 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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