ArcGIS REST Services Directory Login

Layer: Steelhead (Upper Willamette River DPS) (ID: 80)

Parent Layer: Steelhead (Upper Willamette River DPS)

Name: Steelhead (Upper Willamette River DPS)

Display Field: DPS

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The base geospatial information is the Watershed Boundary Dataset (WBD), which was queried by two 2-digit "regions" HU 17 (Pacific Northwest) and HU 18 (California), and downloaded in June 2012. The WBD HU 17 "region" included transboundary hydrologic data, or HUs that cross the U.S.-Canadian border. The WBD data were merged with "Assessment Watersheds" for the Slocan River drainage in British Columbia, north of the transboundary HUs, to represent areas historically occupied by fish.There are 5 objects stored in this geodatabase:hydrologic (feature class)link (table)DPS (table)population (table)fish (feature class)The hydrologic feature class is the base geospatial data from the Watershed Boundary Dataset and British Columbia Assessment Watersheds. Some of the hydrologic polygon features have been split to better represent fish populations. No overlapping polygons.The link table contains the relationships between spatial and tabular data.The DPS table contains information on Distinct Population Segments, which are the listed entities under the Endangered Species Act. A DPS can be further refined to an entity called an Evolutionarily Significant Unit (ESU) for salmon. An ESU can also be a listed entity under the Endangered Species Act. For purposes of this database, DPSs and ESUs are included in this single table.The population table contains fish units smaller than the steelhead DPSs and salmon ESUs. The fish feature class is the end product to be used for visualisation of fish data. It was generated in 4 steps. Step 1: used the Make Query Table tool (ArcToolbox 10.2.2 -> Data Management Tools -> Layers and Table Views -> Make Query Table) to combine the hydrologic feature class with the link table (query is based on unique FEATURE_ID). Step 2: joined the DPS table (join is based on unique DPS_ID). Step 3: joined the population table (join is based on unique WCR_POP_ID). Step 4: exported the result to make a permanent fish feature class in the geodatabase because joins are temporary. The fish feature class has overlapping polygons for species located in the same geographic areas and for species with multiple run timings.Coded value domains are utilized in this geodataase for numerous fields. In order to export any geodatabase tables with the values (not the codes), use the Table to Excel tool (ArcToolbox 10.2.2 -> Conversion Tools -> Excel -> Table to Excel). In the tool options, check the box for "Use domain and subtype description".

Definition Expression: N/A

Copyright Text: Geodatabase version 1.0 was designed and populated by Shanna Dunn, completed December 2015. The information reviewed during the data assessment and used to compile this geodatabase came from a variety of sources. Credits go to the participants of Biological Review Teams and Technical Recovery Teams, recovery planning teams, staff from the West Coast Region, Northwest Fisheries Science Center, and Southwest Fisheries Science Center, external partners, and especially the states and tribes for collecting groundtruthed fish distribution data. The StreamNet 2012 data was used extensively during processing. Credit also goes to the United States Geological Survey and the Natural Resources Conservation Service for producing and maintaining the Watershed Boundary Dataset and National Hydrography Dataset, which together make it possible to consistently map fish geography.

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Supported Operations:   Query   Generate Renderer   Return Updates