<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2020/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2020/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2020/01/DescriptiveReport http://svn.pydro.noaa.gov/2020/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-R341-KR-19</ns2:number><ns2:name>Kuskokwim Bay, AK &amp; Vicinity</ns2:name><ns2:generalLocality>Kuskokwim Bay, AK</ns2:generalLocality><ns2:fieldUnit>Terrasond</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13247</ns2:registryNumber><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions>OPR-R241-KR-19</ns2:registryInstructions><ns2:sublocality>28 NM SW of Kwigillingok</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2019</ns2:year><ns2:chiefOfParty>Andrew Orthmann</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2019-05-10</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2019-07-01</ns2:start><ns2:end>2019-08-18</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></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 3N, MLLW. 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>The project area is located in southwest Alaska in Kuskokwim Bay, SW of the entrance to the Kuskokwim River in a relatively remote area of the Arctic. Vessel traffic consists largely of barges servicing the communities that include Bethel up the Kuskokwim River to the NE, as well as vessels transiting between Kuskokwim Bay and Etolin Strait, to the west.

The area is normally not navigable during winter due to discontinuous sea ice in the bay and river ice flows from the Kuskokwim River. The area is highly exposed, with only limited protection from the north. The seafloor is relatively shallow (less than 20 meters) and gently sloping. Bottom samples returned primarily black sand.

Bathymetric data collection was carried out in July and August of 2019 under project OPR-R341-KR-19, with final processing and reporting carried out from September through December, 2019. Supporting tide data was acquired from June through October, 2019. Work was completed concurrently with other assigned areas within Kuskokwim Bay and near Nunivak Island, and done in accordance with the Hydrographic Survey Project Instructions (dated May 10th, 2019) and the NOS Hydrographic Surveys Specifications and Deliverables (HSSD), March 2019 edition.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">59.8083305556</ns2:latitude><ns2:longitude hemisphere="W">164.485423611</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">59.3016883333</ns2:latitude><ns2:longitude hemisphere="W">163.335220278</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Image showing survey extents.</ns2:caption><ns2:link>SupportFiles\H13247_Extents.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Per consultation with HSD OPS, area from the unassigned adjacent survey area &quot;HXXXXX&quot; was added to this survey. Surveying to all extents of the HXXXXX area was not required. Refer to the Survey Coverage section of this report for more discussion.

Data was successfully acquired to all originally assigned limits of H13247.</ns2:discussion><ns2:images><ns2:caption>Original survey limits of H13247 (right side of image) were achieved. Area from the unassigned sheet HXXXXX (red dashed polygon, left side of image) was partially surveyed and added to H13247.</ns2:caption><ns2:link>SupportFiles\HXXXXX_Area.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:topic><ns2:discussion>The overall project OPR-R341-KR-19 is intended to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products in the U.S. Arctic to support commerce in the region. Automatic Identification Systems (AIS) traffic patterns feeding the Hydrographic Health model, along with direct user feedback helped to define the survey area in Kuskokwim Bay, Southwest Alaska. This area is largely unsurveyed and contains mud flats, uncharted shoals, and poorly modeled tides, forcing vessel traffic between the Kuskokwim River and northern communities to take an extended southerly route to stay in safe water. Surveying these areas within Kuskokwim Bay will allow for shorter routes, increasing the safety and efficiency of vessel traffic. This work will also directly support the maritime services available to the native communities of Kwigillingok and Kongiganak.

Furthermore, this project will provide support for other NOAA Hydrographic surveys and regional tidal products by installing temporary water level measuring stations in the vicinities of Cape Newenham and Nushagak Peninsula located in Bristol Bay.

Survey data within the survey limits is intended to supersede all prior survey data within the project limits.</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 xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area within Sheet 2</ns2:waterDepth><ns2:requiredCoverage>Set Line Spacing MBES at 400 m (Refer to HSSD Section 5.2.2.4 Option A)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete 5301 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:results deviation="true"><ns2:discussion>Coverage requirements were met.

5,761 linear nautical miles (LNM) was acquired project-wide, which exceeded the required minimum of  5,301 LNM. The overage of 460 LNM (about 8.7% of required LNM) was collected to compensate for any inefficiencies incidental to the execution of line collection such as excess crossline LNM, data acquired on turns in order to scout depths between lines in shallow water, or lines ran closer together than required.


Survey of &quot;HXXXXX&quot; and Incorporation into H13247:

This survey is divided into two parts for coverage tracking purposes. The eastern part is the originally assigned H13247, and the western part is the unassigned &quot;HXXXXX&quot; area from the project instructions. The eastern part was surveyed in full, achieving all extents and the required line spacing of 400 m. Refer to the image of the two parts previously in this report.

MBES data collection in the western part, HXXXXX, commenced when it became obvious that survey of the seven sheets assigned under the project would not require all 5,301 LNM assigned in the project instructions. The eastern part of HXXXXX was surveyed first in order to be coterminous with the original H13247 extents before proceeding into the western portion. Most lines in the HXXXXX area were also acquired at 400 m spacing per the project instructions requirement for &quot;Sheet 8&quot;. However, after consultation with NOAA OPS, the final sets of lines (located in the SW portion of the survey area) were spaced at 800 m to cover more area with the remaining LNM.

To simplify reporting and data management, all data collected in &quot;HXXXXX&quot; was incorporated into H13247 instead of being assigned as a new H#.

Refer to Appendix II for correspondence regarding the area.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Image showing survey coverage.</ns2:caption><ns2:link>SupportFiles\H13247_Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>693.3</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>34.7</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>994.1</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>105.3</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>1687.4</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>140</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>8.3</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>4</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>354.5</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2019-07-01</ns2:surveyDates><ns2:surveyDates>2019-07-04</ns2:surveyDates><ns2:surveyDates>2019-07-07</ns2:surveyDates><ns2:surveyDates>2019-07-16</ns2:surveyDates><ns2:surveyDates>2019-07-17</ns2:surveyDates><ns2:surveyDates>2019-07-18</ns2:surveyDates><ns2:surveyDates>2019-07-19</ns2:surveyDates><ns2:surveyDates>2019-07-20</ns2:surveyDates><ns2:surveyDates>2019-07-21</ns2:surveyDates><ns2:surveyDates>2019-07-22</ns2:surveyDates><ns2:surveyDates>2019-07-23</ns2:surveyDates><ns2:surveyDates>2019-07-24</ns2:surveyDates><ns2:surveyDates>2019-07-25</ns2:surveyDates><ns2:surveyDates>2019-07-26</ns2:surveyDates><ns2:surveyDates>2019-07-27</ns2:surveyDates><ns2:surveyDates>2019-07-28</ns2:surveyDates><ns2:surveyDates>2019-08-17</ns2:surveyDates><ns2:surveyDates>2019-08-18</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>ASV-CW5</ns2:hullID><ns2:LOA units="meters">5.5</ns2:LOA><ns2:draft units="meters">0.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:LOA units="meters">32</ns2:LOA><ns2:draft units="meters">1.8</ns2:draft></ns1:vessel><ns1:images><ns2:caption>ASV-CW5 (foreground), and Q105 (background).</ns2:caption><ns2:link>SupportFiles\Vessels.jpg</ns2:link></ns1:images><ns1:discussion>The Qualifier 105 (Q105) is a 32 m aluminum-hull vessel owned and operated by Support Vessels of Alaska. The Q105 acquired multibeam data and provided housing and facilities for on-site data processing. The vessel was also used to collect bottom samples, deploy/recover BMPG tide gauges, conduct sound speed casts, and deploy/recover the ASV-CW5 vessel.

The ASV-CW5 (C-Worker 5) is a 5.5 m aluminum-hull Autonomous Surface Vessel (ASV) owned and operated by L3-Harris ASV. The ASV was operated in an unmanned but monitored mode, collecting multibeam data in close proximity to the Q105.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>SeaBat 7125 SV</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>SeaBat 7101</ns2:model><ns2:type>MBES</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>Teledyne Oceanscience</ns2:manufacturer><ns2:model>rapidCAST</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>rapidPro SVT</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>Both survey vessels were outfit for MBES data collection with similar survey equipment. The ASV-CW5 was equipped with a Reson SeaBat 7125 MBES while the Q105 used a Reson SeaBat 7101 MBES. Both vessels used Applanix POSMV 320 V5 (Wavemaster II) units for attitude and position measurements. Sound speed profiles were collected using a Valeport rapidPro SVT sensor (deployed using a Teledyne Oceanscience RapidCast system) from the Q105 only.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:topic><ns2:discussion>Effort was made to ensure crosslines had good temporal and geographic distribution, were angled to enable nadir-to-nadir comparisons, and that the required minimum percent of mainscheme LNM was achieved. 

Crosslines were conducted with both vessels to ensure there was ample overlap for inter-vessel comparisons, with each vessel crossing the other's mainscheme lines. Since the two vessels worked in close proximity and normally ran parallel lines, crosslines were often collected in sets whenever both vessels were in simultaneous operation. Crosslines were also occasionally collected while transiting across the survey area to reach a different survey priority such as bottom sample locations or infills, leading to crosslines that were diagonal to the direction of mainscheme lines.

The crossline analysis was conducted using CARIS HIPS “Line QC Report” process. Each crossline (with all associated file segments) was selected and run separately through the process, which calculated the depth difference between each accepted crossline sounding and a &quot;QC&quot; BASE (CUBE-type) surface’s depth layer created from the mainscheme data. The QC surface was created with the same parameters and resolution used for the final surface, with the important distinction that the QC surface did not include crosslines so as to not bias the results. Differences in depth were grouped by beam number and statistics were computed, including the percentage of soundings with differences from the QC surface falling within IHO Order 1a.

When at least 95% of the sounding differences exceed IHO Order 1a, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.” A 5% (or less) failure rate was considered acceptable since this approach compares soundings to a surface (instead of a surface to a surface), allowing for the possibility that noisy crossline soundings that don't adversely affect the final surface could be counted as a QC failure in this process.

Lines selected as crosslines and their percentage (%) of soundings passing IHO Order 1a, sorted from highest passing to lowest, are listed below.

0261-Q105-202-B5XL00000 -- 100.0% pass
0287-Q105-203-B2EW10400 -- 100.0% pass
0355-Q105-208-B_XL -- 100.0% pass
0552-Q105-229-BXL-01 -- 100.0% pass
0553-Q105-229-BXL-02 -- 100.0% pass
0554-Q105-229-BXL-03 -- 100.0% pass
0555-Q105-229-BXL-04 -- 100.0% pass
0557-Q105-229-BXL-06 -- 100.0% pass
0558-Q105-229-BXL-05 -- 100.0% pass
0560-Q105-229-BXL-07 -- 100.0% pass
0561-Q105-229-BXL-08 -- 100.0% pass
0562-Q105-229-BXL-09 -- 100.0% pass
0567-Q105-229-B8_XL2 -- 100.0% pass
0568-Q105-230-B8_XL3 -- 100.0% pass
0569-Q105-230-BXL-15 -- 100.0% pass
0570-Q105-230-BXL-15 -- 100.0% pass
0571-Q105-230-BXL-16 -- 100.0% pass
0572-Q105-230-BXL-17 -- 100.0% pass
0573-Q105-230-BXL-17 -- 100.0% pass
0575-Q105-230-BXL-18 -- 100.0% pass
0576-Q105-230-BXL-19 -- 100.0% pass
0565-ASV-CW5-202-B1EW07600 -- 100.0% pass
0636-ASV-CW5-205-B6EW10400 -- 100.0% pass
0663-ASV-CW5-208-B_XL -- 100.0% pass
0665-ASV-CW5-209-B3_XL -- 100.0% pass
1525-ASV-CW5-229-B8_XL1 -- 100.0% pass
1526-ASV-CW5-230-B8_XL4 -- 100.0% pass

Results: Agreement between the mainscheme surface and crossline soundings is excellent. For each crossline, at least 95% of the crossline soundings compare to the mainscheme surface within IHO Order 1a. None were considered to fail QC.

Refer to Separate II: Digital Data for the detailed Crossline QC reports.</ns2:discussion></ns2:topic><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod><ns2:measured units="meters">0.13</ns2:measured><ns2:zoning units="meters">0</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Q105</ns2:hullID><ns2:measuredCTD units="meters/second">0.5</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:measuredXBT xsi:nil="true"/><ns2:surface units="meters/second">.025</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>ASV</ns2:hullID><ns2:measuredCTD units="meters/second">0.5</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:measuredXBT xsi:nil="true"/><ns2:surface units="meters/second">.025</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>0.13 was provided and used as the uncertainty of the NOAA-provided ERTDM model. Refer to Appendix I for correspondence.

The uncertainty layer of the final surface was examined in CARIS HIPS. Uncertainty falls in the range of 0.261 to 0.439 m. Most grid cells are on the lower end of the uncertainty range, approximately 0.270 m.  100% of grid cells have uncertainty within allowable TVU for the depth.</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>NOAA's &quot;Gridded Surface Comparison V19.4&quot; utility was used to complete the junction comparisons. The utility differences the surfaces from the junctioning surveys and generates statistics, including the percentage of grid cells that compare to within allowable TVU for the depth. 4 m-resolution CUBE surfaces were used for all comparisons.</ns2:discussion><ns2:images><ns2:caption>Image showing survey junctions.</ns2:caption><ns2:link>SupportFiles\H13247_Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H13246</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2019</ns2:year><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement between the two surveys is excellent. The mean difference is 0.01 m with a standard deviation of 0.06 m. 100% of overlapping grid cells compare within the allowable TVU for the depth.</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="true"><ns2:issue><ns2:title>POSMV Dropouts (ASV-CW5)</ns2:title><ns2:discussion>Approximately every 24 hours during survey operations the POSMV on the ASV-CW5 would drop offline. This was observed as sudden output of obviously erroneous data by the POSMV such as excessive vessel speeds, incorrect headings, and erroneous motion, followed by an automatic reinitialization of the POSMV. The issue would often repeat 1-2 additional times over a 5-10 minute period before resuming normal operations for an additional 24 hours. No definite cause was determined.

When this occurred the ASV-CW5 would break offline, note the issue in the acquisition log, circle back and proceed with rerunning the affected section of line. The affected section of line was subsequently rejected in processing. Since affected data was rejected and reran there is no adverse affect on final deliverables.</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>2 hours</ns1:castFrequency><ns1:discussion>Sound speed profiles or &quot;casts&quot; were acquired aboard the Q105 while underway with a Teledyne Oceanscience RapidCAST system, which utilized a Valeport rapidPro SVT sound speed profiler. 

Surface sound speed at the sonar head was monitored continuously and a new cast was collected when the surface speed varied from the previous profile's speed at the same depth by greater than 2 m/s, leading to a cast interval of approximately 2 hours.

Casts were taken as deep as possible. On survey lines with significant differences in depth, the deeper portion of the line was favored to ensure that changes across the full water column were measured.

The cast data was used to correct the sounding data for both vessels, using the &quot;nearest in distance within time&quot; (set to 4 hours) within CARIS HIPS.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><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>GPS Vertical Busts</ns2:title><ns2:discussion>Vertical busts attributable to GPS positioning error between crosslines or overlapping mainscheme are apparent periodically in the data set. These are normally less than 0.15 m, with extreme cases showing up to 0.30 m of vertical separation. However, all crosslines--including those exhibiting or crossing areas exhibiting vertical busts--pass within IHO Order 1a, and final surfaces are within allowable TVU for the depth.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="true"><ns2:discussion>Deviations from the Corrections to Echo Soundings section of the DAPR are itemized below. Note that in all cases final data is within specifications.


Delayed Heave Exceptions

The following lines could not have Delayed Heave loaded. This was usually due to a software crash or other issue causing logging to the associated POS file to cease early. Real-time heave was used instead during all processing phases including SVP correction, Compute GPS Tide, and Merge on these lines.

0029-ASV-CW5-182-B6EW07200_-_0002
0029-ASV-CW5-182-B6EW07200_-_0003
0030-ASV-CW5-182-B6EW07200_-_0001
0031-ASV-CW5-182-B6EW07200_-_0001
0038-ASV-CW5-182-B4EW09200_-_0004
0080-ASV-CW5-188-B6EW12800_-_0001
0081-ASV-CW5-188-B6EW12800_-_0001
0643-ASV-CW5-205-B7EW00800_-_0011
0590-ASV-CW5-204-B5EW01200_-_0004


GPS Height Smoothing

The following lines were loaded with GPS heights that had been smoothed to remove spikes and/or shortterm drifts using a 6-minute moving average. The smoothed GPS height data was loaded using CARIS' Generic Data Parser utility from text files at a rate of 1 Hz, which are included with the survey deliverables. Since the smoothing process removed heave data from the GPS record, the &quot;Apply Dynamic Heave&quot; option was set to &quot;None&quot; during computation of GPS Tide for these lines. More details are available in the DAPR.

0511-ASV-CW5-197-B6EW08800_-_0001
0511-ASV-CW5-197-B6EW08800_-_0002
0511-ASV-CW5-197-B6EW08800_-_0003
0511-ASV-CW5-198-B6EW08800_-_0004


Applanix Smart Base (ASB)

The following POS file was processed using Applanix Smart Base (ASB) instead of the project default PP-RTX to improve vertical matchup on a few lines, also listed below.

POS File:

2019-228-2348-ASV

Lines:

1516-ASV-CW5-229-B6EW12400_-_0002
1516-ASV-CW5-229-B6EW12400_-_0003
1517-ASV-CW5-229-B6EW12800_-_0001
1518-ASV-CW5-229-B6EW12400_-_0001</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>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Extended Attribute Files V2019.3</ns1:featureObjectCatalog><ns1:discussion>NOAA Extended Attributes were used for the Final Feature File (FFF) submitted with the survey deliverables.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13247_MB_4m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13247_MBAB_1m_ASV_400kHz_1of2</ns2:surfaceName><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13247_MBAB_1m_ASV_400kHz_2of2</ns2:surfaceName><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13247_MBAB_1m_Q105_240kHz_1of2</ns2:surfaceName><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13247_MBAB_1m_Q105_240kHz_2of2</ns2:surfaceName><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>MBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:discussion>The final depth information for this survey was submitted as a CARIS BASE surface (CSAR format) which best represented the seafloor at the time of the 2019 survey. The surface was created from fully processed data with all final corrections applied. 

The surface was created using NOAA CUBE parameters and resolutions by depth range in conformance with the 2019 HSSD. The surface was finalized, and designated soundings were applied where applicable. Horizontal projection was selected as UTM Zone 3 North, NAD83.

A non-finalized versions of the CSAR surface is also included which does not have a depth cutoff applied. This does not have the &quot;_Final&quot; designation in the filename.

An S-57 (.000) Final Feature File (FFF) was submitted with the survey deliverables as well. The FFF contains data not readily represented by the final surface, including bottom samples and shoreline verification results (if any). Each object is encoded with mandatory S-57 attributes and NOAA Extended Attributes (V2019.3).

Georeferenced multibeam backscatter mosaics (Geotif format in NAD83 UTM Zone 3N, 1 m resolution) were also produced and are provided with the survey deliverables. Separate mosiacs were produced for each vessel. Note that backscatter processing and mosaic generation was not a requirement and the mosaics are provided as-is. The mosaics may have flaws or holidays which could be addressed through further processing. However, they are of sufficient quality to show the relative changes in seafloor type across the survey area.</ns1:discussion><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.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:subordinateGauges><ns2:stationName>Port Moller</ns2:stationName><ns2:stationID>9463502</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Cape Pierce</ns2:stationName><ns2:stationID>9465137</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Naknek</ns2:stationName><ns2:stationID>9465203</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Kulukak Point</ns2:stationName><ns2:stationID>9465265</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Levelock</ns2:stationName><ns2:stationID>9465419</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Ishkowik</ns2:stationName><ns2:stationID>9465993</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Cape Mendenhall</ns2:stationName><ns2:stationID>AAAAAAA</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>SW Kuskokwim Bay</ns2:stationName><ns2:stationID>BBBBBBB</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Cape Corwin</ns2:stationName><ns2:stationID>CCCCCCC</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via ERTDM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>R341KR2019_ERTDM_NAD83-MLLW</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>All soundings were reduced to MLLW using the ERTDM NAD83 to MLLW separation model grid file provided by NOAA using ERS methodology. 

Discrete tide zones were generated using project gauge data but were used for comparison purposes only. 

A comparison between the provided ERTDM model and a ERZT model created using the tide zones was undertaken. There is generally good agreement between the models, with project-wide agreement averaging 0.033 m with a standard deviation of 0.271 m.

See the HVCR for additional information.</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 3</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:methodsUsed>RTX</ns2:methodsUsed><ns2:baseStations/><ns2:discussion>The Trimble PP-RTX subscription-based correction service within POSPac was used for final positioning. Results were good overall, with RMS error usually at 0.10 m or better vertically.

Applanix Smart Base (ASB) was used on a handful of lines to improve vertical agreement. These were itemized earlier in this report.

 Refer to the DAPR for additional detail.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="true"><ns2:discussion>The survey vessels were configured to receive RTK-level correctors via Hemisphere AtlasLink SBAS (L-band) receivers. This was utilized throughout the survey on the ASV-CW5 but only briefly at the start of operations on the Q105.

However, all real-time correctors were superseded in  processing with PPK correctors from Applanix POSPac. Refer to the DAPR for additional detail.</ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:WAAS used="true"><ns2:discussion>The FAA Wide Area Augmentation System (WAAS) was used for real-time positioning on the Q105 for the majority of the survey. These positions were superseded in processing with PPK correctors from Applanix POSPac, as described in the DAPR.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:topic><ns2:discussion>The chart comparison was performed by examining the best-scale Electronic Navigational Charts (ENCs) that intersect the survey area. The latest edition(s) available at the time of report compilation were used.

The chart comparison was accomplished by overlaying the finalized BASE surface(s) with shoal-biased soundings and the final feature file (FFF) on the charts in CARIS HIPS. The general agreement between charted soundings and survey soundings was then examined and a more detailed comparison was undertaken for any shoals or other dangerous features. In areas where a large scale chart overlapped with a small scale chart, only the larger scale chart was examined.

When comparing to survey data, chart scale was taken into account so that 1 mm at chart scale was considered to be the valid radius for charted soundings and features.

Results are shown in the following sections. It is recommended that in all cases of disagreement this survey should supersede charted data.

USCG Notice to Mariners (NM) and USCG Local Notice to Mariners (LNM) for District 17 from week 26/2019 through 34/2019 were checked and no items were found that affected the survey area.

Note that ENC metadata and non-specific geographic area objects on the ENCs that overlap the survey area were not investigated.</ns2:discussion></ns2:topic><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:name>US2AK95M</ns2:name><ns2:scale>1534076</ns2:scale><ns2:edition>9</ns2:edition><ns2:updateApplicationDate>2018-08-20</ns2:updateApplicationDate><ns2:issueDate>2019-10-16</ns2:issueDate></ns2:ENC><ns2:comments/></ns1:charts><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.

No DTONs were submitted for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:chartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels></ns1:chartComparison><ns1:additionalResults><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</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>Four bottom samples were assigned via the PRF. Samples were obtained at all locations and returned primarily black sand.

Refer to the FFF submitted with the survey deliverables for results.</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="None Exist"><ns2:discussion>No abnormal seafloor and/or environmental conditions exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</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 insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ENCScaleRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>Field operations and data processing contributing to the completion of this survey were conducted under my direct supervision with frequent personal checks of progress, integrity, and adequacy.</ns1:supervision><ns1:approval>This report, digital data, and all other accompanying records are approved. All records are hereby respectfully submitted for final review and acceptance.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds the requirements set forth in the 2019 NOS Hydrographic Surveys Specifications and Deliverables document as well as the Hydrographic Survey Project Instructions and Statement of Work. This data is adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies (if any) noted in this Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName><ns2:approverTitle>TerraSond Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2019-12-14</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Survey Outlines</ns2:reportName><ns2:reportDateSent>2019-09-10</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>MMO Training Logsheet and Observation Logs</ns2:reportName><ns2:reportDateSent>2019-09-12</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>NCEI Sound Speed Data Submission</ns2:reportName><ns2:reportDateSent>2019-09-12</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Coast Pilot Report</ns2:reportName><ns2:reportDateSent>2019-09-13</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9465419 Levelock</ns2:reportName><ns2:reportDateSent>2019-11-15</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9465993 Ishkowik</ns2:reportName><ns2:reportDateSent>2019-11-15</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9463502 Port Moller</ns2:reportName><ns2:reportDateSent>2019-11-16</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9465203 Naknek</ns2:reportName><ns2:reportDateSent>2019-11-18</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9465137 Cape Pierce</ns2:reportName><ns2:reportDateSent>2019-11-19</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - 9465265 Kulukak Point</ns2:reportName><ns2:reportDateSent>2019-11-20</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - AAAAAAA Cape Mendenhall</ns2:reportName><ns2:reportDateSent>2019-11-23</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - BBBBBBB SW Kuskokwim Bay</ns2:reportName><ns2:reportDateSent>2019-11-23</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package - CCCCCCC Cape Corwin</ns2:reportName><ns2:reportDateSent>2019-11-27</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>