satchange
Multipurpose satellite change detection in pure Python. Map deforestation, mining, urbanisation, floods, burns, surface-water change and multi-epoch urban growth anywhere on Earth from free Sentinel-1/2 and Landsat data — via Google Earth Engine or Microsoft Planetary Computer (no account needed). Export georeferenced GeoTIFFs, quick-look PNGs, statistics, and print-ready A4 maps.
- 📖 Full hands-on tutorial (English & Bahasa Indonesia): https://firmanhadi21.github.io/rs-change-detection/
- 💻 Source, examples & case study: https://github.com/firmanhadi21/rs-change-detection
Install
Heavy dependencies are optional extras, so the install stays lean:
pip install 'satchange[gee]' # Google Earth Engine backend (free account)
pip install 'satchange[mpc,maps]' # Planetary Computer + maps (no account)
pip install 'satchange[all]' # everything
Quick start
# Deforestation around a coordinate, with a finished map
satchange -s deforestation --lat -3.333 --lon 122.25 --radius 6 --map
# Flood extent from Sentinel-1 SAR — no Earth Engine account needed
satchange -s flood --lat 27.2 --lon 68.3 \
--pre 2022-07-01:2022-07-25 --post 2022-08-20:2022-09-10 --backend mpc
# Urban growth timing across 2010/2015/2020 (Landsat 5/8/9)
satchange -s urban-trend --lat -6.30 --lon 107.15 --map
# List everything
satchange --list
Each run writes a self-contained output/<run-id>/ folder containing the PNG,
GeoTIFF, statistics JSON, metadata, and any maps.
Scenarios
| Scenario | Method | Sensor |
|---|---|---|
deforestation |
NDVI loss | Sentinel-2 |
urbanization |
Built-up gain — NDBI (default), UI, BU, IBI, or thermal NDISI/EBBI via --method |
Sentinel-2 / Landsat |
water |
NDWI change | Sentinel-2 |
burn |
dNBR severity | Sentinel-2 |
mining |
SIRAD radar temporal + NDVI loss | Sentinel-1 + S2 |
flood |
SAR water extent (event vs baseline) | Sentinel-1 |
urban-trend |
NDBI at 3 epochs → RGB growth-timing map | Landsat 5/8/9 |
coastline |
Sea boundary + shoreline change (erosion/accretion) + retreat rate m/yr | S1 / S2 / Landsat |
transit-access |
% population with access to public transport (SDG 11.2.1) | WorldPop + OSM |
island-heat |
SST + LST + wet-bulb (humid heat) trends for small islands | OISST / Landsat / ERA5 |
urban-heat |
Urban heat island (SUHII) + hot-spot map + decadal trend | GHSL + Landsat + MODIS |
Two backends
--backend |
Data source | Account? |
|---|---|---|
gee (default) |
Google Earth Engine | free account + earthengine authenticate |
mpc |
Microsoft Planetary Computer (STAC) | none — streams COGs, processes locally |
Optical scenarios build cloud-masked median composites; radar scenarios auto-select the Sentinel-1 orbit with coverage. The AOI is a square centred on your coordinate. Landsat 7 is skipped (SLC-off gaps).
Make maps from a finished run
satmap output/<run-id> # render A4 map sheets offline (no GEE)
Map sheets include an OpenStreetMap basemap, the change layer, legend, a statistics panel, a location inset, coordinate grid, scale bar and north arrow.
License
MIT © Firman Hadi. Data: Copernicus Sentinel (ESA) and Landsat (USGS/NASA), via Google Earth Engine or Microsoft Planetary Computer.
1 maintainer
Metadata
1 maintainer
Release files for satchange 0.1.30
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 | |
|---|---|---|---|---|
| satchange-0.1.30.tar.gz | 96.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| satchange-0.1.30-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 188.2 kB
Release files / satchange-0.1.30.tar.gz
| Download URL | satchange-0.1.30.tar.gz |
|---|---|
| Size | 96.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8af662c3935c9c6ac5bf5e2355ebf040fe5bb63fd3310f9017b68df23f596cd7
|
|
BLAKE2b-256 checksum How to use checksums |
87131376af0e7500013eef865bac946fa2be67daea2550ec92118e7108b95883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 28, 2026.
Transparency logRelease files / satchange-0.1.30-py3-none-any.whl
| Download URL | satchange-0.1.30-py3-none-any.whl |
|---|---|
| Size | 92.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8728b9fe13897d472df5311b999b2e74dd2af7470c8d9a8ea1fe4646fd21da2e
|
|
BLAKE2b-256 checksum How to use checksums |
4786ca41e77dabfe8d494854799d146999f6a1d3a0ae7fb53bc076b9c63b6888
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 28, 2026.
Transparency logSecurity for satchange 0.1.30
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for satchange-0.1.30.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 Jul 28, 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.
