SCET (Shoreline Change Estimation Toolkit)
A pure-Python toolkit for extracting shorelines from segmented raster imagery
and computing shoreline change rates. Transect casting, shoreline/transect
intersection, and change-rate calculation are delegated to the
OpenDSAS CLI (dsas), a fast,
cross-platform reimplementation of USGS DSAS.
Installation
pip install scet-toolkit
This installs scet-toolkit's dependencies including opendsas, which
provides the dsas CLI used for transect/intersection/rate calculations.
The deep-learning segmentation step (scet.segmentation, used by
SCET.process_folder/process_image) is included: the DeepLabV3+ network is
plain PyTorch, so there is no mmcv/mmsegmentation or GDAL to build and any
Python 3.9+ works. torch is CUDA-build-sensitive: if the default wheel isn't
right for your platform, install torch from https://pytorch.org first (matching
your CUDA version), then pip install scet-toolkit. Inference uses the GPU
when available and falls back to CPU.
Usage
from scet import SCET, Config
config = Config(checkpoint_file="path/to/checkpoint.pth")
scet = SCET(config)
scet.process_folder(input_naip_zipfiles_folder="...", output_folder="...")
Or drive the shoreline pipeline directly, given a folder of already-segmented,
dated raster images (filenames ending in a 4-digit year, e.g. 1_2001.tif):
from scet.options import Options
from scet.pipeline import generate_result_from_folder
generate_result_from_folder("images/", "output/", Options())
This writes shoreline.shp, baseline.shp, transect.shp, and
intersection.shp to the output folder.
Development
conda create -n my_env python==3.12
conda activate my_env
bash build.sh # pip install -e .
Testing
pip install -e ".[test]"
pytest # full suite, including end-to-end pipeline tests
pytest -m "not e2e" # unit tests only (skip anything that shells out to `dsas`)
The end-to-end tests build synthetic georeferenced rasters, run the full
images -> shoreline/baseline -> dsas cast/cal pipeline, and check the
output shapefiles. They need the dsas executable (installed with the
opendsas dependency) on PATH and self-skip if it is missing.
Metadata
Release files for scet-toolkit 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| scet_toolkit-0.3.1.tar.gz | 40.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scet_toolkit-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.5 kB
Release files / scet_toolkit-0.3.1.tar.gz
| Download URL | scet_toolkit-0.3.1.tar.gz |
|---|---|
| Size | 40.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aea05d0a72fceffac17e48907a1a5f93408529019ee324cedc45db95e8b81c63
|
|
BLAKE2b-256 checksum How to use checksums |
ea313a41d15530b1c17667c862c97dfec321a32302a0e501da216ff0a69ffe22
|
| 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 Oct 13, 2026.
Transparency logRelease files / scet_toolkit-0.3.1-py3-none-any.whl
| Download URL | scet_toolkit-0.3.1-py3-none-any.whl |
|---|---|
| Size | 35.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
308d0d8558fcfbe97989567587870df239f9307df97c86e2c44e0ddf41fcd671
|
|
BLAKE2b-256 checksum How to use checksums |
de8413b2430ae0f1bf2df1250ea71675b24cdb9271782b3e22bef8755123da71
|
| 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 Oct 13, 2026.
Transparency log