Towards better utilization of NEXRAD data in hydrology: an overview of Hydro-NEXRAD
Bibliographic record
Abstract
With a very modest investment in computer hardware and the open-source local data manager (LDM) software from University Corporation for Atmospheric Research (UCAR) Unidata Program Center, a researcher can receive a variety of NEXRAD Level III rainfall products and the unprocessed Level II data in real-time from most NEXRAD radars in the USA. Alternatively, one can receive such data from the National Climatic Data Center in Ashville, NC. Still, significant obstacles remain in order to unlock the full potential of the data. One set of obstacles is related to effective management of multi-terabyte datasets. A second set of obstacles, for hydrologists and hydrometeorologists in particular, is that the NEXRAD Level III products are not well suited for applications in hydrology. There is a strong need for the generation of high-quality products directly from the Level II data with well-documented steps that include quality control, removal of false echoes, rainfall estimation algorithms, coordinate conversion, georeferencing and integration with GIS. For hydrologists it is imperative that these procedures are basin-centered as opposed to radar-centered. The authors describe the Hydro-NEXRAD system that addresses the above challenges. With support from the National Science Foundation through its ITR program, the authors have developed a basin-centered framework for addressing all these issues in a comprehensive manner, tailored specifically for use of NEXRAD data in hydrology and hydrometeorology.
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.011 | 0.007 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.013 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.005 | 0.010 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.002 |
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".