-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path0300-methods.Rmd
136 lines (89 loc) · 13.2 KB
/
0300-methods.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
# Methods
## Collaborative GIS Environment
Geographical Information Systems are essential for developing and communicating restoration plans as well as the reasons they are required and how they are developed. Without the ability to visualize the landscape and the data that is used to make decisions it is difficult to conduct and communicate the need for restoration, the details of past and future plans as well as and the potential results of physical works.
<br>
To facilitate the planning and implementation of restoration activities in the Neexdzii Kwah (and elsewhere within the Widzin Kwah Water Sustainability Project area), a collaborative GIS environment (titled `restoration_wedzin_kwa`) has been established using [QGIS](https://qgis.org/en/site/) and [Mergin Maps](https://merginmaps.com/) (source code [here](https://github.com/MerginMaps). This environment is intended to be a space where project team members can access and view and contribute to the amalgamation of background spatial data and the development of restoration as well as monitoring for the project. The collaborative GIS environment allows users to view, edit, and analyze shared up to date spatial data on personal computers in an office setting as well as phones and tablets in the field. At the time of reporting, the environment was being used to develop and share maps, conduct spatial analyses, communicate restoration plans to stakeholders as well as to provide a central place to store methodologies and tools for conducting field assessments on standardized pre-developed digital forms. The platform can also be used to track the progress of restoration activities and monitor changes in the landscape over time helping encourage the record keeping of past and future restoration activities in a coordinated manner.
<br>
The shared QGIS project was created using scripts currently kept in [`dff-2022`](https://github.com/NewGraphEnvironment/dff-2022) with the precise calls to project creation scripts tracked in the `project_creation_and_permissions.txt` document kept in the main QGIS project directory. Information about how GIS project creation and update scripts function can be viewed [here](https://github.com/NewGraphEnvironment/dff-2022/tree/master/scripts/qgis) with outcomes of their use summarized below:
- download and clip user specified layers from the [BC Data Catalougue](https://catalogue.data.gov.bc.ca/) as well as data layers stored in custom Amazon Web Services buckets for an area of interest defined by a list of watershed groups and load to a geopackage called `background_layers.gpkg` stored in the main directory of the project. An additional `lateral_habitat.tiff` layer is also clipped to the user defined area and loaded to the project.
- A project directory is created to hold the spatial data and `QGIS` project information (ie. layer symbology and naming conventions, metadata, etc.).
- Metadata for individual project spatial layers is kept in the `rfp_tracking` table within the `background_layers.gpkg` along with tables related to user supplied stream width/gradient inputs to `bcfishpass` to model potentially high value habitat that is accessible to fish species of interest.
```{r qris, eval=FALSE}
## QRis
# [QGIS Riverscapes Studio](https://qris.riverscapes.net/) (QRis) is a free plugin for QGIS that helps you digitize your riverscape data. QRis is a great planning tool for helping users with spatial representation of riverscapes.
#
# QRis has two distinct types of features:
#
# * Static: These are features that are relatively permanent, such as the valley bottom.
# * Dynamic: These are features that change over time, such as the active channel.
#
# QRis will be a useful tool for digitizing the upper Wetzin'kwa river and prioritizing restoration sites. To start using QRis, follow the instructions for [getting started](https://qris.riverscapes.net/getting-started/).
```
## Open Source - Iterative Reporting
A key question we have been asking ourselves is:
<br>
>"What is the most useful way to present information?"
<br>
From our perspective - the most useful way to present information is in a version controlled format that allows it to be interactive, reproducible, read online, served out as a static document, updated, copied, used as a template, etc. Iterative reporting, managed with a version control system such as
[git](https://docs.github.com/en/get-started/using-git/about-git) (see example of tracking edits [here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/commits/main/0300-methods.Rmd))
with a permissive license is a great way to do all those things. Although there is a steep learning curve to using programming tools and producing this type of product and although it can be quite time consuming - it then allows leveraging of all the components of the work to future projects for everyone. Licensing is also key for work to be shared. [MIT License](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/blob/main/LICENSE.md) is an example of a license that promotes collaboration and sharing/leveraging of work while.
<br>
From our perspective - restoration planning are the type of initiatives that are well suited to an iterative reporting format such as
can be demonstrated within this [code
repository](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024) which builds and serves this
[online report](https://newgraphenvironment.github.io/restoration_wedzin_kwa_2024/).
### Issue and Discussion Tracking
Issues and discussions are effective ways to track tasks, enhancements, and bugs for the project. Issues can be used to keep track of all the things that need to be done, and can be used to discuss in-line with references to code used to address them linked to the issues through `git` commit messages. Issues for this project are kept [here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/issues) and
discussions are kept [here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/discussions).
### Tables and Figures
There are many tables within this document that can take a long time to format. Within this document the tables have been imported often as simple csv files or pages of an excel workbook and pulled into the project using scripts. This allows others to access the data and use it in their own projects. These tables can also then be easily updated
with new data as it becomes available often with the formatting for presentation to reader handled by the scripting. An example of this can be
seen here in Table \@ref(tab:kable-resources) with the actual file served
[here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/tree/main/data):
```{r kable-resources}
read_csv("data/aquatic_restoration_resources.csv") %>%
fpr::fpr_kable(caption_text = "Aquatic Restoration Resources.")
```
<br>
Any figures used in the reporting are saved in the project and can be used by anyone else in their work to tell there own
story and help their teams achieve their goals. An example of this can be seen here Table \@ref(tab:kable-resources)
with the actual file served
[here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/blob/main/fig/collaboration.jpg).
### Data Sourceing from Skeena Salmon Data Centre
Whenever possible we have attempted to tie into existing data govenment infrastructure in the Skeena region by downloading data directly from the [Skeena Salmon Data Centre](https://data.skeenasalmon.info/) using the application programming interface to their [CKAN](https://ckan.org/features/api) database. To facilitate and simlify this process we developed a function to download data from the CKAN database and load it into local versions of the project repository. This `fetch_package` function is kept in the `scripts/functions.R` file of the project and can be used to download entire "packages" of data from the Skeena Salmon Data Centre.
### Documentation of Workflows
Select workflows were documented in memo format to illustrate the process used for others and promote reproducibility/leverageing of Neexdzii Kwah. The memos are stored in the `memo` directory of the project [here](https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/tree/main/memos) and can be viewed in Table Table \@ref(tab:tab-memos) by downloading the `.html` documents to a local computer and opening in a web browser such as `Chrome` (usually a double click of the document will open it in the browser).
```{r tab-memos}
## make a tibble of the list and display it as a fpr_kable
list.files("memos", full.names = FALSE) %>%
tibble::tibble(memo_name = .) %>%
fpr::fpr_kable(caption_text = "Memos stored at https://github.com/NewGraphEnvironment/restoration_wedzin_kwa_2024/tree/main/memos.",
scroll = FALSE,
scroll_box_height = "300px"
)
```
## Historic Information Regarding Impacts and Restoration Initiatives
Historic information regarding impacts and restoration initiatives, prescriptions and activities is an important component of the restoration planning process. A wealth of information is present for the Neexdzii Kwah however it is located in many different locations and not always spatially represented. To address this, a comprehensive review of past impact indentification and restoration recommendations is underway. This review included a review of the literature, interviews with local experts, and a review of the restoration prescriptions and activities that have been conducted in the Neexdzii Kwah. For information regarding relatively recent restoration efforts such as physical works conducted through Healthy Watersheds Initiative, representatives from the Morice Watershed Monitoring Trust amalgamated all information located on physical drives and either provided emails with the data attached or provided links to the data for the study team for download and review. This information was then subsequently downloaded and re-uploaded to a `OneDrive` folder for the study team to access.
## Future Restoration Site Selection
### Evaluation of Historic and Current Imagery
Evaluation of historic and current imagery to understand and quantify watershed characteristics and morphological changes in the Neexdzii Kwah and its major tributaries over time and guide future restoration efforts. This will require that the study team acquire, georeference, archive and analyze historic imagery for the Neexdzii Kwah watershed and compare with an analysis of recent data to quantify historic changes in stream morphology resulting in loss of quantity and quality of water and fish habitat. Through this process we hope to highlight areas of historic dredging, realignment, and floodplain disconnections due to infrastructure that have degraded watershed health and fish habitat.
### Fish Passage
At the time of writing, extensive work related to fish passage restoration planning was underway in the Neexdzii Kwah watershed
as well as other areas of the greater Skeena watershed. Methodology for this work is presented in @irvine2023BulkleyWatershed,
@irvine2022BulkleyRiver and @irvine2021BulkleyRiver. Although these references detail work related to linear connectivity
(ie. upstream/downstream) there is ongoing work related to lateral connnectivity (ie. floodplain connectivity) with methodology
realted to disconnections due to the railway documented in `bcfishpass` [@norris2024smnorrisbcfishpass] [here](https://github.com/smnorris/bcfishpass/tree/main/model/03_habitat_lateral).
The results of this analysis and future analysis incorporating major roadways as well (currently under development) will
be added to the shared QGIS project and used to inform future restoration activity prioritization.
### Local Knowledge for Riparian Area and Erosion Protection Site Selection
To facilitate project activities in the short term - the project team will select among some known areas of riparian
removal and bank erosion where landowners are amenable to project activities including installation of cattle exclusion
fencing and riparian planting in the next two fiscal years.
### Delineation of Areas of High Fisheries Values
Spatially delineate areas of high fisheries values based on modelled and known spawning and rearing habitat for fish species of interest.
Project team members have mentioned that there was work done in the past to spatially delineate areas of high value habitat
for chinook and potentially sockeye salmon. This data will hopefully be aquired. Additionally background literature includes some decriptions of traditional Wet'suwet'en
Fisheries sites which can be spatialized for the project.
### Parameter Ranking to Select Future Restoration Sites
Analysis of background and current data will be used to inform priority ranking criteria used to select sites for restoration activities in the long term. **Although this has not yet been conducted** - included in this process can be:
- GIS and user input parameters were selected based on project team meetings and review of available spatial information to rank future restoration sites. Whenever possible standardized names for layers (schema and table) and fields were used to facilitate the reproducibility of similiar analysis on other or updated datasets, both by ourselves and by others.