software · Global

HydroCouple

HydroCouple Interface Specifications

Claim this listing

Represent HydroCouple? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered llm-inferred: typed field data exchange over BufferDescriptor hyperslabs · OGC Simple Features geometry, UGRID-congruent mesh views, networks, rasters, regular grids · temporal and spatio-temporal component data items · component lifecycle, capabilities discovery and error queues
Formats llm-inferred: C++20 header-only (.h) · Python bindings (ABC mirror and Cython bridge) · OGC WKB binary geometry (ISO 19125 encoding)
Access docs-verified: Free and open source under the MIT licence; local install via CMake or vcpkg; no API key; no runtime library dependencies

Use cases llm-inferred: Coupling hydrology and hydraulics components in an integrated catchment or drainage model · Wrapping an in-house FRA or flood model as a coupled component with typed exchange items · Driving compiled C++ model components from Python workflows via the Cython bridge · Exchanging gridded or mesh model outputs (UGRID-congruent) between coupled components
Audience llm-inferred: model software developers building coupled water-resources components · hydrologists and hydraulic modellers with in-house models to couple · HPC and research software engineers

Constraints llm-inferred: Alpha release (2.0.0-alpha.2): interfaces may change · Interface standard only: supplies no model components, datasets or regional data · Requires a C++20 toolchain (GCC 11+, Clang 13+, MSVC 19.29+) and CMake 3.19+ · Not a data API: no live or time-series data source for UK catchments · Integration work (building a coupled model) is needed before any consultancy use

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Verified via GitHub API (2026-10-15). Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · research sweep: manual-2026-10-15 (hydrocouple.org)