1887 - 2017 USGS CoNED Topobathy DEM (Compiled 2020): Puget Sound, WA

Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base.

Bulk download of data files in the original coordinate system.

Information on the NOAA Office for Coastal Management (OCM)

The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.

Original posting of the data by USGS as one large tiff image

Link to the USGS page for the topobathymetric model for Puget Sound. This page includes a link to download the spatial metadata.

This dataset was only used to fill in where higher resolution topographic data were not available.

This dataset is only used in small near-shore areas of Saturna Island where higher resolution data are not available.

This dataset covers the city of Bellingham, WA.

This dataset covers east-central Clallam County, WA.

This dataset covers the Dungeness coastline between Oyster House Road and Glerin Creek, and stretches from the mouth of the Dungeness River inland approximately 10 miles.

This dataset covers the Dungeness River, WA.

This dataset covers the lower mainland, British Columbia.

This dataset covers 146 square miles in the vicinity of Hood Canal.

Lake Whatcom, WA

This dataset covers a portion of the Nisqually Reach of Puget Sound.

This dataset covers the Nisqually National Wildlife Refuge.

Nooksack River

This dataset covers a portion of the Nooksack River.

This dataset covers the Lummi River Delta, a portion of the Nooksack River, and a portion of Bellingham Bay.

Nooksack Delta.

This dataset covers portions of Skagit and Whatcom Counties.

This covers portions of the following counties: King, Skagit, Snohomish, Whatcom.

The NOS Hydrographic Surveys were used in areas not covered by other bathymetry. The following surveys were included as rasters (BAGs) or used for interpolation: F00399, F00541, F00589, F00613, F00638, H01815, H01887, H01954, H02049, H02079, H02080, H02215, H02216, H06477, H06557, H06577, H06607, H06612, H06614, H06615, H06617, H06645, H06650, H06653, H06746, H06747, H06748, H06818, H07080, H07962, H08084, H08085, H08086, H08087, H08115, H08116, H08117, H08317, H08319, H08321, H08322, H08323, H08324, H08331, H08333, H08398, H08399, H08400, H08459, H08478, H08479, H08480, H08518, H08519, H08520, H08895, H08909, H08916, H08929, H09417, H10534, H10564, H10608, H10621, H10626, H10755, H10766, H10783, H10792, H10828, H10887, H10911, H10939, H11018, H11039, H11041, H11188, H11268, H11269, H11316, H11317, H11371, H11375, H11377, H11419, H11420, H11458, H11548, H11549, H11550, H11551, H11552, H11553, H11556, H11605, H11631, H11632, H11642, H11646, H11749, H11750, H11810, H11826, H11827, H12024, H12025, H12050, H12050, H12074, H12075, H12051, H12052, H12053, H12074, H12075, H12159, H12216, H12280, H12281, H12310, H12311, H12312, H12313, H12322, H12323, H12368, H12369, H12418, H12419, H12420, H12562, H12563, H12563, H12564, H12564, H12623, H12625, H12626, W00426.

This dataset covers portions of wester Pierce County, WA.

Port Townsend, WA

North Puget Sound Lowlands

Puget Sound, WA

Hood Canal

Lummi Bay

Bellingham Bay

Bellingham Bay

Bellingham Bay

San Juan County and Lummi Island, Wa

San Juan County, WA

Skagit River

Skagit Delta

Skokomish Delta

Skokomish Delta

Snohomish Delta

Snohomish Delta

Stillaguamish Delta

Stillaquamish Delta

This dataset covers portions of the following Washington counties: Whatcom, Skagit, Snohomish, Thurston, Lewis, Clark, Cowlitz, Wahkiakum, Skamania, and Gray's Harbor.

Thurston and Gray's Harbor Counties, WA

Mount Baker

Cedar River Watershed and Floodplain

Chehalis River Watershed Area

Washington El Nino

Jefferson and Clallam Counties, WA

King County, WA

Western Washington

Varies in Puget Sound

City of Redmond, WA

The principal methodology for developing the integrated topobathymetric elevation model can be organized into three main components. The "topography component" consists of the land-based elevation data, which is primarily comprised from high-resolution LiDAR data. The topographic source data will include LiDAR data from different sensors (Topographic, Bathymetric) with distinct spectral wavelengths (NIR-1064nm, Green-532nm). The "bathymetry component" consists of hydrographic sounding (acoustic) data collected using boats rather than bathymetry acquired from LiDAR. The most common forms of bathymetry that are used include: multi-beam, single-beam, and swath. The final component, "Integration", encompasses the assimilation of the topographic and bathymetric data along the near-shore based on a predefined set of priorities. The land/water interface (+1 m- -1.5 m) is the most critical area, and green laser systems, such as the Experimental Advanced Airborne Research LiDAR (EAARL-B) and the Coastal Zone Mapping and Imaging LiDAR (CZMIL) that cross the near-shore interface are valuable in developing a seamless transition. The end product from the topography and bathymetry components is a raster with associated spatial masks and metadata that can be passed to the integration component for final model incorporation. Topo/Bathy Creation Steps: Topography Processing Component: a) Quality control check the vertical and horizontal datum and projection information of the input lidar source to ensure the data is referenced to NAVD88 and NAD83, UTM. If the source data is not NAVD88, transform the input LiDAR data to NAVD88 reference frame using current National Geodetic Survey (NGS) geoid models and VDatum. Likewise, if required, convert the input source data to NAD83 and reproject to UTM. b) Check the classification of the topographic LiDAR data to verify the data are classified with the appropriate classes. If the data have not been classified, then classify the raw point cloud data to non-ground (class 1) ground (class 2), and water (class 9) classes using LP360-Classify. c) Derive associated breaklines from the classified LiDAR to capture internal water bodies, such as lakes and ponds and inland waterways. Inland waterways and water bodies will be hydro-flattened where no bathymetry is present. d) Extract the ground returns from the classified LiDAR data and randomly spatial subset the points into two point sets based on the criteria of 95 percent of the points for the "Actual Selected" set and the remaining 5 percent for the "Test Control" set. The "Actual Selected" points will be gridded in the terrain model along with associated breaklines and masks to generate the topographic surface, while the "Test Control" points will be used to compute the interpolation accuracy (Root Mean Square Error) from the derived surface. e) Generate the minimum convex hull boundary from the classified ground LiDAR points that creates a mask that extracts the perimeter of the exterior LiDAR points. The mask is then applied in the terrain to remove extraneous terrain artifacts outside of the extent of the ground LiDAR points. f) Using a terrain model based on triangulated irregular networks (TINs), grid the "Actual Selected" ground points using breaklines and the minimum convex hull boundary mask at a 1-meter spatial resolution using a natural neighbor interpolation algorithm. g) Compute the interpolation accuracy by comparing elevation values in the "Test Control" points to values extracted from the derived gridded surface; report the results in terms of Root Mean Square Error (RMSE).

Bathymetry Processing Component: a) Quality control check the vertical and horizontal datum and projection information of the input bathymetric source to ensure the data is referenced to NAVD88 and NAD83, UTM. If the source data is not NAVD88, transform the input bathymetric data to NAVD88 reference frame using VDatum. Likewise, if required, convert the input source data to NAD83 and reproject to UTM. b) Prioritize and spatially sort the bathymetry based on date of acquisition, spatial distribution, accuracy, and point density to eliminate any outdated or erroneous points and to minimize interpolation artifacts. c) Randomly spatial subset the bathymetric points into two point sets based on the criteria of 95 percent of the points for the "Actual Selected" set and the remaining 5 percent for the "Test Control" set. The "Actual Selected" points will be gridded in the empirical bayesian krigging model along with associated masks to generate the bathymetric surface, while the "Test Control" points will be used to compute the interpolation accuracy (Root Mean Square Error) from the derived surface. d) Spatially interpolate bathymetric single-beam, multi-beam, and hydrographic survey source data using an empirical bayesian krigging gridding algorithm. This approach uses a geostatistical interpolation method that accounts for the error in estimating the underlying semivariogram (data structure - variance) through repeated simulations. e) Cross validation - Compare the predicted value in the geostatistical model to the actual observed value to assess the accuracy and effectiveness of model parameters by removing each data location one at a time and predicting the associated data value. The results will be reported in terms of RMSE. f) Compute the interpolation accuracy by comparing elevation values in the "Test Control" points to values extracted from the derived gridded surface; report the results in terms of RMSE.

Mosaic Dataset Processing (Integration) Component: a) Determined priority of input data based on project characteristics, including acquisition dates, cell size, retention of features, water surface treatment, visual inspection and presence of artifacts. b) Develop an ArcGIS geodatabase (Mosaic Dataset) and spatial seamlines for each individual topographic (minimum convex hull boundary) and bathymetric raster layer included in the integrated elevation model. c) Generalize seamline edges to smooth transition boundaries between neighboring raster layers and split complex raster datasets with isolated regions into individual unique raster groups. d) Develop an integrated shoreline transition zone from the best available topographic and bathymetric data to blend the topographic and bathymetric elevation sources. Where feasible, use the minimum convex hull boundary, create a buffer to logically mask input topography/bathymetry data. Then, through the use of TINs, interpolate the selected topographic and bathymetric points to gap-fill, if required any near-shore holes in the bathymetric coverage. Topobathymetric LiDAR data sources such as the EAARL-B or CZMIL systems provide up-to-date, high-resolution data along the critical land/water interface within inter-tidal zone. e) Prioritize and spatially sort the input topographic and bathymetric raster layers based on date of acquisition and accuracy to sequence the raster data in the integrated elevation model. f) Based on the prioritization, spatially mosaic the input raster data sources to create a seamless topobathymetric composite at a cell size of 1 meter using blending (spatial weighting). g) Performed a visual quality assurance (Q/A) assessment on the output composite to review the mosaic seams for artifacts. h) Generate spatially referenced metadata for each unique data source. The spatially reference metadata consists of a group of geospatial polygons that represent the spatial footprint of each data source used in the generation of the topobathymetric dataset. Each polygon is to be populated with attributes that describe the source data, such as, resolution, acquisition date, source name, source organization, source contact, source project, source URL, and data type (topographic LiDAR, bathymetric LiDAR, multi-beam bathymetry, single-beam bathymetry, etc.).

Data as one mosaicked GeoTiFF were downloaded from the USGS Sciencebase site. Data were tiled into 4096x4096 tiles, converted to cloud optimized geotiffs, and the vertical georeferencing was added to the files (NAVD88 meters).