1851 - 2020 USGS CoNED Topobathy DEM (Compiled 2022): Coastal Carolinas

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.

Link to the spatial metadata gdbs and data dictionary for North Carolina and South Carolina.

Dorchester County, SC

Charleston, Colleton, Jasper Counties, SC

Marion County, SC

Florence County, SC

Allendale county SC, USA

Hampton County SC

SC Beaufort County

Horry County, NC

VA, NC, SC, GA and FL

Coastal SC

South Carolina Georgetown County

East Central SC

Southern Coast (VA, NC, SC)

NC, SC Coast

East Coast (NC, VA)

NC

NC

Coast of NC, SC, GA and FL

Coast of NC, SC, GA and FL

NC, SC, and GA

Coastal counties of NC

Georgetown County SC

NY, NJ, DE, MD, VA, NC, SC, and GA

Coverage DC, DE, MD, PA, and VA

Berkeley County, SC

Charleston County, SC

Williamburg County, SC

NC

The principal methodology for developing the integrated topobathymetric digital elevation model (TBDEM) can be organized into three main components. The "topography component" consists of the land-based elevation data, which is primarily comprised from high-density 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 watercraft rather than bathymetry acquired from green laser lidar within an airborne platform. The most common forms of bathymetric acquisitions include are 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 elevation) 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 TBDEM created 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 the North American Vertical Datum of 1988 (NAVD88), the North American Datum of 1983 (NAD83), and the Universal Transverse Mercator (UTM) projection. 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 NOAA’s Vertical Datums Transformation (VDatum) software. 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 (RMSE) 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 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 are 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 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 (RMSE) 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.

Integration Component: a.) Analyze the input data priority based on project characteristics, including acquisition dates, cell size, retention of features, water surface treatment, visual inspection, and presence of artifacts. b.) Prioritize and spatially sort the input topographic, topobathymetric, and bathymetric raster layers based on date of survey acquisition date, accuracy, spatial distribution, and point density to sequence the raster data in the integrated elevation model. c.) Develop an ArcGIS geodatabase (Mosaic Dataset) and spatial seamlines for each individual topographic, topobathymetric, and bathymetric raster layer included in the integrated elevation model. d.) Create an overview project masking polygon (based on final pilot study AOI) e.) Using Grid Index Features, create a 6000x6000 fishnet feature class for tile-based integration processing f.) Create simple raster (vector) boundaries (custom simple_raster_bnd_batch tool) from the final set of input rasters based on the input priority. The rasters should be prioritized with the highest priority ranking on top and so forth. g.) Generate spatially referenced metadata for each input raster (custom make spatial metadata tool) from the simple raster boundary files, based on the input priority. The boundaries should be prioritized with the lowest priority (input raster layer) ranking on top and so forth. The spatially referenced metadata consists of the group of geospatial polygons that represent the spatial footprint of each data source used in the generation of the TBDEM. Each polygon is populated with raster metadata 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, topobathymetric lidar, multibeam bathymetry, single-beam bathymetry, etc.). h.) Generalize seamline edges to smooth transition boundaries between neighboring raster layers and split complex raster datasets with isolated regions into individual unique raster groups. i.) Using the spatial metadata and tile fishnet, spatially mosaic (custom make micro mosaic dataset tool) the input raster data sources based on priority to create a seamless topobathymetric composite at a cell size of 1-meter using a linear spatial blending (ten pixel overlapping area) technique between input source layers. j.) Perform a visual quality assurance (Q/A) assessment on the output TBDEM composite to review the integrated mosaic for artifacts and anomalies.

The NOAA Office for Coastal Management (OCM) received two GeoTiff format files from USGS for the North and South Carolina project area. The bare earth raster files were at a 1 m grid spacing. The data were in UTM Zone 17 NAD83(2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 6346, Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes.

In January 2023 the Office for Coastal Management (OCM) received a replacement tiff from USGS for the NC portion of this data. The new NC tiff (named version 20) includes the following:

1. Additional bathymetry in Neuse, Pamlico, and Chowan Rivers

2. Lowered inappropriately elevated channels

3. Replaced an input project formerly processed with a nearest-neighbor resampling with bilinear.

The bare earth raster file was at a 1 m grid spacing. The data were in UTM Zone 17 NAD83(2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 6346, Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes. The earlier version of the NC tiff was deleted.