Tracking Dynamic Northern Surface Water Changes with High-Frequency Planet CubeSat Imagery
Bibliographic record
Abstract
Recent deployments of CubeSat imagers by companies such as Planet may advance hydrological remote sensing by providing an unprecedented combination of high temporal and high spatial resolution imagery at the global scale. With approximately 170 CubeSats orbiting at full operational capacity, the Planet CubeSat constellation currently offers an average revisit time of <1 day for the Arctic and near-daily revisit time globally at 3 m spatial resolution. Such data have numerous potential applications for water resource monitoring, hydrologic modeling and hydrologic research. Here we evaluate Planet CubeSat imaging capabilities and potential scientific utility for surface water studies in the Yukon Flats, a large sub-Arctic wetland in north central Alaska. We find that surface water areas delineated from Planet imagery have a normalized root mean square error (NRMSE) of <11% and geolocation accuracy of <10 m as compared with manual delineations from high resolution (0.3–0.5 m) WorldView-2/3 panchromatic satellite imagery. For a 625 km2 subarea of the Yukon Flats, our time series analysis reveals that roughly one quarter of 268 lakes analyzed responded to changes in Yukon River discharge over the period 23 June–1 October 2016, one half steadily contracted, and one quarter remained unchanged. The spatial pattern of observed lake changes is heterogeneous. While connections to Yukon River control the hydrologically connected lakes, the behavior of other lakes is complex, likely driven by a combination of intricate flow paths, underlying geology and permafrost. Limitations of Planet CubeSat imagery include a lack of an automated cloud mask, geolocation inaccuracies, and inconsistent radiometric calibration across multiple platforms. Although these challenges must be addressed before Planet CubeSat imagery can achieve its full potential for large-scale hydrologic research, we conclude that CubeSat imagery offers a powerful new tool for the study and monitoring of dynamic surface water bodies.
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.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".