GIS Data: Prince George’s County, Maryland – Shoreline Inventory Data 2023
Bibliographic record
Abstract
The shoreline inventory files have been generated to support the application of the Maryland Shoreline Stabilization Model (SSM), developed by the Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science (VIMS), to enhance and streamline regulatory decision making in Maryland. This shoreline inventory includes the features needed as inputs to run the SSM. The data developed for the Shoreline Inventory is based on a three-tiered shoreline assessment approach. This assessment characterizes conditions by using observations made remotely at the desktop using high resolution imagery. The three-tiered shoreline assessment approach divides the shore zone into three regions: 1) the immediate riparian zone, evaluated for land use; 2) the bank, evaluated for height, and natural protection (i.e., marshes and beaches); and 3) the shoreline, describing the presence of shoreline structures for shore protection and recreational purposes. The 2023 Inventory for Prince George’s County was generated using on-screen, digitizing techniques in ArcGIS® - ArcMap v10.6.1 or greater. Three GIS shapefiles are developed, PrinceGeorges_lubc_2023, PrinceGeorges_astru_2023, and PrinceGeorges_sstru_2023. The shapefiles use a shoreline basemap from the NOAA Continuously Updated Shoreline (CUSP) shoreline, which it is updated in-house by using the most recent available MD Six Inch Imagery to reflect the most current land-water interface position. The shoreline is re-coded to reflect features and attributes observed. The metadata file accompanies the shapefiles and defines attribute accuracy, data development, and any use restrictions that pertain to data.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.004 | 0.010 |
| Science and technology studies | 0.001 | 0.000 |
| 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.054 | 0.027 |
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".