NV5 Geospatial 20220407 LiDAR point cloud Product: These lidar data are processed Classified LAS 1.4 files, formatted to 4339 individual 1000 m x 1000 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Geographic Extent: 3 counties in Minnesota, covering approximately 1619 total square miles. Dataset Description: The MN_LakeSuperior_2021_B21, Work Unit 218907 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification 2020, Revision A. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zone 15N, Meter and vertical datum of NAVD88 Geoid 18, Meter. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 4339 individual 1000 m x 1000 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. It should be noted that there are 16 less LAS and intensity than the tile layout count due to them being fully inside waterbodies. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in spring 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, NV5 Geospatial utilized a total of 0 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 217 independent accuracy checkpoints, 125 in Bare Earth and Urban landcovers (125 NVA points), 92 in Tall Weeds categories (92 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a .5 meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Contract No. G16PC00016, Task Order No. 140G0221F0113; CONTRACTOR: NV5 Geospatial USGS-NGP Base Specification v2.1 Riegl VQ1560i unlimited 0.35 8.0 0.46 4.73 1326 180 29 400 2000 3 0.24 1064 1 0.18 1470.0 20 Geoid 18 NAD 1983 2011 UTM Zone 15N, Meter USGS-NGP Base Specification v2.1 Riegl VQ1560ii unlimited 0.35 8.0 0.35 8.16 1500 160 30 350 2000 3 0.27 1064 1 0.18 1732.0 20 Geoid 18 NAD 1983 2011 UTM Zone 15N, Meter USGS-NGP Base Specification v2.1 Optech Galaxy T2000 8 0.35 8.0 0.33 9.18 1828 145 19 95 1100 3 0.46 1064 1 0.25 1259.0 20 Geoid 18 NAD 1983 2011 UTM Zone 15N, Meter 0 0.0 0 1.4 6 Withheld (ignore) points were identified in these files using the standard LAS Withheld bit. Any overage point deemed geometrically reliable will be used within the normal classification schema. Overage points are not specifically flagged with any special bit value. 16 1 Processed, but Unclassified 2 Bare-Earth Ground 7 Low Noise 9 Water 17 Bridge Decks 18 High Noise 20 Ignored Ground 20210425 20210502 Ground condition Complete None planned -92.2030763178 -91.174398961 47.5754918122 46.6217850133 561000.0 637323.498287 5269438.3888 5164698.42613 None Model LAS Point Cloud Remote Sensing Elevation Data LiDAR None Minnesota Douglas County Lake County St. Louis County No restrictions apply to these data. None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of their limitations. Acknowledgement of the organization providing these data to the public would be appreciated for products derived from these data. NV5 Geospatial John DiGiovanni mailing and physical

523 Wellington Way

Lexington KY 40503 USA 859-277-8700 859-277-8901 john.digiovanni@nv5.com Monday through Friday 8:00 AM to 5:00 PM (Eastern Time) If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours. MicroStation Connect; TerraScan Version 21.016; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; Optech LMS 4.4, RiProcess 1.8.6; Windows 10 Operating System \\point_cloud\tilecls\*.las Data cover the entire area specified for this project. These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a ___ (cm) RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- ___ cm at a 95% confidence level. This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. Ayres 20220407 Vector digital data and tabular digital data Ayres Ayres None external hard drive 20210909 Ground condition MN_LakeSuperior_2021_B21_Work_Unit_218907_gnd_ctrl This data source was used (along with airborne GPS/IMU data) to georeference the LiDAR point cloud data. Raw Data and Boresight Processing: 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 NV5 Geospatial 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 technicians then analyzed the results and made any necessary additional adjustment until it was 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 matched 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 7 cm RMSEz within individual swaths and less than or equal to 10 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 checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. MN_LakeSuperior_2021_B21_Work_Unit_218907_gnd_ctrl 2022 LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using proprietary tools. A buffer of 0.5 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. Any noise that was identified either through manual review or automated routines was classified to the appropriate class ( ASPRS Class 7 and/or ASPRS Class 18) followed by flagging with the withheld bit. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for point cloud data. NV5 Geospatial proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information. 2022 Point Universal Transverse Mercator 15 0.9996 -93 0.0 500000 0.0 coordinate pair 0.001 0.001 Meter North American Datum of 1983 (2011) Geodetic Reference System 80 6378137.0 298.257222101 NAVD88 Geoid 18 0.001 Meter Explicit elevation coordinate included with horizontal coordinates 20220407 NV5 Geospatial mailing and physical

523 Wellington Way

Lexington KY 40503 USA 859-277-8700 859-277-8901 Monday through Friday 8:00 AM to 5:00 PM (Eastern Time) FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 None. None. None. Unclassified NONE None. None.