Neighbourhood vs. Individual Property Scale Coastal Protection: A Case Study in Qualicum Beach, British Columbia
Bibliographic record
Abstract
Individual property owners throughout the Salish Sea are faced with the need to adapt their shorelines to accommodate potentially degradative coastal processes, such as sea level rise and erosion. Simultaneously, there is a wide-spread push towards natural and nature-based approaches to coastal protection; however, these types of approaches (such as beach nourishments) are often ill-suited for implementation on individual properties, with frontages typically less than 100 m long. This challenge typically requires undesirable trade-offs during design to accommodate the physical constraints of an individual property. Alternatively, designs may be implemented on a neighbourhood-scale with fewer design trade-offs, and spreading both costs and benefits across a broader community. In this presentation, we will explore the differences between neighbourhood and individual property scale coastal protection by focusing on a case study in Qualicum Beach, British Columbia (BC). At this location, Northwest Hydraulic Consultants (NHC) – on behalf of private property owner, Craig Hodge – developed a nature-based design for coastal protection spanning two adjacent properties owned by the same individual. The existing shoreline consisted of a concrete seawall and a rock revetment. The design aimed to re-naturalize the shoreline to reduce erosion and wave-induced flooding through construction of a gravel beach, rocky headlands, and a raised and vegetated backshore. After significant permitting and approval-related hurdles, the project was successfully constructed in Fall 2021. Expanding on this concept, NHC – on behalf of the Stewardship Centre for British Columbia (SCBC) – developed a neighbourhood-scale version of the same design. This presentation will provide background on the project goals, site constraints, project design, and construction outcomes. The individual property-scale design will be compared and contrasted to the neighbourhood-scale design. Challenges and opportunities posed by each project scale will be highlighted.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.008 | 0.002 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".