Checking for non-preferred file/folder path names (may take a long time depending on the number of files/folders) ...
This resource contains some files/folders that have non-preferred characters in their name. Show non-conforming files/folders.
This resource contains content types with files that need to be updated to match with metadata changes. Show content type files that need updating.
Authors: |
|
|
---|---|---|
Owners: |
|
This resource does not have an owner who is an active HydroShare user. Contact CUAHSI (help@cuahsi.org) for information on this resource. |
Type: | Resource | |
Storage: | The size of this resource is 104.2 MB | |
Created: | Oct 05, 2022 at 9:46 p.m. | |
Last updated: | Jun 20, 2023 at 12:26 p.m. (Metadata update) | |
Published date: | Jun 20, 2023 at 12:25 p.m. | |
DOI: | 10.4211/hs.f738261bc1ed42f0bc71a5b14e0f90ac | |
Citation: | See how to cite this resource | |
Content types: | Geographic Feature Content |
Sharing Status: | Published |
---|---|
Views: | 648 |
Downloads: | 6 |
+1 Votes: | Be the first one to this. |
Comments: | No comments (yet) |
Abstract
This is a repository for the code + data associated with the publication titled "Assessing downstream aquatic habitat availability relative to headwater reservoir management in the Henrys Fork Snake River" by Christina N Morrisett, Robert W Van Kirk, and Sarah E Null in River Research and Applications (2023).
Reservoirs are sometimes managed to meet agricultural and other water demands, while also maintaining streamflow for aquatic species and ecosystems. In the Henrys Fork Snake River, Idaho (USA), irrigation-season management of a headwater reservoir is informed by a flow target in a management reach ~95 km downstream. The target is in place to meet irrigation demand and maintain aquatic habitat within the 11.4 km management reach and has undergone four flow target assignments from 1978 to 2021. Recent changes to irrigation-season management to maximize reservoir carryover warranted investigation into the flow target assignment. Thus, we created a streamflow-habitat model using hydraulic measurements, habitat unit mapping, and published habitat suitability criteria for Brown Trout (Salmo trutta), Rainbow Trout (Oncorhynchus mykiss), and Mountain Whitefish (Prosopium williamsoni). We used model output to compare habitat availability across two management regimes (1978–2017 and 2018–2021). We found that efforts to minimize reservoir releases in 2018–2021 did not reduce mean irrigation-season fish habitat relative to natural flow, but did reduce overall fish habitat variability during the irrigation season compared to streamflow management in 1978–2017. Field observations for this research led to an adjusted flow target in 2020 that moved the target location downstream of intervening irrigation diversions. Using our model output, we demonstrated that moving the location of the target to account for local irrigation diversions will contribute to more consistently suitable fish habitat in the reach. Our study demonstrates the importance of site selection for establishing environmental flow targets.
Subject Keywords
Coverage
Spatial
Content
readme.txt
This document provides orientation to the data, code, and outputs provided within the repository. ###---------DATA----------### The data folder is organized into multiple subfolders, described as follows. In DataAllASCII, you will find the ASCII files for each pass within a given site on a given day. The files are named SiteCode_YYYY-MM-DD_0_PassNumber. In DataBlockAreas, you will find the ArcGIS excel output for each unit mapped within a habitat type. This includes the geometric area, latitude, and longitude of each unit. Each file is for a given habitat type. In DataFlowDiversions, you will find diversion data for the four canals within the management reach (15-min data within 2019-21 sample period and daily data for 1978-2021 study period). You will also find reach gain data, natural flow data, and data on draft dates at Island Park Reservoir as calculated by Rob Van Kirk in code not provided. In DataFlowMMT, you will find data taken from WinRiverII ADCP measurement summaries estimating streamflow for a given pass on a given date. Each file is for a given single-channel measurement site. In DataFlowSuitModsBySite, you will find the summary of model type required for a given life stage and site within a given species (file), as well as the relationship between width + flow. These were hand-input from 0_SuitFlowRelationships.RMD and 0_WidthPropFlowRelationships.RMD. In DataMMTSummary, you will find the WinRiverII ADCP measurement summaries for channel width for a given pass on a given date. In DataShapeFiles, you will find subfolders for the shapefiles created for the habitat units (Figure 1) and center-line comparison (Figure 4). We acknowledge that references to site names/habitat types change throughout the data + code as our project evolved + we received reviewer feedback. We did not have an easy way to go back and update all files names and code calls. So please reference the following: BB1 = SmallPool (within braided reaches, sampled within braids downstream of the Trestle bridge in the lower subreach). Habitat type = BP3 in manuscript (Table 2). BB2 = MedPool (within braided reaches, sampled within braids downstream of the Trestle bridge in the lower subreach). Habitat type = BP2 in manuscript (Table 2). BB3 = BigPool (within braided reaches, sampled within braids downstream of the Trestle bridge in the lower subreach). Habitat type= BP1 in manuscript (Table 2). RR1 and RL1 = BigFlat (within braided reaches, sampled within braids in the upper subreach). Habitat type = BWR in manuscript (Table 2). RR2 and RL3 = SmallFlat (within braided reaches, sampled within braids in the upper subreach). Habitat type = BNR in manuscript (Table 2). RR3 and RL2 = BigU (within braided reaches, sampled within braids in the upper subreach). Habitat type = BWB in manuscript (Table 2). RR4 and RL4 = SmallU (within braided reaches, sampled within braids in the upper subreach). Habitat type = BNB in manuscript (Table 2). TP0 (within single channel, sampled just upstream of the Trestle bridge at the downstream-most extent of the upper subreach). Habitat type = SP in manuscript (Table 2). TP1 (within single channel, sampled in lower subreach). Habitat type = SR in manuscript (Table 2). TP2 (within single channel, sampled in lower subreach). Habitat type = SB in manuscript (Table 2). ###---------CODE----------### Code is ordered by number prefix from 0_ to 3_. With one exception, the code should generally be operated in that order if starting from the beginning. However, if downloading the repository in full, then each code piece should run on its own without the need for consecutive runs of individual pieces. The code 0_ReachGains.R analyzes streamflow in the management reach, both measured in the field and recorded broadly, to quantify reach gains + losses (related to river-aquifer dynamics). The code 0_SuitFlowRelationships.RMD explores statistical relationships between suitability and streamflow for a given species + life stage at each site. The suitabilites were calculated within 1_SPECIES.R. The information gleaned from this RMD is input back into 1_SPECIES.R. The RMD output SuitFlowRelationships.html accompainies code 0_SuitFlowRelationships.RMD. The code 0_WidthPropFlowRelationships.RMD explores statistical relationships between wetted width and streamflow for a given site. The code 1_SPECIES.R, where species is BrownTrout, RainbowTrout, or MountainWhitefish creates the suitability curves from relevant literature, reads in ADCP data + calculates habitat suitability for each site + streamflow, and calculates continuous WUA. The code 2_InputsForViz.R takes in the WUA vectors created in 1_SPECIES and creates additional output for 3_VizforPublication.R. The code 2_VizBySpecies.R takes in WUA vectors created in 1_SPECIES and creates annual output for each species. The code 3_SensitivityAnalysis.R tests the sensitivity of our WUA output to our habitat type assignments. The code 3_VizforPublication.R takes in output from 1_SPECIES and 2_InputsForViz to create figures + statistics shown in manuscript. The code files aictable.R and logit.transform.R are utility files with functions needed to conduct analysis in other code files. ###---------OUTPUT----------### Organized by subfolders: BrownTrout, MountainWhitefish, RainbowTrout, and Publication. The species folders hold data and graphic output from 1_SPECIES.R, 2_InputsForViz, and 2_VizBySpecies. The Publication folder contains all the figures published in the manuscript and its supplement.
Data Services
Credits
Funding Agencies
This resource was created using funding from the following sources:
Agency Name | Award Title | Award Number |
---|---|---|
Local Highway Technical Assistance Council | ||
Fremont County Idaho | ||
Henry's Fork Foundation | ||
U.S. Bureau of Reclamation | WaterSMART Applied Science | R21AP10036 |
National Science Foundation | 1633756, 1653452 |
Contributors
People or Organizations that contributed technically, materially, financially, or provided general support for the creation of the resource's content but are not considered authors.
Name | Organization | Address | Phone | Author Identifiers |
---|---|---|---|---|
Sarah Null | Utah State University;iUTAH | Utah, US |
How to Cite
This resource is shared under the Creative Commons Attribution-NoDerivs CC BY-ND.
http://creativecommons.org/licenses/by-nd/4.0/
Comments
There are currently no comments
New Comment