Jenny L Hanson Stephanie R Sattler John W Lund 20240912 tabular digital data https://doi.org/10.5066/P9JH0O1X Daniel M Wagner John W Lund Kelly M Sanks 20200710 raster digital data https://www.sciencebase.gov U.S. Geological Survey https://doi.org/10.5066/p9gxt1x1 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 Lake Superior at the Duluth Entry, Duluth, Minnesota. The point data is the same as that in the LAS dataset used to create a digital elevation model (DEM) of the approximately1.87 square kilometer surveyed area. Lidar data were collected July 28, 2020 using a boat mounted Velodyne unit. Multibeam sonar data were collected July 28-29, 2020 using a Norbit integrated wide band multibeam system (iWBMSc) sonar unit. Methodology for data collection 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 areas that have been scoured by high water levels and wave activity. This pre-placement survey was completed as a baseline survey of the Duluth Entry before the USACE conducts a beach nourishment in September 2020. The XYZ files are provided for input use in CAD and other computer programs that require space-delimited position and elevation information. Due to time constraints, surveys were conducted under windy conditions causing a high heave error. These conditions affected the data (heave) and are noticeable in higher resolution datasets. 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 20200728 20200729 ground condition Complete None planned -92.09220 -92.07030 46.78430 46.76240 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:60677173d34edc0435c09d47 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 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 Midwest 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 2020; GeoCue's LP360 version 2020.1.80.0; Esri ArcGIS for Desktop version 10.7.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 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 = -2.33 degrees; roll = -0.27 degrees; and latency = 0 milliseconds for the July 28, 2020 multibeam data, and yaw = -2.5 degrees; pitch = 1.33 degrees; roll = -0.1 degrees; and latency = 0 milliseconds for the July 29, 2020 multibeam data. These corrections were applied to the multibeam sonar data during post-processing in Hypack 2020 software. Multibeam settings included a 140-degree swath that was further reduced to 65 beam angle limits in Hypack post-processing. For deeper areas, the beam angle limits were reduced to 45. 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 2020 software. The 'SVP Adjust Tool' in the 64-bit Hysweep Editor was used to help compensate for some sound velocity errors recorded during the survey. 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 2020 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 in post-processing, but a patch test was not formally conducted during acquisition. 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 of interest along Minnesota Point near the Duluth Entry. The beach face was surveyed from the southern tip of Canal Park, approximately 0.15 miles north of the Duluth Entry pier, to 2 kilometers (km; 1.24 miles [mi]) south of the pier along the beach. 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 0.85 kilometers (km; 0.5 miles [mi]) offshore. 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 estimated position accuracy for the solutions were calculated for the estimated standard deviation of less than 0.07 m (0.23 ft) in the X, or "easting", direction and less than 0.07 m (0.23 ft) in the Y, or "northing direction for July 28, 2020 lidar positional data. The estimated standard deviation of less than 0.06 (0.2 ft) in the X, or "easting", direction and less than 0.1 m (0.33 ft) in the Y, or "northing direction for July 28-29 multibeam data. 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 estimated standard deviation of the Z ("down", or vertical) direction was less than 0.14 m (0.46 ft) for the July 28 lidar positional data, and 0.15 m (0.49 ft) for July 28-29 multibeam positional data. 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. 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. . 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. Sound velocity profiles were collected every 1-2 hours using a Sound Velocity Profiler unit. Data were collected in meters using the World Geodetic System (WGS) of 1984 Universal Transverse Mercator (UTM) Zone 15 North horizontal projection. 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. 20200728 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. 20200728 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 GNSS navigation 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. 20200728 Raw data collected with the Norbit iWBMSc sonar were edited using Hysweep's MBMAX64 module of Hypack 2020 software. The SBET solution from the NovAtel Inertial Explorer position system and boresight calibration file were applied to the multibeam data in HYPACK 2020 MBMAX64. 20201020 The water-surface elevation from the National Oceanic and Atmospheric Administration (NOAA) Duluth, Minnesota, tide station (9099064) was applied to the multibeam sonar data as the vertical reference. Sound velocity profiles collected using the Sound Velocity Profiler unit were imported into Hysweep's MBMAX64 to correct soundings for spatial and temporal changes in sound velocity by interpolating between profiles based on geographic position and time of day. The 'SVP Adjust Tool' in the 64-bit Hysweep Editor was used to help compensate for some sound velocity errors recorded during the survey. Soundings from beams greater than 65 degrees from nadir were removed, and further screened using the 4 standard deviation and over/under filters to remove remaining erroneous soundings. TPU in the multibeam survey was accounted for in the final dataset using the CUBE method in Hypack 2020 software (Calder and Mayer, 2003). Filtered multibeam sonar data were exported from Hypack in LAS format. 20201020 Lidar data were classified using LP360 software. 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 LAS were exported to the North American Datum (NAD) of 1983 UTM Zone 15 N horizontal projection with just the ground class remaining. The exported file was clipped to a boundary file (manually delineated) during the export. The LAS were exported to a 1-meter elevation (DEM) surface in order to conduct a quality control/quality assurance check for erroneous soundings. 20201205 The multibeam LAS datasets were imported to LP360 for further manual classification of noise. A "clean" LAS dataset that did not contain any low or high noise was then exported, projected, and clipped to a boundary file (manually delineated). The LAS were exported to a 1-meter elevation (DEM) surface in order to conduct a quality control/quality assurance check for erroneous soundings. 20201215 The "clean" LAS datasets were exported again in LP360 to an ASCII format, or as a XYZ text file and the elevation was converted from meters to feet using an R-script. 20201228 Vector Point Universal Transverse Mercator 15 0.9996 -93.0 0.0 500000.0 0.0 coordinate pair 0.01 0.01 meters North American Datum of 1983 (NAD 83) Geodetic Reference System 1980 6378137.0 298.257222 International Great Lakes Datum of 1985 0.001 feet Explicit elevation coordinate included with horizontal coordinates lidar.xyz comma delimited text file Producer Defined X_Easting Easting coordinate of point in lidar.xyz Producer Defined 569320.42 570280.78 meters relative to UTM 15N Y_Northing Northing coordinate of point in lidar.xyz Producer Defined 5179121.25 5181349.40 meters relative to UTM 15N Z_Elevation elevation of point in lidar.xyz Producer Defined 602.690 761.745 Foot US relative to IGLD 85 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. Producer Defined 0 202 integer Classification Classification code for a point in lidar.xyz Producer Defined 2 2 Code 2 indicates ground points multibeam.xyz comma delimited text file. Producer Defined X_Easting Easting coordinate of point in multibeam.xyz Producer Defined 569329.62 570966.87 meters relative to UTM 15N Y_Northing Northing coordinate of point in multibeam.xyz Producer Defined 5179189.08 5181598.33 meters relative to UTM 15N Z_Elevation elevation of point in lidar.xyz Producer Defined 541.633 601.673 Foot US relative to IGLD 85 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 - ScienceBase mailing

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/P9JH0O1X 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