H2MARE - Geospatial Processing for Climate and Ocean Data
A Python pipeline for downloading and preprocessing multi-source oceanographic and atmospheric data into analysis-ready formats. H2MARE streamlines the acquisition and harmonization of data from major climate and ocean observation services, optimized for large-scale spatiotemporal analysis.
Features
- Multi-source data integration: Download and process data from CMEMS, AVISO, and ERA5.
- Format conversion: Automated conversion from NetCDF/GRIB to optimized Zarr and Parquet formats.
- Data compilation: Regrid and interpolate multi-resolution datasets to a common grid.
- Point and geometry extraction: Extract time series for specific locations or spatial features.
Data Sources
H2MARE supports the following data providers. API keys and authentication are required for each.
- CMEMS — Copernicus Marine Service: satellite and in-situ ocean observations
- AVISO — Archiving, Validation and Interpretation of Satellite Oceanographic data
- CDS-ERA5 — ERA5 hourly atmospheric reanalysis (1940–present)
Refer to each provider's documentation for authentication setup before use.
Installation
Prerequisites
- Python >= 3.11
- uv — fast Python package and project manager
Install from PyPI
pip install h2mare
# or
uv add h2mare
Install from source
git clone https://github.com/h2ugoparra/h2mare.git
cd h2mare
uv sync
Configuration
H2MARE requires two configuration files in your working directory before first use.
1. config.yaml
Defines variables, dataset IDs, bounding boxes, and processing parameters.
Start from config.example.yaml — copy it to config.yaml and edit. It holds four entries chosen to cover the shapes you are likely to need: a plain 2-D daily variable, a 3-D one with depth levels, an hourly packed ERA5 one, and the h2ds entry the compile step writes to.
The repository's own config.yaml configures 16 variables and is a reference, not a starting point — useful for seeing how a particular source is wired up, too heavy to copy wholesale. Every field is documented in the configuration reference.
2. .env
# Path to external or large-capacity storage for processed Zarr files
STORE_ROOT=/path/to/your/storage
# AVISO credentials (required for FSLE, Eddies)
AVISO_USERNAME=your_username
AVISO_PASSWORD=your_password
AVISO_FTP_SERVER=ftp-access.aviso.altimetry.fr
AVISO credentials cross the network in cleartext. The AVISO server offers plain FTP only — it refuses
AUTH TLS("500 AUTH not understood", checked 2026-09-01) — so there is no FTPS option to enable. Use a password unique to AVISO, and prefer running downloads from a trusted network.
CMEMS credentials are configured via the copernicusmarine client. ERA5 / CDS credentials are configured via the cdsapi client. See the CDS documentation for setup.
Note: Both files must be present in the directory where you run
h2mare. You can also set theH2MARE_ROOTenvironment variable to point to a different directory containing them.
Quick Start
# Download and process a single variable for a specific date range
uv run h2mare run -v sst --start-date 2021-01-01 --end-date 2021-12-31
# Multiple variables at once
uv run h2mare run -v seapodym -v mld -v o2 -v chl
# Infer missing dates from the existing store and download what's new
uv run h2mare run -v sst
# Download only (skip Zarr conversion)
uv run h2mare run -v sst --no-convert
# Validate configuration without downloading
uv run h2mare run -v sst --dry-run
# Process all configured variables
uv run h2mare run
# Check the stores for days that went missing without failing anything
uv run h2mare audit --all
Coverage elsewhere in the pipeline is a frontier — a start date and an end date — so a year holding
January 1st and December 31st reports itself complete however much is missing in between. audit
reads the time axes and reports the holes. See the CLI docs
for the value check and for known_gaps, which excludes days the provider never published.
Development
# Run the full test suite
uv run pytest tests/
# Run a single test file
uv run pytest tests/test_zarr_catalog.py -v
# Lint and format
uv run ruff check h2mare/
uv run ruff format h2mare/
Built with
| Library | Role |
|---|---|
| xarray | N-dimensional labelled arrays and NetCDF/Zarr I/O |
| zarr | Chunked, compressed array storage |
| dask | Parallel and out-of-core computation |
| polars | Fast DataFrame engine for Parquet I/O |
| duckdb | In-process SQL for Parquet overlap resolution and scanning |
| geopandas | Geometry-based spatial extraction |
| plotly | Interactive time-series and spatial visualizations |
| copernicusmarine | CMEMS dataset access |
| cdsapi | ERA5 / CDS dataset access |
Contributing
Contributions are welcome! Please feel free to submit issues or pull requests on GitHub.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
This project was developed under the framework of COSTA project. This project relies on data from Copernicus Marine Service, AVISO, Copernicus Climate Data Store, and NOAA NCEI. We gratefully acknowledge these organizations for providing open access to their datasets.
Metadata
Release files for h2mare 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| h2mare-0.8.1.tar.gz | 427.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| h2mare-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 707.3 kB
Release files / h2mare-0.8.1.tar.gz
| Download URL | h2mare-0.8.1.tar.gz |
|---|---|
| Size | 427.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93a7e983a6cb1153533fbabba4649b60fa970842874b9decd1cfc596ca86b156
|
|
BLAKE2b-256 checksum How to use checksums |
055811964bda6f49f7fa955360f4f37e0ba9d4c6ac3e3f589c23737dc1f5058b
|
| 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 14, 2026.
Transparency logRelease files / h2mare-0.8.1-py3-none-any.whl
| Download URL | h2mare-0.8.1-py3-none-any.whl |
|---|---|
| Size | 279.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32f847835e5cbbb9ae0e5a1a383e5102695a6b02b1dd1bae810541cc3fca9e3f
|
|
BLAKE2b-256 checksum How to use checksums |
c917903fa0f01131c39c001bb8c0b60ebf55733f1cbcdadf0f4c3363856e4130
|
| 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 14, 2026.
Transparency log