2020 USACE USGS Topobathy Lidar DEM: Cape May & Atlantic City, NJ
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:66981 | Updated: January 10, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2020 USACE USGS Topobathy Lidar DEM: Cape May & Atlantic City, NJ, https://www.fisheries.noaa.gov/inport/item/66981.
Full Citation Examples
These files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. The 3-D position data are sub-divided into a series of LAS files, which are tiled into 1-km by 1-km boxes defined by the Military Grid Reference System. The LAS file index is provided by the shape files, "MGRS_1km_18S.shp ", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, effort, area, "Box" number and data product type. An example file name is "2020_USGS_NJ_18SVJ9738_BareEarth_1mGrid.tif", where 2020 is the year of data collection, USGS is the effort under which data were collected, NJ is the area of data collection, 18SVJ9738 is the "Box" number and BareEarth_1mGrid is the data product type.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
Distribution Information
-
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.
-
GeoTIFF
Bulk download of data files in the original coordinate system.
None
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.
Controlled Theme Keywords
BATHYMETRY, BATHYMETRY/SEAFLOOR TOPOGRAPHY, COASTAL ELEVATION, COASTAL PROCESSES, DIGITAL ELEVATION/TERRAIN MODEL (DEM), elevation, TERRAIN ELEVATION
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-75.028618° W,
-74.244779° E,
39.550852° N,
38.927716° S
2020-07-02 - 2020-07-03
Item Identification
Title: | 2020 USACE USGS Topobathy Lidar DEM: Cape May & Atlantic City, NJ |
---|---|
Status: | Completed |
Creation Date: | 2020 |
Abstract: |
These files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. The 3-D position data are sub-divided into a series of LAS files, which are tiled into 1-km by 1-km boxes defined by the Military Grid Reference System. The LAS file index is provided by the shape files, "MGRS_1km_18S.shp ", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, effort, area, "Box" number and data product type. An example file name is "2020_USGS_NJ_18SVJ9738_BareEarth_1mGrid.tif", where 2020 is the year of data collection, USGS is the effort under which data were collected, NJ is the area of data collection, 18SVJ9738 is the "Box" number and BareEarth_1mGrid is the data product type. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record. |
Purpose: |
This data was collected by the USACE in support of the U.S. Geological Survey to assess changes in elevation above and below water along the coast of New Jersey. |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM)
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > SOLID EARTH > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL PROCESSES
|
ISO 19115 Topic Category |
elevation
|
Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > NEW JERSEY
|
Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > SEA FLOOR
|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords |
LIDAR > Light Detection and Ranging
|
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords |
Airplane > Airplane
|
Physical Location
Organization: | Office for Coastal Management |
---|---|
City: | Charleston |
State/Province: | SC |
Data Set Information
Data Set Scope Code: | Data Set |
---|---|
Data Set Type: | Elevation |
Data Presentation Form: | Model (digital) |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit: | Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. |
Support Roles
Data Steward
Date Effective From: | 2022 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2022 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Metadata Contact
Date Effective From: | 2022 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2022 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -75.028618 | |
---|---|---|
E° Bound: | -74.244779 | |
N° Bound: | 39.550852 | |
S° Bound: | 38.927716 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2020-07-02 |
End: | 2020-07-03 |
Spatial Information
Spatial Resolution
Horizontal Distance: | 1.0 Meter |
---|
Spatial Representation
Representations Used
Grid: | Yes |
---|
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||
|
Reference System 2
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Access Information
Security Class: | Unclassified |
---|---|
Data Access Procedure: |
Data is available online for bulk and custom downloads. |
Data Access Constraints: |
None |
Data Use Constraints: |
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. |
Distribution Information
Distribution 1
Start Date: | 2022-04-08 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9483/details/9483 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2022 - Present) |
File Name: | Customized Download |
Description: |
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. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2022-04-08 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/USACE_NJ_DEM_2020_9483/index.html |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2022 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in the original coordinate system. |
File Type (Deprecated): | GeoTIFF |
Distribution Format: | GeoTIFF |
URLs
URL 1
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9482/ept.json |
---|---|
Name: | Entwine Point Tiles (EPT) |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 2
URL: | https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?m=9482&g=geoid18 |
---|---|
Name: | Potree 3D View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 3
URL: | https://coast.noaa.gov/dataviewer/ |
---|---|
Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type: |
Online Resource
|
File Resource Format: | HTML |
Description: |
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. |
URL 4
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9482/supplemental/usace2020_nj_m9482.kmz |
---|---|
Name: | Browse graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | KML |
Description: |
This graphic displays the footprint for this lidar data set. |
URL 5
URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9482/details/9482 |
---|---|
Name: | Custom Point Download |
URL Type: |
Online Resource
|
File Resource Format: | Zip |
Description: |
Link to custom download, from the Data Access Viewer (DAV), the lidar point data from which these raster Digital Elevation Model (DEM) data were created. |
Data Quality
Horizontal Positional Accuracy: |
CZMIL topographic data - Compiled to meet 1 m horizontal accuracy at 95% confidence level. CZMIL bathymetric data - Compiled to meet 3.5 + 0.05d m horizontal accuracy at 95% confidence level, d is depth. |
---|---|
Vertical Positional Accuracy: |
CZMIL topographic data - Compiled to meet 20 cm vertical accuracy at 95% confidence level. CZMIL bathymetric shallow FOV data - Compiled to meet SQRT((0.25^2) +((0.0075d)^2)) m vertical accuracy at 95% confidence level, d is depth. CZMIL bathymetric deep FOV data - Compiled to meet SQRT((0.30^2) +((0.013d)^2)) m vertical accuracy at 95% confidence level, d is depth. |
Completeness Measure: |
JALBTCX evaluates final data coverage using techniques that are common to the lidar industry. These techniques are performed in a 3D environment for visual review of the final data coverage and verification of data alongside lidar waveforms and imagery collected concurrent with the lidar. Data reviewers perform checks to verify (1) extreme high and/or low elevation values have been invalidated, (2) elevations in areas of swath overlap are internally consistent, (3) binned standard deviation values meet CZMIL specifications, (4) point cloud classifications are valid, and (4) CZMIL processing modes are valid. |
Completeness Report: |
Every effort within operational constraints was made to achieve the intended data coverage and planned point densities. |
Conceptual Consistency: |
Planned data coverage for this dataset includes the shoreline along the coast of New Jersey. Lidar and imagery data acquisition was focused on a 1500 meter swath of the shoreline that generally extends from the shoreline onshore 500 meters and from the shoreline offshore to 1000 meters or laser extinction, whichever occurs first. The planned point spacing is 70 centimeters on land and in shallow water. In deeper water the planned point spacing is 2 meters. Gaps or data holidays exist in the bathymetric portion of the data coverage due to a number of operational and environmental conditions, including by not limited to, active surf, low-reflectivity bottom substrate materials and turbidity in the water column. Please see the Report of Survey for additional details. |
Quality Control Procedures Employed: |
Every effort within operational constraints was made to acquire data that meets specifications as outline in this project's Statement of Work. Per flight block, elevations in areas of swath overlap are internally consistent and meet CZMIL specifications. Anomalous high and/or low elevation values have been removed, and point cloud classification algorithms have been validated via manual review and QC. Temporal differences in elevation exist in areas of active near shore processes from the dune to the depth of closure. JALBTCX conducts operations in a manner to ameliorate temporal differences, to include the collection of entire flight blocks within single missions. For a given flight block, it's adjacent flight blocks are captured within 3 days as weather and airspace permit. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-CO |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
Lineage Statement: |
CZMIL data is processed from raw lidar waveforms to point clouds using the CZMIL HydroFusion software package. Point clouds are then classified and edited in industry-standard software packages. Derivative data products are generated through the application of gridding and contouring algorithms in a GIS environment. The data processing workflow, including software packages, algorithms and parameters are provided in detail, herein this metadata as Process Steps. |
---|
Sources
USACE JALBTCX
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | USACE JALBTCX |
Process Steps
Process Step 1
Description: |
These data were collected using the CZMIL system. It is owned and operated by the U.S. Army Corps of Engineers (USACE). The system collects topobathy lidar data at 10 kHz and RGB imagery at 2 Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of NovAtel and POS A/V 610 equipment. All raw data streams are transferred to the office for downloading and processing in CZMIL's HydroFusion software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid and have the withheld bit set. |
---|---|
Process Date/Time: | 2020-07-02 00:00:00 |
Process Step 2
Description: |
LAS files are imported into TerraScan V13 module within MicroStation V8i, classifies valid topobathy data as ground points (2) and unclassified points (1), and valid bathymetric points (29). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm's "ground" surface instead of manually reclassifying those points. They are partitioned into a series of 1-km delivery boxes, one Classified LAS file per box. The format of the file is LAS version 1.2. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), and 29 (valid bathymetric data). Vertical positions are also transformed from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The files are then compressed with the open-source LASzip utility, which is part of the LAStools package (LAStools, "Efficient LiDAR Processing Software" (version 170923, unlicensed)), obtained from http://rapidlasso.com/LAStools. |
---|---|
Process Date/Time: | 2021-01-14 00:00:00 |
Process Step 3
Description: |
Data classified as ground points (2) and bathymetric points (29) in the las files are converted to a grid by generating a triangulated irregular network (TIN) and then extracting the grid node elevations from the TIN surface. The origin point of the grid is located at a horizontal position whose value is evenly divisible by the 1m grid resolution such that rasters from subsequent surveys have common cell boundaries. JALBTCX uses Quick Terrain Modeler V8.2.1 to perform this operation utilizing the following parameters; "Legacy Triangulation", "Max Sample Excursion - 500", "Max Triangle Side "500", and "Tiling Settings Snap to Grid (Expand)." The grid is exported from Quick Terrain Modeler as a GeoTIFF 32-Bit DEM file. Utilizing an in-house python script within Jupyter Notebook, the null data values in the file are converted from -9999 to NoData with the Set Null tool from the ArcGIS Spatial Analyst Toolbox. The script also calls the Define Projection tool from the ArcGIS Data Management Toolbox to set the file's coordinate system information to "The North American Datum of 1983 (2011)." The raster is then multiplied against a corresponding 1m mask raster, an intermediate mask image produced from JALBTCX's 1mGrid data product, to remove interpolated areas where data does not exist. Horizontal positions, provided Universal Transverse Mercator Zone 18 North (NAD83 2011). Vertical positions are referenced to the NAD83 (2011) ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12B model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). |
---|---|
Process Date/Time: | 2021-01-28 00:00:00 |
Process Step 4
Description: |
The NOAA Office for Coastal Management (OCM) received GeoTiff format files from USACE JALBTCX for the New Jersey coastline project area. The bare earth raster files were at a 1 m grid spacing. The data were in UTM Zone 18, (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 6347, Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes. |
---|---|
Process Date/Time: | 2022-04-08 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2020 USACE USGS Topobathy Lidar: Cape May & Atlantic City, NJ |
Catalog Details
Catalog Item ID: | 66981 |
---|---|
GUID: | gov.noaa.nmfs.inport:66981 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2022-04-08 20:06+0000 |
Metadata Record Last Modified By: | Kirk Waters |
Metadata Record Last Modified: | 2024-01-10 19:24+0000 |
Metadata Record Published: | 2024-01-10 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2022-04-11 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2023-04-11 |