aceComparative hydro-climatic forecasting of reservoir storage and cross-scale bathymetric evaluation in Mingde and Shihmen reservoirs
Accurate reservoir storage forecasting is critical for water security and risk management, yet most data-driven approaches emphasize short-term predictive skill without accounting for long-term changes in storage capacity caused by sedimentation. This study addresses this gap by examining whether monthly, hydro-climatic machine learning forecasts of effective water storage capacity can be meaningfully evaluated against observed, multi-year capacity changes derived from bathymetric surveys. Forecasting performanc…
Monthly hydro-climatic machine learning models reproduced observed storage variability at two Taiwan reservoirs with high Nash-Sutcliffe efficiency when static capacity curves were assumed.
Same hydro-climatic models failed to capture multi-year effective capacity loss from sedimentation when benchmarked against bathymetric surveys, producing relative errors up to 292% and systematic bias in droughts.
Framework relies only on hydro-climatic forcing and static capacity curves, so it cannot account for sedimentation-driven capacity change and is biased during extremes.
Evidence
- Peer-reviewedEnvironmental Science and Pollution Research2026-09-28
How should this claim be treated?
Truvace Impact Record TRV-2026-1217, v1: “Comparative hydro-climatic forecasting of reservoir storage and cross-scale bathymetric evaluation in Mingde and Shihmen reservoirs.” Truvace, 2026-09-30. /record/TRV-2026-1217 (accessed at citation time). sha256 4fc7dd26f5541b69…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1217 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.