Five (5) foot-interval index contour isolines for townships and the entire county. Index contours selected from 5 foot contours(10 foot, 20 foot, 40 foot, 50 foot & 100 foot) for entire county.

Metadata also available as - [Questions & Answers]

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: King County
Publication_Date: 20071005
Title:
Five (5) foot-interval index contour isolines for townships and the entire county. Index contours selected from 5 foot contours(10 foot, 20 foot, 40 foot, 50 foot & 100 foot) for entire county.
Edition: One
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: King County, WA
Publisher: King County
Other_Citation_Details: None
Online_Linkage: <http://www5.kingcounty.gov/gisdataportal/Default.aspx>
Description:
Abstract:
Contour isolines with interval in feet as defined by numerical suffix to data tile. For example t22r04_ctr005 indicates contours for the township 24, range 04 tile with a 5-foot contour interval. Zone and region layers are constructed with a greater contour interval such as _ctr010 representing a 10-foot contour interval. All tiles have identical attribute structures with defined index contours. For file name consistency all township tiles are titled with a 005 suffix. However, due to software-limitations in processing and display restrictions not all tiles contain five-foot contours. For Range 2 through 7, tiles contain five-foot contours, regardless of elevation range. For Range 8 through 14, tiles do not contain five-foot contours for elevation ranges greater than 1000. This means that for tiles where all elevations are greater than 1000 there will be no five foot contours. This 1000-foot demarcation was used to reduce file size and improve drawing performance in elevated, high-relief areas while still providing adequate topographic definition. The 1000-ft breakover point was also chosen as a rough urban/rural dividing line. These contours were derived from the digital ground model grid lattice (DGM) developed initially from the mass point LiDAR file, as detailed in the Process section. As several processing steps were involved, including smoothing and artifact removal, these contours are provided only as an interpretation of the earth's surface and do not meet the definition of topography per chapter 18.43 of the Revised Code of Washington. These contours do not depict the topography relative to any particular property. Any use of this information without additional verification by competent professionals is inappropriate.
Purpose:
The contour interval represents a best compromise between the vertical and horizontal accuracy of the source data and the need for a general use cartographic and analysis product. At the contour interval indicated for a given tile the data provide a reasonable depiction of the general shape of the land useful for determining general landform, slope, and elevation. As, by nature, LiDAR data contain some percent of non-ground points, the contours cannot be considered absolute or without error. The index contour attributes allow the data to be reselected or symbolized to display less detail for smaller scale areas.
Supplemental_Information:
The contours were generated to the extent of the individual tiles of the idxptrbmr index (index polygons for township-range, minimum bounding rectangle).Effort was made to minimize any edge effects at the edge of a tile but the tiles have not been edge-matched to adjacent tiles. A supplemental set of tiles were created in early 2005. This set is found in the idxptrmbr folder called dgm_ctrneat. It consists of the same contour information in the original dgm_contour folder, but the tiles are edgematched and clipped to the extent of the PLSS twnshp grid. Although these files are derived from the dgm_contour set they are not necessarily produced at the same time that updates to the dgm_contour set are made.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20091201
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Annually
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -122.570391
East_Bounding_Coordinate: -121.061646
North_Bounding_Coordinate: 47.986732
South_Bounding_Coordinate: 47.048720
Keywords:
Theme:
Theme_Keyword_Thesaurus: Not applicable
Theme_Keyword: bathymetry
Theme_Keyword: topo
Theme_Keyword: Digital Ground Model (DGM)
Theme_Keyword: Contours
Theme_Keyword: LiDAR digital elevation data
Theme_Keyword: Elevation data
Theme_Keyword: Bare-Earth
Theme_Keyword: Virtually Deforested
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Categories
Theme_Keyword: elevation
Place:
Place_Keyword_Thesaurus: Not applicable
Place_Keyword: Washington state
Place_Keyword: Pacific NW
Place_Keyword: King County
Place_Keyword: WA
Place_Keyword: Seattle
Access_Constraints:
A cooperative data sharing arrangement between the Puget Sound LiDAR Consortium and King County is allows certain formats of the LiDAR data to be distributed with out license or restriction. Certain processing and data handling charges for necessary cost recovery may apply. Access to raw mass point files is by special request and request evaluation only.
Use_Constraints:
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. These contours are based upon LiDAR returns which inherently contain some "non ground-surface" values. In addition, the contours were smoothed, as outlined in the Process Section, to create a more traditional cartographic product. As such, these contours represent only the general shape of the land and do not meet the definition of topography per chapter 18.43 of the Revised Code of Washington. These contours do not depict the topography relative to any particular property. Any use of this information without additional verification by competent professionals is inappropriate.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: King County GIS Center
Contact_Person: Victor High
Contact_Position: Senior GIS Specialist
Contact_Address:
Address_Type: mailing and physical
Address: 201 S Jackson St, Suite 706
City: Seattle
State_or_Province: WA
Postal_Code: 98104
Country: US
Contact_Voice_Telephone: 206-477-4408
Contact_Electronic_Mail_Address: victor.high@kingcounty.gov
Browse_Graphic:
Browse_Graphic_File_Name: <http://www5.kingcounty.gov/sdc/DataImages/contour005.jpg>
Browse_Graphic_File_Description:
JPG File of layer overlain on base of WA counties or local cities
Browse_Graphic_File_Type: JPG
Native_Data_Set_Environment: Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Elevation attributes are derived from the LATTICECONTOUR function within ArcInfo and are accurate relative to the vertical accuracy of the underlying bare-earth dgm data.
Logical_Consistency_Report:
Processing routines were adjusted and/or contour interval increased to mininimze, though not necessarily, eliminate all crossing contours, especially in areas of steep relief. All contours are labeled. Contours were created on a tile by tile basis, using a buffer of adjacent data to minimize edge effects and to have contours overlay as closely as possible. However township tiles have not been butt-joined and edge-matched. As stated in the Abstract not all tiles contain five-foot contours. This restriction is dependent on the tile's extent (i.e., amount of relief) and whether the tile has elevation ranges less than 1000 feet. For tile-based data stored in the Spatial Data Warehouse, the following image shows all tiles with with five-foot contours (either above or below 1000 feet) and then the only tiles with five-foot contours above 1000 feet. <http://www5.kingcounty.gov/sdc/raster/elevation/images/FiveFootContourDistribution.jpg> One copy of the tiles has been modified for storage in the SDE Geodatabase. These tiles have been clipped to a midline neatline between townships and edgematched. All 5-foot contours above 1000 feet have been removed for all tiles so that no dangling arcs will occur. These tiles will have five foot contours only if there are elevations less than 1000 feet within the tile's extent.
Completeness_Report:
Contours cover the entirety of each tile to the extent that LiDAR data is available for that area. No gaps occur within the contour lines.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
The contours were generated from ArcInfo lattice grids based on 6-foot center to center posting. Horizontal accuracy will be approximately 1/2 of the posting distance or about 3 feet in areas where point density is high (equivalent to 5-7 feet point spacing). Where point density is considerably reduced due to poorer to-ground penetration rates, the horizontal accuracy will be reduced proportionally and may be only accurate to 10-15 feet and locally accuracy will be even poorer. Areas of built-up manmade features do not have any 'bare-earth' points and any elevation interpretation, including contour delineation, is created by interpolation from the nearest bare-earth points outside the built-up area. In these cases the contour interpretation may accurately reflect the amount of overall slope change but cannot accurately depict the area covered by the built-up feature.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
Vertical Datum is NAVD88. The elevation attribute, provided in integer feet, represents an interpretation of the tinned elevation values interpolated to a six-foot centered lattice. Limited testing has indicated that the contours represent LiDAR elevation values within 1/5 of the contour interval though in areas of steep terrain and dense vegetation canopy the contour elevation value should be considered accurate to only 1/2 the contour interval. Locally the contour interpretation of the ground elevation will be poorer, especially in areas of dense vegetation (particularly dense understory vegetation) and areas of steep slope. The contour interpretation is directly related to the vertical accuracy of the underlying bare-earth digital ground model from which it is created. Vertical accuracy of the bare-earth data varies considerably. Quality Assessment evaluation of vertical accuracy indicate that, as a whole, the data exhibits a RMSE (Root Mean Square Error) of 30 cm or less in areas without vegetation canopy or dense subcanopy. This is equivalent to a National Standard for Spatial Data Accuracy (NSSDA) of 58.8 cm at the 95% confidence interval (1.96 x RMSEz). In areas of dense vegetation canopy, but where some bare-earth penetration is available, the data generally has less than 60 cm RMSE, equivalent to 117.6 cm NSSDA Accuracy. Better accuracies are obtained in many areas, but poorer accuracies are also prevalent due to low penetration rates, incomplete vegetation and elevated feature removal, errant points due to multiple reflection travel paths and other edge-effects. Water and areas immediately adjacent to open water areas are always suspect due to the inability to obtain good returns from these surfaces.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: King County ESA/SAO contract with 3di Technologies, Boulder, CO
Publication_Date: 20030101
Title:
King County ESA/SAO Lowland LiDAR Project (Phase I) and King County ESA/SAO Upland LiDAR Project (Phase 2)
Geospatial_Data_Presentation_Form: tabular digital data
Publication_Information:
Publication_Place: Boulder, CO
Publisher: 3di Technologies
Other_Citation_Details:
The King County ESA/SAO project is comprised of two separate project areas (phases). Phase I (lowland phase) includes the portion of western King County and southern Snohomish County that completes that portion of the County not covered by the PSLC project. The second phase (upland phase) includes the remainder of the County.
Type_of_Source_Media: None
Source_Citation_Abbreviation:
King County ESA/SAO Lowland LiDAR Project (Phase I) and King County ESA/SAO Upland LiDAR Project (Phase 2)
Process_Step:
Process_Description:
Data from 2004 3di West for Snoqualmie, Green River Study was integrated into master elevation database. This new elevation control was assembled from stereo pair orthoimagery, and approximates 2-foot contour accuracy necessary for FEMA flood plain mapping. The TIN surface created for the project was converted to a point dataset and then incorporated into the elevation database similar to the original lidar data. Data from 2007 Ground LiDAR ascii data from Watershed Science for parts of White River are integrated into master elevation database. This is the first update that was converted from Arc\Info GRID\AML to ARCGIS SDE RASTER\Python. See documentation: \\Gisimage\images\AllWorkspaces\ELEVATION\Documentation\DGM Update Procedure.doc The following townships were updated: T19R06 T19R07 T21R04 T21R05 T21R06 T22R04 T22R05 T23R04 T23R05 T24R04 T24R07 T25R06 T25R07 T26R06 T26R07 T27R06
Process_Step:
Process_Description:
Contours built from dgm township GRIDs, neat clipped, then appended together without edge matching.
Process_Step:
Process_Description:
2016 Quantum Spatial lidar update for western part of county. Township contours updated: t19r08, t19r09, t19r10, t20r07, t20r08, t20r09, t20r10, t21r07, t21r08, t22r07, t22r08, t22r09, t22r10, t22r11, t23r07, t23r08, t23r09, t23r10, t23r11, t24r07, t24r08
Process_Step:
Process_Description: Townships updated: t21r04, t21r05, t23r07, t24r07,
Process_Step:
Process_Description:
Produce tile list of DXF contours needed by intersecting p_lidar_all extent layer with index layer idxp7500. Write python script gisimage\images\ElevMaint\ctr27500\clip_dxf3.py to: Check for existence of DXF file If no file, then Select each tile. Build a clip. Clip SDE layer GISPROD plib.sde.plibrary.TOPO.contour005_line. ExportCAD_conversion using DXF_R2004 option
Process_Date: 20061126
Process_Step:
Process_Description:
Tiles are clipped from contour005 using the 7500 index squares. Contours are then converted into Autocad version 2004 DXF format.
Process_Date: 20081128
Process_Step:
Process_Description:
Contours are derived from the latest DGM mosaic model. A 5 foot county wide contour layer is maintained in SDE Maint. Township DGM are extracted from the mosaic, contoured at 5 feet, the old township selected and deleted, and the new contour township appended back. Separate township layers are produced for posting to shapefiles and ftp portal. 5 Index contour layers for the county are also produced by selection from the master county wide 5 foot contour layer. 10, 20, 40, 50 and 100 foot contour indexes for the county are produced.
Process_Date: 20161025
Process_Step:
Process_Description:
Townships updated: t19r07, t20r04, t20r05, t20r06, t20r07, t21r02, t21r03, t21r04, t21r05, t21r06, t21r07, t21r08, t21r09, t21r10, t21r11, t22r02, t22r03, t22r04, t22r05, t22r06, t22r07, t22r08, t22r09, t22r10, t22r11, t23r02, t23r03, t23r04, t23r05, t23r06, t23r07, t23r08, t23r09, t24r03, t24r04, t24r05, t24r06, t24r07, t24r08, t25r03, t25r04, t25r05, t25r06, t25r07, t25r08, t25r09, t25r10, t26r03, t26r04, t26r05, t26r06, t26r07, t26r08, t26r09, t26r10, t27r03, t27r04, t27r05, t27r06, t27r07
Process_Date: 20170915
Process_Step:
Process_Description:
Lidar update 2019 from Cedar, Green, Snoqualmie, & South Vashon pts.
Process_Date: 20190729

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 0

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: NAD 1983 HARN StatePlane Washington North FIPS 4601 Feet
Lambert_Conformal_Conic:
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_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.00025
Ordinate_Resolution: 0.00025
Planar_Distance_Units: foot_us
Geodetic_Model:
Horizontal_Datum_Name: D North American 1983 HARN
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: topography.GISC.reg_ctr005_line
Entity_Type_Definition_Source: ESRI
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2659999
Enumerated_Domain:
Enumerated_Domain_Value: 2660000
Enumerated_Domain:
Enumerated_Domain_Value: 2660001
Enumerated_Domain:
Enumerated_Domain_Value: 2660002
Enumerated_Domain:
Enumerated_Domain_Value: 2660003
Enumerated_Domain:
Enumerated_Domain_Value: 2660004
Enumerated_Domain:
Enumerated_Domain_Value: 2660005
Enumerated_Domain:
Enumerated_Domain_Value: 2660006
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: TILE_ID
Attribute_Definition: Tile identifier
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Unrepresentable_Domain:
Integer value defining township and range of tile; i.e., T22R04 would be 2204
Attribute:
Attribute_Label: ELEVATION
Attribute_Definition: Elevation of contour isoline in feet
Attribute_Definition_Source: KCGISC
Attribute:
Attribute_Label: IDX_MINOR
Attribute_Definition:
Indexes each elevation value as to either a 5-foot multiple only,or a 5 and 10-foot multiple. For example, the 105 foot isoline would be indexed as a 5, while a 110 foot isoline would be indexed as a 10.
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10
Attribute:
Attribute_Label: IDX_20FT
Attribute_Definition:
Indexes each elevation value as to whether it is a multiple of 20, cumulative multiple of 100, 500 or 100, or none of these. Useful for showing 100 foot boss contours with aggregate 20's.
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Attribute:
Attribute_Label: IDX_40FT
Attribute_Definition:
Indexes each elevation value as to whether it is a multiple of 40, cumulative multiple of 200 or 1000, or not either. Useful for showing every 200 foot boss contour with aggregate 40's, comparable to many USGS topographic maps.
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Attribute:
Attribute_Label: IDX_50FT
Attribute_Definition:
Indexes each elevation value as to whether it is a multiple of 50, cumulative multiples of 100, 500 or 1000 (feet), or none of these. Useful for showing generalized contours at 50 foot intervals.
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain:
Enumerated_Domain_Value: 50
Attribute:
Attribute_Label: IDX_100FT
Attribute_Definition:
Indexes each elevation value as to whether it is a multiple of 100, a cumulative multiple of 500 or 1000 (feet), or none of these. Useful for showing generalized contours at 100 foot intervals.
Attribute_Definition_Source: KCGISC
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: FIPS_CODE
Attribute:
Attribute_Label: Shape.STLength()

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: KCGIS Center
Contact_Person: Cheryl Wilder
Contact_Position: Data Sales Coordinator
Contact_Address:
Address_Type: mailing and physical
Address: 201 S Jackson St, Suite 700
City: Seattle
State_or_Province: WA
Postal_Code: 98104
Country: US
Contact_Voice_Telephone: 206-263-5220
Resource_Description: /plibrary2/topo/shapes/arc/contour005.shp
Distribution_Liability:
King County disclaims any warranty of use of any digital product or data beyond that for which it was designed.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
Digital_Transfer_Option:
Fees:
Contact KCGIS Client Services for the cost of reproduction - <http://www.kingcounty.gov/operations/GIS/GISData/GISDataDistribution.aspx>

Metadata_Reference_Information:
Metadata_Date: 20201207
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: King County GIS Center
Contact_Person: Mike Leathers
Contact_Position: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical
Address: 201 S Jackson St, Suite 700
City: Seattle
State_or_Province: WA
Postal_Code: 98104
Country: US
Contact_Voice_Telephone: 206-263-4867
Contact_Electronic_Mail_Address: firstname.lastname@kingcounty.gov
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time

Generated by mp version 2.9.12 on Mon Mar 15 10:27:47 2021