Cirrus
Cirrus is a STAC-based geospatial processing pipeline platform, implemented using a scalable architecture deployed on AWS. Cirrus provides the generic infrastructure for processing, allowing a user to focus on implementing the specific processing logic for their data.
As input, Cirrus takes a STAC ItemCollection along with a process definition block.
That input is called a "payload" and follows the Payload model defined in the
stac-task package, with slightly tighter requirements on the presence and content
of the process definition block.
An input payload is run through a workflow that generates one or more output STAC Items. These output Items are added to the Cirrus static STAC catalog in S3, and are also broadcast via an SNS topic. Subscriptions to that topic can trigger additional workflows or external processes, such as indexing into a STAC API catalog (e.g., stac-server).
Cirrus workflows range from the simple publishing of unmodified input items to the complex transformation of input Items and generation of wholly-new output Items. The current state of a payload in a processing pipeline is tracked in a state database to prevent duplicate processing and allow for a user to follow the state of any input payload through the pipeline.
As shown in this high-level overview of Cirrus, users input data to Cirrus through the use of feeders. Feeders are simply programs that get/generate some type of STAC metadata, combine it with processing parameters, and pass it into Cirrus as a payload.
Cirrus Development
If developing new code for cirrus-geo, checkout the Contributing Guide.
Documentation
Documentation for deploying, using, and customizing Cirrus is contained within the docs directory:
- Learn how to get started
- Understand the architecture of Cirrus and key concepts
- Use Cirrus to process input data and publish resulting STAC Items
- Cirrus features several component types that each represent a specific role within the Cirrus architecture
About
Cirrus is an Open-Source pipeline for processing geospatial data in AWS. Cirrus was developed by Element 84 originally under a NASA ACCESS project called Community Tools for Analysis of NASA Earth Observation System Data in the Cloud.
2 maintainers
Metadata
2 maintainers
Release files for cirrus-geo 2.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 | |
|---|---|---|---|
| cirrus_geo-2.0.0.tar.gz | 528.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cirrus_geo-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 599.5 kB
Release files / cirrus_geo-2.0.0.tar.gz
| Download URL | cirrus_geo-2.0.0.tar.gz |
|---|---|
| Size | 528.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b41955a7ac4403d85739dbfa52f4b985adeedc672955ba2cb526209ceddecedd
|
|
BLAKE2b-256 checksum How to use checksums |
8435941e6c6260bd514155926b1bef798dc8be3719605950852db997daa33e7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 22, 2026.
Transparency logRelease files / cirrus_geo-2.0.0-py3-none-any.whl
| Download URL | cirrus_geo-2.0.0-py3-none-any.whl |
|---|---|
| Size | 71.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bde4cd20e0d05406af2494eccf2aa5ef0a397ed47a045ed4d497830582da02f3
|
|
BLAKE2b-256 checksum How to use checksums |
2fa866a01acf8e6ddcbf321ca858e6ee7eb9ab663ad815cb063c5bc069b73999
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 22, 2026.
Transparency log
