A Python toolbox for coastal, port and ocean engineering. A wave record becomes a design condition, the design condition sizes a structure, and the structure comes out as a dimensioned drawing with its quantities and notes. Every relation names its source and states its range of validity.
Install
pip install pyCoastal # PyPI
pip install -e ".[dev]" # from a clone, with tests and plotting
Quick start
from pyCoastal.applications.structures import DesignConditions
from pyCoastal.applications.seawall import design_seawall
from pyCoastal.applications.sections import seawall_sheet
conditions = DesignConditions.from_peak_period(Hm0=2.8, Tp=9.5, depth=8.5)
wall = design_seawall(conditions, still_water_level=2.9, seabed_level=-5.6)
print(wall.summary())
seawall_sheet(wall, size="A3").save("seawall.png")
What is inside
| Area | Modules |
|---|---|
| Design conditions | applications.extremes (POT, annual maxima, bootstrap bands) |
| Structures | applications.structures, seawall, piles, berthing |
| Scour | applications.scour (pier, contraction, abutment over a tidal cycle) |
| Ports and rivers | applications.port, channel, river |
| Coastline | applications.nourishment, surge, sediment |
| Drawings | drafting, applications.sections (drawing sheets and DXF) |
| Numerics | numerics, physics, tools (grids, operators, SWE, NS, waves) |
| Literature | pedia (PyCoaPedia: topics, synthesis, claims, equations, papers) |
PyCoaTools (webapp/index.html) runs the design modules in the browser.
PyCoaPedia is the knowledge base of the coastal and ocean engineering
literature, every claim with its regime and DOI: browse it in
webapp/pedia.html, query it with python -m pyCoastal.pedia search "...",
or read pedia/.
Documentation
- For people:
pyCoastal manual.pdf, built fromdocs/manual/withpython docs/manual/build_manual.py. - For AI agents:
AGENTS.mdandllms.txt, the Markdown API reference indocs/reference/, and the PyCoaPedia SQLite database (pedia/SCHEMA.md).
Citation
Biondi, S. (2025). pyCoastal: a Python package for Coastal Engineering, v0.2.0. https://github.com/stebiondi/pyCoastal
MIT License. Copyright (c) 2025 Stefano Biondi.
Release files for pyCoastal 0.2.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 | |
|---|---|---|---|
| pycoastal-0.2.0.tar.gz | 5.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pycoastal-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.5 MB
Release files / pycoastal-0.2.0.tar.gz
| Download URL | pycoastal-0.2.0.tar.gz |
|---|---|
| Size | 5.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96a0600af83e471ee31f8bb51640f8b2eea0c2b759138a5d5f99c084811c4f63
|
|
BLAKE2b-256 checksum How to use checksums |
d9783d0efde67155f125829f793b2553b1c71c33d708ed4af4191e31938858fa
|
| 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 24, 2026.
Transparency logRelease files / pycoastal-0.2.0-py3-none-any.whl
| Download URL | pycoastal-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6efdcd9a382133ab0e4f87ab1413dae9434a093c72270593e6684904fc16c303
|
|
BLAKE2b-256 checksum How to use checksums |
7fc067c396372b8e133af20cf3f8cacdf5915ba6fe66813cdc7756b522c48288
|
| 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 24, 2026.
Transparency log