Data Management Plan

These files contain topographic lidar and bathymetric data classified as ground (2), unclassified (1), and NOAA OCM bathymetry (11) in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. Rejected or invalid data is classified as noise (7). These data were collected by a HawkEye II (HEII) lidar sensor. The HEII integrates topographic and bathymetric lidar sensors, and a digital camera 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 Geographical Information Systems (GIS). Specialized in-house

and commercial software packages are used to process the native lidar data into 3D positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). For the topographic data, vertical positions were acquired to the NAD83 ellipsoid. The National Geodetic Survey's (NGS) GEOID09 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The bathymetry files for this data set were received by NOAA OCM after the initial topographic files. The bathymetry files were added to the existing topographic data set. The bathymetry files were received in csv format and in geographic coordinates, referenced to the North American Datum of 1983 (NAD83). They were in ellipsoid heights, in meters. For data storage and Digital Coast provisioning, the NOAA OCM converted the topographic files to ellipsoid heights and the bathymetry files to las format. The bathymetry files were also classified as 11 (NOAA OCM bathymetry). The 3D position data are sub-divided into a series of files each covering approximately 5 kilometers of shoreline.

In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.

Original contact information:

Contact Org: JALBTCX

Title: Data Production Manager

Phone: 228-252-1121

Email: JALBTCX@usace.army.mil

Lineage Statement:
The USACE collected, processed, and provided the data to the NOAA Office for Coastal Management (OCM). OCM received the data and processed it to be available for custom download from the Data Access Viewer (DAV) and for bulk download from https.

Process Steps:

• 2010-11-30 00:00:00 - These data were collected using a HEII system. The system collects topographic lidar data at 64kHz, bathymetric lidar data at 4kHz and RGB imagery at 1Hz. Aircraft position, velocity and acceleration information are collected using an Applanix POS A/V 410. All raw data are processed using AHAB's Coastal Survey Studio (CSS) 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. Fledermaus and GreenC Solutions software is used to inspect and QA/QC data, and anomalous data are flagged as invalid. Data are exported to LAS format using GreenC Solutions and imported to Terrascan for classification. A customized classification macro is used to distinguish ground points (2) and unclassified points (1). The classification results are reviewed and any misclassified points are manually edited. In areas of dense vegetation the bare ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. Classified data are exported from Terrascan and Blue Marble Desktop converts all classified LAS data from UTM to NAD83 geographic coordinates and NAVD88 heights using the Geoid 09 model.
• 2012-02-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic data in LAS v1.2 format. The files contained LiDAR elevation measurements. The data were received in geographic coordinates (NAD83) and vertically referenced to NAVD88 using the Geoid09 model. The vertical units of data were meters. The data were classified according to ASPRS LAS classification scheme (1 = unclassified, 2 = ground). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from orthometric heights to ellipsoidal heights (GRS80) using Geoid 09. 2. The LAS data were sorted by latitude and the headers were updated.
• 2015-01-12 00:00:00 - The NOAA Office for Coastal Management (OCM) received the bathymetric data for this data set at a later date than the topographic data. The bathymetric data was processed to be included with the existing topographic data. The data were received in csv format, in geographic coordinates (NAD83) and were in ellipsoidal heights. The vertical units of data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The csv files were converted to las files. 2. The las points were classified as 11 (NOAA OCM bathymetry).

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;