SAR L1 Product Format plugins collection for SCT (SAR Calibration Toolbox).
This repository is a monorepo consisting of several standalone Python packages, each dedicated to reading and interpreting Level 1 product formats from a specific SAR sensor/mission. Plugins integrate with SCT via a unified protocol, enabling all analyses regardless of the input format.
| Package | PyPI | CI | Description |
|---|---|---|---|
| sct-sentinel1-reader |  |
 |
Sentinel-1 (A/B/C/D) Level 1 products |
| sct-novasar1-reader |  |
 |
NovaSAR-1 Level 1 products |
| sct-saocom-reader |  |
 |
Saocom Level 1 products |
| sct-iceye-reader |  |
 |
ICEYE Level 1 products |
| sct-radarsat2-reader |  |
 |
RADARSAT-2 Level 1 products |
| sct-eos04-reader |  |
 |
EOS-04 Level 1 products |
| sct-cosmo-reader |  |
 |
COSMO-SkyMed Level 1 products |
| sct-asar-reader |
 |
 |
ENVISAT/ERS ASAR Level 1 products |
| sct-aresys-reader |  |
 |
Aresys internal Level 1 product format |
| sct-strix-reader |  |
 |
Synspective StriX Level 1 products |
| sct-terrasarx-reader |  |
 |
TerraSAR-X Level 1 products |
| sct-biomass-reader | TBD | TBD | Biomass Level 1 products |
Full documentation is available at https://aresys-srl.github.io/sct_plugins.
Each plugin is a standalone Python package available on PyPI and can be installed
using pip:
pip install <package-name>All plugins in this repository are licensed under the MIT License, except for the following:
| Package | License |
|---|---|
| sct-asar-reader | GNU General Public License v3.0 or later (GPL-3.0-or-later) |
Warning
Using the sct-asar-reader plugin in a project may require the combined work to comply with the terms of
the GPL-3.0 license. Please review the GPL-3.0 license before integrating this package into your project.
Contributions are welcome! If you encounter a bug, have a feature request, or want to contribute code:
- Report bugs & request features: open an issue on GitHub. Include a clear description, steps to reproduce, and your environment details.
- Submit changes: fork the repository, create a feature branch, and open a pull request. Ensure your code passes the existing linting and test suite.
- Questions: use GitHub Discussions for general questions and discussions.
Copyright © 2026-present Aresys S.r.l. info@aresys.it