Skip to main content

SAR Calibration Toolbox (SCT)

License: MIT Python 3.11+ SCT CI

SAR Calibration Toolbox (SCT) is the official Aresys Python toolbox for SAR quality assessment and data processing. This software provides several features to perform quality analysis of SAR L1 products (both SLC and GRD).

SCT is based on PERSEO (docs), the Aresys modular Python framework for SAR product handling, processing, and analysis. It also integrates plugins using the stevedore library.

SCT provides a comprehensive set of analyses for SAR product quality assessment:

  • Point Target Analysis — IRF metrics, RCS estimation, localization errors
  • Radiometric Analysis — NESZ, Rain Forest, Average Elevation Profiles, Scalloping
  • Interferometric Coherence Analysis — interferometric coherence intensity and histograms
  • Spectral Analysis — point & distributed target spectral content in frequency domain
  • Elevation Notch Analysis — antenna pointing estimation
  • Target Ambiguity Ratio (PTAR/DTAR) — point target and distributed ambiguity ratio computation

Supported input products include:

  • Sentinel-1 (A/B/C/D) SAFE format
  • ICEYE
  • NovaSAR-1
  • Radarsat-2
  • Envisat/ERS
  • SAOCOM
  • COSMO SkyMed
  • EOS-04
  • STRIX

and more through a plugin-based architecture.

Installation

This package is available on PyPI and can be installed with pip:

pip install sct[recommended]

[!IMPORTANT] After installing SCT, install the plugin corresponding to the product format you want to process. The base SCT package does not include any format reader plugins by default.

Documentation

Related Repositories

Repository Description Documentation
aresys-srl/sct_plugins SCT input product format plugins docs
aresys-srl/sct_plugins_analyses SCT analyses plugins docs
aresys-srl/perseo Python Ecosystem for Remote Sensing & Earth Observation docs

Contributing

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.

License

This project is licensed under the MIT License.

Copyright © 2026-present Aresys S.r.L. info@aresys.it

Release files for sct 3.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sct 3.2.1
File Size Uploaded
sct-3.2.1.tar.gz 1.9 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for sct 3.2.1
File Interpreter ABI Platform
sct-3.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 1.9 MB

Release files / sct-3.2.1.tar.gz

Download URL sct-3.2.1.tar.gz
Size 1.9 MB
Tags Source
SHA-256 checksum
How to use checksums
aab47d6c67e97d5a8e77fb40a8875a4163301ace9605ddf427ab0b98dce1fa98
BLAKE2b-256 checksum
How to use checksums
bebe964d0c240025fee0e54afdf9e8497a1c3e2213bf41aba38e02b2013dda9b
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 Sep 1, 2026.

Transparency log

Release files / sct-3.2.1-py3-none-any.whl

Download URL sct-3.2.1-py3-none-any.whl
Size 43.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
79f63c8522263b1a106b490c0319cc022d78608a7addef64e436534c89785372
BLAKE2b-256 checksum
How to use checksums
883d65e244ba80d63a3be6398a9e98d718bcbecfab21e582af6e14701ca8c2ac
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 Sep 1, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

3.2.1 This release

2 release files

3.2.0

2 release files

3.1.0

2 release files

3.0.1

2 release files

3.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page