river-gauge-shipping-utac
GenesisAeon Package 130 -- Rhine / Western-Europe low-water inland shipping impacts (container throughput, Kaub gauge, cascade mechanics, IfW Kiel GDP note). Deliberately has no UTAC/CREP/AFET bridge -- see DISCLAIMER.md.
Complements glacier-buffer-utac
(P99) with the economic / logistics side of low-water events. Own
package, not a P99 extension -- cross-reference only; do not rederive
P99 hydrology here.
For a plain-language German companion, see WHITEPAPER.md.
What's real here
- Bedoya-Maya et al. (2024, Transportation Research Part D) -- DOI 10.1016/j.trd.2024.104190: -0.2% throughput per day under critical water level; -5.9% when disruption > 24 days; vulnerability doubled since 2018; without resilience 7-20% projected annual container throughput loss by 2050.
- Vinke et al. (2022, Climate Risk Management) -- DOI 10.1016/j.crm.2022.100400: cascade / network-effect model (Rhine 2018). Encoded as mechanics note, not a single threshold.
- Kaub 78 cm -- operational consensus (not single-study); severe events: load factor 10-30% of nominal.
- IfW Kiel (2018) -- ~0.4% GDP on annual view; industrial production ~1% (peak 1.5%) at 30 days below 78 cm Kaub (kielinstitut.de).
Explicitly omitted: unconfirmed Bundesbank 0.2pp Q3-2018 figure.
Quickstart
pip install river-gauge-shipping-utac
from river_gauge_shipping_utac import (
CRITICAL_WATER_LEVEL_CM,
AVG_THROUGHPUT_LOSS_PCT_PER_DAY_UNDER_CRITICAL,
is_relationship_generalizable_beyond_rhine,
does_vulnerability_increase_over_time,
is_kaub_threshold_from_single_study,
)
print(CRITICAL_WATER_LEVEL_CM) # 78
print(AVG_THROUGHPUT_LOSS_PCT_PER_DAY_UNDER_CRITICAL) # -0.2
print(is_relationship_generalizable_beyond_rhine()) # False
print(does_vulnerability_increase_over_time()) # True
print(is_kaub_threshold_from_single_study()) # False
Development
pip install -e ".[dev]"
ruff check src tests
mypy src
pytest
Citation
See CITATION.cff and .zenodo.json.
Metadata
Release files for river-gauge-shipping-utac 1.0.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 | Provenance | |
|---|---|---|---|---|
| river_gauge_shipping_utac-1.0.0.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| river_gauge_shipping_utac-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / river_gauge_shipping_utac-1.0.0.tar.gz
| Download URL | river_gauge_shipping_utac-1.0.0.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cc82246768998f0b42ffe659e085b54eaa1195d56a9a0a0964fea38855a862e
|
|
BLAKE2b-256 checksum How to use checksums |
2097ba7a3d4432d7d862bf43c1b0fe34d5c831e417a3a66a98e1c4a24eaeabb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / river_gauge_shipping_utac-1.0.0-py3-none-any.whl
| Download URL | river_gauge_shipping_utac-1.0.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ee9579fa4c98448f82f3f90388b1bfd6ca0725e7fee4d3d2558f16f127623d7
|
|
BLAKE2b-256 checksum How to use checksums |
c71621230283b57bcac4a6b592d205a67b28dcc6383030018d8c5df1ebd0ac48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for river-gauge-shipping-utac 1.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.