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.
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.
fpbMltFtr (type: esriFieldTypeString, alias: fpbMltFtr, SQL Type: sqlTypeOther, length: 7, nullable: true, editable: true, Coded Values: [yes: multiple features at road - stream xing], [no: single feature], [unknown: Number of features unknown])
fpbFPasSta (type: esriFieldTypeString, alias: fpbFPasSta, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true, Coded Values: [Blocked: Not passable], [Partial: Partially passable - a barrier to at least some fish at some time], [Passable: Completely passable], ... 2 more ...)
fpbFySta (type: esriFieldTypeString, alias: fpbFySta, SQL Type: sqlTypeOther, length: 20, nullable: true, editable: true, Coded Values: [FuncNonCrit: Functioning – does not meet current criteria], [NeedsMaintNonCrit: Needs repair or maintenance and does not meet current state or NMFS fish passage criteria], [Abandoned: Abandoned fishway - no longer needed (e.g. fishway at natural falls)], ... 7 more ...)
fpbFtrSTy (type: esriFieldTypeString, alias: fpbFtrSTy, SQL Type: sqlTypeOther, length: 30, nullable: true, editable: true, Coded Values: [DamPermanent: Dam - permanent throughout the year], [DamSeasonal: Dam - in place for only part of the year], [OpenArch: Culvert - open arch], ... 14 more ...)
fpbFtrNmSr (type: esriFieldTypeString, alias: fpbFtrNmSr, SQL Type: sqlTypeOther, length: 5, nullable: true, editable: true, Coded Values: [GNIS: Geographic Names Information System], [other: Other source than GNIS])
fpbModTy (type: esriFieldTypeString, alias: fpbModTy, SQL Type: sqlTypeOther, length: 10, nullable: true, editable: true, Coded Values: [Baffles: Baffles - feature added to a culvert to increase the hydraulic roughness], [StreamSim: A channel that simulates characteristics of the adjacent natural stream channel], [Weirs: Weirs - feature built across a stream to raise its level], ... 2 more ...)
fpbFyTy (type: esriFieldTypeString, alias: fpbFyTy, SQL Type: sqlTypeOther, length: 15, nullable: true, editable: true, Coded Values: [Pool: Pool style fishways have a series of distinct pools in which the energy of the flow entering each one is entirely dissipated prior to flowing to the next.], [BaffledChute: Chutes or flumes with roughness, designed to reduce velocity, allowing fish passage.], [Hybrid: Combination of multiple fishway types.], ... 4 more ...)
fpbFySTy (type: esriFieldTypeString, alias: fpbFySTy, SQL Type: sqlTypeOther, length: 20, nullable: true, editable: true, Coded Values: [PoolVertSlot: Vertical slot], [PoolAndWeir: Pool and weir], [PoolWeirOrifice: Weir and orifice], ... 18 more ...)