OR/WA Hydrography Framework Partnership 2006/06/20 vector digital data Portland, Oregon OR BLM Server=ilmorso0db5; Service=5162; User=osodba; Version=SDE.DEFAULT This metadata describes watercourses data in publication format for the Washington and 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. This publication format is intended to improve the usability of the 1:24,000 hydrography dataset and associated attributes that are currently stored as event tables within the PNW Hydrography Framework dataset and/or as reaches within the Aquatic Resource Information Management System (ARIMS). Attributes that are commonly used by BLM's field organization are provided in this publication format as attributes on polygons, lines, and points. This is an initial deployment of the publication format. Modifications, additions, and subtractions to its content will be made based on field staff experience with the dataset. The publication format includes only the most commonly used attribute information. Less commonly used attributes are available from the Clearinghouse dataset and ARIMS. The overhead required to extract the data from the Clearinghouse and ARIMS for this publication dataset is an important factor in its design. It is recognized that a multitude of publication formats are possible to simplify and improve the usability of the complex hydrography dataset. A decision was made to not include a separate representation of the hydrography data to specifically meet cartographic requirements. This may be added in the future as these requirements are refined. The Pacific Northwest Hydrography Framework Clearinghouse, may be described as a central data repository where partners co-manage the interagency hydrography and watershed boundary data layer(s). Updates are submitted in a controlled environment and the resulting dataset is available to all for analysis and mapping purposes. Because of the variety of processes and sources used by the individual editors, these portions of the "Data Quality" section are intentionally left blank. For a complete description of the The Pacific Northwest Hydrography Framework Clearinghouse please refer to the following documents and website: http://hydro.reo.gov ftp://ftp.or.blm.gov/gisweb/pdf/hydrodatadictv_09_04.pdf ftp://ftp.or.blm.gov/gisweb/pdf/watershed_datadic_09_04.pdf 20060620 Unknown publication date In work Continually -124.125 -116 49.125 41.5 None WC Hydrography Fisheries Water Watercourses ARIMS Streams Rivers ISO 19115 inlandWaters None Oregon Washington Pacific Northwest Discretionary, contains no sensitive information - generally considered releasable. None OR BLM/USFS Dan Wickwire / Ken Adee mailing address

P.O. Box 2965

Portland Oregon 97208 USA 503-808-6272 Dan_Wickwire@or.blm.gov Microsoft Windows; ESRI ArcCatalog 9 All associated attributes are stored as event tables on the LLID routes. The stream routes are indexed starting from zero at the mouth of the stream to some maximum value at the headwaters. All route measures will be initially calibrated in kilometers to three decimal places. As these routes are edited, every effort will be made to keep the measure value at a given map location from shifting. This will be accomplished by stretching or shrinking the measure values to accommodate lengthening or shrinking along the route as its X,Y coordinates are edited. Thus, over time, the measures will only approximate kilometers along a watercourse or shoreline. These measures are simply an indexing scheme for linear referencing, not a stored attribute of shoreline or watercourse length. This feature has been modeled to allow for flow modeling. All arcs point downstream. This layer has had route events applied to it from ARIMS database using the LLID identifier for the stream. Refer to the REO website for current data holdings at http://hydro.reo.gov. WC data was extracted from the Pacific Northwest Hydrography Framework Clearinghouse Data was clipped by 4th Field watersheds. Then appended to 3 regional pieces (west, central, east) that were then processed by software/hardware available. Route events were queried from the ARIMS database and aggregated into one event overlay table. Single event table was overlayed with the line work using the "Make Eventlayer" ArcGIS command, then new feature class was created by use of the copy features ArcGIS command. Metadata imported. Metadata imported. Metadata imported. C:\DOCUME~1\ssalas\LOCALS~1\Temp\2\xml6.tmp Dataset copied. \\ilmorso3ds2\or\loc\gis\workspace\or\oso\ssalas\ArcSDE\Hydro_Pub.mdb 0 Vector String 178609 0.00000001 0.00000001 Decimal degrees North American Datum of 1983 Geodetic Reference System 80 6378137 298.257 wc_pub carto_type Watercourse cartographic feature code. The code used to describe the cartographic feature type that the watercourse represents. This represents feature codes developed initially by the USGS and used on the DLG's. 100 Alkali flat 101 Reservoir 103 Glacier or permanent snowfield 105 Inundation 106 Fish hatchery or farm 107 Industrial water impoundment 109 Sewage disposal pond or filtration bed 110 Tailings pond 111 Marsh, wetland, swamp, bog 114 Cranberry bog 115 Flats (tidal, mud, sand, gravel) 116 Bay, estuary, gulf, ocean or sea 117 Shoal 402 Gravel pit or quarry filled with water 408 Spillway 412 Stream or river 414 Ditch or canal 415 Aqueduct 417 Penstock 418 Siphon 419 Channel in water area 420 Wash or ephemeral drain 421 Lake or pond 425 Fish ladder 901 Impoundment 999 Unknown or unclassified continuity Watercourse continuity code. This is the classification of stream flow primarily in relation to its expression at the earth's surface. The most common condition is that a stream is continuous in space. con Continuous. A channel with no interruptions in space. int Interrupted. A perennial flow with intervening intermittent or ephemeral segments or an intermittent flow with intervening ephemeral segments. sub Sub-surface. Watercourse reach that represents a sub-surface flow. unk Unknown or unclassified. f_mes Watercourse beginning address. The index measure of the beginning, or downstream, extent of the event. The address or index at which an event or attribute can be associated to a route. Example: 0.03467428 feat_src_cd Feature source code. The compilation map or image source used when adding or updating hydrography watercourse data. 1 USGS Topographic Map 2 Orthophotography 3 Aerial Photograph 4 Multi-Spectral Satellite Imagery 5 Field Survey of on the ground observation 6 Planning Map 7 Field Map 8 Digital Elevation Model (DEM) 9 Radar Imagery 10 Laser Imagery 11 Cartographic Feature File (CFF) 12 National Wetlands Inventory (NWI) Map 13 Imagery - Unspecified Source 99 Unknown or unclassified feat_type Watercourse hydrographic feature code. The code used to describe the hydrographic feature type that the watercourse represents. DC Ditches, canals, flumes ES Bays, estuaries, and oceans GL Glaciers or permanent snowfields IM Impoundments IW Impounded wet areas LA Lakes and ponds PP Pipelines and water conveyance structures SC Side channels to rivers or streams ST Streams and rivers UN Unknown or unclassified fed_buf_dist Actual Riparian Reserve width, in meters, using the Northwest Forest Plan determinates. This is a slope distance converted to a horizontal distance. Example: 18 fishbearing Field that is coded based on actual or modeled fish presence. PV Presence verified PNV Presence not verified AV Absence verified ANV Absence not verified UV Use verified UNV Use not verified gnisname Watercourse GNIS name. The name of the feature as represented within the GNIS. The USGS is the mandated source of this information. Not all features contained within the coverage will have GNIS names. Example: Deschutes River llid Watercourse longitude/latitude identifier number. The 13-character longitude/latitude-derived unique watercourse route identifier (this is also known as LLID in the federal arena.) All watercourse segments are grouped into watercourse routes. The identifier is based on the position of the downstream point (mouth) of the watercourse. The identifier code is composed by concatenating the decimal degree values (to four places of precision) of the coordinates (minus the decimal points). Example: 1215613480987 local_name Watercourse Local name. The name of the feature as represented locally. Not all features contained within the coverage will have Local names. Example: Deschutes River OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. periodicity Watercourse periodicity code. This is a classification for watercourses in terms of the seasonal behavior of the feature over time or in terms of its surface flow. eph Ephemeral. Watercourse that exists only as a result of storm precipitation. int Intermittent or seasonal. Watercourse that is dry during certain times of the year. per Perennial. Watercourse that essentially exists year round. unk Unknown or unclassified. Used when condition information is unknown or unclassified. pfc Characteristics of the lotic riparian wetland areas adjacent to "flowing water" aquatic sites. PFC Proper functioning condition FARU Functional-at-risk upward trend FARD Functional-at-risk downward trend NF Nonfunctional U Unknown planflow Characteristics of the flow pattern of a stream over space as defined by the Northwest Forest Plan P Perennial I INTERMITTENT NWFP Z INTERMITTENT ICBEMP X NO PLAN Shape Feature geometry. ESRI Coordinates defining the features. Shape_Length Length of feature in internal units. ESRI Positive real numbers that are automatically generated. streamorder A dimensionless measure of the position of a stream in the hierarchy of tributaries. Where two n-order streams join, a segment of n+1 order is formed Example: 3 t_mes Watercourse ending address. The index measure of the ending, or upstream, extent of the event. The address or index at which an event or attribute can be associated to a route. Example: 64.60700226 ver_date Used to track the ground-truthing of stream channels, this is the date on which the stream was actually verified to exist on the ground. No entry indicates no field verification has been done. Example: 10/13/1996 Eric Hiebenthal Bureau of Land Management/Northrop Grumman Data Administration Supervisor mailing address

P.O. Box 2965

Portland OR 97208 USA 503-808-6565 503-808-6374 ehiebent@blm.gov 7:30 a.m. to 4:00 p.m. No warranty is made by the Bureau of Land Management as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data. 20060623 Stanley Frazier Bureau of Land Management, Oregon State Office State Data Administrator mailing address

P.O. Box 2965

Portland OR 97208 USA (503)808-6009 (direct); (503) 808-6004 (front desk) (503)808-6419 Stan_Frazier@or.blm.gov FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time None None Not Classified