s1bursts makes Sentinel-1 synthetic aperture radar (SAR) data easy to use from Python. It searches and downloads the data from the Copernicus Data Space Ecosystem (CDSE), processes it with ESA SNAP into backscatter and coherence, and composites them on the MGRS grid with local resolution weighting.
Features
- Search the CDSE catalog by area, time window, polarization, orbit and more
- Download single bursts, with automatic fallback between CDSE's burst service and its S3 storage
- Process to terrain-corrected backscatter and interferometric coherence, with SNAP processing graphs built from Python arguments
- Composite many acquisitions onto the 10 km MGRS grid with local resolution weighting, which favors the acquisitions with the highest spatial resolution at each pixel
- Store everything on local disk or S3
Installation
pip install s1bursts
Processing needs ESA SNAP 13 or 14, and downloading a free CDSE account. The installation guide covers both.
Quick start
With your CDSE credentials in the environment, download and process two acquisitions of one burst over the Aletsch glacier, 12 days apart:
from s1bursts import BurstCatalog, BurstProcessor, FileManager, SearchQuery, TimeRange
fm = FileManager("data/quickstart")
catalog = BurstCatalog(fm)
bursts = catalog.search(
SearchQuery(
time_range=TimeRange("2022-08-01", "2022-08-13"),
burst_id=30346,
sub_swath="IW1",
polarization="VV",
)
)
catalog.download(bursts).raise_on_failure()
# "auto" geocodes each burst in its own UTM zone, here EPSG:32632.
processor = BurstProcessor(fm)
rtc = processor.create_backscatter(bursts, crs="auto").raise_on_failure()
pairs = bursts.find_pairs(baseline=12)
coherence = processor.create_coherences(pairs, crs="auto").raise_on_failure()
Documentation
The documentation has a user guide, tutorials on real data, and the API reference.
Development
uv sync # set up the environment
uv run pytest # offline unit tests
uv run pytest -m integration # network and SNAP tests (needs credentials and SNAP)
uv run ruff format && uv run ruff check --fix
uv run pyrefly check
See the contributing guide for the integration tests and how to build the documentation.
Citation
If you use s1bursts in your research, please cite it with its DOI,
10.5281/zenodo.23918246, which always
points to the latest release. Zenodo lists a DOI for each version, and
CITATION.cff
holds the citation metadata.
License
Metadata
Release files for s1bursts 0.9.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 | Provenance | Actions |
|---|---|---|---|---|
| s1bursts-0.9.0.tar.gz | 342.2 kB | With provenance | Details for s1bursts-0.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| s1bursts-0.9.0-py3-none-any.whl | Python 3 | none | any | Details for s1bursts-0.9.0-py3-none-any.whl |
Total release size: 489.0 kB
Release files / s1bursts-0.9.0.tar.gz
| Download URL | s1bursts-0.9.0.tar.gz |
|---|---|
| Size | 342.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7063ee351c27c4adfcada59526e64fbf089d7335822ceac78b03df9182fb7a44
|
|
BLAKE2b-256 checksum How to use checksums |
d0ddfe95307753586d91ea5bcf0e96119ffe931ce8df373b22c4346dc233cdb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / s1bursts-0.9.0-py3-none-any.whl
| Download URL | s1bursts-0.9.0-py3-none-any.whl |
|---|---|
| Size | 146.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2ed52a10482e6d6c2076a661529cd9a72e814860eeb54ad3ab7d90c7e0a0754
|
|
BLAKE2b-256 checksum How to use checksums |
58b4ec13a72dd13a4f3b9714205d18e11f6ccfd3be04c197303023bf161939fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logSecurity for s1bursts 0.9.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for s1bursts-0.9.0.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 Nov 7, 2026.
Transparency logA 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.