Skip to content

Support kinematic wave floodplain routing#870

Draft
vers-w wants to merge 18 commits intomasterfrom
feat/kinwave_floodplain
Draft

Support kinematic wave floodplain routing#870
vers-w wants to merge 18 commits intomasterfrom
feat/kinwave_floodplain

Conversation

@vers-w
Copy link
Copy Markdown
Collaborator

@vers-w vers-w commented Mar 18, 2026

Issue addressed

Fixes #235

Explanation

Checklist

  • Updated tests or added new tests
  • Branch is up to date with master
  • Tests & pre-commit hooks pass
  • Updated documentation if needed
  • Updated changelog.qmd if needed

vers-w added 18 commits March 11, 2026 09:15
Initialized as `nothing`.
Introduce one struct for riverflow routing `RiverFlowModel` and one struct for overlandflow routing `OverlandFlowModel`. The routing method (subtype of `AbstractRoutingMethod`) is used to differentiate between different routing approaches for river and overland flow. Extending to other routing methods is now easier.
Remove `AbstractRoutingMethod` from these abstract types and add the routing method as first field to `RiverFlowModel` and `OverlandFlowModel`. This simplifies dispatching a bit and looks a bit cleaner.
Also add `slope` parameter that can be used by kinematic wave routing (as alternative to local inertial routing) using a staggered scheme.
Use a separate function for reading river parameters that can also be used by kinematic wave routing with a staggered scheme.
Using the term kinematic wave is not entirely correct as the Manning's equation is used as an alternative for the local inertial approach on a staggered grid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add 1D floodplain schematization to kinematic wave routing

1 participant