Digital Ground Model Data Sources for King County

Frequently anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How should this data set be cited?

   County, King, 20170914, Digital Ground Model Data Sources for King County: King County, King County, WA.

   Online Links:

   • <http://www5.kingcounty.gov/gisdataportal/Default.aspx>

   Other_Citation_Details: None

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -122.572116

   East_Bounding_Coordinate: -121.005504

   North_Bounding_Coordinate: 47.986933

   South_Bounding_Coordinate: 47.048724

3. What does it look like?

   <http://www5.kingcounty.gov/sdc/DataImages/dgm_source.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: 01-Jan-2011

   Currentness_Reference: publication date

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):

      • GT-polygon composed of chains (171)

   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.00025
      Ordinates (y-coordinates) are specified to the nearest 0.00025
      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?

   maint.GISC.dgm_source_area

   Polygon attribute table (Source: ESRI)

   OBJECTID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   SHAPE

   Feature Geometry (Source: ESRI)

   Coordinates defining the features

   area_name

   Area polygon name updated. (Source: King County)

   SERIAL_ID

   Unique identifier for each source (Source: King County)

   Integer

   DATA_SOURCE

   The organization data came from acronym.

   DESCRIP

   Description of data source organization.

   TILESUFFIX

   data source code.

   Value	Definition
   3d04	3di 2004
   3d09	3di 2009
   gs	USGS
   jb	Joined NOAA Bathymetry
   jb03	Joined 2003 Bathymetry
   jn	Joined PSLC King County
   js	Joined USGS King County
   kc	King County 2002
   pc10	Pierce County 2010
   ps	Puget Sound Lidar Consortium 2000 - 2002
   ps05	Puget Sound Lidar Consortium 2005
   ps09	Puget Sound Lidar Consortium 2009
   sc06	Snohomish County 2006
   sc10	Snohomish County 2010
   ws09	Watershed Science 2009
   ws10	Watershed Science 2010
   ws11	Watershed Science 2011
   ws12	Watershed Science 2012
   ws13	Watershed Science 2013
   noaa	National Oceanic and Air Administration Bathmetry
   wadoe	Washington Deptment of Ecology Bathymetry

   VINTAGE

   Shape.STArea()

   Shape.STLength()

   Entity_and_Attribute_Overview: None

   Entity_and_Attribute_Detail_Citation: None

Who produced the data set?

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

2. Who also contributed to the data set?

3. To whom should users address questions about the data?
   King County GIS Center
   Attn: Victor High
   Senior GIS Analyst
   201 S Jackson St, Suite 706
   Seattle, WA 98104
   US
   

   206-477-4408 (voice)
   

Why was the data set created?

King County's Elevation (digital ground model - DGM) Database has at its core a high-resolution base from lidar collected in 2002 and 2003. As new elevation data becomes available to infill missing areas (i.e., other sources for bathymetry data as lidar does not collect water areas), or becomes available that improves on the existing lidar base, it is appended to the elevation database. Where necessary, users may wish to obtain the source and vintage of information in the current database by using this map (or its underlying datafile - dgm_source.shp). The source data file also serves as an index to the various raw data files (zipped ascii files) that may exist for a given area in a location where multiple sources overlap.

How was the data set created?

1. From what previous works were the data drawn?

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

   Date: 18-May-2011 (process 1 of 13)

   Added Watershed Science 2010 LiDAR data polygons

   Date: 28-Jul-2011 (process 2 of 13)

   Added Watershed Science 2011 LiDAR data polygons

   Date: 07-Nov-2012 (process 3 of 13)

   Polygons for 2001 Multibeam Bathymetry, 2003 Blue Green Bathymetry, Snohomish 2006, Kitsap 2000, and Pierce 2010 lidar data added

   Date: 14-Jan-2014 (process 4 of 13)

   Added Watershed Science 2012 LiDAR data polygons

   Date: 14-Jan-2014 (process 5 of 13)

   Added Watershed Science 2013 LiDAR data polygons

   Date: 11-Aug-2014 (process 6 of 13)

   Redefined Bathymetry polygon JB shape. Redefined JB01 polygons suffix to NOAA. Redefined JB03 polygons suffix to WADOE.

   Date: 10-Mar-2015 (process 7 of 13)

   Added Quantum Spatial- Watershed Science 2014 LiDAR data polygons and NOAA 2014 Bathymetry polygons

   Date: 01-Dec-2015 (process 8 of 13)

   Added Quantum Spatial- Watershed Science 2015 LiDAR data polygons

   Date: 07-Sep-2017 (process 9 of 13)

   Added Quantum Spatial- Watershed Science 2016 LiDAR data polygons

   Date: 07-Sep-2017 (process 10 of 13)

   Added Quantum Spatial- Watershed Science 2016 LiDAR data polygons

   Date: 14-Sep-2017 (process 11 of 13)

   Added Quantum Spatial- Watershed Science 2017 LiDAR data polygons

   Date: 25-Jul-2018 (process 12 of 13)

   Added Quantum Spatial- Watershed Science 2018 LiDAR data polygons

   Date: 29-Jul-2019 (process 13 of 13)

   Added Quantum Spatial- Watershed Science 2019 LiDAR data polygons

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

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

1. How well have the observations been checked?

   None

2. How accurate are the geographic locations?

3. How accurate are the heights or depths?

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

   The project area source polygons cover the entire extent of the elevation database.

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

   Project area boundaries define extent of each projects contribution to the underlying 7500 data tile. Where project areas overlap, multiple versions of the tile will exist, each with a unique suffix defining the data sources in that tile. A tile is named with the most recent data source suffix even if the newest source contributes only a small portion to the extent of the new tile.

How can someone get a copy of the data set?

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

Access_Constraints: None

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.

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
   US
   

   206-477-4421 (voice)
   

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

   /plibrary2/survey/shapes/polygon/dgm_source.shp

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?
   • Availability in digital form:

     Data format:	ESRI Shapefile
     Network links:	//gisdw/kclib/plibrary2/survey/shapes/polygon/dgm_source.shp /plibrary2/survey/shapes/polygon/dgm_source.shp

   • Cost to order the data:

     Contact KCGIS Client Services for the cost of reproduction - <http://www.kingcounty.gov/operations/GIS/GISData/GISDataDistribution.aspx>

Who wrote the metadata?

Dates:

Last modified: 04-Feb-2021

Metadata author:

King County GIS Center
Attn: Victor High
GIS Analyst
201 S Jackson St, Suite 706
Seattle, WA 98104
US

206-263-4845 (voice)
victor.high@kingcounty.gov

Metadata standard:

FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)