Oregon Rivers (River Reach)

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: WDFW, IDFG, and ODFW.
Publication_Date: 2001
Title: Oregon Rivers (River Reach)
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Source Scale 1:100000.

PSMFC has, via the StreamNet project, made several major enhancements in the PNW River Reach file which are now incorporated in the system. The major enhancement has been the addition of a new attribute which allows for the development and use of a stream based routing system.

The impetus and methodology for deriving the new stream based identifier was developed by an interagency committee that was formed under the Presidentís 1993 Forest Plan. The Interorganizational Resource Information Coordinating Council (IRICC), comprised of representatives from federal, state, tribal, and local entities, was tasked with developing data standards that could be used across agency boundaries that would facilitate implementation of the Forest Plan. They recognized that for stream related data, a comprehensive and regionally standard hydrologic system was necessary to ensure that data could be readily collected and shared between agencies. They further recognized that the utility of such a system would be greatly enhanced if a method for identifying a given stream within the hydrologic coverage was available. After looking at the various options available in the region, the IRICC group officially adopted the PNW Reach File system as the base hydrologic layer and developed a new attribute called the Longitude/ Latitude ID (LLID) for use in uniquely identifying streams. This attribute consists of the longitude and latitude of the mouth of the stream. All reaches (or arcs) that comprise a given stream were to be assigned a unique LLID. Longitude would precede latitude to conform with standard x,y ordering. The code will be 13 characters long, with 7 for decimal degrees of longitude and 6 for decimal degrees of latitude, with implied decimal points. After the IRICC decision, a fast track effort was put in place to add the new LLID field to the PNW Reach File and this effort is largely complete (all streams in OR and WA, all named streams in ID and MT). In the PNW Reach File a stream is defined a series of contiguous arcs comprising a waterway with identical values in the FEAT_NAME field. Only arcs representing the transport path of water (stream, braided stream, some canals, and centerlines and connector arcs within lakes and reservoirs) with a SAVENEG value of NO were included. For features that were unnamed, stream IDís were applied visually using best professional judgment.

StreamNet has used the new LLID as the basis for building a regionally consistent stream routing system. By using this routing system, one can exploit the benefits of ArcInfoís dynamic segmentation, including the use of event tables for data collection and sharing. We believe this is a significant enhancement to the reach file which will greatly facilitate its use.

Online_Linkage: <http://www.oregon.gov/DAS/IRMD/GEO/sdlibrary.shtml>
Description:
Abstract:
These files incorporate changes and corrections to the 100k Reach Files originally posted on this site in the fall of 1997. Numerous routing errors have been corrected, flow direction of routes and arcs has been made consistent, and attribute miscodes have been addressed. In addition, the files maintained by WDFW, IDFG, and ODFW have been made consistent, especially in the hucs along the state borders. All of the LLIDs in these coverages have been approved by the state fish and wildlife agencies, and will be kept unchanged unless compelling reasons necessitate updates. Some routes may have LLIDs different than those posted in earlier versions, but every effort has been made to minimize this as much as is practical. Archival versions of the previous reach files can be made available to help in any updates to event data or other databases using the LLID attribute.
Purpose:
The U.S. Geological Survey (USGS) in Portland, in cooperation with Bonneville Power Administration, the Northwest Power Planning Council, and other Federal and state agencies and NW Indian Tribes produced a 1:100,000-scale River Reach data layer for the Pacific Northwest in the early 1990s. The Pacific Northwest (PNW) River Reach Files are a geo-referenced river reach data layer that encompasses the Columbia RiverBasin within the conterminous United States, the coasts of Oregon and Washington, Puget Sound in Washington, the Klamath and Goose Lake Basins in southern Oregon and the Bear Lake Basin in southeastern Idaho. The system is basically a 1:100,000 scale enhancement of the pre-existing 1:250,000 scale EPA River Reach File 2 (RF2).
Supplemental_Information:
This process was a primary task of the PNW River Reach Project because these reach identifiers are an integral hydrologic component in a regional rivers and fisheries information system now known as StreamNet (formerly the Coordinated Information System (CIS) and the Northwest Environmental Database (NED)). StreamNet is an ongoing effort by federal, state, and tribal organizations within the region to compile reach and stream specific information pertinent to the Regionís fish and wildlife resources in Oregon, Idaho, Washington, and Montana. The PNW Reach Files carry the U.S. Environmental Protection Agency's (US EPA) river reach numbers. The system was transferred over to the StreamNet project at Pacific States Marine Fisheries Commission (PSMFC) in early 1997 for maintenance, enhancement, and distribution. PSMFC is also the lead contractor responsible for supervising the integration and conversion of the PNW Reach Files into the new National Hydrography Dataset. This particular version contains only the streams in Oregon and its overlapping HUCs. It was provided to the OGDC by the Oregon Department of Fish and Wildlife.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2001
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -124.800375
East_Bounding_Coordinate: -115.572523
North_Bounding_Coordinate: 46.530524
South_Bounding_Coordinate: 41.126895
Keywords:
Theme:
Theme_Keyword_Thesaurus: None.
Theme_Keyword: hydrography
Theme_Keyword: rivers
Theme_Keyword: river reach
Theme_Keyword: water resources
Theme_Keyword: fish and wildlife
Place:
Place_Keyword: PNW
Place_Keyword: Oregon
Place_Keyword: Idaho
Place_Keyword: Montana
Temporal:
Temporal_Keyword: 2001
Access_Constraints: None
Use_Constraints:
Many different types of GIS analysis can be performed on the Reach Files. These might include buffering around reaches, stream network routing, basin characteristics analysis or dynamic segmentation. Furthermore, the system provides an ideal environment for storing, organizing, and displaying stream related fisheries and habitat data.
Browse_Graphic:
Browse_Graphic_File_Name: <http://navigator.state.or.us/sdl/data/image/k100/rivers.html>
Browse_Graphic_File_Description: Oregon Rivers (River Reach)
Browse_Graphic_File_Type: JPEG
Data_Set_Credit:
MARTIN HUDSON - WASHINGTION DEPARTMENT OF FISH AND WILDLIFE KEITH HUPPERTS, BRENT FORSBERG, AND JON BOWERS - OREGON DEPARTMENT OF FISH AND WILDLIFE BART BUTTERFIELD - IDAHO DEPARTMENT OF FISH AND GAME JEFF HUTTEN AND STEVE CARSON - MONTANA DEPARTMENT OF FISH, WILDLIFE, AND PARKS
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.1.0.722
Cross_Reference:
Citation_Information:
Originator: River Reach Project
Title: PNW River Reach File Documentation
Online_Linkage: <http://navigator.state.or.us/sdl/data/metadata/k100/rivers.pdf>

Data_Quality_Information:
Lineage:
Process_Step:
Process_Description:
Read 100K hydrography DLGs for each map into GIS. 2. Edgematch north and west edges of each map to adjacent 100K quads. 3. CLIP each 100K quad with adjusted Hydrologic Unit boundary. 4. APPEND clipped quad pieces together. 5. Correct internal node errors using automated snapping. 6. Remove non-attributed pseudo nodes. 7. Copy polygons to Waterbody coverage. 8. Edit out double-banked streams, shorelines, and braided areas and put into Water bodies coverage. 9. Add centerlines through waterbodies and wide streams and connector arcs from centerlines to tributaries. 10. Create Trace coverage from EPA Reach File. 11. Edit Trace, correcting stream names and topologic structure where 12. Adjust Trace segment endpoints to align with corresponding 100K endpoint. 13. CONFLATE (Transfer) Trace-ID from Trace reaches to corresponding reaches in 100K coverage. 14. Make check plots to verify results of conflation. 15. Transfer EPA extended attributes (SEG, LEVEL, SEQNUM, FLAG) to 100K reaches. 16. Assign unconflated 100K reaches a provisionary reach code. 17. Move provisionary codes to SEG. 18. Add State, County, and quad boundary items to reaches in 100K-scale Reach File. 19. Compute sinuosity for each reach. 20. Block man-made waterways, braided reaches, and other features determined as not part of the basin network by calculating their LENGTH item to negative. 21. Determine allocation centers. Usually mouth of basin. 22. ALLOCATE from centers. 23. WRITEALLOCATION ROUTING results to Reach File Arc Attribute Table. 24. Use DIRECTION item to flip reaches to flow in a downstream direction 25. Calculate PNTR# to internal record number of Arc Attribute Table 26. Unblock previously blocked arcs. 27. Calculate river mile for allocated reaches.

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 38881

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Lambert Conformal Conic
Lambert_Conformal_Conic:
Standard_Parallel: 43.000000
Standard_Parallel: 45.500000
Longitude_of_Central_Meridian: -120.500000
Latitude_of_Projection_Origin: 41.750000
False_Easting: 1312335.958000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.004096
Ordinate_Resolution: 0.004096
Planar_Distance_Units: international feet
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: rivers
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: STREAMS_
Attribute:
Attribute_Label: STREAMS_ID
Attribute:
Attribute_Label: LLID
Attribute:
Attribute_Label: NAME
Overview_Description:

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Data Administrator
Contact_Organization: Geospatial Enterprise Office
Contact_Position: Data Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: 955 Center St. NE Room 470
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Contact_Voice_Telephone: 503.378.2166
Contact_Electronic_Mail_Address: gis at gis.state.or.us
Hours_of_Service: 8:00am - 5:00pm M-F
Resource_Description: Downloadable Data
Distribution_Liability:
The Oregon Geospatial Data Clearinghouse (OGDC), the State of Oregon or any of the data providers cannot accept any responsibility for errors, omissions, or positional accuracy in the digital data or underlying records. There are no warranties, expressed or implied, including the warranty of merchantability or fitness for a particular purpose, accompanying any of these products.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
File_Decompression_Technique:
The files were subsequently compressed using Info-Zip's free version of Zip. This archiving method is compatable with the familiar PKZip. You can download compiled Unzip binaries for many systems from the uunet archive.
Transfer_Size: 34.157
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://navigator.state.or.us/sdl/data/shapefile/k100/rivers.zip>
Access_Instructions: Access via HTTP with web browser
Digital_Form:
Digital_Transfer_Information:
Format_Name: ARC/Info Export File
File_Decompression_Technique:
The files were subsequently compressed using Info-Zip's free version of Zip. This archiving method is compatable with the familiar PKZip. You can download compiled Unzip binaries for many systems from the uunet archive.
Transfer_Size: 220kb
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://navigator.state.or.us/sdl/data/e00/k100/rivers.zip>
Access_Instructions: Access via HTTP with web browser

Metadata_Reference_Information:
Metadata_Date: 20060919
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Geospatial Enterprise Office
Contact_Person: Data Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: 955 Center St. NE Room 470
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Contact_Voice_Telephone: 503.378.2166
Contact_Electronic_Mail_Address: gis at gis.state.or.us
Hours_of_Service: 8:00am - 5:00pm M-F
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.8.6 on Tue Sep 19 13:07:41 2006