Regional Ecosystem Office 2002 vector digital data Regional Ecosystem Office Contact Person: Dale Guenther Contact Mailing Address: P.O. Box 3623 Portland, OR 97208-3263 Country: USA Contact Voice Telephone: 503-808-2188 Contact Facsimile Telephone: 503-808-2163 Server=kclora; Service=5151; User=gis; Version=SDE.DEFAULT GIS.ENVIRO_HUC6_WATERSHEDS_POLY This geospatial dataset is a hydrologic boundary layer containing Sixth Field (HUC 6) Watersheds for Kitsap County. This data set is a compiliation of two datasets; the Regional Ecosystem Office's (REO) dataset for Hydrologic Unit Boundaries for Oregon, Washington and California (REOHUC13 Coverage), and Kitsap Conty physical shoreline coverage derived from LIDAR. Because the delineation of the REO's Hydrologic Unit Boundaries was developed from digitized 1:24,000 base maps, only the inland watershed boundaries lying within Kitsap County were incorporated into this dataset. The physical shorelines boundaries represented within the county were developed from LIDAR and are more accurate than those digitized from 1:24,000 base maps. All watershed boundaies represented outside the county are original to the Hydrologic Unit Boundaries dataset. The REO's metadata was incorporated into this dataset metadata and is cited accordingly. NOTE: For cartographic purposes, hydrologic units encompassing more than one county are depicted as two to three separate polygons and can be queried by "County". These areas must be merged prior to doing any watershed analysis. The REO dataset was developed by delineating the boundary lines on 1:24,000 base maps and digitizing the delineated lines. Digital Elevation Model was used in part of the process to establish preliminary boundaries. The data set contains geo-referenced digital map data and associated attributes. The hydrologic unit code attached to each delineated polygon is linked to the attribute data, which can contain information on area in acres, non-contributing area, state(s) the HU falls within, name for the 7th and 8th level HU, 5th and 6th level code for downstream hudrologic unit, and hydrologic unit modifications. Each line has attributes that describe the HU level (1-8), originating source for that line and a metadata ID number that links the line to its associated metadata file (REO Hydrologic Unit Boundaries Metadata, 2002). The watershed and subwatershed hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. These smaller sized hydrologic units (up to 250,000 acres) are useful in many programs supported by the NRCS and others. This data set is intended as a tool for water-resource management and planning activities, particularly for site-specific and localized studies, which require the amount of detail provided by a large-scale map. (REO Hydrologic Unit Boundaries Metadata, 2002) For additional information please refer to the Regional Ecosystem Office Watersheds site and the Hydrologic Unit Boundaries for Oregon, Washington, and California metatdata respectively: http://www.reo.gov/gis/projects/watersheds/index.htm http://www.reo.gov/gis/projects/watersheds/REOHUCv1_3.htm en 2002 publication date Complete As needed 236.855985 237.547939 47.942773 47.156001 1074048.3370001237761.41400065283.471000348192.880000 Hydrologic units Watershed Boundaries Subwatershed Boundaries HUC6 None The U.S. Department of Agriculture, Natural Resources Conservation Service, should be acknowledged as the data source in products derived from these data. These data should not be used at scales greater than 1:24,000. This is public information and may be interpreted by organizations, agencies, units of government, or others based on needs; however they are responsible for the appropriate application of the data. Federal, state, or local regulatory bodies are not to reassign to the Natural Resources Conservation Service any authority for the decisions they make. The Natural Resources Conservation Service will not perform any evaluations of these maps or purposes related solely to State or local regulatory programs. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can cause misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated. Files are dated, and users are responsible for obtaining the latest version of the data. (REO Hydrologic Unit Boundaries Metadata, 2002) Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722 SDE Feature ClassKim RivardForest Service(503) 808-2294 Polygon identifiers are manually checked with the original base map using the attribute file. Verification on polygon identification continuity on each side of a neatline is done visually on the screen as adjacent quad representations are assembled into larger area data layers. (REO Hydrologic Unit Boundaries Metadata, 2002) Certain node/geometry and topology (GT) polygon/chain relationships are collected or generated to satisfy topological requirements. (The GT-polygon corresponds to a hydrologic unit or a portion of a hydrologic unit at the edge of a Quadrangle sheet.) Some of these requirements include: chains must begin and end at nodes, left and right GT-polygons are defined for each chain element and are consistent throughout, and the chains representing the limits of the file (neatline) are free of gaps. The tests of logical consistency are performed using vendor software. The neatline is generated by connecting the explicitly entered four corners of the digital file. All data outside the enclosed region are ignored and all data crossing geographically straight lines are clipped at the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline (i.e., with the longitude/latitude lines in geographic coordinates). All internal polygons are tested for closure with vendor software and are checked on hard copy plots. All data are checked for common boundary lines (i.e., adjacent polygons with the same label). Quadrangles are edge matched within the Sub-basin area and edge locations generally do not deviate from centerline more than 0.01 inches. (REO Hydrologic Unit Boudnaries Metadata, 2002) The accuracy of these maps is generally based on the contour information or DEM data available for the base maps. Such data may be supplemented with site visits to locate ridge lines for hydrologic unit boundaries in flat terrain areas, changes in drainage patterns due to man's activities. The differences in positional accuracy between the hydrologic unit boundaries and their digitized map locations is unknown. Hydrologic unit boundaries generally were digitized within 0.01 inches of their locations on the digitizing source. The digital map elements are edge matched against the data for the adjacent Quadrangle. Edge match locations generally do not deviate from centerline to centerline by more than 0.01 inches. (REO Hydrologic Unit Boundaries Metadata, 2002) Dataset copied. Kitsap County GISGIS Managermailing address

614 Division St, MS-21

Port OrchardWA98366United States(360) 337-4438(800) 816-2782(360) 337-4555GIS Manager <gis@co.kitsap.wa.us>8:00 AM - 4:30 PM (PST), Mon - Fri Dataset copied.Server=kclora; Service=5151; User=gis; Version=SDE.DEFAULT2004051509415100Dataset copied.Server=kcldev; Service=5161; User=gis; Version=SDE.DEFAULT2004051512491500 Vector G-polygon 18 SimplePolygonFALSE18TRUEFALSE coordinate pair 0.001000 0.001000 survey feet Lambert Conformal Conic47.50000048.733333-120.83333347.0000001640416.6666670.000000 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet National Geodetic Vertical Datum of 1929 1.000000 Explicit elevation coordinate included with horizontal coordinates Sixth Field (HUC 6) Watersheds for Kitsap County Feature Class 18 OBJECTID Internal feature number. ESRI OBJECTID OID 4 10 0 Sequential unique whole numbers that are automatically generated. ACRES Area of polygon Computed ACRES Double 8 38 8 HUC_NUMBER Hydrologic Unit Field Code- In order to identify an area, be it 1st through Nth Levels, each is assigned the combination of Levels which comprise it. Starting at the uppermost end of the drainage, the first 7th level hydrologic unit would be assigned the code 01 for the 13th and 14th digits. When combined with the 6th level code, the full Hydrologic Unit Code in the above example would be 17100203020901XX. REO HUC_NUMBER String 16 0 0 HUC_TYPE Hydrologic Unit Types-This item allows users to query hydrologic units based on composition type. Information is presented as a running string where each individual character of the string represents the composition type of a particular unit (e.g.- character number 1 represents the composition type of a 1st level unit, character number 2 represents the composition type of a 2nd level unit, etc). Where a hydrologic unit level has not been delineated or the type has yet to be classified, an X will serve as a placeholder. This is an optional item that may be populated for 1st through 8th level units where deemed necessary. REO HUC_TYPE String 8 0 0 T True, pure, or ""classic"" hydrologic units are land areas having all the surface drainage within its boundary converging at a single point. REO C Composite hydrologic units, or remnant areas are drainage areas typically formed as the residual areas after delineation of classic watersheds. The most common example of a remnant area is the small triangular wedge between the boundaries of adjacent hydrologic units flowing into the same side of another stream. REO F Frontal hydrologic units are areas that include multiple, non-convergent rivers. Frontal units would most likely be related to hydrologic units feeding into the Pacific Ocean or Columbia River. REO X Unclassified hydrologic units REO S (None) REO R (None) REO REGION_NAME 1st Field Hydrologic Unit Naming Protocol REO REGION_NAME String 30 0 0 SUBREGION_NAME 2nd Field Hydrologic Unit Code. Based on data from HUC_NUM item REO SUBREGION_NAME String 30 0 0 BASIN_NAME 3rd Field Hydrologic Unit Naming Protocol REO BASIN_NAME String 30 0 0 SUBBASIN_NAME 4th Field Hydrologic Unit Naming Protocol REO SUBBASIN_NAME String 30 0 0 WATERSHED_NAME 5th Field Hydrologic Unit Naming Protocol REO WATERSHED_NAME String 80 0 0 SUBWAT_NAME 6th Field Hydrologic Unit Naming Protocol REO SUBWAT_NAME String 80 0 0 CATCHMENT_NAME 7th Field Hydrologic Unit Naming Protocol REO CATCHMENT_NAME String 80 0 0 SUBCATCH_NAME 8th Field Hydrologic Unit Naming Protocol REO SUBCATCH_NAME String 80 0 0 OLD_HUCNUMBER OLD_HUCNUMBER String 16 0 0 STATES STATES String 12 0 0 NCONTRIB NCONTRIB Double 8 38 8 DS_HUC5 DS_HUC5 String 10 0 0 DS_HUC6 DS_HUC6 String 12 0 0 HUC_MOD HUC_MOD String 80 0 0 COMMENT_ COMMENT_ String 100 0 0 REGION REGION String 2 0 0 SUBREGION SUBREGION String 4 0 0 BASIN BASIN String 6 0 0 SUBBASIN SUBBASIN String 8 0 0 WATERSHED WATERSHED String 10 0 0 SUBWAT SUBWAT String 12 0 0 CATCHMENT 7th Field Hydrologic Unit Code Based on data from HUC_NUM item REO CATCHMENT String 14 0 0 SUBCATCH 8th Field Hydrologic Unit Code Based on data from HUC_NUM item REO SUBCATCH String 16 0 0 FIRST_FIELD 2-digit identifier Based on data from HUC_NUM item REO FIRST_FIELD String 2 0 0 SECOND_FIELD 2-digit identifier Based on data from HUC_NUM item REO SECOND_FIELD String 2 0 0 THIRD_FIELD 2-digit identifier Based on data from HUC_NUM item REO THIRD_FIELD String 2 0 0 FOURTH_FIELD 2-digit identifier Based on data from HUC_NUM item REO FOURTH_FIELD String 2 0 0 FIFTH_FIELD 2-digit identifier Based on data from HUC_NUM item REO FIFTH_FIELD String 2 0 0 SIXTH_FIELD 2-digit identifier Based on data from HUC_NUM item REO SIXTH_FIELD String 2 0 0 SEVENTH_FIELD 2-digit identifier Based on data from HUC_NUM item REO SEVENTH_FIELD String 2 0 0 EIGHTH_FIELD 2-digit identifier Based on data from HUC_NUM item REO EIGHTH_FIELD String 2 0 0 COUNTY County in which a polygon is located. Hydrological units encompassing multiple counties are depicted by two to three polygons strictly for cartographic purposes. A notation is made in the "Comments" attribute field as to the polygon part and hydrological unit the polygon belongs to. These hydrological unit polygons must be merged to do watershed analysis. Kitsap County GIS COUNTY String 10 0 0 Kitsap All or portion of hydrologic unit lies within Kitsap County Pierce All or portion of hydrologic unit lies within Pierce County SHAPE Feature geometry. ESRI SHAPE Geometry 4 0 0 Coordinates defining the features. SHAPE.AREA Area of feature in internal units squared. ESRI SHAPE.AREA Double 0 0 0 Positive real numbers that are automatically generated. SHAPE.LEN Length of feature in internal units. ESRI SHAPE.LEN Double 0 0 0 Positive real numbers that are automatically generated. The hydrologic Unit Boundaries coverage contains attributes for polygons, arcs and seven Arc/Info regions. Hydrologic Unit delineations are closed polygons that encompass all area draining toward the lowest point (called pour point) in the polygon. Because of nominal sizes for the different hydrologic unit level: Watershed (40,000 to 250,000 acres) and Subwatershed (generally 10,000 to 40,000 acres), some polygons do not include all areas up to the drainage divide but all areas to one or more other upstream hydrologic units. A unique hydrologic unit code is used to identify each hydrologic unit. The hydrologic unit codes start with the 8-digit Sub-basin (sub-basin) number that contains the Watershed. Likewise the Subwatershed hydrologic unit codes start with the 10-digit Watershed number that contains the Subwatershed. Attributes associated with a hydrologic unit code includes: ACRES, HUC_NUM, HUC_TYPE, REGION_NAME, SUBREGION_NAME, BASIN_NAME, SUBBASIN_NAME, WATERSHED_NAME, SUBWAT_NAME, CATCHMENT_NAME, SUBCATCH_NAME, OLD_HUCNUM, STATES, NCONTRIB_DA, DS_HUC5, DS_HUC6, HUC_MOD, COMMENT, REGION, SUBREGION, BASIN, SUBBASIN, WATERSHED, SUBWAT, CATCHMENT, SUBCATCH, FIRST_FIELD, SECOND_FIELD, THIRD_FIELD, FOURTH_FIELD, FIFTH_FIELD, SIXTH_FIELD, SEVENTH_FIELD, EIGHTH_FIELD, HUC_LEVEL, LINESOURCE, LINEVER, LINEDATE, LINEORG, METADATA_ID, COMMENT (REO Hydrologic Unit Boundaries Metadata, 2002) Pacific Northwest Regional Hydrologic Unit Boundary Database Attribute Standards ""URL" (REO Hydrologic Unit Boundaries Metadata, 2002) Downloadable Data ESRI Shape Filezipftp://kcwppub3.co.kitsap.wa.us/gis/datacd/arcview/layers/enviro/huc6wshd.zip 20060613 Kitsap County GIS mailing address Port Orchard WA 98366

614 Division St, MS-21

United States (360) 337-4443 GIS Manager(800) 816-2782(360) 337-4555GIS Manager <gis@co.kitsap.wa.us>8:00 AM - 4:30 PM (PST), Mon - Fri FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile enhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile 2004051512491500FALSE20060613123113002006061312311300{4E6585E7-6BD8-48F6-B819-127FE12E4DBB}Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722GIS.ENVIRO_HUC6_WATERSHEDS_POLY236.855985237.54793947.94277347.15600111074048.3371237761.414348192.8865283.4711ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002Server=kclora; Service=5151; User=gis; Version=SDE.DEFAULTArcSDE ConnectionSDE Feature ClassNAD_1983_StatePlane_Washington_North_FIPS_4601_Feet1820060613