ArcGIS REST Services Directory
JSON

Layer: Streams (ID:20)

View In:   Map Viewer

Name: Streams

Display Field: GNIS_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: This data set contains data for fish presence, spawning and designated crititical habitat. Updated 11/13/2015 for chinook spawning. Last updated 12/10/15 for bulltrout spawning. Updated 6/7/16 chinook spawning on panther. Last updated 9/5/18 by Gamett for revision. Updated 12/20/18 by Garcia for revision.

Copyright Text: Base layer used was obtained from National Hydrologic Data set from USGS. Corrections were made to this layer as needed. Steelhead Designated Critical Habitat was obtained from the National Marine Fisheries Service (NMFS) Bull Trout Designated Critical Habitat was obtained from the Fish and Wildlife Service (FWS) Presence, Spawning, Chinook Designated Critical Habitat developed by Forest Fish Biologist D. Garcia and B. Gamett. APPENDIX D – PROTOCOL FOR MAPPING CHINOOK SALMON CRITICAL HABITAT CURRENTLY DESIGNATED ON THE SALMON-CHALLIS NATIONAL FOREST This document summarizes the process that will be used by the Salmon-Challis National Forest (SCNF) to map Chinook salmon critical habitat (CSCH) as currently designated by NOAA Fisheries on the SCNF. Critical habitat has been designated for Snake River spring/summer Chinook salmon and includes “river reaches presently or historically accessible…to Snake River spring/summer Chinook salmon” (Federal Register 58(247):68543-68554). However, this designation did not provide a detailed description of the specific areas included in the designation. Such a description is essential when completing site specific consultations to determine if CSCH is present within the action areas. The purpose of this project is to create a GIS layer that delineates the specific areas that are designated as CSCH in this rule. It should be emphasized that this process is not to “designate” CSCH but to portray the SCNFs interpretation, using the identified process, of those areas that have already been designated by the rule. For the purposes of the project, we assume CSCH to be all areas currently or historically occupied by Chinook salmon. This process includes only those areas within the administrative boundary of the SCNF. The process will use the NHD stream layer as the base layer. By default, all streams will initially be considered to not be CSCH. The following steps will then be used to map designated CSCH. Step 1: Add reaches identified by the Intrinsic Potential Model An Intrinsic Potential Model (IPM) developed by the National Marine Fisheries Service (Cooney and Holzer 2006) has been used to model potential spawning and rearing habitat within the SCNF. All stream reaches identified by the IPM shall be mapped as CSCH. Step 2: Remove reaches that were inappropriately identified by the IPM The IPM has the potential to identify streams or portions of streams where Chinook salmon could not have occurred. This step involves identifying these reaches and removing them from the CSCH layer. Forest fish staff will review stream reaches selected by the IPM and identify those that were inappropriately included. This may include, but not be limited to, stream reaches that are a) ephemeral, b) above natural barriers, or c) too small to support Chinook salmon. Documentation supporting the removal of each stream reach must be provided. Step 3: Add reaches where Chinook salmon have occurred based on redd data, but have not been identified in previous steps as CSCH Chinook salmon redd surveys have been conducted by various organizations. These data will be reviewed by Forest fish staff and all sites where Chinook salmon redds have occurred that have not already been identified as CSCH shall be mapped. Documentation supporting the inclusion of each stream reach must be provided. Step 4: Add reaches where Chinook salmon have been observed during SCNF fisheries assessments, but have not been identified in previous steps as CSCH The SCNF has conducted various fisheries assessments and resulting data contain site-specific information regarding Chinook presence in streams. These data may include, but not be limited to, a) general fish population assessments, b) fish population monitoring, c) project specific monitoring, d) observation by Forest Service personnel, and e) R1/R4 surveys. These data will be reviewed by Forest fish staff and all sites where Chinook salmon have occurred that have not already been identified as CSCH shall be mapped. Documentation supporting the inclusion of each stream reach must be provided. Step 5: Add reaches where Chinook salmon have been observed during fisheries assessments conducted by external organizations, but have not been identified in previous steps as CSCH Various organizations other than the SCNF have conducted fisheries assessments and resulting data are valuable for identifying areas where Chinook salmon have occurred within the SCNF. Such organizations may include, but not be limited to a) the Idaho Department of Fish and Game, b) the Department of Environmental Quality, and c) Native American Tribes. These data will be reviewed by Forest fish staff and all sites where Chinook salmon have occurred that have not already been identified as CSCH shall be mapped. Documentation supporting the inclusion of each stream reach must be provided. Step 6: Add reaches that may provide or may have provided tributary refugia to Chinook salmon, but have not been identified in previous steps as CSCH Chinook salmon may occupy portions of tributary streams that are not directly associated with spawning areas. Chinook salmon can encounter water temperature or turbidity conditions that are temporarily less than optimal or are lethal (Torgersen et al. 1999; Scrivener et al. 1993). When this occurs, the fish may move to tributary streams that have more suitable conditions but that the fish would not otherwise occupy. We refer to these areas as tributary refugia. It is important to know how far Chinook salmon may move up tributary refugia. However, most of the information that we found (e.g. – Scrivener et al. 1994, Malsin et al. 1996-1999, Murray and Rosenau 1989) was not directly applicable to the set of conditions present on the SCNF in central Idaho. Those studies with data most closely representing conditions found in central Idaho show that fish seeking refugia primarily use confluence areas (Strange 2007; Torgersen et al. 1999). Since we were not able to locate information on use-patterns in tributary refugia, we used professional judgment to estimate how far up these tributaries Chinook salmon might move. Based on our review of fish population and stream habitat data from the Salmon River basin, we concluded that Chinook salmon likely do not move more than 0.25 miles up a tributary if the only reason they are in the stream is to seek refugia. Although the previous steps in this process have likely identified most stream reaches that are tributary refugia, it is possible that some of these areas have still not yet been included. This step allows the addition of tributary refugia using the following set of criteria as a guideline for mapping. Professional judgment shall be used and documentation supporting the addition of each stream reach must be provided. a) Proximity to CSCH: The tributary must connect to a stream or river currently included as CSCH. b) Watershed Size: An evaluation of the smallest tributaries where Chinook salmon presence was confirmed within the SCNF can be useful in estimating the lower limits to watershed size constraining use of streams by Chinook. The average lower limit to watershed size where Chinook were present or presumed likely to use as refuge on the South Zone of the SCNF was approximately seven square miles. This value or a value that is appropriate for a given geographic area may be used to identify tributaries where it is reasonable to assume that Chinook salmon can access and use as refuge. c) Fish-Bearing Streams: Streams accessible to other salmonids can reasonably be assumed to be accessible to Chinook. Tributaries that contain other salmonids and are not smaller that the lower limit to watershed size shall be considered for inclusion as CSCH for 0.25 miles upstream from the confluence. Tributaries meeting this criterion, but exhibiting barriers to migration at the confluence shall be considered for exclusion from CSCH. d) Non-Fish-Bearing Streams: Streams inaccessible to other salmonids can reasonably be assumed to be inaccessible to Chinook and shall generally be considered for exclusion from CSCH. * Streams lacking fish occurrence data shall be evaluated for inclusion in or exclusion from CSCH based upon the watershed size and professional judgment. Step 7: Add reaches that, based on professional judgment, may be currently or may have been historically occupied by Chinook salmon, but have not been identified in previous steps as CSCH It is possible that the previous steps have not identified all reaches that either currently contain or historically contained Chinook salmon. This step allows Forest fish staff to use professional judgment to identify any additional CSCH that may have been missed in the previous steps. Documentation supporting the addition of each stream reach must be provided. Step 8: Add reaches that are downstream from CSCH identified in the previous steps Since Chinook salmon migrate to the Pacific Ocean, they will occur at least seasonally in all areas downstream of the stream reaches identified as CSCH in the previous steps. Therefore, all reaches downstream of areas identified in the previous steps as CSCH shall also be mapped as CSCH. Last updated 05/08/2015. Forest SDE Aquatic Fish Presence Layer Rules and Guidelines (Version 09-3-2018) General • The purpose of this layer is to depict the following in streams: o All fishes that are found on the Forest o Designated critical habitat for ESA listed fishes, o and 3) on the Forest. • In 2017 and 2018, a thorough review was completed to identify all fish species that occur on the Salmon-Challis National Forest. The species fields in this layer have been revised to include all species identified in that review. The species fields, corresponding species names, and species specific instructions are provided below. • The species fields are attributed with a “Y”, “YP”, “N”, or “M”. In the past we have used a “U” when it was unknown if a species occurred in a stream or stream reach. We have now eliminated the use of “U”. We are eliminating the use of “U” because we want to estimate the total distribution of species across the Forest. I globally replaced all “U” attributes with an “N” attribute for the entire layer. The species fields should be attributed with one of the following attributes: o Y: The species has been documented in the stream reach. o YP: The species has not been documented in the stream reach but it likely occurs in the stream reach. This attribute is generally used when fish data are not available for a stream reach. This determination is based on the professional judgement of a fish biologist. o M: The species has not been documented in the stream reach but likely migrates through it. This is generally used for Bull Trout and Westslope Cutthroat Trout. o N: The species has not been documented or likely does not occur in the stream reach. • In general, species fields are only attributed for perennial streams. • Species fields are not attributed for side channels even if the side channels show as perennial and is occupied with fish. There are three primary reasons for this. First, the length of occupied habitat is generally considered to be the length of the main channel and does not include side channels. Therefore, attributing the side channels will overestimate the length of occupied stream habitat. Second, side channels are not always mapped so attributing them will result in inconsistencies. Third, side channels that show as perennial may actually be intermittent or completely dry. For named streams that have a side channel, the side channel can be differentiated from main channel by looking at the “GNIS_NAME” field. The “GNIS_NAME” field will have the stream name on the main channel and the side channel will either have the attribute “Side Channel” or it will be blank. For unnamed streams, pick one of the channels for the main channel.   Field Descriptions Field Description Attributes Comments OBJECTID Numeric value that identifies each object (arc) in the layer Number Do not edit GNIS_ID Numeric value assigned to named streams Number Do not edit GNIS_NAME Stream name Stream name REACHCODE Numeric value assigned to each reach using the USGS hydrologic unit code classification system Number Do not edit FLOWDIR Designates flow direction 1 FTYPE Feature type Described here FCODE Feature code Described here STRM_TYPE Identifies streams as perennial or intermittent/ephemeral P: Perennial IE: intermittent/ephemeral This should be revised if needed. TRT_STH Steelhead occurrence Y, YP, N, M1 In the Salmon River basin, steelhead are considered present in a stream reach if Oncorhynchus mykiss are present in the stream reach and it is possible for them to move to the Pacific Ocean and then return to the same stream reach. Since steelhead migrate to the ocean, all stream reaches downstream of the reach with steelhead are considered to contain steelhead and should be attributed with a “Y”. Steelhead do not occur in the Big Lost River, Little Lost River, Birch Creek, or Wood River basins. TRT_RBT Rainbow Trout occurrence Y, YP, N, M1 All O. mykiss are considered to be Rainbow Trout in the Big Lost River, Little Lost River, Birch Creek, or Wood River basins, and in some cases, within the Salmon River basin. O. mykiss are considered to be Rainbow Trout in the Salmon River basin if there is clear evidence they cannot move to the Pacific Ocean and return to the same stream reach. TRT_BULL Bull Trout occurrence Y, YP, N, M1 TRT_CT_W Westslope Cutthroat Trout occurrence Y, YP, N, M1 All Cutthroat Trout in streams in the Salmon River basin are considered to be Westslope Cutthroat Trout unless there is specific genetic data indicating they are Yellowstone Cutthroat Trout. TRT_CT_Y Yellowstone Cutthroat Trout occurrence Y, YP, N, M1 All Cutthroat Trout in streams in the Big Lost River, Little Lost River, Birch Creek, and Wood River basins are considered to be Yellowstone Cutthroat Trout unless there is specific genetic data indicating they are Westslope Cutthroat Trout. TRT_BROOK Brook Trout occurrence Y, YP, N, M1 TRT_BRXBL Brook Trout x Bull Trout Hybrid occurrence Y, YP, N, M1 TRT_GOLDEN Golden Trout occurrence Y, YP, N, M1 SLM_CHNK Chinook Salmon occurrence Y, YP, N, M1 Since Chinook Salmon migrate to the ocean, all stream reaches downstream of the reach with Chinook Salmon are considered to contain Chinook Salmon and should be attributed with a “Y”. SLM_SCK Sockeye Salmon occurrence Y, YP, N, M1 Sockeye Salmon use the Salmon River as a migration corridor between the Pacific Ocean and lakes in Stanley Basin. Therefore, the Salmon River is attributed with a “Y”. Additional stream reaches may be attributed with a “Y” if they are used by Sockeye Salmon. These will typically be the lower ends of tributaries to the Salmon River where juvenile sockeye may seek thermal refugia. Sockeye Salmon do not occur in the Big Lost River, Little Lost River, Birch Creek, or Wood River basins. SLM_KOK Kokanee occurrence Y, YP, N, M1 All O. nerka are considered to be Kokanee in the Big Lost River, Little Lost River, Birch Creek, or Wood River basins, and in some cases, within the Salmon River basin. O. nerka are considered to be Kokanee in the Salmon River basin if there is clear evidence they cannot move to the Pacific Ocean and then return to the same stream reach. MTN_WF_SR Mountain Whitefish, Salmon River basin occurrence Y, YP, N, M1 Any Mountain Whitefish in the Salmon River basin. This field should not be used for Mountain Whitefish in the Big Lost River basin. MTN_WF_BL Mountain Whitefish, Big Lost River basin occurrence Y, YP, N, M1 Any Mountain Whitefish in the Big Lost River basin. These fish are separated from other Mountain Whitefish because they constitute a unique form of Mountain Whitefish and Mountain Whitefish in the Big Lost River basin are designated as a Forest Service sensitive species. This field should not be used for Mountain Whitefish in the Salmon River basin. GRAYLING Arctic Grayling occurrence Y, YP, N, M1 SCLPN_UKN Sculpin, any species occurrence Y, YP, N, M1 Attributed as a “Y” if any sculpin species is present or the specific species is not known. SCLPN_MOTT Mottled Sculpin occurrence Y, YP, N, M1 Present only in the Salmon River basin. Generally in medium to large streams. SCLPN_PTE Paiute Sculpin occurrence Y, YP, N, M1 Present only in the Big Lost River basin. SCLPN_SHTH Shorthead Sculpin occurrence Y, YP, N, M1 An analysis of sculpin species distribution data indicated that Shorthead Sculpin are present in most streams that contain sculpin on the Forest. Therefore, if sculpin are present in a stream, it is likely that at least some of them are Shorthead Sculpin. If sculpin were present in a reach I assumed they were Shorthead Sculpin and coded this field with a “Y” unless sampling data indicated otherwise (eg – some streams in the Big Lost River basin). SCLPN_TRNT Torrent Sculpin occurrence Y, YP, N, M1 Present only in the Salmon River basin. Generally in large streams. SUCKER_UKN Sucker, any species occurrence Y, YP, N, M1 Attributed as a “Y” if any sucker species is present or the specific species is not known. SUCKER_BLP Bridgelip Sucker occurrence Y, YP, N, M1 SUCKER_LGS Largescale Sucker occurrence Y, YP, N, M1 SUCKER_MTN Mountain Sucker occurrence Y, YP, N, M1 DACE_UKN Dace, any species occurrence Y, YP, N, M1 Attributed as a “Y” if any dace species is present or the specific species is not known. DACE_LONG Longnose Dace occurrence Y, YP, N, M1 DACE_SPECK Speckled Dace occurrence Y, YP, N, M1 DACE_LPD Leopard Dace occurrence Y, YP, N, M1 DACE_UMA Umatilla Dace occurrence Y, YP, N, M1 NRTH_PKMW Northern Pikeminnow occurrence Y, YP, N, M1 RED_SHNR Redside Shiner occurrence Y, YP, N, M1 PAC_LAMP Pacific Lamprey occurrence Y, YP, N, M1 W_STRGN White Sturgeon occurrence Y, YP, N, M1 CHISELM Chiselmouth occurrence Y, YP, N, M1 BASS Smallmouth Bass occurrence Y, YP, N, M1 CARP Common Carp occurrence Y, YP, N, M1 TRT_TIG Tiger Trout occurrence Y, YP, N, M1 TIG_MUS Tiger Muskellunge occurrence Y, YP, N, M1 FISH_PRESE Any fish present Y or N This should be attributed with a “Y” if any species is attributed with a “Y”, “YP”, or “M” HIST_BULL DELETE DELETE DELETE ST_SP Steelhead spawning Y or N Rename SP_STH BULL_SP Bull Trout spawning Y or N Rename SP_BULL CHNK_SP Chinook Salmon spawning Y or N Rename SP_CHNK TRT_CUTT_SP DELETE DELETE DELETE MTN_WHTFSH_SP DELETE DELETE DELETE DCH_STEEL Steelhead Designated Critical Habitat Y or N Rename DCH_STH PDCH_BT DELETE DELETE DELETE FINAL_DCH_BT Bull Trout Designated Critical Habitat Y or N Rename DCH_BULL DCH_CHNK2 Chinook Salmon Designated Critical Habitat Y or N Rename DCH_CHNK SOURCECODE DELETE DELETE DELETE SOURCEDOC DELETE DELETE DELETE MILES Length of arc in miles Number Calculated using ArcMap LENGTHKM Length of arc in km Number Calculated using ArcMap DCH_SLM_SC Sockeye Salmon Designated Critical Habitat Y or N Rename DCH_SCK and group with other DCH fields RHCA REV_DATE SHAPE_LEN 1 The species fields should be attributed as follows: • Y: The species has been documented in the stream reach. • YP: The species has not been documented in the stream reach but it likely occurs in the stream reach. This attribute is generally used when fish data are not available for a stream reach. This determination is based on the professional judgement of a fish biologist. • M: The species has not been documented in the stream reach but likely migrates through it. This is generally used for Bull Trout and Westslope Cutthroat Trout. • N: The species has not been documented or likely does not occur in the stream reach.

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 1000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: true

HasM: true

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field: STRM_TYPE

Fields:
Types:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 1/7/2022 7:00:35 PM

Schema Last Edit Date: 1/7/2022 7:00:35 PM

Data Last Edit Date: 1/7/2022 7:00:35 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat