nnja-ai: multi-modal, AI-ready weather observations
This is the companion Python SDK to the Brightband AI-ready reprocessing of the NOAA NASA Joint Archive (NNJA). It is meant to serve as a helpful interface between a user and the underlying NNJA datasets (which currently consist of parquet files on GCS).
The V1 release of the NNJA-AI dataset and SDK represents a major increment in availability of NNJA data, with ~50 TiB of observations made available in parquet form along with a data catalog and code examples in this SDK.
Background
The NNJA archive project is a curated archive of Earth system data from 1979 to present. This data represents a rich trove of observational data for use in AI weather modelling, however the archival format in which the data is originally available (BUFR) is cumbersome to work with. In partnership with NOAA, Brightband is processing that data to make it more accessible to the community.
Data
NNJA datasets are organized by sensor/source (e.g. all-sky radiances from the GOES ABI). The list of all NNJA datasets can be found on the NNJA project page, while the subset that is currently found in the NNJA-AI archive can be found here or by exploring the data catalog (this will be be expanding rapidly).
Getting Started
To install this package directly from the GitHub repository, you can use the following pip command:
pip install git+https://github.com/brightbandtech/nnja-ai.git
You can find an example notebook here showing the basics of opening the data catalog, finding a dataset, subsetting, and finally loading the data to pandas. Though to get started, you can open the data catalog like so:
from nnja_ai import DataCatalog
catalog = DataCatalog()
print("datasets in catalog:", catalog.list_datasets())
datasets in catalog:
['amsua-1bamua-NC021023',
'atms-atms-NC021203',
'mhs-1bmhs-NC021027',
'cris-crisf4-NC021206',
...]
How to Cite
If you use this library or the Brightband reprocessed NNJA data, please cite it using the following DOI:
Additionally, please follow the citation guidance on the NNJA project page.
The NNJA-AI data is distributed with the same license as the original NNJA data, CC BY 4.0.
Metadata
Release files for nnja-ai 1.0.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 | |
|---|---|---|---|
| nnja_ai-1.0.0.tar.gz | 18.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nnja_ai-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.4 kB
Release files / nnja_ai-1.0.0.tar.gz
| Download URL | nnja_ai-1.0.0.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e64006c0a9046c04cffebef3e8d154fa0c31f574d72c50bb7c3c1d7ac691dcc5
|
|
BLAKE2b-256 checksum How to use checksums |
07b6cd4275ff9519a0337cf58c4e721f199351aaff6fd6b78ec1a5b7815071ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 5, 2025.
Transparency logRelease files / nnja_ai-1.0.0-py3-none-any.whl
| Download URL | nnja_ai-1.0.0-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71d8858b919f60fa0e3810c6ab8e1431669e23f9c709d2d5907e53c1b2bbb59a
|
|
BLAKE2b-256 checksum How to use checksums |
e0022770f013fe79b3244037ac8757d218c03c25ee1b89a0e2cd217974b7eb9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 5, 2025.
Transparency log