Advancing Field-Based GNSS Surveying for Validation of Remotely Sensed Water Surface Elevation Products
Bibliographic record
Abstract
To advance monitoring of surface water resources, new remote sensing technologies including the forthcoming Surface Water and Ocean Topography (SWOT) satellite (expected launch 2022) and its experimental airborne prototype AirSWOT are being developed to repeatedly map water surface elevation (WSE) and slope (WSS) of the world’s rivers, lakes, and reservoirs. However, the vertical accuracies of these novel technologies are largely unverified; thus, standard and repeatable field procedures to validate remotely sensed WSE and WSS are needed. To that end, we designed, engineered, and operationalized a Water Surface Profiler (WaSP) system that efficiently and accurately surveys WSE and WSS in a variety of surface water environments using Global Navigation Satellite Systems (GNSS) time-averaged measurements with Precise Point Positioning corrections. Here, we present WaSP construction, deployment, and a data processing workflow. We demonstrate WaSP data collections from repeat field deployments in the North Saskatchewan River and three prairie pothole lakes near Saskatoon, Saskatchewan, Canada. We find that WaSP reproducibly measures WSE and WSS with vertical accuracies similar to standard field survey methods [WSE root mean squared difference (RMSD) ∼8 cm, WSS RMSD ∼1.3 cm/km] and that repeat WaSP deployments accurately quantify water level changes (RMSD ∼3 cm). Collectively, these results suggest that WaSP is an easily deployed, self-contained system with sufficient accuracy for validating the decimeter-level expected accuracies of SWOT and AirSWOT. We conclude by discussing the utility of WaSP for validating airborne and spaceborne WSE mappings, present 63 WaSP in situ lake WSE measurements collected in support of NASA’s Arctic-Boreal and Vulnerability Experiment, highlight routine deployment in support of the Lake Observation by Citizen Scientists and Satellites project, and explore WaSP utility for validating a novel GNSS interferometric reflectometry LArge Wave Warning System.
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.003 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
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".