harmony-py
Harmony-Py is a Python library for integrating with NASA's Harmony Services.
Harmony-Py provides a Python alternative to directly using Harmony's OGC Coverage RESTful API and Harmony's OGC EDR RESTful API. It handles NASA Earthdata Login (EDL) authentication and optionally integrates with the CMR Python Wrapper by accepting collection results as a request parameter. It's convenient for scientists who wish to use Harmony from Jupyter notebooks as well as machine-to-machine communication with larger Python applications.
We welcome feedback on Harmony-Py via GitHub Issues
Documentation
View the full API documentation on ReadTheDocs →
Using Harmony Py
Prerequisites
- Python 3.10 through 3.14 (other versions are end of life or untested)
Installing
The library is available from PyPI and can be installed with pip:
$ pip install -U harmony-py
This will install harmony-py and its dependencies into your current Python environment. It's recommended that you install harmony-py into a virtual environment along with any other dependencies you may have.
Examples & Tutorials
Looking for examples of harmony-py in action? Check out these resources:
- Example Jupyter Notebooks - In this repository, see the
examples/directory for hands-on tutorials - TEMPO Atmospheric Data Tutorial - Learn how to access and analyze TEMPO data from NASA's ASDC using harmony-py
- Subsetting NASA Earthdata Using Harmony - Tutorial on requesting spatial and temporal subsets of ICESat-2 data using harmony-py
Running Examples & Developing on Harmony Py
Prerequisites
- Python 3.10 through 3.14, ideally installed via a virtual environment
Installing Development & Example Dependencies
-
Install dependencies:
$ make install -
Optionally register your local copy with pip:
$ pip install -e ./path/to/harmony_py
Running the Example Jupyter Notebooks
Jupyter notebooks in the examples subdirectory show how to use the Harmony Py library. Start up the Jupyter Lab notebook server and run these examples:
The Jupyter Lab server will start and open in your browser. Double-click on a notebook in the file-browser sidebar and run the notebook. Note that some notebooks may have cells which prompt for your EDL username and password. Be sure to use your UAT credentials since most of the example notebooks use the Harmony UAT environment.
$ make examples
Developing
Generating Documentation
Documentation on the Read The Docs site is generated automatically. It is generated by using sphinx with reStructuredText (.rst) and other files in the docs directory. To generate the docs locally and see what they look like:
$ make docs
You can then view the documentation in a web browser under ./docs/_build/html/index.html.
IMPORTANT: The documentation uses a notebook from the examples directory rendered as HTML. If you've modified that notebook (see Makefile for notebook that is currently rendered), you will need to run make docs locally. You will see a change to the docs/user/notebook.html file after doing so. This file should be committed to the git repo since it is used when the latest docs are pushed to the Read The Docs site (it can't currently be generated as part of the build).
Running the Linter & Unit Tests
Run the linter on the project source:
$ make lint
To automatically fix formatting issues found by the linter:
$ make format
Run unit tests and test coverage. This will display terminal output and generate an HTML coverage report in the htmlcov directory.
$ make test
For development, you may want to run the unit tests continuously as you update tests and the code-under-test:
$ make test-watch
Generating Request Parameters
The harmony.Request constructor can accept parameters that are defined in the Harmony OGC API schema. If this schema has been changed and the Request constructor needs to be updated, you may run the generator utility. This tool reads the Harmony schema and generates a partial constructor signature with docstrings:
$ python internal/genparams.py ${HARMONY_DIR}/services/harmony/app/schemas/ogc-api-coverages/1.0.0/ogc-api-coverages-v1.0.0.yml
Either set HARMONY_DIR or replace it with your Harmony project directory path. You may then write standard output to a file and then use it to update the harmony.Request constructor and code.
CI
Harmony-py uses GitHub Actions to run the Linter & Unit Tests. The test coverage output is saved as a build artifact.
Building and Releasing
New versions of Harmony-Py will be published to PyPi via a GitHub action whenever a draft release is marked as published https://github.com/nasa/harmony-py/releases.
4 maintainers
Metadata
4 maintainers
Release files for harmony-py 1.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| harmony_py-1.8.0.tar.gz | 770.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| harmony_py-1.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 811.3 kB
Release files / harmony_py-1.8.0.tar.gz
| Download URL | harmony_py-1.8.0.tar.gz |
|---|---|
| Size | 770.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7bcf2891afdca0fa14dbbbf3a5e0139a2cbc84348e575e706f25ffb61749564
|
|
BLAKE2b-256 checksum How to use checksums |
ad077809e06a1173aabd9598284116c66a4c55867a5077316b65b201a3d97182
|
| 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 Oct 6, 2026.
Transparency logRelease files / harmony_py-1.8.0-py3-none-any.whl
| Download URL | harmony_py-1.8.0-py3-none-any.whl |
|---|---|
| Size | 40.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3cd666cd25f6373d433030f8bed398fbbd296ada3663ff0458acb7bcf994497
|
|
BLAKE2b-256 checksum How to use checksums |
c1e3b1c5b0f12a86f186825c980f88b24f46eb9782cc160708283069fa38abcf
|
| 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 Oct 6, 2026.
Transparency log
