King County vector basemap with lidar derived hillshade overlaid.

Mountain peaks and other significant topographic features, with elevations, for King County

DRNBASIN is replaced with a higher detail TOPO_CATCHMENT. The difference between the two is DRNBASIN was digitized from existing paper maps based on USGS quad maps in the early 1990s. While the TOPO_CATCHMENT was produced using Arc/Info GRID Watershed commands on 6 foot cell GRIDS built from LIDAR ascii ground model data. Topo_Catchment is higher in accuracy then DRNBASIN

These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the Sea Level Rise and Coastal Flooding Impacts Viewer. It depicts potential sea level rise and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at sea level rise and coastal flooding impacts. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The Sea Level Rise and Coastal Flooding Impacts Viewer may be accessed at: https://coast.noaa.gov/slr. This metadata record describes the Washington, Southwest Puget Sound digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer described above. This DEM includes the best available lidar known to exist at the time of DEM creation that met project specifications. This DEM includes data for King, Pierce, and Thurston Counties. The DEM was produced from the following lidar data sets: 1. 2016 King County, WA Lidar 2. 2016 West Washington Lidar 3. 2010-2011 USGS ARRA Lidar: Pierce County The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88, Geoid12B) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 3 meters.

These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the Sea Level Rise and Coastal Flooding Impacts Viewer. It depicts potential sea level rise and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at sea level rise (slr) and coastal flooding impacts. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The Sea Level Rise and Coastal Flooding Impacts Viewer may be accessed at: http://www.coast.noaa.gov/slr This metadata record describes the digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer described above. This DEM includes the best available data known to exist at the time of DEM creation that met project specifications, for mainland Virginia, this includes portions of the following counties: Alexandria, Arlington, Charles City, Chesapeake, Essex, Fairfax, Falls Church, Franklin City, Fredericksburg City, Gloucester, Hampton, Isle of Wight, James City, King and Queen, King George, King William, Lancaster, Mathews, Middlesex, New Kent, Newport News, Norfolk, Northumberland, Poquoson City, Portsmouth, Prince George, Prince William, Richmond, Southampton, Stafford, Suffolk, Surry, Sussex, Virginia Beach, Westmoreland, Williamsburg, and York. This DEM also includes the District of Columbia. The DEM is derived from the following lidar: 1. New Kent, Charles City, Prince George Counties 2012 FEMA Middle Counties VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/Middle_Counties/Metadata/Project_Report/Dewberry_ProjectReport_MiddleCounties.pdf Additional coverage provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 2. King William County 2011 FEMA King William County VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/KingWilliamCo/KingWilliam_Metadata/Dewberry_ProjectReport_KingWilliam.pdf Additional coverage provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 3. Hampton and Portsmouth Cities 2011 FEMA Virginia Southern Cities Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/SouthernCities/SouthernCities_Metadata/Dewberry_ProjectReport_SouthernCities.pdf 4. Franklin City and Southampton County 2011 FEMA Virginia Counties South Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/VA_Counties_South/SouthernCo_Metadata/Dewberry_ProjectReport_Southampton.pdf 5. Fredericksburg City and Essex, King George, Prince William, Richmond, Stafford, Westmoreland Counties 2011 FEMA Virginia Counties North Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/VA_Counties_North/NorthernCo_Metadata/Dewberry_ProjectReport_NorthernCounties.pdf 6. Northumberland, Middlesex, Lancaster, King and Queen, Gloucester, Mathews, James City, Williamsburg, Surry, Isle of Wight, Suffolk Counties 2010/2011 USGS Eleven County Coastal VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/a11county/Metadata/PROJECT_REPORT/Final%20Project%20Report%20for%20USGS%20Virginia%20LiDAR_01312011.pdf Additional coverage for Surry and King and Queen counties provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 7. Alexandria, Arlington, and Falls Church Counties 2008 NGA Capital Region Lidar The lidar data is not publicly available, the data was provided by the State of Virginia as bare earth DEMs. 8. Fairfax County 2008 NGA Capital Region Lidar The lidar data is not publicly available, the data was provided by the State of Virginia as bare earth DEMs. 2012 FEMA Virginia Lidar This data may be downloaded from USGS EarthExplorer at: http://earthexplorer.usgs.gov/ 9. York, Poquoson City, Newport News, Norfolk, Chesapeake, Virginia Beach, and Sussex Counties Data provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 2010 US Army Corps of Engineers (USACE) Lidar This data may be downloaded at: http://www.coast.noaa.gov/dataviewer/index.html?action=advsearch&qType=in&qFld=ID&qVal=1132 The metadata for this data may be accessed at: http://coast.noaa.gov/dataviewer/webfiles/metadata/usace2010_va_template.html 10.District of Columbia Washington, DC and Environs, 2008, 1/9 Arc second National Elevation Dataset (NED) This data may be downloaded at: http://viewer.nationalmap.gov/viewer/ Hydrographic breaklines were delineated from LiDAR intensity imagery generated from the LiDAR datasets. The DEM is hydro flattened such that water elevations are less than or equal to 0 meters. The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 10 meters.

Generalized 20-foot contour isolines derived from Puget Sound lowlands combined bathymetry and elevation digital elevation model.

City of Seattle 2 ft contours derived from Lidar captured in 2021. Contour lines display at 2ft, 10ft and 50ft intervals dependent on scale. Lines have been smoothed and generalized for display and performance.

Development Detail:

This vector tile service includes topographic contour lines representing elevation at 2-foot intervals within the city of Seattle.

The contours were derived from a bare earth - digital elevation model (DEM) with a pixel resolution of 1.5 feet. The lidar data that created the DEM were collected by NV5 Geospatial over the spring and summer months of 2021 and provided to the city by King County in 2022.

The DEM used to generate the contours was filtered using the Focal Statistics tool in ArcGIS, which served to limit some abrupt changes in cell values. A 3x3 rectangular neighborhood analysis was applied and a mean value was calculated per raster cell.

After running the Focal Statistics tool, 2-foot contours were generated from the filtered DEM. To reduce file size and improve performance, the contours were generalized further using the Smooth Line tool in ArcGIS. A smoothing algorithm type of Polynomial Approximation with Exponential Kernel (PAEK) and a smoothing tolerance of 20 feet was selected in the Smooth Line tool parameter options.

Finally, after executing both generalization tools (Focal Statistics and Smooth Line), all lines less than 25 feet in length were omitted from the final output.

Please note: The 2-foot contours are intended to be used for general reference and cartographic purposes only and should not be used for analysis purposes.

Layered GeoPDF 7.5 Minute Quadrangle Map. Layers of geospatial data include orthoimagery, roads, grids, geographic names, elevation contours, hydrography, and other selected map features.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

DRNBASIN is replaced with a higher detail TOPO_CATCHMENT. The difference between the two is DRNBASIN was digitized from existing paper maps based on USGS quad maps in the early 1990s. While the TOPO_CATCHMENT was produced using Arc/Info GRID Watershed commands on 6 foot cell GRIDS built from LIDAR ascii ground model data. Topo_Catchment is higher in accuracy then DRNBASIN

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Normally, any FIRM that has associated flood profiles has cross sections. The S_XS table contains information about cross section lines. These lines usually represent the locations of channel surveys performed for input into the hydraulic model used to calculate flood elevations. Sometimes cross sections are interpolated between surveyed cross sections using high accuracy elevation data. Depending on the zone designation (Zone AE, Zone A, etc.), these locations may be shown on Flood Profiles in the FIS report and can be used to cross reference the Flood Profiles to the planimetric depiction of the flood hazards. This information is used in the Floodway Data Tables in the FIS report, as well as on the FIRM panels.

A spatial tiling index designed for storage of file-based image and other raster (i.e., LiDAR elevation, landcover) data sets. An irregular grid of overlapping polygons, each enclosing its respective Public Land Survey System (PLSS) township in an orthogonal polygon minimally encompassing all portions of that township, i.e., minimum bounding rectangle. The amount of overlap between adjacent tiles varies depending on the geometry of the underlying township. Currently extended to include all townships within or partially within King County as well as those townships in the southwestern portion of Snohomish County included within King County's ESA/SAO project area. The name of the spatial index is derived from the acronym (I)n(D)e(X) (P)olygons for (T)ownship-(R)ange, (M)inimum (B)ounding (R)ectangle, or idxptrmbr. Tile label is the t(township number)r(range number)as in t24r02. The meridian zone identifiers, N for townships and E for range is inferred as this index is intended as a local index for ease of use by the majority of users of GIS data. Lowercase identifiers are used for consistency between Unix and Windows OS storage. This index or tile level is the primary user-access level for most LiDAR elevation, orthoimagery and high-resolution raster landcover data. However, not all image and raster data is stored at the tiling level if a given data's resolution does not justify storing the data as multiple tiles.

Tolt River watershed area 5ft contours derived from Lidar captured in 2021. Contour lines display at 5ft, 25ft, 50ft, 100ft, 200ft and 400ft intervals dependent on scale. Lines have been smoothed and generalized for display and performance.Development Detail:This vector tile service includes topographic contour lines representing elevation at 5-foot intervals within the Tolt River watershed area.The contours were derived from a bare earth - digital elevation model (DEM) with a pixel resolution of 1.5 feet. The lidar data that created the DEM were collected by NV5 Geospatial over the spring and summer months of 2021 and provided to the city by King County in 2022.The DEM used to generate the contours was filtered using the Focal Statistics tool in ArcGIS, which served to limit some abrupt changes in cell values. A 3x3 rectangular neighborhood analysis was applied and a mean value was calculated per raster cell.After running the Focal Statistics tool, 5-foot contours were generated from the filtered DEM. To reduce file size and improve performance, the contours were generalized further using the Smooth Line tool in ArcGIS. A smoothing algorithm type of Polynomial Approximation with Exponential Kernel (PAEK) and a smoothing tolerance of 20 feet was selected in the Smooth Line tool parameter options.Finally, after executing both generalization tools (Focal Statistics and Smooth Line), all lines less than 25 feet in length were omitted from the final output.Please note: The 5-foot contours are intended to be used for general reference and cartographic purposes only and should not be used for analysis purposes.

These 4' contours were produced as part of the VGIN mapping project executed in 2006 and 2007. Contours were provided to jurisdictions who chose to use the upgrade option for contour generation. The contours are provided in Personal Geodatabase format. Due to size limitations, a jurisdiction may contain more than one GeoDatabase.