Combining high-resolution satellite images and altimetry to estimate the volume of small lakes
Bibliographic record
Abstract
Abstract. This study presents an approach to determining the volume of water in small lakes (<100 ha) by combining satellite altimetry data and high-resolution (HR) images. In spite of the strong interest in monitoring surface water resources on a small scale using radar altimetry and satellite imagery, no information is available about the limits of the remote-sensing technologies for small lakes mainly used for irrigation purposes. The lake being studied is located in the south-west of France and is only used for agricultural irrigation purposes. The altimetry satellite data are provided by an RA-2 sensor onboard Envisat, and the high-resolution images (<10 m) are obtained from optical (Formosat-2) and synthetic aperture radar (SAR) antenna (Terrasar-X and Radarsat-2) satellites. The altimetry data (data are obtained every 35 days) and the HR images (77) have been available since 2003 and 2010, respectively. In situ data (for the water levels and volumes) going back to 2003 have been provided by the manager of the lake. Three independent approaches are developed to estimate the lake volume and its temporal variability. The first two approaches (HRBV and ABV) are empirical and use synchronous ground measurements of the water volume and the satellite data. The results demonstrate that altimetry and imagery can be effectively and accurately used to monitor the temporal variations of the lake (R2ABV = 0.98, RMSEABV = 5%, R2HRBV = 0.90, and RMSEABV = 7.4%), assuming a time-varying triangular shape for the shore slope of the lake (this form is well adapted since it implies a difference inferior to 2% between the theoretical volume of the lake and the one estimated from bathymetry). The third method (AHRBVC) combines altimetry (to measure the lake level) and satellite images (of the lake surface) to estimate the volume changes of the lake and produces the best results (R2AHRBVC = 0.98) of the three methods, demonstrating the potential of future Sentinel and SWOT missions to monitor small lakes and reservoirs for agricultural and irrigation applications.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".