<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2019/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport http://svn.pydro.noaa.gov/2019/01/DR.xsd"><ns1:metadata><ns1:registryMetadata><ns2:registryNumber>H13114</ns2:registryNumber><ns2:sublocality>Northwest of Sanak Island</ns2:sublocality><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:sheetID>3</ns2:sheetID></ns1:registryMetadata><ns1:assignment>Contractor</ns1:assignment><ns1:projectMetadata><ns2:generalLocality>Southwestern Alaskan Peninsula</ns2:generalLocality><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:number>OPR-P377-KR-18</ns2:number><ns2:name>Southwest Alaska Peninsula</ns2:name></ns1:projectMetadata><ns1:surveyMetadata><ns2:datesOfSurvey><ns2:start>2018-06-08</ns2:start><ns2:end>2018-07-22</ns2:end></ns2:datesOfSurvey><ns2:projectType>Navigable Area</ns2:projectType><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:year>2018</ns2:year><ns2:chiefOfParty>Andrew Orthmann</ns2:chiefOfParty><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone><ns2:PIDate>2018-04-24</ns2:PIDate><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes></ns1:surveyMetadata></ns1:metadata><ns1:areaSurveyed><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage (Refer to HSSD Section 5.2.2.3)  Acquire backscatter data during all multibeam data acquisition (Refer to HSSD Section 6.2)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>LNM no less than 5715 LNM. Report significant shoaling via weekly progress report. COR may adjust survey prioritization based on observed shoaling.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:comments/><ns2:results deviation="true"><ns2:discussion>Total project-wide LNM acquired for project OPR-P377-KR-18 totaled 5,738, which exceeded the required 5,715.</ns2:discussion></ns2:results></ns1:surveyCoverage><ns1:surveyStatistics><ns2:surveyDates>2018-07-22</ns2:surveyDates><ns2:surveyDates>2018-07-21</ns2:surveyDates><ns2:surveyDates>2018-07-19</ns2:surveyDates><ns2:surveyDates>2018-07-15</ns2:surveyDates><ns2:surveyDates>2018-07-14</ns2:surveyDates><ns2:surveyDates>2018-07-13</ns2:surveyDates><ns2:surveyDates>2018-07-12</ns2:surveyDates><ns2:surveyDates>2018-07-11</ns2:surveyDates><ns2:surveyDates>2018-07-05</ns2:surveyDates><ns2:surveyDates>2018-07-04</ns2:surveyDates><ns2:surveyDates>2018-06-30</ns2:surveyDates><ns2:surveyDates>2018-06-29</ns2:surveyDates><ns2:surveyDates>2018-06-26</ns2:surveyDates><ns2:surveyDates>2018-06-21</ns2:surveyDates><ns2:surveyDates>2018-06-14</ns2:surveyDates><ns2:surveyDates>2018-06-13</ns2:surveyDates><ns2:surveyDates>2018-06-09</ns2:surveyDates><ns2:surveyDates>2018-06-08</ns2:surveyDates><ns2:comments/><ns2:totalSurveyStats><ns2:bottomSamples>7</ns2:bottomSamples><ns2:diveOps>0</ns2:diveOps><ns2:SNM>86.2</ns2:SNM><ns2:DP>0</ns2:DP><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints></ns2:totalSurveyStats><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>45.2</ns2:XL_MBES_SBES><ns2:MS_MBES>398.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>61.8</ns2:XL_MBES_SBES><ns2:MS_MBES>471.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>107</ns2:XL_MBES_SBES><ns2:percentXLLNM>12.3</ns2:percentXLLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES>869.6</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES></ns2:totalLNM></ns2:LNM><ns2:discussion>Only bottom samples were acquired on 7/21 and 7/22.</ns2:discussion></ns1:surveyStatistics><ns1:surveyPurpose><ns2:discussion>The purpose of this project is to provide contemporary surveys to update National Ocean Service nautical charting products to support an increase in vessel traffic in Unimak Passage. Unimak Passage is the gateway to the Bering Strait utilized by cargo, fishing, and trans-Pacific vessels delivering goods to the Aleutian Islands, western Alaska, and the Arctic. This passage and area is specifically utilized by the fishing fleet in Bristol Bay and the Bering Sea and this area was specifically requested by the Alaska Marine Pilots, Alaska Fisheries Development Foundation, the 17th District of the United States Coast Guard, and the Alaska Marine Highway. This project was last surveyed using partial bottom coverage techniques in the 1930's. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyLimits><ns2:comments/><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results></ns1:surveyLimits><ns1:areaDescription><ns2:images><ns2:caption>Survey extents and overview</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/H13114%20Extents.jpg</ns2:link></ns2:images><ns2:discussion>The survey area is located in the Aleutian Island region of southwest Alaska. The closest community is False Pass, population 35 (2010), located approximately 13 NM to the north on Unimak Island. The closest major hub is Dutch Harbor, population 4,376 (2010), located approximately 117 NM to the WSW.

Field work was carried out in June and July of 2018 under project OPR-P377-KR-18, with final processing and reporting carried out from August through December, 2018. Four additional survey areas located to the west, north, and south were surveyed concurrently during this project. Work was done in accordance with the Hydrographic Survey Project Instructions (dated April 24th, 2018) and the NOS Hydrographic Surveys Specifications and Deliverables (HSSD), April 2017 edition.</ns2:discussion><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">54.482344</ns2:latitude><ns2:longitude hemisphere="W">163.029991</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">54.653065</ns2:latitude><ns2:longitude hemisphere="W">163.345451</ns2:longitude></ns2:northWest></ns2:limits><ns2:comments/></ns1:areaDescription><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:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Survey coverage graphic</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/H13114%20Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic></ns1:areaSurveyed><ns1:verticalAndHorizontalControl><ns1:horizontalControl><ns2:WAAS used="true"><ns2:discussion>WAAS was used for real-time positioning only.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/><ns2:RTK used="false" xsi:nil="true"/><ns2:projection>Projected UTM 3</ns2:projection><ns2:PPK used="true"><ns2:discussion>CORS station geometry allowed for Applanix SmartBase (ASB) processing on this project, with AB06 (False Pass) used as the the primary control station. However, ASB was only used on lines that experienced issues with PP-RTX. Lines using ASB are itemized in the Data Acquisition and Processing section of this report.</ns2:discussion><ns2:baseStations><ns2:CORSStations><ns2:stationID>False Pass</ns2:stationID><ns2:HVCRSiteID>AB06</ns2:HVCRSiteID></ns2:CORSStations></ns2:baseStations><ns2:comments/><ns2:methodsUsed>Smart Base</ns2:methodsUsed></ns2:PPK><ns2:PPP used="true"><ns2:discussion>The Trimble PP-RTX subscription-based correction service within POSPac was used for final positioning for the majority of lines. Results were good overall, usually at 0.10 m or better vertically.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum></ns1:horizontalControl><ns1:verticalControl><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:tideStations/><ns2:comments/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:VDATUM_or_constantSep used="true"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-P377-KR-18_NSPMVD_EPSG6332_NAD83-MLLW_Revised.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:comments/><ns2:methodsUsed>ERS via ERTDM</ns2:methodsUsed></ns2:VDATUM_or_constantSep></ns1:verticalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:additionalResults><ns1:shoreline><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work. The survey area does not intersect shoreline.</ns2:discussion></ns2:results></ns1:shoreline><ns1:newSurveyRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results></ns1:newSurveyRecommendation><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No abnormal seafloor and/or environmental conditions exist for this survey.</ns2:discussion></ns2:results></ns1:abnormalSeafloorEnviroCond><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results></ns1:submarineFeatures><ns1:constructionOrDredging><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:ATONS><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results></ns1:ATONS><ns1:insetRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results></ns1:insetRecommendation><ns1:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>During this survey the Alaska Marine Highway System (AMHS) ferry MV Tustumena was observed transiting the area. AMHS provides ferry service approximately every two weeks during the summer months between Homer, Kodiak, and Dutch Harbor as well as various ports between.</ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures></ns1:additionalResults><ns1:chartComparison><ns1:methods><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 the review were used.

The chart comparison was accomplished by overlaying the finalized BASE surfaces with shoal-biased soundings, and final feature file 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) were checked for updates affecting the area. No updates affecting the survey area issued subsequent to the date of the Hydrographic
Survey Project Instructions and before the end of the survey were found.</ns2:discussion><ns2:comments/></ns1:methods><ns1:channels><ns2:comments/><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></ns1:channels><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Only one potentially hazardous feature (14.241 m sounding at 54-31-18.906 N, 163-14-03.774 W) was found and was discussed previously in this report. Given the scale of the chart this potential hazard is adequately charted, although the chart should be updated with the actual position and depth.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Seven bottom samples locations were assigned that fell within the extents of this sheet. Samples were successfully obtained at all locations

Black gravel was the most common primary constituent returned in the samples. Black sand and white shells were also common constituents.

Two samples corresponded to the location of previously charted nature of the seafloor features:

1. Sample at 54-37-25.713 N, 163-10-30.486 W returning gravel (and shells) agrees well with the nearby charted sample which denotes gravel.
2. Sample at 54-34-13.909 N, 163-10-54.372 W returning gravel (and shells with sand) agrees well with the nearby charted sample which denotes sand and gravel.</ns2:discussion></ns2:results></ns1:bottomSamples><ns1:charts><ns2:ENC><ns2:images><ns2:caption>Soundings from this survey (red) shown on chart US3AK61M (black). Soundings in meters.</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/US3AK61M_Overlap.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Charted sounding (black) is similar in depth but about 370 m WNW of the actual sounding for the bottom feature here, which is the shoalest part of this project area.</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/US3AK61M_sounding.jpg</ns2:link></ns2:images><ns2:discussion>Agreement is poor overall, although there is good agreement in a few cases.

There appears to be a slight shift to the northwest for many charted soundings (and countours). In other words, moving the position of the charted soundings (and contours where applicable) to the southeast by 200 - 400 m would create a better match with survey data in many (but not all) cases.

Sounding discrepancies of particular note are itemized below.

The shoalest charted sounding inside this project area (13.7 m at 54-31-22.619 N, 163-14-23.393 W) appears to describe the seafloor shoaling found by this survey centered on 54-31-18.906 N, 163-14-03.774 W, where this survey found a least depth of 14.241 m. The least depths are therefore roughly equivalent but they are displaced horizontally by about 370 m, with the actual position to the ESE of the charted position.


</ns2:discussion><ns2:comments/><ns2:chart><ns2:preliminary>false</ns2:preliminary><ns2:edition>23</ns2:edition><ns2:name>US3AK61M</ns2:name><ns2:updateApplicationDate>2018-08-13</ns2:updateApplicationDate><ns2:issueDate>2018-08-13</ns2:issueDate><ns2:scale>300000</ns2:scale></ns2:chart></ns2:ENC><ns2:ENC><ns2:images><ns2:caption>Soundings from this survey (red) shown on chart US4AK5CM (black). Soundings in meters.</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/US4AK5CM_Overlap.jpg</ns2:link></ns2:images><ns2:discussion>Agreement is fair to good between this chart and the survey. Most charted soundings have survey soundings nearby that agree to within 1-2 meters, with greatest discrepancies on slopes and areas of rugged seafloor where it is likely the survey technology used to produce the charted soundings did not fully capture the least depths of the area. There is no apparent overall trend of shoaling or deepening. There are no sounding disagreements of particular note.</ns2:discussion><ns2:comments/><ns2:chart><ns2:preliminary>false</ns2:preliminary><ns2:edition>7</ns2:edition><ns2:name>US4AK5CM</ns2:name><ns2:updateApplicationDate>2018-07-06</ns2:updateApplicationDate><ns2:issueDate>2018-07-06</ns2:issueDate><ns2:scale>80660</ns2:scale></ns2:chart></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results></ns1:chartedFeatures></ns1:chartComparison></ns1:resultsAndRecommendations><ns1:dataAcquisitionAndProcessing><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:backscatter><ns1:equipmentAndVessels><ns1:comments/><ns1:equipment><ns1:comments/><ns1:majorSystem><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 26 plus</ns2:model><ns2:type>Tide Guage, Submerged</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>5700</ns2:model><ns2:type>Base Station</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne Oceanscience</ns2:manufacturer><ns2:model>Rapidcast</ns2:model><ns2:type>Sound Speed Deployment System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>RapidSV</ns2:model><ns2:type>Sound Speed 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>Applanix</ns2:manufacturer><ns2:model>POS MV 320 v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>Seabat T50</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:equipment><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:comments/><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 ASV Global. The ASV was operated in an unmanned but monitored mode, collecting multibeam data in close proximity to the Q105.</ns1:discussion><ns1:images><ns2:caption>Survey vessels used on this project - ASV-CW5 (foreground), Q105 (background)</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/Vessels.jpg</ns2:link></ns1:images><ns1:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:draft units="meters">0.5</ns2:draft><ns2:LOA units="meters">5.5</ns2:LOA></ns1:vessel><ns1:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:draft units="meters">1.8</ns2:draft><ns2:LOA units="meters">32</ns2:LOA></ns1:vessel></ns1:vessels></ns1:equipmentAndVessels><ns1:dataProcessing><ns1:additionalDataProcessing><ns2:comments><ns2:branchComment><ns2:comment>Note that Table 10 documents processing depth ranges, not surface depth ranges. In review, all single resolution gridded surfaces were replaced with a Variable Resolution surface created using the Ranges method. This surface matches the single resolution surfaces for minimum and maximum depths (14.24m to 117.36m)</ns2:comment></ns2:branchComment></ns2:comments></ns1:additionalDataProcessing><ns1:surfaces><ns1:comments/><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13114_MB_1m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13114_MB_2m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13114_MB_4m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">36</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13114_MB_8m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">72</ns2:min><ns2:max units="meters">160</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter></ns1:surface><ns1:discussion>The final depth information for this survey was submitted as CARIS BASE surfaces (CSAR format) which best represented the seafloor at the time of the 2018 survey. The surfaces were created from fully processed data with all final corrections applied.

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

Non-finalized versions of the CSAR surfaces are also included which do not have a depth cutoff applied. These do not have the &quot;_Final&quot; designation in the filename.

An S-57 (.000) file was submitted with the survey deliverables as well. The final feature file (FFF) contains meta-data and other data not readily represented by the final surfaces, including bottom samples and shoreline verification results, if applicable. Each object is encoded with mandatory S-57 attributes and NOAA Extended Attributes (V#5.7).

A georeferenced multibeam backscatter mosaic (Geotif format in NAD83 UTM Zone 3N, 1 m resolution) was also produced and is provided with the survey deliverables. Note that backscatter processing and mosaic generation was not a requirement of this survey and the mosaic is provided for interest only. The mosaic may have flaws or holidays which could be addressed through further processing. However, it is of sufficient quality to show the relative changes in seafloor type across the survey area.</ns1:discussion></ns1:surfaces><ns1:drSoftware><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><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: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:featureObjectCatalog>NOAA Profile V_5_7</ns1:featureObjectCatalog></ns1:drSoftware></ns1:dataProcessing><ns1:echoSoundingCorrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:corrections><ns2:comments><ns2:branchComment><ns2:comment>The hydrographer provided an explained in DR Section B.3 but inaccurately stated that real-time TPU was used in favor of post-processed TPU values. Just to clarify, the HIPS and SIPS processing software provides only two options in their compute TPU dialog box, for source of uncertainty, either 1) post-processed (real-time and dynamic) uncertainty based on vessel kinematics logged in the POS-MV or 2) a priori (static) uncertainty estimates from manufacturer's specifications contained within the HIPS Vessel File. The choice to use a priori uncertainty estimates almost certainly inflated the uncertainty estimates. This is brought up solely as a matter of clarification, and the inflated uncertainties involved do not affect the data's ability to meet and exceed gridded uncertainty specifications. </ns2:comment></ns2:branchComment></ns2:comments><ns2:results deviation="true"><ns2:discussion>* All ASV lines used real time attitude data (gyro, pitch, roll) as well as real-time TPU instead of the standard applciation of post-processed versions. This was due to roll alignment issues on some groups of lines when using the post-processed versions of the attitude data. Note that post-processed navigation and GPS height data was still applied per standard practice.

* Applanix SmartBase was used instead of PP-RTX for the post-processing method for the following sets of lines in order to improve small vertical offsets observed on overlapping data:

ASV vessel all lines on JD200 and line with prefix 2051 from JD196
Q105 vessel lines with prefix 404-412 (JD180), all lines on JD192 and JD193, line 0144 from JD165.

* Q105 line 0144 on JD165 had a gap in post-processed data because POS file logging was cutoff. Navigation and motion is therefore realtime; GPS height is post-processed but interp'd from known measured values across the gap. TPU was computed from vessel settings instead of real-time. The 2nd segment of this line also does not have delayed heave applied as a result. After the corrections, the line compares well within specifications to overlapping neighbors.




</ns2:discussion></ns2:results></ns1:corrections><ns1:calibrations><ns2:comments/><ns2:results deviation="false"><ns2:calibration xsi:nil="true"/><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:calibrations></ns1:echoSoundingCorrections><ns1:qualityControl><ns1:junctions><ns2:images><ns2:caption>Image showing junctions with this survey</ns2:caption><ns2:link>file:///M:/OPRP377KR18/Surveys/H13114/Office_Processing/Reports_office/SupportFiles/H13114%20Survey%20Junctions.jpg</ns2:link></ns2:images><ns2:discussion>This survey junctions with three contemporary surveys. All were accomplished as part of the same overall project and surveyed concurrently.

NOAA's &quot;Gridded Surface Comparison V18.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.</ns2:discussion><ns2:junction><ns2:discussion>Agreement is excellent. The mean difference between the two surveys in their overlapping area is 0.03 m, with a standard deviation of 0.22 m. Over 99.5% of grid cells compare to within the allowable TVU.</ns2:discussion><ns2:survey><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:year>2018</ns2:year><ns2:registryNumber>H13112</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:comments/></ns2:junction><ns2:junction><ns2:discussion>Agreement is excellent. The mean difference between the two surveys in their overlapping area is 0.01 m, with a standard deviation of 0.19 m. Over 99.5% of grid cells compare to within the allowable TVU.</ns2:discussion><ns2:survey><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:year>2018</ns2:year><ns2:registryNumber>H13113</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:comments/></ns2:junction><ns2:junction><ns2:discussion>Agreement is excellent. The mean difference between the two surveys in their overlapping area is 0.02 m, with a standard deviation of 0.19 m. Over 99.5% of grid cells compare to within the allowable TVU.</ns2:discussion><ns2:survey><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:year>2018</ns2:year><ns2:registryNumber>H13115</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:relativeLocation>SW</ns2:relativeLocation></ns2:survey><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl><ns1:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:title>Sound Speed Error</ns2:title><ns2:discussion>Mild to moderate sound speed error is evident periodically throughout the data set. This is observed as a general downward or upward cupping (&quot;frowning&quot; or &quot;smiling&quot;) of the seafloor profiles. The issue was addressed in the field through a relatively high cast frequency and tightening of line spacing. In processing filters were used to remove outer beam soundings most subject to the error, and areas showing excessive &quot;frowning&quot; or &quot;smiling&quot; received additional manual data editing to reject soundings that adversely affected the final surfaces. The effect on final surfaces is relatively minor, generally less than 0.30 m, and within specifications.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:comments/><ns1:discussion>Sound speed profiles or casts were acquired aboard the Q105 while underway with an Teledyne Oceanscience RapidCAST system, which utilized a Valeport RapidSV sound speed profiler. The interval between subsequent casts was 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 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 4 hours&quot; option within CARIS HIPS.</ns1:discussion><ns1:castFrequency>2 hours</ns1:castFrequency></ns1:soundSpeedMethods><ns1:uncertainty><ns2:discussion>Real-time (dynamic) error estimates were computed and loaded for the majority of the survey data. This replaced the static error estimates for attitude and navigation during final TPU computation. Exceptions, if they exist, are listed in Section B.3 of this report. Refer to the DAPR for more information on derivation of the values used for TPU estimates.

The BASE surfaces were finalized in CARIS HIPS so that the uncertainty value for each grid cell is the greater of either standard deviation or uncertainty. The uncertainty layer of each final surface was then examined for areas of uncertainty that exceeded allowable TVU for the depth (Order 1a for depths less than 100 m, and Order 2 for depths 100 m and deeper). Uncertainty for the surfaces ranges from 0.21 to 2.57 m.

Greater than 99.5% of grid cells have uncertainty values within allowable TVU. Highest uncertainties were found in areas of varying bottom topography such as slopes and near bottom features where high standard deviations are caused by the wide depth ranges of soundings contributing to each grid cell, outer edges of multibeam swathes without adjacent line overlap, and areas with unrejected noisy soundings. Despite elevated TPU values for these grid cells, the data is within specifications.</ns2:discussion><ns2:values><ns2:soundSpeedUncertainty><ns2:hullID>ASV-CW5</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface><ns2:measuredXBT xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Qualifier 105</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface><ns2:measuredXBT xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:tideUncertainty><ns2:zoning units="meters">0</ns2:zoning><ns2:measured units="meters">0.098</ns2:measured><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod></ns2:tideUncertainty></ns2:values><ns2:comments/></ns1:uncertainty><ns1:crosslines><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 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 usually collected in sets when both vessels were in simultaneous operation. These lines were often collected when transiting across the survey area to reach a different survey priority.

The crossline analysis was conducted using CARIS HIPS “Line QC Report” process. Each crossline was selected individually and run through the process, which calculated the depth difference between each accepted crossline sounding and a &quot;QC&quot; BASE (CUBE-type, 8 m resolution) surface’s depth layer created from the mainscheme data. QC surfaces were created with the same parameters used for 8 m surfaces as the final surfaces, with the important distinction that the QC surfaces 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. Note for simplicity IHO Order 1a was used for all comparisons even though the looser IHO Order 2 standard was allowable for depths greater than 100 m.

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(s) could be counted as a QC failure in this process.

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

1054-180-ASV-CW5-BC1XL -- 100.0% pass
0328-177-Q105-B1-XL -- 100.0% pass
0460-185-Q105-B1-XL -- 100.0% pass
1517-186-ASV-CW5-C1_XL4 -- 99.9% pass
0398-172-ASV-CW5-B2-C1_XL1 -- 99.9% pass
0397-172-ASV-CW5-B2_C1_XL1 -- 99.9% pass
0467-185-Q105-C2-XL -- 99.9% pass
0815-177-ASV-CW5-C2-1206-XL -- 99.9% pass
1072-180-ASV-CW5-C2-XL -- 99.9% pass
0816-177-ASV-CW5-C2-1206_XL -- 99.9% pass
0264-172-Q105-B2-C1-XL2 -- 99.8% pass
1384-185-ASV-CW5-C2-XL -- 99.8% pass
1390-185-ASV-CW5-C2-XL -- 99.8% pass
2121-200-ASV-CW5-C_XL1_ASV -- 99.8% pass
0469-186-Q105-C1_XL2 -- 99.8% pass
0478-186-Q105-C1-XL_3 -- 99.8% pass
0327-177-Q105-C1-XL -- 99.7% pass
1073-180-ASV-CW5-C2-XL -- 99.6% pass
0130-164-Q105-C2-XL-1 -- 99.6% pass
0418-180-Q105-C2-Q105-C2-XL -- 99.5% pass
2118-200-ASV-CW5-C3_XL1 -- 99.5% pass
0462-185-Q105-C2-XL -- 99.5% pass
0747-193-Q105-C-C_XL -- 99.5% pass
0874-200-Q105-C_XL1 -- 99.4% pass
0747-193-Q105-C-C_XL -- 99.4% pass
0481-186-Q105-C1-XL -- 99.4% pass
1055-180-ASV-CW5-BC1XL -- 99.4% pass
1505-ASV-CW5-C1_XL -- 99.3% pass
2007-192-ASV-CW5-C2-XL -- 99.2% pass
2120-200-ASV-CW5-C_XL1 -- 99.2% pass
0717-192-Q105-C2-XL -- 99.1% pass
0404-180-Q105-C2-XL -- 98.9% pass
0206-164-ASV-CW5-C2-XL-2 -- 98.9% pass
2119-200-ASV-CW5-C3_XL1 -- 98.8% pass
0873-200-Q105-C3_XL1 -- 97.9% pass

Results: Agreement between the mainscheme surface and crosslines soundings is excellent. At least 95% of crossline soundings compare to the mainscheme surface within IHO Order 1a. 

Refer to Separate II: Digital Data for the detailed Crossline QC Reports.</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:sonarQCChecks><ns2:comments/><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></ns1:sonarQCChecks><ns1:coverageEquipmentAndMethods><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:coverageEquipmentAndMethods><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:title>Q105 Roll Alignment</ns2:title><ns2:discussion>It became evident during operations that a roll bias was periodically present in data collected on the Q105 vessel. This was determined to correlate to deployment and retrieval of the hydraulic multibeam arm, which was not on the same physical mount as the motion sensor IMU on this vessel. Exact cause is unknown but small fluctuations in hydraulic pressure in the arm actuator are suspected. Effect on pitch and yaw, if any, was not discernible. The issue was addressed in processing by systematically examining lines exhibiting trouble and determining new roll alignment values--which was possible due to significant overlap with adjacent survey lines--and applying them via the HVF. There may be remnants of this error remaining periodically in the Q105 data set but the effect on final surfaces is minor and well within specifications. Additional discussion is available in the DAPR.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results></ns1:equipmentEffectiveness></ns1:qualityControl></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:additionalReports><ns2:reportDateSent>2018-08-28</ns2:reportDateSent><ns2:reportName>Marine Mammal Observers Training Logsheet and Observation Logs</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2018-11-07</ns2:reportDateSent><ns2:reportName>NCEI Sound Speed Data Submission</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2018-12-17</ns2:reportDateSent><ns2:reportName>Coast Pilot Review Report</ns2:reportName></ns1:additionalReports><ns1:statements><ns1:supervision>Field operations 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:additionalInfo xsi:nil="true"></ns1:additionalInfo><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the 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 the Descriptive Report.</ns1:adequacyOfSurvey><ns1:approval>This report, digital data, and all other accompanying records are approved. All records are respectfully submitted for final review and acceptance.</ns1:approval></ns1:statements><ns1:signingPersonnel><ns2:approverTitle>TerraSond Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2018-12-29</ns2:approvalDate><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>