Shoreline Evolution: Prince George County, Virginia Upper Chippokes Creek, James and Appomattox River Shorelines
Bibliographic record
Abstract
Prince George County is situated between on the James River between Upper Chippokes Creek and the Appomattox Rivers (Figure 1). Because the County’s shoreline is continually changing, determining where the shoreline was in the past, how far and how fast it is moving, and what factors drive shoreline change will help define where the shoreline will be going in the future. These rates and patterns of shore change along Chesapeake Bay’s estuarine shores will differ through time as winds, waves, tides and currents shape and modify coastlines by eroding, transporting and depositing sediments. The purpose of this report is to document how the shore zone of Prince George County has evolved since 1937. Aerial imagery was taken for most of the Bay region beginning that year and can be used to assess the geomorphic nature of shore change. Aerial photos show how the coast has changed, how beaches, dunes, bars, and spits have grown or decayed, how barriers have breached, how inlets have changed course, and how one shore type has displaced another or has not changed at all. Shore change is a natural process but, quite often, the impacts of man, through shore hardening or inlet stabilization, come to dominate a given shore reach. In addition to documenting historical shorelines, the change in shore positions along the larger creeks in Prince George County will be quantified in this report. The shorelines of very irregular coasts, small creeks and around inlets, and other complicated areas will be shown but not quantified.
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.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".