2013-2015 USACE NCMP Topobathy Lidar: Lake Huron (MI)

These files contain classified topo/bathy lidar data. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), and 29 (valid bathymetric data). Classes 1 and 2 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. These data were 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. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 National Adjustment of 2011 (NAD83 NA2011). Vertical positions are referenced to the NAD83 NA11 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12A model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Once converted to orthometric heights, the data are then converted to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration). Upon arrival at NOAA's Office for Coastal Management the data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 12a for Digital Coast provisioning purposes. The 3-D position data are sub-divided into a series of LAS files, which are tiled into quarter-quads or 5km boxes. The LAS file index is provided by the shape file, "mi_huron_boxes.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 name, "Box" number and product type. An example file name is "2013_NCMP_MI_Huron_01_GeoClassified_IGLD85.las", where 2013 is the year of data collection, NCMP is the project under which data were collected, MI_Huron is the area of data collection, 01 is the "Box" number and GeoClassified_IGLD85 is the product type.

Upon arrival to NOAA's Office for Coastal Management the data were converted to geographic coordinates and to GRS80 (ellipsoid) in meters.

These data were collected as a part of the NCMP to depict the elevations above and below the water in the Michigan coastal zone.

10453

The following DEMs are available for this project upon request (coastal.info@noaa.gov):

1m grid

5m grid

1m Bare Earth

A footprint of this data set may be viewed in Google Earth at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4844/supplemental/mi2013_USACE_NCMP_lakehuron_m4844.kmz

LAS 1.2 format (classes 1,2,29)

none

These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

Any conclusions drawn from the analysis of this information are not the responsibility of USACE, JALBTCX, NOAA, the Office for Coastal Management or its partners.

This data can be obtained on-line at the following URL:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4844

The data set is dynamically generated based on user-specified parameters.;

These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.

These data are not attributed. | Quantitative Value: None | Quantitative Test Explanation: These data are not attributed.

Topo data - Compiled to meet 1 m @ 95% confidence level. Bathy data - compiled to meet 3.5 + 0.05*d meters @ 95% confidence level (d is depth).; Quantitative Value: 1.0 meters, Test that produced the value: +/- 1 m, 2 sigma

Topo data - 19.6 cm @ 95% confidence level (10 cm RMSE). Bathy shallow FOV data - SQRT((0.25^2)+((0.0075d)^2)) meters at @ 95% confidence level. Bathy deep FOV data - SQRT((0.30^2)+((0.013d)^2)) meters @ 95% confidence level (d is depth).; Quantitative Value: 0.10 meters, Test that produced the value: +/- 10 cm RMSE

This data set covers the spatial extent of topographic lidar data obtained during this survey.

During inspection and QC of the lidar point cloud, flightline to flightline elevation differences met the CZMIL sensor specifications.