gov.noaa.nmfs.inport:74316 eng UTF8 dataset Elevation Office for Coastal Management resourceProvider NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact 2026-03-04T19:17:17 ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data ISO 19115-2:2009(E) EPSG::6319 2023 NOAA Topobathy Lidar: Northern Lake Michigan & Northern Lake Huron, MI mi2023_lakes_mi_huron_m10247_metadata 2024-08-15 publication NOAA/NMFS/EDM 74316 https://www.fisheries.noaa.gov/inport/item/74316 WWW:LINK-1.0-http--link Full Metadata Record View the complete metadata record on InPort for more information about this dataset. information https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10247/ept.json WWW:LINK-1.0-http--link Entwine Point Tile (EPT) 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. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10247/supplemental/mi2023_lake_mi_lake_huron_m10247.kmz WWW:LINK-1.0-http--link Lidar Footprint Link to the dataset footprint. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10247/supplemental/GreatLakes2023_Topobathy_Lidar_Project_Report.pdf WWW:LINK-1.0-http--link Lidar Report Link to the project lidar report. download https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10247/ept.json WWW:LINK-1.0-http--link 3D Viewer (Potree NOAA) Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. download https://coast.noaa.gov/dataviewer/ WWW:LINK-1.0-http--link NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) 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. download Product: This topobathy lidar dataset consists of processed classified LAS 1.4 files used to create intensity images and topobathymetric DEMs as necessary. Three project areas for this dataset are: 1. Lansing Shoals - 4273 individual 500 m x 500 m tiles 2. Green Bay - 1837 individual 500 m x 500 m tiles 3. Lake Huron - 2871 individual 500 m x 500 m tiles Geographic Extent: The Michigan coastline along parts of northern Lake Michigan and northern Lake Huron, covering approximately 627 square miles. 1. Lansing Shoals portion (Lake Michigan) of the AOI covers approximately 311 square miles 2. Green Bay portion (Lake Michigan) of the AOI covers approximately 116 square miles 3, Lake Huron portion of the AOI covers approximately 200 square miles Dataset Description: The Great Lakes Topobathymetric Lidar project called for the planning, acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 1 meter for bathymetric areas. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), UTM zones 16N and 17N, meters and vertical datum of NAVD88 (Geoid 18), meters. Ground Conditions: 1. Lansing Shoals - Lidar was collected for the Lansing Shoals region from September 14, 2023 to September 25, 2023, while no snow was on the ground and rivers were at or below normal levels 2. Green Bay - Lidar was collected for the Green Bay region from September 28, 2023 to October 5, 2023, while no snow was on the ground and rivers were at or below normal levels. 3, Lake Huron - Lidar was collected for the Northern Lake Huron region from September 16, 2023 to October 4, 2023, while no snow was on the ground and rivers were at or below normal levels. This project has two primary goals to fill critical gaps in our understanding of benthic habitat within Lakes Michigan and Huron. The first goal is the collection of new bathymetric lidar to support multiple agencies including NOAA; US Fish and Wildlife Service; state agencies with Michigan and Wisconsin; and other regional partners' mapping and modeling needs by expanding existing high resolution bathymetry coverage in and around the Entry to Lansing Shoals and Lansing Shoals, Lake Michigan, and Northern Huron in Lake Huron. The second goal is to use this bathymetry in the creation of new benthic mapping products using the Coastal and Marine Ecological Classification Standard (CMECS). Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images and Raster DEMs. The purpose of these lidar data was to produce high accuracy Digital Elevation Model (DEM) with a 1 meter cell size. These lidar point cloud data were used to create intensity images and topobathymetric DEMs as necessary. Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA) completed NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information custodian notPlanned EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY > COASTAL BATHYMETRY EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION theme Global Change Master Directory (GCMD) Science Keywords 17.0 CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > GREAT LAKES CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MICHIGAN VERTICAL LOCATION > LAND SURFACE place Global Change Master Directory (GCMD) Location Keywords 20.8 LIDAR > Light Detection and Ranging instrument Global Change Master Directory (GCMD) Instrument Keywords 17.2 Airplane > Airplane platform Global Change Master Directory (GCMD) Platform Keywords 17.2 DOC/NOAA/NOS/OCM > Office of Coastal Management, National Ocean Service, NOAA, U.S. Department of Commerce dataCentre Global Change Master Directory (GCMD) Data Center Keywords 2017-04-24 publication 8.5 Earth Science Data and Information System, Earth Science Projects Division, Goddard Space Flight Center (GSFC), National Aeronautics and Space Administration (NASA) https://forum.earthdata.nasa.gov/app.php/tag/GCMD%2BKeywords GCMD Keyword Forum Page Global Change Master Directory (GCMD). 2025. GCMD Keywords, Version 22. Greenbelt, MD: Earth Science Data and Information System, Earth Science Projects Division, Goddard Space Flight Center (GSFC), National Aeronautics and Space Administration (NASA). URL (GCMD Keyword Forum Page): https://forum.earthdata.nasa.gov/app.php/tag/GCMD+Keywords information custodian Lidar project InPort otherRestrictions Cite As: Office for Coastal Management, [Date of Access]: 2023 NOAA Topobathy Lidar: Northern Lake Michigan & Northern Lake Huron, MI [Data Date Range], https://www.fisheries.noaa.gov/inport/item/74316. NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. otherRestrictions Access Constraints: None otherRestrictions 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. otherRestrictions 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. unclassified NOAA Data Management Plan (DMP) NOAA/NMFS/EDM 74316 https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocm/dmp/pdf/74316.pdf WWW:LINK-1.0-http--link NOAA Data Management Plan (DMP) NOAA Data Management Plan for this record on InPort. information crossReference vector eng; US elevation CZMIL SuperNOVA; CARIS; LAStools; Microstation; Terrascan; ArcGIS 10.6; Microsoft Windows 10 Enterprise Service Pack 1 -85.898152 -84.774242 45.837508 46.089047 Lansing Shoals -86.79 -86.26 45.43 45.82 Green Bay -84.72 -83.88 45.86 46.05 Lake Huron Dates of collection for Lansing Shoals | Currentness: Ground Condition 2023-09-14 2023-09-15 Dates of collection for Green Bay | Currentness: Ground Condition 2023-09-28 2023-09-29 Date of collection for Lake Huron | Currentness: Ground Condition 2023-09-16 Date of collection for Green Bay | Currentness: Ground Condition 2023-10-03 Date of collection for Green Bay | Currentness: Ground Condition 2023-10-05 Dates of collection for Lansing Shoals | Currentness: Ground Condition 2023-09-19 2023-09-20 Dates of collection for Lansing Shoals | Currentness: Ground Condition 2023-09-23 2023-09-25 Dates of collection for Lake Huron | Currentness: Ground Condition 2023-09-18 2023-09-19 Dates of collection for Lake Huron | Currentness: Ground Condition 2023-09-24 2023-09-26 Date of collection for Lake Huron | Currentness: Ground Condition 2023-10-04 Contract No. 1305M221DNCNP0017 CONTRACTOR: Dewberry Engineers. Lidar data were acquired and calibrated by Dewberry. All follow-on processing was completed by Dewberry. A complete description of this dataset is available in the Final Project Report that will be submitted to NOAA. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v 1.3", "ldrsens" : "CZMIL (Topo Channels)", "ldrmaxnr" : "15", "ldrnps" : "0.38", "ldrdens" : "7", "ldranps" : "0.38", "ldradens" : "7", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "40", "ldrscanr" : "27", "ldrpulsr" : "140", "ldrpulsd" : "1.2-2.1", "ldrpulsw" : "na", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "5", "ldrswatw" : "291", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid 18" }, "ldrinfo" : { "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v 1.3", "ldrsens" : "CZMIL (Shallow/Deep Bathy Channels)", "ldrmaxnr" : "15", "ldrnps" : "0.38", "ldrdens" : "7", "ldranps" : "0.38", "ldradens" : "7", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "40", "ldrscanr" : "27", "ldrpulsr" : "140", "ldrpulsd" : "1.2-2.1", "ldrpulsw" : "proprietary", "ldrwavel" : "532", "ldrmpia" : "1", "ldrbmdiv" : "5", "ldrswatw" : "291", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid 18" }, "ldraccur" : { "ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit. Noise classes, class 7 and class 18, were assigned LAS withheld bit.", "lasolap" : "The LAS overlap bit was not utilized for this dataset.", "lasintr" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare Earth, Ground" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : { "clascode" : "40", "clasitem" : "Bathymetric Bottom" }, "lasclass" : { "clascode" : "41", "clasitem" : "Water Surface" }, "lasclass" : { "clascode" : "42", "clasitem" : "Synthetic Water Surface" }, "lasclass" : { "clascode" : "45", "clasitem" : "Water Column" } }} LAS/LAZ - LASer LAZ Zip NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information distributor https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10247/index.html WWW:LINK-1.0-http--link Bulk Download Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. download https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10247/details/10247 WWW:LINK-1.0-http--link Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. download dataset Horizontal Positional Accuracy Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested. Lidar vendors calibrate their lidar systems during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 41 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter at a 95% confidence level. Vertical Positional Accuracy The topographic portion of this lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10 cm RMSEz Vertical Accuracy Class. Actual NVA accuracy was found to be RMSEz = 6.9 cm, equating to plus or minus 13.6 cm at 95% confidence level. The bathymetric portion of this lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 15.0 cm RMSEz Vertical Accuracy Class. Actual bathymetric vertical accuracy was found to be RMSEz = 13.5 cm, equating to plus or minus 26.4 cm at 95% confidence level. Completeness Report Topobathymetric data covers the project boundary to the fullest extent possible depending on water clarity, environmental conditions, and sensor signal returns. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications. Conceptual Consistency Data covers the entire area specified for this project. Dewberry acquired, processed, and calibrated the lidar data for this project. The data deliverables were provided to the NOAA Office for Coastal Management (OCM) to make the data publicly available on the NOAA Digital Coast. The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification version 1.3. Bare earth DEMs were exported from the classified point cloud. 2024-04-01T00:00:00 Data were processed to an initial LAS format using Teledyne CARIS software. CARIS was also utilized for GPS and inertial processing, and Terrasolid and LAStools were used for data visualization, 3D editing, and export to final LAS/LAZ. Data were processed using NAD83(2011) horizontal and vertical datums. The data are in UTM Zone 16 coordinates and NAVD88 elevations in meters. The data classifications are: unclassified (1); ground (2); noise (7); water surface (topographic sensor) (18); bathymetric bottom (40); water surface (41); derived water surface (42); submerged object, not otherwise specified (e.g., wreck, rock, submerged piling) (43); and no bottom found (bathymetric lidar point for which no detectable bottom return was received) (45). 2023-05-30T00:00:00 Dewberry used algoritms in TerraScan to create the intial ground/submerged topography surface. Dewberry used rasterized aggregate extents of refracted points to create automated 2-D breaklines with LAStools and ArcGIS. Light travels at different speeds in air versus water and its speed and direction of travel change when it enters the water column. The refraction correction process accounts for this difference by adjusting the depth (distance traveled) and horizontal position (change of angle/direction) of the lidar points acquired within water. These breaklines delineate areas where the refraction correction was applied to the lidar data by Dewberry proprietary refraction correction tool. Dewberry used the 2-D refraction extents and additional bathy features to classify the bathymetric bottom and ground points properly in TerraScan. Geometrically unused points at the edges of flight lines were flagged using the withheld bit. This includes synthetically generated class 42 (synthetic water surface) points at the edges of flight lines. All class 42 points were flagged using the synthetic bit. The withheld bit was set on class 7 and class 18 in TerraScan after all classification was complete. All lidar data was peer-reviewed. Dewberry's QAQC also included creating void polygons for use during review. All necessary edits were applied to the dataset. LASTools software was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data are in LAS format 1.4 and point data record format 6. All data was then verified by an Independent QC department within Dewberry. The independent QC was performed by separate analysts who did not perform manual classification or editing. The independent QC involved quantitative and qualitative reviews. 2024-05-31T00:00:00 Data was tested at 0.18 meters nominal pulse spacing and 30.4 points per square meter (ppsm). The average density was tested on the LAS data using geometrically reliable (withheld and noise points excluded) first-return points. (A)NPD was tested using rasters which produce the average number of points within each cell. 2024-05-31T00:00:00 The NOAA Office for Coastal Management (OCM) received topobathy laz files from Dewberry for parts of the northern Lake Michigan and northern Lake Huron coastlines in Michigan. The lidar data had elevation and intensity measurements. The data were in UTM Zones 16N and 17N (NAD83 2011) coordinates and NAVD88 (Geoid18) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 18 - High Noise, 40 - Bathymetric Point, 41 - Water Surface, 42 - Derived Water Surface, 43 - Submerged Object, 45 - No Bottom Found. OCM processed the non-noise classifications of points to the Digital Coast Data Access Viewer (DAV). Points classified as Noise (7, 18) were excluded in the processing and are not available in DAV. Classes available in the DAV are: 1, 2, 40, 41, 42, 43, 45. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations in meters to NAD83 (2011) ellipsoid elevations in meters using the Geoid18 model b. Convert the laz files from UTM Zones 16N and 17N, NAD83(2011), meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database and AWS S3 2025-01-10T00:00:00 Office for Coastal Management processor Classified Lidar Points Dewberry publisher