Description: This map depicts the approximate location of dams in the state of Oregon that the State has statutory authority over. These are dams that are greater than or equal to 10-feet in height and store greater than or equal to 9.2-acre-feet of water behind them. The Oregon Water Resources Department updated the data in 2014.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B523FED78-1B44-4E27-8E86-FD0C63FD7C53%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/oregon_dams_2014.zip
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. This dataset complies with version 1.1 of the OFBPDS data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. The OFPBDS dataset now contains over 40,000 barrier features from 19 separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), Oregon Department of Land Conservation and Development (DLCD) US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county, Lower Columbia River Estuary Partnership and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2019, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed or replaced (e.g. dam removals and culvert replacements) is published simultaneously with the OFPBDS dataset. The OFPBDS database is the most comprehensive compilation of fish passage barrier information in Oregon however, it does NOT represent a complete and current record of every fish passage barrier within the state. Efforts to address deficiencies in data currency, completeness and accuracy are ongoing and are often limited by lack of sufficient resources. Attributes (including key attributes such as fish passage status) are often unknown or incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset current, comprehensive and accurate. Fish passage status is a key attribute. Many barrier features have an unknown passage status. For other features, the passage status may have changed since it was originally documented. Note that this metadata file is best viewed in ArcCatalog. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Metadata
https://spatialdata.oregonexplorer.info/osdl-geoportal/rest/document?id=%7B7A58ECF2-6A7F-4F1D-B9D4-6DD5BEA9E2D3%7D
Download
https://oe.oregonexplorer.info/externalcontent/spatialdatafordownload/ODFW_44_5_ofpbds_shp.zip
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), Oregon Department of Land Conservation and Development (DLCD) US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county, Lower Columbia River Estuary Partnership and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. This dataset complies with version 1.1 of the OFBPDS data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. The OFPBDS dataset now contains over 40,000 barrier features from 19 separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), Oregon Department of Land Conservation and Development (DLCD) US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county, Lower Columbia River Estuary Partnership and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2019, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed or replaced (e.g. dam removals and culvert replacements) is published simultaneously with the OFPBDS dataset. The OFPBDS database is the most comprehensive compilation of fish passage barrier information in Oregon however, it does NOT represent a complete and current record of every fish passage barrier within the state. Efforts to address deficiencies in data currency, completeness and accuracy are ongoing and are often limited by lack of sufficient resources. Attributes (including key attributes such as fish passage status) are often unknown or incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset current, comprehensive and accurate. Fish passage status is a key attribute. Many barrier features have an unknown passage status. For other features, the passage status may have changed since it was originally documented. Note that this metadata file is best viewed in ArcCatalog. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Metadata
https://spatialdata.oregonexplorer.info/osdl-geoportal/rest/document?id=%7B7A58ECF2-6A7F-4F1D-B9D4-6DD5BEA9E2D3%7D
Download
https://oe.oregonexplorer.info/externalcontent/spatialdatafordownload/ODFW_44_5_ofpbds_shp.zip
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), Oregon Department of Land Conservation and Development (DLCD) US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county, Lower Columbia River Estuary Partnership and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: This polyline feature class depicts the river corridors of each Wild and Scenic River designated by Congress or the Secretary of the Interior for the United States and Puerto Rico. This GIS data layer was created from a mulit-agency effort by the US Forest Service, National Park Service, Bureau of Land Managment, and the US Fish and Wildlife Servce. The spatial data were referenced to the latest High Resolution National Hydrological Data Layer (NHD 1:24,000 Scale or better), published by United States Geological Survey (USGS).
Metadata
https://data-usfs.hub.arcgis.com/datasets/usfs::national-wild-and-scenic-river-lines-feature-layer/about
Description: 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. Metadata: http://oe.oregonexplorer.info/ExternalContent/metadata/rivers100k.pdf
Download: http://navigator.state.or.us/sdl/data/shapefile/k100/rivers.zip
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: bold Font Decoration: none
Description: 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. Metadata: http://oe.oregonexplorer.info/ExternalContent/metadata/rivers100k.pdf
Download: http://navigator.state.or.us/sdl/data/shapefile/k100/rivers.zip
Description: This metadata describes watercourses data for the Oregon Framework Hydrography data and the standard system used to identify the states' surface water. The Watercourses (WC) layer consists of stream, canal, flume, pipeline and other linear hydrographic feature centerlines. Where these features (especially streams) are represented as double lined features at the source scale they are represented in this layer by their centerline. Streams that flow through water bodies such as lakes and reservoirs are also represented by a centerline. Metadata: http://oe.oregonexplorer.info/ExternalContent/metadata/wc.xml
Download: http://navigator.state.or.us/sdl/data/shapefile/k24/water_courses.zip
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Description: This metadata describes watercourses data for the Oregon Framework Hydrography data and the standard system used to identify the states' surface water. The Watercourses (WC) layer consists of stream, canal, flume, pipeline and other linear hydrographic feature centerlines. Where these features (especially streams) are represented as double lined features at the source scale they are represented in this layer by their centerline. Streams that flow through water bodies such as lakes and reservoirs are also represented by a centerline. Metadata: http://oe.oregonexplorer.info/ExternalContent/metadata/wc.xml
Download: http://navigator.state.or.us/sdl/data/shapefile/k24/water_courses.zip
Description: This layer was created by CLAMS to improve the existing stream layers which were too coarse, positionally inaccurate, and of limited extent. Also, this stream layer is registered with a Digital Elevation Model (DEM) to allow for better integration with landslide and debris flow models and improved determination of attributes such as: 1. an indication of amount and direction of flow 2. extent of anadromous fish distribution 3. gradient 4. valley floor width.
Metadata
http://oe.oregonexplorer.info/metadata/streamsClams.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/NCE_nip_streams_clams.zip
Description: This metadata describes water point data for the Oregon Framework Hydrography data and the standard system used to identify the states' surface water. The Water Points (WP) layer is the repository for springs, seeps and other hydrographic features with limited spatial extent (i.e. most easily represented by a point).
Metadata:
http://oe.oregonexplorer.info/metadata/hydrowaterpoints.htm
Download:
http://www.pnwhf.org/nat-hyd-dataset.aspx
Description: Water body data for the Oregon Framework Hydrography data and the standard system used to identify the state's surface water. The Water Bodies (WB) layer consists of sounds, bays, lakes, ponds, wetlands, reservoirs, inundation areas, the double lined portions of streams and other hydrographic features best represented as areas.
Metadata: http://oe.oregonexplorer.info/ExternalContent/metadata/wb_24k.xml
Download: http://navigator.state.or.us/sdl/data/shapefile/k24/water_bodies.zip
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 1249999.9999999898 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [name] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 750000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [name] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 500000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [name] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 150000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [name] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: DLG's depict information about geographic features on or near the surface of the Earth, terrain, and political and administrative units. These data were collected as part of the National Mapping Program.
Metadata: http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={3A2D5A62-8A3B-4F4E-8F45-DC5212DD6857}
Download: http://navigator.state.or.us/sdl/data/shapefile/m2/waterbodies.zip
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 5000000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [LANDNAME] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 3000000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [LANDNAME] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 1500000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [LANDNAME] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 500000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [LANDNAME] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 100000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [LANDNAME] Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: The purpose of this project is to collect and distribute data on the glaciers of the American West, exclusive of Alaska.
These data were compiled for public use from the USGS 1:100,000 scale digital line graphs and digital raster graphics. While there are no explicit constraints on the use of the data, please exercise appropriate judgement in the use and interpretation of these data. Public domain data from Portland State University are freely redistributable with proper metadata and source attribution.
Metadata: http://oe.oregonexplorer.info/metadata/oregon_glaciers.htm
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: The Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" “Standard” (http://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications.
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: Funding for the Watershed Boundary Dataset (WBD) was provided by the USDA-NRCS, USGS and EPA along with other federal, state and local agenciesies. Representatives from many agencies contributed a substantial amount of time and salary towards quality review and updating of the dataset in order to meet the WBD Standards. Acknowledgment of the originating agencies would be appreciated in products derived from these data. See dataset specific metadata for further information
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This feature contains a spatial representation of lakes, ponds, and reservoirs with water quality information from Oregon’s 2012 Integrated Report Assessment Database and 303(d). Water bodies in this feature are represented as polygons and the attribute table contains the assessment data associated with that water body. A water body may have assessment information for multiple pollutants or conditions, and may have multiple data records associated with the spatial representation of the water body or segment of the water body. Oregon’s 2012 Integrated Report Assessment Database and 303(d) List are available on-line at http://www.deq.state.or.us/wq/assessment/rpt2012/search.asp. The on-line searchable database should be used in conjunction with this geodatabase, and is the reference source to verify all attribute information about water quality and to obtain assessment information about water bodies that do not have georeferenced locations. Users may contact DEQ for information about Oregon’s water quality assessment process, additional updates to the 2012 IR, and the schedule for future water quality integrated reports. http://www.deq.state.or.us/wq/assessment/assessment.htm. A ReadMe file accompanies the geodatabase and users are encouraged to see the document for additional details.
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: This data set was assembled by the Oregon Department of Environmental Quality, Water Quality Division, Standards and Assessments Section.
Description: This feature contains a spatial representation of streams and stream segments with water quality information from Oregon’s 2012 Integrated Report Assessment Database and 303(d) List. This feature should be used in conjunction with the feature OR_Lakes_WaterQuality_2012. A water body may have assessment information for multiple pollutants or conditions, and may have multiple data records associated with the spatial representation of the water body or segment of the water body. Oregon’s 2012 Integrated Report Assessment Database and 303(d) List are available on-line at http://www.deq.state.or.us/wq/assessment/rpt2012/search.asp. The on-line searchable database should be used in conjunction with these features, and is the reference source to verify all attribute information about water quality and to obtain assessment information about water bodies that do not have georeferenced locations. Users may contact DEQ for information about Oregon’s water quality assessment process, additional updates to the 2012 IR, and the schedule for future water quality integrated reports. http://www.deq.state.or.us/wq/assessment/assessment.htm . Note: Duplicate RecordIDs exist in the dataset due to an EPA listing error. This includes Record #s 6550, 8025, 20340, 20847, and 21121 in the data. A ReadMe file accompanies the geodatabase and users are encouraged to see the document for additional details.
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: This data set was assembled by the Oregon Department of Environmental Quality, Water Quality Division, Standards and Assessments Section.
Description: This feature contains a spatial representation of lakes, ponds, and reservoirswith water quality information from Oregon’s 2010 Integrated Report Assessment Database and 303(d) List as approved by EPA on March 15, 2012. Water bodies in this feature are represented as points at the centroid of a polygon and the attribute table contains the assessment data associated with that water body. Spatial information for the water bodies as polygons is provided in the feature ORLakesAssessed_2010. These features should be used in conjunction with the feature ORStreamsWaterQuality_2010. A water body may have assessment information for multiple pollutants or conditions, and may have multiple data records associated with the spatial representation of the water body or segment of the water body. Oregon’s 2010 Integrated Report Assessment Database and 303(d) List are available on-line at www.deq.state.or.us/wq/assessment/rpt2010/search.asp. The on-line searchable database should be used in conjunction with this geodatabase, and is the reference source to verify all attribute information about water quality and to obtain assessment information about water bodies that do not have georeferenced locations. Users may contact DEQ for information about Oregon’s water quality assessment process, additional updates to the 2010 IR, and the schedule for future water quality integrated reports. This layer does not include additions to the 303(d) list that were proposed by EPA in March 2012.A ReadMe file accompanies the geodatabase and users are encouraged to see the document for additional details.
Metadata:
http://oe.oregonexplorer.info/ExternalContent/metadata/waterqualitylakes.xml
Download:
http://navigator.state.or.us/sdl/data/mdb/k100/WQ_2010_Report.zip
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: This data set was assembled by the Oregon Department of Environmental Quality, Water Quality Division, Standards and Assessments Section.
Description: This feature contains a spatial representation of streams and stream segments with water quality information from Oregon’s 2010 Integrated Report Assessment Database and 303(d) List as approved by EPA on March 15, 2012. This feature should be used in conjunction with the feature ORLakesWaterQuality_2010. A water body may have assessment information for multiple pollutants or conditions, and may have multiple data records associated with the spatial representation of the water body or segment of the water body. Oregon’s 2010 Integrated Report Assessment Database and 303(d) List are available on-line at www.deq.state.or.us/wq/assessment/rpt2010/search.asp. The on-line searchable database should be used in conjunction with these features, and is the reference source to verify all attribute information about water quality and to obtain assessment information about water bodies that do not have georeferenced locations. Users may contact DEQ for information about Oregon’s water quality assessment process, additional updates to the 2010 IR, and the schedule for future water quality integrated reports. www.deq.state.or.us/wq/assessment/assessment.htm. This feature does not include additions to the 303(d) list that were proposed by EPA in March 2012.A ReadMe file accompanies the geodatabase and users are encouraged to see the document for additional details.
Metadata:
http://oe.oregonexplorer.info/ExternalContent/metadata/waterqualitystreams.xml
Download:
http://navigator.state.or.us/sdl/data/mdb/k100/WQ_2010_Report.zip
Service Item Id: ddc345cb31a744b980fb5c1a9da6221e
Copyright Text: This data set was assembled by the Oregon Department of Environmental Quality, Water Quality Division, Standards and Assessments Section.
Description: This is the most comprehensive water quality dataset of the Metolius River Basin. This point spatial data layer represents the water quality data collected from 35 sampling locations throughout the Metolius River Basin over the past 15 years. The Metolius River basin is a sub-basin of the Deschutes Basin within Central Oregon. The water quality parameters are E. coli, dissolved oxygen, nitrate, nitrite, phosphate, phosphorus, pH, etc. The data from several different sources in many different formats were processed and compiled within the Microsoft Access environment. The compiled water quality master table was spatially linked to the point spatial data created based on the geographic coordinate information of sampling locations collected using geographic positioning systems.
Metadata
http://oe.oregonexplorer.info/metadata/MetoliusWaterQuality.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/iw_or_metoliuswaterquality.zip
Description: This map was created to delineate the extent of the active channel and other floodplain features for the Willamette River, Oregon, for the year 1995. The extent of the active channel and features such as alcoves, secondary channels, remnant ponds, and islands were based on digital orthophotographs acquired in 1994-1995. Water bodies (primarily main and secondary channels) were digitized from the photos and interpreted for channel type.
Metadata: http://spatialdata.oregonexplorer.info/GPT9/catalog/search/resource/details.page?uuid={363D8857-204E-4B2F-9008-95395F47310A}
Download: http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/WRB_Channel_1995.zip
Description: This map was created to delineate the extent of the active channel and other floodplain features for the Willamette River, Oregon, for the year 1932. The extent of the active channel and features such as alcoves, secondary channels,and islands were based on US Army Corps of Engineers river survey maps from 1928-1932. Water bodies (primarily main and secondary channels) were captured from the maps and interpreted for channel type.
Metadata: http://spatialdata.oregonexplorer.info/GPT9/catalog/search/resource/details.page?uuid={677EE052-5F6B-46F4-B1F7-E940E2195254}
Download: http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/WRB_Channel_1932.zip
Description: This map was created to delineate the extent of the active channel and other floodplain features for the Willamette River, Oregon, for the year 1895. The extent of the active channel and features such as alcoves, secondary channels,and islands were based on US Army Corps of Engineers river survey maps from 1895. Water bodies (primarily main and secondary channels) were captured from the maps and interpreted for channel type.
Metadata: http://spatialdata.oregonexplorer.info/GPT9/catalog/search/resource/details.page?uuid={FD273244-D684-4C79-AE87-B510D3FE2D7F}
Download: http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/WRB_Channel_1895.zip
Description: This map shows the extent of the active channel and other floodplain features for the Willamette River, Oregon, for the year 1850. The extent of the active channel and features such as alcoves, secondary channels, and islands were based on The Nature Conservancy's estimated natural vegetation of Willamette Valley (1851) land cover digital data. Water bodies (river and floodplain) were captured from the vegetation coverage and interpreted for channel type.
Metadata: http://oe.oregonexplorer.info/metadata/WR_Historic_1850.htm
Download: http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/WRB_Channel_1850.zip