Rivers and Streams in King County

Metadata also available as - [Outline]

Frequently anticipated questions:

What does this data set describe?

Title: Rivers and Streams in King County
Abstract: Streams of King County and surrounding area
The WTRCRS lines were updated in 2005/2006 using 2002 LiDAR products (elevation, aspect, slope, accumulation, and contours) and 2002 Digital Orthophotographs from King County and USGS. In urban areas supplimental data sets of Utility Drainage were used when available. Lines were coded for confidence in correctness of path so that issues can be easily found and resolved by basin stewards or field inspection. In 2008/2009 unique identifers were given to each stream. This identifier, RTE_ID, was used to create a feature class with routed measured geometry (polyline M) that allows linear referencing. corrections, clarifications. Updates to lines for positional accuracy were made as better information, such as LiDAR and higher resolution imagery, became available.
  1. How should this data set be cited?

    County, King, 20090618, Rivers and Streams in King County: King County, King County, WA.

    Online Links:

    Other_Citation_Details: None

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -122.551138
    East_Bounding_Coordinate: -121.068256
    North_Bounding_Coordinate: 48.075001
    South_Bounding_Coordinate: 46.847315

  3. What does it look like?

    <http://www5.kingcounty.gov/sdc/DataImages/wtrcrs.jpg> (JPG)
    JPG File of layer overlain on base of WA counties or local cities

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 05-Sep-2013
    Time_of_Day: 220000
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • String (13072)

    2. What coordinate system is used to represent geographic features?

      The map projection used is NAD 1983 HARN StatePlane Washington North FIPS 4601 Feet.

      Projection parameters:
      Standard_Parallel: 47.5
      Standard_Parallel: 48.73333333333333
      Longitude_of_Central_Meridian: -120.8333333333333
      Latitude_of_Projection_Origin: 47.0
      False_Easting: 1640416.666666667
      False_Northing: 0.0

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.0003280833333333334
      Ordinates (y-coordinates) are specified to the nearest 0.0003280833333333334
      Planar coordinates are specified in foot_us

      The horizontal datum used is D North American 1983 HARN.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    Line feature attribute table (Source: King County)

    Water Course Name (Source: King County)

    Frequency of measurement: Unknown

    Full name of water course

    Basin ID number (Source: King County)

    Integer identifying number - first or first two digits indicate WRIA; next two digits indicate WATERSHED; final two digits indicate BASIN

    Feature length (Source: ESRI)

    Length of feature in feet

    WRIA ID Number (Source: King County)


    WRIA Name (Source: King County)

    Full name of WIRA

    Watershed Name (Source: King County)

    Full name of watershed

    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.


    Route Identification Number (Source: King County)

    Unique identifier for each stream

    Basin Name (Source: King County)

    Full name of basin

    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    A measure of stream hierachy (Source: King County)

    Source of Stream Location (Source: King County)

    Attributes contain watercourse name when available. Arcs can be symbolized by: WRIA, watershed, or basin, but not by catchment. SOURCE contains original undocumented information except for area updated as phase one.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    King County Dept. of Natural Resources and Parks, Water and Lands Resources Division
    Attn: Ken Rauscher
    Senior GIS Analyst
    201 S Jackson St, Suite 703
    Seattle, WA 98104

    206-296-1922 (voice)

    Hours_of_Service: 7:30 - 4:00

Why was the data set created?

This coverage contains water courses for King County drainage basins including some areas in adjoining counties.

How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    (process 1 of 8)
    TITLE: QUALITY CONTROL After the watercourse was edited, it was visually inspected for major errors.

    Person who carried out this activity:

    GIS Center
    Attn: Victor High
    Senior GIS Analyst

    (process 2 of 8)
    TITLE: LEGACY DATA HISTORY WTRCRS was created in a 1997 joint project between WA Dept of Ecology and King County Water and Land Division from an initial source coverage of the standard WA Dept. of Natural Resources hydrography layer. This data set is integrated from numerous sources, primarily at 1:24,000 scale. More information about this initial version, some of which still applies to the current version, can be found in this supplemental document. Beginning in 2001, WLRD started updating this coverage with additional information from other jurisdictions and field data. Although this has obviously resulted in improved data accuracy, the current version also differs from the original in not having a route system. The old routed version can be obtained from the contacts below if desired. Spatial accuracy was improved using 2002 digital orthophotography and LiDAR data. Limited updates were done from 2007 digital orthophotography. Routes added in 2008/2009. Additional updates were done 2009 to 2016.

    Person who carried out this activity:

    King County, Dept. of Natural Resources & Parks, Water & Land Resources Division
    Attn: Ken Rauscher
    Seattle, WA 98104

    206-296-1922 (voice)

    (process 3 of 8)
    A unique hierarchical identifier was added to each stream, RTE_ID. All streams were routed using RTE_ID as the route id.

    (process 4 of 8)
    Updates done as better information becomes available. Acquisition of higher resolution LiDAR has been a valuable source for updates. Field observations from King County personnel is also used.

    Date: 01-Jan-2006 (process 5 of 8)
    TITLE: EDITING PROCESS Heads-up digitizing was the method of updating the exisitng geometry of the streams. In order to correct the geometry of the exisitng watercourse various datasets were used. The heirarchy of their use is as 1. King County 2002 Ortho Imagery 2. USGS Ortho Imagery 3. DEM with 50% Transparency Slope derived from 2002 LiDAR 4. Contours derived from 2002 LiDAR 5. Accumulation dervied from 2002 LiDAR 6. Drainage datasets when available for certain areas The Protocol for determining confidence rating scheme: 1 = stream path is clear and evident, path can be 100% determined through the use of imagery or LiDAR Datasets 2 = stream path is obsured and path cannot be 100% determine (road, urban area). 3 = stream path is not possible due to data provided These arcs are primarily mistakes in the data set There is no possible way that the stream flows in this manner These arcs will be eliminated 4=added arcs (these arcs were added either for proper watershed delineation or from current agricultural datsets provided by WRLD)

    Person who carried out this activity:

    Attn: Victor High
    GIS Analyist

    Date: 01-Jan-2006 (process 6 of 8)
    TITLE: DATA DEVELOPMENT PREP This step compiled the .aml generated datasets as well as the auxillary data into one dataset. .aml primarily used were, accumulation, slope, DEM and STRM40k. The reference datasets primarily used were the following: :\plibrary3\reference\indexes\idxptrmbr.shp Provides an index in order to locate other datasets :\plibrary3\idxptrmbr\dgm_contour Provides information on elevation :\plibrary3\idxptrmbr\ortho_2002kc_nat Provides visual information :\plibrary3\idxptrmbr\ortho_2002usgs_nat Provides visual information :\basin\npdes\culverts.shp Provides information of where culverts are in King County :\basin\npdes\rniscul.shp Provides information of where the rniscul are in King County :\basin\seattle_drainage.lyr Provides drainage information for the City of Seattle In addition, a shapefile named DEMFIX was created in order for the watercourse to cross manmade barriers, such as bridges and overpasses. This was a polygon, short integer. The dataset is primarily for the watershed delineation process but was created in the watercourse data development prep process.

    Person who carried out this activity:

    King County DNRP WRLD
    Attn: Victor High
    GIS Analyist

    Date: 14-Apr-2008 (process 7 of 8)
    TITLE: Extent of WTRCRS reduced The extent of WTRCRS is reduced to features which are encompassed by basins defined by the Phase II project plan. The Phase II project plan includes only those basins that are wholly or part within King County. These are basins that have both defined business requirements and for which generally adequate control is available. The areas outside of this revised extent generally do not. Areas outside of the newly defined bounds are covered by data provided by adjacent counties. Users can use the new layer, WTRCRS_3CO to view a layer that composites the core King County data and adjacent county data.

    Date: 15-Apr-2008 (process 8 of 8)
    TITLE: Schema change Items WTR_CRS_ID and FEATURE_ID dropped. WTRCRS_ID is an attribute from the original early 1990s development of the layer and is no longer maintained. FEATURE_ID was added at the beginning of PHASE 1 development as a way to related external data to features. However it was difficult to maintain and saw limited, if any use. After Phase II development of a measure-based route system is completed, each stream or river will have a unique feature identifier expressed as a route identifier.

  3. What similar or related data should the user be aware of?

    , King County Streams.

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    The only attributes tested were BASIN_NAME and WRIA_NO. This test was done visually by symbolizing by the attribute.

  2. How accurate are the geographic locations?

    Features that could be clearly defined in the King County 2002 Ortho Imagery are generally mapped to within plus or minus one meter. Features that were not clearly defined in the King County 2002 Ortho Imagery were captured using ancillary datasets which may have accuracies in the range of one to five meters. Information concerning the positional accuracie is stored in the RATE item located only in the maintainence version. Limited adjustments were done from 2007 orthophotography.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Data covers entire King County and portions of Snohomish and Pierce County. Data was spatially corrected to 2002 King County Color Ortho Imagery and included the southern portion of Snohomish County and the northern portion of Pierce Cunty along the White River. Phase One includes the re-working of existing watercourse arcs, with limited addition of new arcs. New arcs were only added per se Fish and Ditch (agricultural waterways) edits and to accomodate watershed delineation where necessary. Phase Two includes adding a unique identifier for each stream to be used for Route creation. The Routes allow for linear reference of event tables.

  5. How consistent are the relationships among the observations, including topology?

    Watercourse was mapped to third level heirarchy. Watercourses are mapped through waterbodies, only Lake Washington and Lake Sammanish are coded by the attribute ffield WTR_NAME. Network connectivity was maintained from the existing data except where legacy gaps exist. Instances of this may be where the watercourse goes underground or into pipes. Database attributes were assigned to all features except for WTR_NAME, this field was left NULL for unnamed features.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
King County data are made available with the understanding that they shall be used exclusively by the obtainer or his/her authorized agents. Digital products may not be reproduced or redistributed in any form or by any means without the express written authorization of King County.

  1. Who distributes the data set? (Distributor 1 of 1)

    KCGIS Center
    Attn: Cheryl Wilder
    Data Sales Coordinator
    201 S Jackson St, Suite 700
    Seattle, WA 98104

    206-263-5220 (voice)

  2. What's the catalog number I need to order this data set?


  3. What legal disclaimers am I supposed to read?

    King County disclaims any warranty of use of any digital product or data beyond that for which it was designed.

  4. How can I download or order the data?

Who wrote the metadata?

Last modified: 27-Jan-2017
Metadata author:
King County Dept. of Natural Resources and Parks, Water and Lands Resources Division
Attn: Ken Rauscher
Senior GIS Analyst
201 S Jackson St, Suite 600
Seattle, WA 98104

206-296-1922 (voice)

Hours_of_Service: 7:30 - 4:00 M-F
Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.12 on Sun Oct 17 12:10:44 2021