<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2021/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2021/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2021/01/DescriptiveReport http://svn.pydro.noaa.gov/2021/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-Y390-KR-21</ns2:number><ns2:name>Southern Green Bay, WI</ns2:name><ns2:generalLocality>Green Bay, WI</ns2:generalLocality><ns2:fieldUnit>eTrac</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13471</ns2:registryNumber><ns2:sheetID>5</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Vicinity of Oconto</ns2:sublocality><ns2:stateOrTerritory>Wisconsin</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2021</ns2:year><ns2:chiefOfParty>David Neff, C.H.</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2021-04-26</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2021-06-03</ns2:start><ns2:end>2021-09-03</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks>All times are UTC. The purpose of this survey is to update existing NOS nautical charts. H13471 covers approximately 49 square nautical miles in the vicinity of Oconto, Wisconsin.</ns2:fieldRemarks><ns2:branchRemarks>Any revisions to the Descriptive Report (DR) applied during office processing are shown in red italic text. The DR is maintained as a field unit product, therefore all information and recommendations within this report are considered preliminary unless otherwise noted. The final disposition of survey data is represented in the NOAA nautical chart products. All pertinent records for this survey are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via https://www.ncei.noaa.gov/. 

Products created during office processing were generated in NAD83 UTM 16N, Low Water Datum IGLD-1985. All references to other horizontal or vertical datums in this report are applicable to the processed hydrographic data provided by the field unit.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>eTrac Inc. conducted hydrographic survey operations in the vicinity of Oconto, Wisconsin. H13471 covers approximately 49 square nautical miles of survey area. 499.70 linear nautical miles were acquired during the survey. 

Survey was conducted within these limits between June 03, 2021 (DN154) and September 03, 2021 (DN246).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">44.9207583333</ns2:latitude><ns2:longitude hemisphere="W">87.9205555556</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">44.7556916667</ns2:latitude><ns2:longitude hemisphere="W">87.6770555556</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Survey Limits Overview (light blue area) </ns2:caption><ns2:link>SupportFiles\H13471_SurveyLimits_Overview.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Survey Limits (black line)</ns2:caption><ns2:link>SupportFiles\H13471_SurveyLimits.PNG</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>All data were acquired in accordance with the requirements in the Project Instructions and specifications set forth in the Hydrographic Survey Specifications and Deliverables 2021 Edition (HSSD 2021).			</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:topic><ns2:discussion>The purpose of this survey is to update existing National Ocean Service (NOS) nautical charts.			</ns2:discussion></ns2:topic><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>Survey H13471 is accurate to International Hydrographic Organization (IHO) Order 1a as required per the HSSD 2021.</ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All water in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete 8370 LNM. Transit mileage, system calibration mileage and data which do not meet HSSD specifications shall not count towards the completion of the LNM requirement. Notify the COR/Project Manager upon nearing completion of LNM requirement. The final survey area shall be squared off and ensure the full investigation of any features within the surveyed extent.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Sheets 2, 3, and 5</ns2:waterDepth><ns2:requiredCoverage>Set Line Spacing MBES at 200m at an oblique angle to the contours, complete coverage on all significant shoals and features in waters less than 20m.	</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>ACHARE area within sheet 5 (Oconto Reach)</ns2:waterDepth><ns2:requiredCoverage>Set Line Spacing MBES at 35m at an oblique angle to the contours, complete coverage on all significant shoals and features in waters less than 20m.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Inshore Limit</ns2:waterDepth><ns2:requiredCoverage>The Inshore Limit is the Navigable Area Limit Line (Refer to HSSD 1.3.2), except for the ACHARE-identified area in Sheet 5. The inshore limit for the ACHARE-identified area in Sheet 5 is the the surveyed 1.9 m depth contour or the inshore limit of safe navigation, whichever is further offshore.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Survey coverage was in accordance with the requirements listed above and in the HSSD. Within the assigned the ACHARE-identified area, data acquisition could not be collected at an oblique angle to the contour due to safety. Additionally, the 1.9m depth contour could not be fully met due to safety. 

Note: Survey coverage did not extend to the entire assigned survey boundary as the Navigable Area Limit Line (NALL) was reached.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Survey Coverage</ns2:caption><ns2:link>SupportFiles\H13471_SurveyCoverage.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Survey Coverage with 3.5m NALL displayed</ns2:caption><ns2:link>SupportFiles\H13471_SurveyCoverage_NALL.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Survey Coverage with 1.9m and 3.5m NALL displayed in Channel</ns2:caption><ns2:link>SupportFiles\H13471_SurveyCoverage_NALL_1p9_3p5.PNG</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>R/V Endeavor</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>0.54</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>10.15</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>R/V Rapid</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>84.22</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>R/V Voxel</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>377.21</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>27.57</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>462</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>38</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>8.17</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>14</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>0</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2021-06-03</ns2:surveyDates><ns2:surveyDates>2021-06-04</ns2:surveyDates><ns2:surveyDates>2021-06-09</ns2:surveyDates><ns2:surveyDates>2021-06-11</ns2:surveyDates><ns2:surveyDates>2021-06-12</ns2:surveyDates><ns2:surveyDates>2021-06-13</ns2:surveyDates><ns2:surveyDates>2021-06-14</ns2:surveyDates><ns2:surveyDates>2021-06-15</ns2:surveyDates><ns2:surveyDates>2021-06-16</ns2:surveyDates><ns2:surveyDates>2021-07-04</ns2:surveyDates><ns2:surveyDates>2021-07-05</ns2:surveyDates><ns2:surveyDates>2021-07-06</ns2:surveyDates><ns2:surveyDates>2021-07-11</ns2:surveyDates><ns2:surveyDates>2021-07-12</ns2:surveyDates><ns2:surveyDates>2021-07-13</ns2:surveyDates><ns2:surveyDates>2021-07-22</ns2:surveyDates><ns2:surveyDates>2021-07-23</ns2:surveyDates><ns2:surveyDates>2021-08-04</ns2:surveyDates><ns2:surveyDates>2021-08-05</ns2:surveyDates><ns2:surveyDates>2021-09-03</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>R/V Endeavor</ns2:hullID><ns2:LOA units="meters">13.4</ns2:LOA><ns2:draft units="meters">0.8</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>R/V Rapid</ns2:hullID><ns2:LOA units="meters">8.5</ns2:LOA><ns2:draft units="meters">0.6</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>R/V Voxel</ns2:hullID><ns2:LOA units="meters">14.0</ns2:LOA><ns2:draft units="meters">0.6</ns2:draft></ns1:vessel><ns1:discussion>The R/V Endeavor is a 13.4 meter aluminum catamaran equipped with an over-the-side Pitman Arm with secondary tie point. 

The R/V Rapid is a 8.5 meter aluminum monohull equipped with both a Universal Sonar Mount (USM) starboard and port multibeam pole mount.

The R/V Voxel is a 14.0 meter aluminum catamaran equipped with an electro hydraulic actuated moonpool accessed adjustable aluminum and stainless steel custom mount.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>R2Sonic</ns2:manufacturer><ns2:model>2024</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>R2Sonic</ns2:manufacturer><ns2:model>I2NS</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV 320 v5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>SmartX</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>BaseX2</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>MicroX SV</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>Note: R/V Endeavor utilized a dual head R2Sonic 2024 multibeam echosounder system, an AML Micro.X for the surface sound speed system, an AML/eTrac MVP-X for the sound speed system,  an AML Base.X2 as a spare for the sound speed system, and a POS MV 320 V5 for the positioning and attitude system.

R/V Rapid utilized a dual head R2Sonic 2024 multibeam echosounder system,  an AML Micro.X for the surface sound speed system, an AML Base.X2 for the sound speed system, and a R2Sonic I2NS for the positioning and attitude system.

R/V Voxel utilized a single head R2Sonic 2024 multibeam echosounder system, an AML Micro.X for the surface sound speed system, an AML Smart.X for the sound speed system, and a POS MV 320 V5 for the positioning and attitude system.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:topic><ns2:discussion>A beam-to-beam statistical analysis was performed using the Cross Check tool in Qimera. A 4 meter Combined Uncertainty and Bathymetric Estimator (CUBE) weighted dynamic surface was created incorporating only the mainscheme lines and excluded crosslines. The Cross Check tool was used to perform the beam-by-beam comparison of the crossline data to the mainscheme surface. Comparisons showed excellent agreement, well above 95% of the allowable TVU.

Note: This surface was created for QC only and is not submitted as a surface deliverable. 

Below is a histogram of the crossline comparison statistics showing IHO Order 1a compliance per beam.</ns2:discussion><ns2:images><ns2:caption>H13471 Crossline Comparison</ns2:caption><ns2:link>SupportFiles\H13471_CrossCheck.png</ns2:link></ns2:images></ns2:topic><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod><ns2:measured units="meters">0.045</ns2:measured><ns2:zoning xsi:nil="true"/></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>R/V Endeavor</ns2:hullID><ns2:measuredCTD units="meters/second">0.05</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:measuredXBT xsi:nil="true"/><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>R/V Rapid</ns2:hullID><ns2:measuredCTD units="meters/second">0.05</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:measuredXBT xsi:nil="true"/><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>R/V Voxel</ns2:hullID><ns2:measuredCTD units="meters/second">0.05</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:measuredXBT xsi:nil="true"/><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Standard deviation and uncertainty layers of the Dynamic Surface were utilized during data processing to search for features, water column noise, and systematic errors. 

IHO Order 1a uncertainty specification was met by 100% of the nodes. 

The final Bathymetric Attributed Grid (BAG) surface's uncertainty was generated through the NOAA QC Tools and an image of the results is located below.

For H13471 the following percentages represent the results of the TPU calculation: 

Set Line Spacing MBES (Finalized 4m CUBE weighted Dynamic Surface in NOAA QC Tools) = 100% of nodes are within the allowable TVU. 

Complete Coverage MBES (Finalized 1m CUBE weighted Dynamic Surface in NOAA QC Tools) = 100% of nodes are within the allowable TVU.</ns2:discussion><ns2:images><ns2:caption>H13471 Finalized 4m Set Line Spacing MBES TVU Statistics</ns2:caption><ns2:link>SupportFiles\H13471_MB_4m_LWD_Final_TVU.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13471 Finalized 1m Complete Coverage MBES TVU Statistics</ns2:caption><ns2:link>SupportFiles\H13471_MB_1m_LWD_Final_TVU.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment><ns2:comment>Survey specific sound speed TPU values reported in Table 8 are inconsistent with those applied to the processed sounding data. Both measured and surface sound speed uncertainty vary from 0.03 to 0.05 m/ sec.

The Qimera-exported BAG uncertainty values originate solely from the standard deviation of the soundings that contributed to each CUBE hypothesis, scaled to the 95% confidence interval, and do not use total propagated vertical uncertainty estimates in this calculation.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>Depth differences between junctioning surveys were evaluated using the JunctionTrac program, developed in-house by eTrac Inc. For each junction, each CUBE weighted dynamic surface's nodes were exported to an ASCII CSV file where the fields were (Easting, Northing, Depth) for each node. A 4 meter difference surface between the junctioning datasets was also created and exported to an ASCII CSV file where the fields were (Easting, Northing, Diff) for each node. The three ASCII CSV files were then loaded into the JunctionTrac program and junction statistics were computed. A file was also created in this process to locate any nodes from the difference surface that exceed the allowable TVU, which was imported into Qimera and any identified points from JunctionTrac were analyzed. Note: the difference surfaces were created for comparison efforts only and are not submitted as surface deliverables.</ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H13468</ns2:registryNumber><ns2:scale>100000</ns2:scale><ns2:year>2021</ns2:year><ns2:fieldUnit>eTrac</ns2:fieldUnit><ns2:relativeLocation>SW</ns2:relativeLocation></ns2:survey><ns2:discussion>The junction comparison was performed using all overlapping data between H13468 and H13471. Below is a histogram of junction comparison statistics showing the difference between the junctioning surfaces and allowable TVU as well as difference statistics. 100% of nodes were within allowable TVU. </ns2:discussion><ns2:images><ns2:caption>H13471 - H13468 Junction Comparison</ns2:caption><ns2:link>SupportFiles\H13471_H13468_Junctions_JunctionTrac.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>H13471 - H13468 Difference Statistics</ns2:caption><ns2:link>SupportFiles\H13471_H13468_Junctions_DiffTrac.PNG</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13470</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2021</ns2:year><ns2:fieldUnit>eTrac</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>Note: The junction comparison between H13470 and H13471 will be submitted with the H13470 DR.</ns2:discussion><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>SVP casts were generally taken every 2 hours. Occasionally casts would exceed a 2 hour frequency, however would never exceed a 4 hour frequency. </ns1:castFrequency><ns1:discussion>On R/V Endeavor, R/V Rapid, and R/V Voxel casts were applied in QPS Qinsy acquisition software at the time of the cast. Surface SVP measured at 1Hz was compared to surface speed from the current profile in real-time. If the surface velocity comparison was in excess of 2m/s at any time during survey operations, a new cast was taken.  

Surface sound speeds were compared in real-time and profile to profile for each cast on the vessel. Additionally, the processor reviewed profiles in Qimera to remove spurious readings within a cast, compare day-to-day casts, and to check distribution over the surveyed area, in order to better understand trends for efficient acquisition planning.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Data Density Evaluation</ns2:title><ns2:discussion>In order to determine if the density of the data met the specified 5 soundings per node, data density was evaluated using DensityTrac in the AmiTrac program, developed in-house by eTrac Inc. Each finalized CUBE weighted dynamic surface's nodes were exported to a BBH file. The BBH file was then loaded into the DensityTrac program and density statistics were computed. 

For H13471 the following percentages represent the results of the density query: 

Set Line Spacing MBES (Finalized 4m CUBE weighted Dynamic Surface ) = 99.6958% of nodes are composed from at least 5 soundings.

Complete Coverage MBES (Finalized 1m CUBE weighted Dynamic Surface ) = 99.8561% of nodes are composed from at least 5 soundings.</ns2:discussion><ns2:images><ns2:caption>H13471 Finalized 4m Set Line Spacing MBES Density Distribution</ns2:caption><ns2:link>SupportFiles\H13471_Density_4m.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>H13471 Finalized 1m Complete Coverage MBES Density Distribution</ns2:caption><ns2:link>SupportFiles\H13471_Density_1m.PNG</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Backscatter data were collected throughout the survey and are retained in the raw DB files. Every effort was made in the field to collect quality backscatter data while maintaining the primary mandate of high quality bathymetric data. While no processing or analysis of backscatter was required, eTrac Inc. verified coverage and general quality of the backscatter data collected. A beam intensity window was monitored in Qinsy during acquisition to ensure backscatter data collection. Raw backscatter data were viewed in QPS FMGeocoder to further confirm collection criteria had been met. Shown below is an example of the unprocessed backscatter mosaic from H13471 DN187 (R/V Voxel).</ns2:discussion><ns2:images><ns2:caption>Raw Backscatter from R/V Voxel (DN187)</ns2:caption><ns2:link>SupportFiles\H13471_Backscatter.PNG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:featureObjectCatalog>NOAA Profile Version 2021</ns1:featureObjectCatalog><ns1:discussion>Feature Object Catalog, NOAA Profile Version 2021 was used only in CARIS. Qimera was used as the primary processing software.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13471_MB_4m_LWD_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.68</ns2:min><ns2:max units="meters">22.77</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13471_MB_1m_LWD_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">3.8</ns2:min><ns2:max units="meters">22.79</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>A 4m surface is provided meeting Set Line Spacing MBES with backscatter specifications for H13471.

A 1m surface is provided meeting Complete Coverage MBES backscatter specifications for H13471. This surface is created for the significant shoals that were developed in waters less than 20m deep per our Project Instructions.

Note: Both surfaces' depth ranges were extended past 20m to include the remaining deeper values beyond 20m to avoid creating superfluous surfaces at a lower resolution.</ns1:discussion><ns1:images><ns2:caption>H13471 Finalized 4m CUBE weighted Dynamic Surface Coverage</ns2:caption><ns2:link>SupportFiles\H13471_SurfaceCoverage_1m.PNG</ns2:link></ns1:images><ns1:images><ns2:caption>H13471 Finalized 1m CUBE weighted Dynamic Surface Coverage</ns2:caption><ns2:link>SupportFiles\H13471_SurfaceCoverage_4m.PNG</ns2:link></ns1:images><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR and DAPR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR_Y390_KR_21_NAD83_to_LWD_IGLD85.qgfvom</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>Survey data were vertically referenced to the ellipsoid. A time dependent, 7 parameter transformation from ITRF-2014 to NAD83_2011 was performed in QPS Qinsy. Using VDatum, a vertical separation model was created to transform the ellipsoidally referenced data from NAD83_2011 to LWD_IGLD85. The transformation and the separation model were applied in QPS Qinsy on the vessels in real-time to achieve LWD_IGLD85 in the field.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:projection>Projected UTM 16</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>RTX</ns2:methodsUsed><ns2:baseStations/><ns2:discussion>Applanix PosPac MMS was utilized to post process realtime positioning data utilizing Trimble's PP-RTX implementation of Trimble CenterPoint RTX to create a Smoothed Best Estimate of Trajectory (SBET).</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="true"><ns2:discussion>GNSS satellite corrections were received on each vessel using the G2+ carrier signal from the Marinestar Global Correction System maintained by Fugro. </ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:WAAS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:topic><ns2:discussion>A chart comparison was conducted for H13472 using Pydro CA tools, Qimera, and Caris HIPS and SIPS. Survey data were compared against the largest scale ENC to accomplish the chart comparison. The largest scale ENC does not cover the entire survey boundary so a second chart was used to complete the chart comparion. Details of the ENCs used are listed below. 

US5WI03M, scale: 20000, edition: 4, update application date: 01/06/2021, issue date: 01/06/2021
US4WI03M, scale: 80000, edition: 25, update application date: 09/01/2021, issue date: 09/01/2021

Throughout survey operations sounding comparisons between the charted depths and the surveyed depths were analyzed to identify depth discrepancies. Using the 4 meter CUBE weighted Dynamic surface soundings were generated in the &quot;Sounding Selection&quot; tab of Pydro CA tools. Soundings were displayed against the charted soundings and a visual comparison was made in Caris HIPS and SIPS. Additionally, potential DtoNs and discrepancies were generated using the &quot;DTM vs Chart&quot; tab of Pydro CA tools. The results were displayed through CA tools and investigated in CARIS HIPS and SIPS and Qimera.

An overview image of the generated soundings on each chart is included below. Additionally, a detailed example image of the generated soundings on the charts is included below. Lastly, an overview of the identified DtoN's location is included.

Results of the chart comparison are included in the following sections.</ns2:discussion><ns2:images><ns2:caption>Generated Soundings used for Chart Comparison (US5WI03M)</ns2:caption><ns2:link>SupportFiles\H13471_ChartComparison_US5WI03M.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Generated Soundings used for Chart Comparison (US4WI03M)</ns2:caption><ns2:link>SupportFiles\H13471_ChartComparison_US4WI03M.PNG</ns2:link></ns2:images></ns2:topic><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:name>US5WI03M</ns2:name><ns2:scale>20000</ns2:scale><ns2:edition>4</ns2:edition><ns2:updateApplicationDate>2021-06-01</ns2:updateApplicationDate><ns2:issueDate>2021-06-01</ns2:issueDate></ns2:ENC><ns2:ENC><ns2:name>US4WI03M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>18</ns2:edition><ns2:updateApplicationDate>2021-08-30</ns2:updateApplicationDate><ns2:issueDate>2020-11-04</ns2:issueDate></ns2:ENC><ns2:comments/></ns1:charts><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>There were 3 DtoNs found in H13471, and added to the Final Feature File (FFF). Each feature in the FFF has been given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format 71XXX). Refer to the FFF for determinations and recommendations of each feature. The DtoNs were submitted in the following Danger to navigation reports: 

H13471_DtoN_01
H13471_DtoN_02_03

H13471_DtoN_01 contains 7 soundings; H13471 DtoN_02 contains 1 sounding; H13471_DtoN_03 contains 1 sounding.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>There were 29 charted features assigned to H13471 that are included in the Final Feature File (FFF). Each feature in the FFF has been given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format 71XXX). Refer to the FFF for determinations and recommendations of each feature.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>1 new feature was found in H13471. Note: DtoNs are not included in the number of new features in this section. DtoNs can be found separately in section D.1.2.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>Oconto Harbor is maintained channel and has a charted controlled depth of 1.0m and 1.10m. Dredge Area controlled depths in Oconto Harbor were compared against soundings derived from our 4m surface as described in section D.1.

Pensaukee Harbor is a channel with a depth range value of 0.10m. This channel was not addressed due to be inshore of NALL.

No discrepancies were found. Per investigation requirements the features were not included in the FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels></ns1:chartComparison><ns1:additionalResults><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>There were 17 charted AtoNs assigned in H13471.  Each feature was given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format 71XXX). Refer to the FFF for determinations of each feature. Note: All AtoNs were included in the number of charted features within section D.1.3.  </ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>14 bottom samples were obtained in accordance with section 7.1 of the HSSD 2021 in areas designated by the field through discussions with our COR. Detailed information and images of the bottom samples are located in the Final Feature File (FFF). Each bottom sample has been given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format EX).</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No Overhead Features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No Submarine Features exist for this survey. </ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="Investigated"><ns2:discussion>In some regions, marine vegetation was picked up by the MBES. The vegetation was investigated by collecting additional lines in various directions in a few different areas throughout OPR-Y390-KR-21. The overlap of the vegetation throughout the investigation lines was not consistent and therefore could be determined to be marine vegetation moving in the water column. After the investigation was complete, the marine vegetation was rejected from the dataset by data processors. Below is an example where this occurred in this survey. No data gaps were observed in the delivered surfaces from rejecting the marine vegetation in this survey. </ns2:discussion><ns2:images><ns2:caption>Marine Vegetation Rejected</ns2:caption><ns2:link>SupportFiles\H13471_Abnormal_Environmental_Conditions.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>There were 3 Dredge Areas assigned in H13471. 2 dredge areas had no discrepancies from the chart. 1 dredge area was not addressed due to being inshore of NALL. Per investigation requirements the features were not included in the FFF.

There were 2 Shoreline Construction Features assigned in H13471. Note: The Shoreline Construction Features were included in the FFF and were included in the number of charted features within section D.1.3.

Refer to the FFF for determinations of each feature.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:ENCScaleRecommendation><ns2:results recommended="false"><ns2:discussion>No new ENC scales are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ENCScaleRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>David Neff</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2021-09-24</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>