Extracted Data From: Lake Level Viewer
Bibliographic record
Abstract
This submission includes publicly available data extracted in its original form. Please reference the Related Publication listed here for source and citation information: NOAA Office for Coastal Management. (2025, March 1). Lake Level Viewer. Data Download. https://chs.coast.noaa.gov/htdata/Inundation/GreatLakes/BulkDownload/index.html. If you have questions about the underlying data stored here, please contact NOAA Office for Coastal Management by submitting this form: https://coast.noaa.gov/contactform/. If you have questions or recommendations related to this metadata entry and extracted data, please contact the CAFE Data Management team at: climatecafe@bu.edu. This dataset consists of the geospatial data layers that are behind NOAA's Digital Coast Lake Level Viewer, which models lake level rise and flooding impacts along the US side of the Great Lakes. The water levels illustrate the extent and relative depth of water from 3 feet below to 10 feet above each lake's respective Low Water Datum (LWD). Water extent is as it would appear on a calm day with no wind-driven waves or seiche effect. The data do not consider natural processes such as erosion, subsidence, or future construction. The data are intended for use as a screening-level tool for planning and management decisions. Datasets are subdivided into the following folders, and in some cases are geographically segmented by portions of the individual lakes (Erie, Huron, Michigan, Ontario, St. Clair, and Superior): DEMs: lidar-based high resolution digital elevation models stored as geotiffs Depth Rasters: rasters of lake level rise inundation from -3 ft to 10ft above the LWD as geotiffs Extent Rasters: single value rasters of lake level rise inundation from -3 ft to 10ft above the LWD as geotiffs Lake Level Vectors: polygon data representing the extent of lake level rise inundation as geopackages Documentation for the LL tool and methodology for creating the datasets is included in a PDF file. https://chs.coast.noaa.gov/htdata/Inundation/GreatLakes/BulkDownload/index.html
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.002 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.006 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.422 | 0.346 |
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; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
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".