Impacts of roads and cranberry agriculture on bog wetland hydrology with restoration recommendations for Langley Bog
Bibliographic record
Abstract
Bog wetlands store a disproportionate amount of carbon for their size, making their conservation an important part of climate change mitigation.The goal of this project is to investigate how roads and agriculture impact the hydrology and vegetation composition of Langley Bog and to provide restoration recommendations.Langley Bog, in Langley Township, BC, is a formerly mined peatland with a fill road running through the center and surrounded to the north and west by cranberry farms.From November 2020 to November 2021, depth to water table and pH were measured monthly at nine wells.Twelve vegetation transects were completed in July 2021.Sites adjacent to the road were correlated with a decrease in summer water level, while sites adjacent to the cranberry farms were correlated with an increase in spring pH levels.A positive relationship was found between an increase in water-table level and percent cover of wetland obligate species.Roads may be lowering the water table through subsidence and drainage.The cranberry farms may be increasing the pH through the deposition of fertilizer.These impacts may have been exacerbated by the unusually dry 2020 summer season.To raise the water table, tree and road removal is recommended to restore lateral flow and decrease evapotranspiration.Culverts installed under the primary fill road will provide additional hydrologic connectivity.Building a berm at outlet points will also help prevent water loss, keeping a higher water table.To increase carbon sequestration, Sphagnum mosses are to be reintroduced to denuded areas in Langley Bog.Tree removal will help in moss establishment by maintaining open bog conditions free from shading.Existing rare ecosystems present in Langley Bog would benefit from the removal of point source pollutants and invasive species on the site.Given the urgency of climate change, restoring the functionality of Langley Bog and protecting the existing stored carbon is a practical and achievable way to move Metro Vancouver a step closer to carbon neutrality.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 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".