Jenny L Hanson Lund, John (William) W Jayme M Strange Erin Coenen 20240912 tabular digital data https://www.sciencebase.gov U.S. Geological Survey https://doi.org/10.5066/P92LLRW5 Jenny L Hanson John W Lund Stephanie R Sattler 20211025 raster digital data https://www.sciencebase.gov U.S. Geological Survey Hanson, J.L., Sattler, S.R., and Lund, J.W., 2021, 10-meter Digital elevation model (DEM) of beach topography and near-shore bathymetry of Lake Superior at Minnesota Point, Duluth, MN, July 2020: U.S. Geological Survey data release, https://doi.org/10.5066/P9JH0O1X. https://doi.org/10.5066/P9JH0O1X. This dataset consists of two files containing northing, easting, and elevation ("XYZ") information for light detection and ranging (lidar) data representing the beach and near-shore topography of Minnesota Point near the Superior Entry of Lake Superior, Duluth, Minnesota. The point data is the same as that in the LAS dataset used to create a digital elevation model (DEM) of the approximately 2.27 square kilometer surveyed area. Lidar data were collected using a boat mounted Velodyne unit. Multibeam sonar data were collected using a Norbit integrated wide band multibeam system compact (iWBMSc) sonar unit. Single-beam sonar data were collected using a Ceescope sonar unit. All elevation data were collected September 15-17, 2021. Methodology similar to Wagner, D.M., Lund, J.W., and Sanks, K.M., 2020 was used. Data were collected in cooperation with the U.S. Army Corps of Engineers (USACE), Detroit District, to define beach topography and near-shore bathymetry after placing dredge spoils to mitigate beach erosion. This post-placement survey was completed to evaluate movement of placed material and overall changes to the barrier island and surrounding near-shore area approximately 2-years after nourishment placement. The XYZ files are provided for input use in CAD and other computer programs that require space-delimited position and elevation information. This is the third year of data collected for this location. The first data set was collected in August of 2019. The second data set was collected in 2020, and this current set of data in 2021. Data for each year is provided in the same formats. Lidar patch test values were estimated but a patch test was not formally conducted. The uncertainty of the lidar is unknown. Post data release, we found discernible errors in the positioning. Please use the data with caution. 20210915 20210917 ground condition Complete None planned -92.04150 -92.00490 46.72870 46.71080 ISO 19115 Topic Category elevation structure Data Categories for Marine Planning Bathymetry and Elevation USGS Thesaurus limnology lidar digital elevation models bathymetry USGS Metadata Identifier USGS:632b4e7ad34e4bed63ff4ab0 Common geographic areas Southwestern Lake Superior Great Lakes Duluth Lake Superior Superior None. Please see 'Distribution Info' for details. None. Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations. Jenny L Hanson U.S. Geological Survey, MIDCONTINENT REGION Biologist mailing address

2630 Fanta Reed Road

La Crosse WI 54603 US 608-781-6372 608-783-6066 jhanson@usgs.gov Funding for the project was provided by the Great Lakes Restoration Initiative (GLRI) in cooperation with the U.S. Army Corps of Engineers (USACE), Detroit District. The Mounds View, MN office of the USGS Upper Midwest Water Science Center (UMID) teamed up with the La Crosse, WI USGS Upper Mississippi Environmental Sciences Center (UMESC) to collect the lidar and multibeam data, using the UMESC's Velodyne puck and Norbit iWBMSc mounted on UMID's boat. Environment as of Metadata Creation: Microsoft Windows 10 Enterprise; Xylem's Hypack 2021; GeoCue's LP360 version 2020.1.80.0 and version 2021.1.47.0; Esri ArcGIS for Desktop version 10.8.1; Waypoint Inertial Explorer version 8.90 Daniel M Wagner John W Lund Kelly M Sanks 20200720 dataset https://www.sciencebase.gov U.S. Geological Survey Wagner, D.M., Lund, J.W., and Sanks, K.M., 2020, Beach topography and near-shore bathymetry of Lake Superior at Minnesota Point, Duluth, MN, August 2019: U.S. Geological Survey data release, https://doi.org/10.5066/P9GXT1X1. https://doi.org/10.5066/p9gxt1x1 Prior to the bathymetric survey, a boresight calibration procedure was performed to determine the alignment offsets between reference frame of the sonar and that of the inertial measurement unit (IMU) that is part of the positioning system. The offsets determined from the boresight calibration procedure were applied to the bathymetric data during data collection. Patch tests were conducted on the Norbit iWBMSc multibeam sonar to determine latency and angular differences (yaw, pitch, and roll) between the sonar head and the IMU that is incorporated with the NovAtel positioning system. The patch test involves surveying over various bathymetric features in the same and opposite directions at different speeds, from which the angular offsets can be identified, quantified, and corrected. The following corrections were determined from the patch test: yaw = 1.67 degrees, pitch = 1.00 degrees, roll = -0.30 degrees, and latency = 0 milliseconds for the September 15-16, 2021 multibeam data; and yaw = -1.00, pitch = -1.33, roll = -0.17, and latency = 0 milliseconds for the September 17, 2021 multibeam data. These corrections were applied to the multibeam sonar data during post-processing in Hypack 2021 software. Multibeam settings included a 140-degree swath that was further reduced to 65 beam angle limits in Hypack post-processing. During the bathymetric survey, data quality was assessed continuously by the sonar operator. Data-quality flags and alarms from the sonar and positioning systems were noted and investigated. To account for spatial and temporal changes in sound velocity, profiles were collected every 1-2 hours using a Sound Velocity Profiler unit and applied to the multibeam sonar data during post-processing in Hypack 2021 software. Total propagated uncertainty (TPU) in the multibeam survey was estimated and accounted for in the final dataset using the Combined Uncertainty and Bathymetric Estimator (CUBE) method in Hypack 2021 software (Calder and Mayer, 2003). The CUBE method uses the uncertainties of the various components of error, such as position, sound speed, and loading conditions to compute TPU and adjust the final soundings accordingly. Lidar patch test values were estimated but a patch test was not formally conducted. The uncertainty of the lidar is unknown. Please use the data with caution. Positions and elevations of the point data from which the DEM and contours were derived fall within expected ranges and plot in the correct locations on available aerial imagery. A survey area was provided by the USACE (Detroit district), to show the area required along the Minnesota Point. The beach face was surveyed from approximately 2 kilometers (km; 1.24 miles [mi]) along the southern section of Park Point Beach to the breakwall at the Superior, Wisconsin entry to Superior Bay. Along this distance, the bathymetry of Lake Superior was surveyed from approximately 0.5 m (1.64 ft) to a depth of 12.2 m (40 ft) offshore, which corresponds approximately to the northeastern end of the breakwall. During the survey, position and elevation data were collected using a NovAtel MarineSPAN Global Navigation Satellite System/Inertial Navigation System (GNSS/INS). The accuracy of the positioning data was improved in post-processing using the daily static occupations of a nearby National Geodetic Survey (NGS) Continuously Operating Reference Station (CORS). The data files from the daily static occupations were processed in WayPoint Inertial Explorer using the precise point kinematic method to help correct the 3D positioning location. The final navigation solution (called a smoothed best estimate of trajectory, or SBET, solution) was applied to the LiDAR and multibeam sonar data during post-processing. For the multibeam, the average root mean square (RMS) errors of the post-processed solutions were 0.0096 m (0.03 ft) in the X, or "easting", direction and 0.0020 m (0.01 ft) in the Y, or "northing" direction. The average RMS errors were 0.0195 m (0.06 ft) in the X direction, and 0.0194 m (0.06 ft) in the Y direction for the lidar. The horizontal positioning of the single-beam sonar data were collected using a real-time network (RTN) connection to Minnesota's network of continuously operating GNSS reference stations (MnCORS, https://www.dot.state.mn.us/surveying/cors/). During the survey, position and elevation data were collected using a NovAtel MarineSPAN Global Navigation Satellite System/Inertial Navigation System (GNSS/INS). The accuracy of the positioning data was improved in post-processing using the daily static occupations of a nearby National Geodetic Survey (NGS) Continuously Operating Reference Station (CORS). The data files from the daily static occupations were processed in WayPoint Inertial Explorer using the precise point kinematic method to help correct the 3D positioning location. The final navigation solution (called a smoothed best estimate of trajectory, or SBET, solution) was applied to the lidar and multibeam sonar data during post-processing. The average root mean squared error in the Z ("down", or vertical) direction for the multibeam was less than 0.0153 m (0.05 ft). The average root mean squared error in the Z ("down", or vertical) direction for the lidar was less than 0.0236 m (0.08 ft). To correct vertical soundings to the International Great Lakes Datum conversion of 1985 (IGLD 85, the Hypack geodesy settings were predefined to add a height above chart datum, by calculating the hydraulic corrector, or conversion between the dynamic height and the IGLD 85 height. Combined with the National Oceanic and Atmospheric Administration (NOAA) tide station 9099064 (located at the Duluth entry to the harbor on the northwest end of Minnesota Point, https://tidesandcurrents.noaa.gov/stationhome.html?id=9099064), the water surface elevation was vertically referenced for the multibeam sonar data. Vertical measures of the single-beam sonar data were collected using an RTK connection to the MnCORS network. Bathymetric data were collected using a Norbit iWBMSc sonar unit. A planned survey using a grid with survey lines spaced 100 feet apart was used for data collection. Generally, each subsequent pass was closer than the planned survey lines while moving progressively toward or away from shore until the lakebed was surveyed to a depth of at least 40 feet, which corresponded approximately to the northeast end of the breakwall at the Superior, Wisconsin entry to Superior Bay. Sound velocity profiles were collected every 1-2 hours using a Sound Velocity Profiler unit. The geodetic parameters used to collect the data were predefined as the Universal Transverse Mercator (UTM) North American Datum of 1983 (NAD83) Zone 15 (96W-90W). The distance and depth units were meters. The CONUS 2012b geoid model was used. To correct vertical soundings to the International Great Lakes Datum conversion 1985 (IGLD 85), the Hypack geodesy settings were predefined to add a height above chart datum, by calculating the hydraulic corrector, or conversion between the dynamic height and the IGLD 85 height. Lidar data were collected using a Velodyne VLP-16 unit mounted to the port side of the survey vessel. The Velodyne VLP-16 was coupled to a NovAtel positioning system for position and motion corrections. Data were collected simultaneously with multibeam data angled 90 degrees to the shoreline. Single-beam data were collected using a Ceescope SV-1470 unit mounted through the built-in survey well of the vessel hull. Positioning was acquired using a Trimble RTK GPS system. Single-beam was used to collect areas too shallow for the multibeam - specifically areas less than 2 meters. 20210915 Data collected with the NovAtel's positioning system during the lidar and multibeam sonar surveys were post-processed using version 8.90 of Waypoint Inertial Explorer software. The horizontal and vertical accuracy of the differential global navigation satellite systems (GNSS) solution was improved in post-processing by correcting the navigation solution based on the average solution of the daily occupations of nearby National Geodetic Survey (NGS) Continuously Operating Reference Stations (CORS). The post-processed navigation solution, known as a smoothed best estimate of trajectory (SBET) solution, was exported to a file for use in post-processing of lidar and multibeam sonar data. 20210915 Raw data collected with the Norbit iWBMSc were initially processed in Hysweep's MBMAX64 module of Hypack 2021 software. The SBET solutions were applied to the multibeam data to correct for positioning and motion. The following corrections were applied in Hypack 2021: water-surface elevation from the National Oceanic and Atmospheric Administration (NOAA) Duluth, Minnesota, tide station (9099064) was applied to all data as the vertical reference; sound velocity profiles to correct soundings for spatial and temporal changes in sound velocity by interpolating between profiles based on geographic position and time of day; offsets from the sonar to the IMU; and patch test values. Filters applied included basic filtering of beam angle limits of 65 (soundings from beams greater than 65 degrees from nadir were removed) and the following sweep filters: over/under filter, minimum beam quality of 3, and the Savitsky-Golay filter to remove remaining erroneous soundings. TPU in the multibeam survey was accounted for in the final dataset using the CUBE method in Hypack 2021 software (Calder and Mayer, 2003). The edited multibeam data was then exported as a LAS for further classification of noise. 20220115 Raw data collected with the Velodyne VLP-16 were initially processed in Hysweep's MBMAX64 module of Hypack 2021 software. The SBET solutions were applied to the lidar data to correct for positioning and motion. The following corrections were applied in Hypack 2021: water-surface elevation from the National Oceanic and Atmospheric Administration (NOAA) Duluth, Minnesota, tide station (9099064) was applied to all data as the vertical reference; offsets from the Velodyne VLP-16 to the IMU; patch test values determined using Hypack methodology (Yaw = -0.60, Pitch = -43.00, Roll = -1.10, GPS Latency = 0.00), and RTK Tide Heave corrections. The lidar data were exported as LAS for further classification. 20220115 Raw data collected with the Ceescope SV-1470 were initially processed in the SBMAX64 software. The following corrections were applied in Hypack 2021: water-surface elevation from the National Oceanic and Atmospheric Administration (NOAA) Duluth, Minnesota, tide station (9099064) was applied to all data as the vertical reference; sound velocity profiles to correct soundings for spatial and temporal changes in sound velocity by interpolating between profiles based on geographic position and time of day; draft offset; and heave processing. Erroneous points were edited in the profile window. The edited single-beam data was then exported as a LAS for further classification of noise. 20220123 The single-beam LAS datasets were imported to LP360 for further manual classification of noise. High and low noise was classified accordingly. The LAS data that did not contain any low or high noise were then classified as water and exported as a 1-meter elevation surface in order to conduct a quality control/quality assurance check for erroneous soundings. A survey area boundary (SAB) shapefile was manually delineated around the LAS. The SAB was used to clip/export the LAS file and project to NAD 1983 Zone 15 North, IGLD 85 (meters). 20220205 The multibeam LAS datasets were imported to LP360 for further manual classification of noise. High and low noise was classified accordingly. The LAS data that did not contain any low or high noise were then classified as water and exported as a 1-meter elevation surface in order to conduct a quality control/quality assurance check for erroneous soundings. A survey area boundary (SAB) shapefile was manually delineated around the LAS. The SAB was used to clip/export the LAS file and project to NAD 1983 Zone 15 North, IGLD 85 (meters). 20220211 Lidar data were classified using LP360. High and low noise were classified into the ignored ground class. Vegetation was classified into the medium-vegetation class. The data were examined in three dimensions; any remaining noise that was missed were reclassified. The new LAS were exported to a 1-meter elevation surface in order to conduct a quality control/quality assurance check for erroneous soundings. A survey area boundary (SAB) shapefile was manually delineated around the LAS. The SAB was used to clip/export the LAS file and project to NAD 1983 Zone 15 North, IGLD 85 (meters). 20220412 Using the scale tool in LP360, the horizontal and vertical measures (meters) were recalculated to feet. The LAS files were then exported as XYZ. 20220412 Vector Point 8050169 Universal Transverse Mercator 15 0.9996 -93.0 0.0 1640416.666666667 0.0 coordinate pair 0.6096 0.6096 meters North_American_Datum_1983 GRS_1980 6378137.0 298.257222101 International Great Lakes Datum of 1985 0.001 feet Explicit elevation coordinate included with horizontal coordinates XYZ_MNPoint_Sept2021_Lidar.xyz comma delimited text file. Producer Defined X_Easting Easting coordinate for point in MNPoint_Sept2021_Lidar.xyz Producer Defined 1882621.812 1886222.534 feet, US relative to IGLD85 Y_Northing Northing coordinate for point in MNPoint_Sept2021_Lidar.xyz Producer Defined 16973258.778 16975639.093 feet, US relative to IGLD85 Z_Elevation Elevation of point in MNPoint_Sept2021_Lidar.xyz Producer Defined 603.018 631.89 feet, US relative to IGLD85 Intensity Intensity is a measure of the return strength of the laser pulse (from the LiDAR unit) reflected from a surface. It is based, in part, on the reflectivity of the surface. Intensity is normalized to a scale of 0-255. Producer Defined 0 100 integer Classification Classification code for a point in MNPoint_Sept2021_Lidar.xyz Producer Defined 2 2 Code 2 indicates ground points XYZ_MNPoint_Sept2021_MB.xyz comma delimited text file. Producer Defined X_Easting Easting coordinate for point in MNPoint_Sept2021_MB.xyz Producer Defined 1882612.2980000002 1885788.971 feet, US relative to IGLD85 Y_Northing Northing coordinate for point in MNPoint_Sept2021_MB.xyz Producer Defined 16973411.895 16976145.458 feet, US relative to IGLD85 Z_Elevation Elevation of point in MNPoint_Sept2021_MB.xyz Producer Defined 578.675 598.688 feet, US relative to IGLD85 XYZ_MNPoint_Sept2021_SB.xyz comma delimited text file. Producer Defined X_Easting Easting coordinate for point in MNPoint_Sept2021_SB.xyz Producer Defined 1880771.1230000001 1884700.716 feet, US relative to IGLD85 Y_Northing Northing coordinate for point in MNPoint_Sept2021_SB.xyz Producer Defined 16973523.673 16978382.531 feet, US relative to IGLD85 Z_Elevation Elevation of point in MNPoint_Sept2021_SB.xyz Producer Defined 592.29 601.64 feet, US relative to IGLD85 The entity and attribute information provided here describes the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set. The entity and attribute information were generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information. U.S. Geological Survey GS ScienceBase mailing address

Denver Federal Center, Building 810, Mail Stop 302

Denver CO 80225 United States 1-888-275-8747 sciencebase@usgs.gov Although these data have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Vector Digital Data Sets https://doi.org/10.5066/P92LLRW5 None. No fees are applicable for obtaining the dataset. 20240912 Jenny L Hanson U.S. Geological Survey, MIDCONTINENT REGION Biologist mailing address

2630 Fanta Reed Road

La Crosse WI 54603 US 608-781-6372 608-783-6066 jhanson@usgs.gov FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998