<?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:resultsAndRecommendations><ns1:additionalResults><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:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Two bottom samples locations were assigned in the PRF. Samples were successfully retrieved at both locations.

Sticky gray mud were the primary constituents in both samples. Samples were photographed but not retained. Refer to the FFF submitted with the survey deliverables for results.</ns2:discussion></ns2:results></ns1:bottomSamples><ns1:ENCScaleRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new ENC scales are recommended for this area.</ns2:discussion></ns2:results></ns1:ENCScaleRecommendation><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:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Ice scour features caused by wind-driven pack ice dragging on the seafloor are relatively common in the area. The linear features are ephemeral and not navigationally significant, usually resulting in no more than 1 m of vertical relief from the surrounding seafloor.</ns2:discussion></ns2:results></ns1:abnormalSeafloorEnviroCond><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: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:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><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:submarineFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results></ns1:submarineFeatures></ns1:additionalResults><ns1:chartComparison><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: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: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 27/2020 through 38/2020 were checked. 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:topic><ns2:images><ns2:caption>Soundings from this survey (blue) overlaid on soundings from the  charts (black). Units are in meters.</ns2:caption><ns2:link>SupportFiles\Sounding_Comparison.jpg</ns2:link></ns2:images><ns2:discussion>There are few charted soundings overlapping the project area, but general agreement is excellent, with all agreeing to 0.5 m or better. No shoaling or deepening trends are apparent.</ns2:discussion></ns2:topic><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:updateApplicationDate>2018-07-18</ns2:updateApplicationDate><ns2:edition>9</ns2:edition><ns2:issueDate>2019-09-30</ns2:issueDate><ns2:scale>300000</ns2:scale><ns2:name>US3AK83M</ns2:name></ns2:ENC><ns2:ENC><ns2:updateApplicationDate>2018-09-18</ns2:updateApplicationDate><ns2:edition>11</ns2:edition><ns2:issueDate>2020-01-07</ns2:issueDate><ns2:scale>400000</ns2:scale><ns2:name>US3AK80M</ns2:name></ns2:ENC><ns2:comments/></ns1:charts><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey. No DTONs were submitted.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><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:chartComparison></ns1:resultsAndRecommendations><ns1:verticalAndHorizontalControl><ns1:horizontalControl><ns2:WAAS used="true"><ns2:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control during data acquisition. All real-time positions were replaced in final processing with post-processed kinematic (PPK) positions generated in Applanix POSPac software, as described previously.</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>Post-processing of all navigation data was done in Applanix POSPac MMS (v8.4) software. 

Initial processing was done in the field using Trimble PP-RTX methodology.

Following completion of operations and availability of precise ephemeris data, navigation data was reprocessed in POSPac using Applanix SmartBase (ASB) methodology to achieve better overall results than the initial PP-RTX method, and applied to all survey data. ASB processing was possible because the project area was fully encompassed by a network formed by three or more CORS base stations. ASB processing was further facilitated by the presence of the nearby stations at St. Michael (AT01) and Unalakleet (AB17).

ASB processing replaced all initial PP-RTX positions. Therefore, all final data is corrected with ASB. Exceptions, if any, were noted previously in this report.</ns2:discussion><ns2:discussion> Note: The area is within UTM zone 4N, but 3N was used for projection instead. This was done to simplify operations by keeping all survey sheets under OPR-R385-KR-20, which laid mostly in 3N, in a common UTM zone.</ns2:discussion><ns2:baseStations><ns2:CORSStations><ns2:stationID>AT01</ns2:stationID><ns2:HVCRSiteID>StMichael AK2018</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>BET1</ns2:stationID><ns2:HVCRSiteID>Bethel WAAS</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AC31</ns2:stationID><ns2:HVCRSiteID>BaldHead Ak2006</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AC07</ns2:stationID><ns2:HVCRSiteID>Buckland AK2007</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AB17</ns2:stationID><ns2:HVCRSiteID>Unalakleet AK2008</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AB09</ns2:stationID><ns2:HVCRSiteID>Razorback AK2007</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AB04</ns2:stationID><ns2:HVCRSiteID>Mekoryuk AK2008</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AB04</ns2:stationID><ns2:HVCRSiteID>Savoonga AK2007</ns2:HVCRSiteID></ns2:CORSStations></ns2:baseStations><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:methodsUsed>RTX</ns2:methodsUsed><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:verticalControl><ns2:tideStations/><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:comments/><ns2:VDATUM_or_constantSep used="true"><ns2:discussion>All soundings were reduced to MLLW using the ERTDM NAD83 to MLLW separation model grid file provided by NOAA using ERS methodology.

Tide gauges and ERTDM validation sites (GPS buoys) were installed as part of the overall project but were not used for reduction of soundings. Gauge data and validation results have been separately provided to NOAA CO-OPS. Reports (with accompanying data packages) that have been submitted directly to CO-OPS are itemized in Section E of this report.

Discrete tide zones were generated using project gauge data but were not used for sounding reduction. Zones were used for an ERZT comparison to the provided ERTDM grid, with the two methods having an overall agreement of 0.02 m with a standard deviation of 0.12 m. Zones are provided in the Water Levels directory. Additional detail is available with the project HVCR.</ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-R385-KR-20_ERTDM_NAD83-MLLW_04162020.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via ERTDM</ns2:methodsUsed><ns2:comments/></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:verticalAndHorizontalControl><ns1:approvalSheet><ns1:additionalReports><ns2:reportDateSent>2020-07-29</ns2:reportDateSent><ns2:reportName>9468151 Stebbins Install Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-07-31</ns2:reportDateSent><ns2:reportName>9999771 Norton Sound Buoy Install Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-07-31</ns2:reportDateSent><ns2:reportName>9999770 St Michael Install Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-09-10</ns2:reportDateSent><ns2:reportName>9469031 Koyuk Install Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-14</ns2:reportDateSent><ns2:reportName>9999776 Eastern Norton Sound Buoy Install Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-17</ns2:reportDateSent><ns2:reportName>9999771 Western Norton Sound Buoy Removal Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-18</ns2:reportDateSent><ns2:reportName>Final Summary Report for OPR-R385-KR-20 Norton Sound</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-20</ns2:reportDateSent><ns2:reportName>Survey Outlines for OPR-R385-KR-20</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-21</ns2:reportDateSent><ns2:reportName>9468151 Stebbins Removal Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-22</ns2:reportDateSent><ns2:reportName>9999776 Eastern Norton Sound Buoy Removal Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-28</ns2:reportDateSent><ns2:reportName>9469031 Koyuk Removal Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-10-30</ns2:reportDateSent><ns2:reportName>9999770 St Michael GNSS-R Analysis Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-11-09</ns2:reportDateSent><ns2:reportName>NCEI Sound Speed Profile Data Submission</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-11-30</ns2:reportDateSent><ns2:reportName>MMO Training and Observation Logs</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2020-12-04</ns2:reportDateSent><ns2:reportName>Coast Pilot Review Report for OPR-R385-KR-20</ns2:reportName></ns1:additionalReports><ns1:signingPersonnel><ns2:approverTitle>Lead Hydrographer</ns2:approverTitle><ns2:approvalDate>2021-01-12</ns2:approvalDate><ns2:approverName>Thomas Morino</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2021-01-12</ns2:approvalDate><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName></ns1:signingPersonnel><ns1:statements><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><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 2019 NOS Hydrographic Surveys Specifications and Deliverables, Hydrographic Survey Project Instructions and Statement of Work. 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, if any, noted in the Descriptive Report.</ns1:adequacyOfSurvey><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:statements></ns1:approvalSheet><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:qualityControl><ns1:additionalQualityControl><ns2:issue><ns2:title>GPS Vertical Busts</ns2:title><ns2:discussion>Although vertical agreement is generally very good, vertical busts attributable to GPS positioning error between crosslines or overlapping mainscheme are apparent sporadically in the data set. These are normally less than 0.20 m of vertical separation. Any that approached or exceeded IHO Order 1a were investigated and addressed in processing. All crosslines 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:junctions><ns2:images><ns2:caption>Graphic showing survey Junctions.</ns2:caption><ns2:link>SupportFiles\H13374_Survey_Junctions.jpg</ns2:link></ns2:images><ns2:discussion>This survey did not junction other contemporary surveys.</ns2:discussion><ns2:comments/></ns1:junctions><ns1:equipmentEffectiveness><ns2:comments/><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></ns1:equipmentEffectiveness><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:crosslines><ns2:topic><ns2:discussion>Crossline LNM totaled 10.2% of mainscheme.

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 collected in sets whenever both vessels were in simultaneous operation. The collection of crosslines in sets while spreading sets out across the survey area for good distribution led to incidental collection of additional crossline LNM beyond the required 8% of mainscheme.

Crosslines were often 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.

3871-ASV-CW5-254-E1_XL06 -- 100.0% pass
3873-ASV-CW5-254-E1_XL04 -- 100.0% pass
0855-Q105-254-E1_XL02 -- 100.0% pass
0856-Q105-254-E1_XL03 -- 100.0% pass
0858-Q105-254-E1_XL05 -- 100.0% pass
3869-ASV-CW5-254-E1_XL01 -- 99.9% pass

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

Refer to Separate II: Digital Data for the detailed Crossline QC reports.</ns2:discussion></ns2:topic><ns2:comments/></ns1:crosslines><ns1:soundSpeedMethods><ns1:comments/><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 SWIFT sound speed profiler. The ASV was not equipped with a 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 2 hours) within CARIS HIPS.</ns1:discussion></ns1:soundSpeedMethods><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:uncertainty><ns2:discussion>The uncertainty layer of the final surface was examined in CARIS HIPS, as well as analyzed in Pydro QC Tools V3.2.13 Grid QA v6.

Uncertainty of the final grid cells range from 0.289 to 0.515 m. 100% of grid cells have TVU falling within the allowable range by depth. Largest values were observed to be in areas of highly variable seafloor where many soundings of different depths contribute to the value of the relatively large ( 4 m ) grid cell, resulting in a higher standard deviation for the grid cell. All final grid cells are within specifications.

 </ns2:discussion><ns2:values><ns2:soundSpeedUncertainty><ns2:hullID>Qualifier 105</ns2:hullID><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">1</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.135</ns2:measured><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod></ns2:tideUncertainty></ns2:values><ns2:comments/></ns1:uncertainty><ns1:factorsAffectingSoundings><ns2:comments/><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></ns1:factorsAffectingSoundings></ns1:qualityControl><ns1:equipmentAndVessels><ns1:equipment><ns1:comments/><ns1:discussion>The survey vessels were outfit for MBES data collection with similar survey equipment. Both vessels utilized Reson Seabat T-50 MBES systems, except the Q105 was configured with a dual-head setup while the ASV-CW5 used a single-head system. Both vessels used Applanix POSMVs for attitude and position measurements (Oceanmaster on the Q105, Wavemaster II on the ASV). Sound speed profiles were collected using Valeport rapidProSV and SWIFT sensors (deployed using a Teledyne Oceanscience RapidCast system) from the Q105 only.</ns1:discussion><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>SeaBat T50-R</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>SeaBat T50-R</ns2:model><ns2:type>MBES Backscatter</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>SWiFT SVP</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem></ns1:equipment><ns1:vessels><ns1:images><ns2:caption>ASV-CW5 (foreground), and Qualifier 105 (background).</ns2:caption><ns2:link>SupportFiles\Vessels.jpg</ns2:link></ns1:images><ns1:comments/><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: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: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 tide buoys, conduct sound speed casts, conduct feature investigations via skiff/UAS, and deploy/recover the ASV-CW5 vessel.

The ASV-CW5 (ASV) is a 5.5 m aluminum-hull Autonomous Surface Vessel (ASV), C-Worker 5 model, 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:vessels><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:comments/></ns1:equipmentAndVessels><ns1:dataProcessing><ns1:drSoftware><ns1:comments/><ns1:featureObjectCatalog>NOAA Extended Attribute Files V2020.3</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13374_MB_4m_MLLW_Final</ns2:surfaceName><ns2:purpose>MBES Set Line Spacing</ns2:purpose><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:resolution units="meters">4</ns2:resolution><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:surfaceName>H13374_MBAB_1m_400kHz_1of1</ns2:surfaceName><ns2:purpose>MBES Set Line Spacing</ns2:purpose><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter></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 2020 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 (V2020.3).

A georeferenced multibeam backscatter mosaic (Geotif format in NAD83 UTM Zone 3N, 1 m resolution) was also produced and provided with the survey deliverables. Note that backscatter processing and mosaic generation was not a requirement and the mosaic is provided as-is. 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:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing><ns1:echoSoundingCorrections><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:corrections><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results></ns1:corrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections></ns1:dataAcquisitionAndProcessing><ns1:areaSurveyed><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Image showing overview of survey coverage.</ns2:caption><ns2:link>SupportFiles\H13374_Survey_Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><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:surveyPurpose><ns2:topic><ns2:discussion>The area serves as the approach to the community of Unalakleet. In addition, the Project Instructions describe the purpose of the project as follows:

This project will provide contemporary data to update National Ocean Service (NOS) nautical charting products and services and increase maritime safety and commerce in the region. The Hydrographic Health Model and Automatic Identification Systems (AIS) traffic patterns identify this area as a hotspot where vessels are transiting in close proximity to the seafloor. This area was also identified as a high priority survey area by external stakeholders who identified the area extending from east of St. Michael Island to southwest of Egg Island as an area of refuge used by vessels transiting the Bering Sea. In addition, Stephens Pass between St. Michael and Stuart Islands was also identified as a travel lane for local shallow draft fishing traffic.

The survey area includes the remote coastal communities of Stebbins (Yup'ik name: Tapraq) and St. Michael, both located on Saint Michael Island. These villages rely on coastal shipping as a primary source of income, supplies, and fuel. This survey will improve the safety of the maritime traffic and services available to these communities by improving the quality of existing bathymetric data in the area, which currently predates the 1890s. Tide gauges will also be installed to provide tide data in an area currently underserved with tide observations. This will help improve tide predictions and fulfill further objectives of the Alaska Water Level Watch program. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:discussion></ns2:topic><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:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:statistics><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>7.8</ns2:XL_MBES_SBES><ns2:MS_MBES>53.2</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:statistics><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>8.2</ns2:XL_MBES_SBES><ns2:MS_MBES>103.5</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:XL_MBES_SBES>16</ns2:XL_MBES_SBES><ns2:percentXLLNM>10.2</ns2:percentXLLNM><ns2:MS_MBES>156.7</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:totalLNM></ns2:LNM><ns2:discussion>This survey was one of six completed under project OPR-R385-KR-20, with project-wide on-site hydrographic operations running from July 5 through September 17, 2020. Dates listed are for this survey only.</ns2:discussion><ns2:surveyDates>2020-09-09</ns2:surveyDates><ns2:surveyDates>2020-09-10</ns2:surveyDates><ns2:comments/><ns2:totalSurveyStats><ns2:bottomSamples>2</ns2:bottomSamples><ns2:diveOps>0</ns2:diveOps><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:SNM>25.7</ns2:SNM></ns2:totalSurveyStats></ns1:surveyStatistics><ns1:areaDescription><ns2:images><ns2:caption>Image showing overview of survey extents.</ns2:caption><ns2:link>SupportFiles\H13374_Survey_Extents.jpg</ns2:link></ns2:images><ns2:discussion>The survey area is located in Norton Sound, Alaska, approximately 100 nautical miles southeast of Nome. The area is off the road system and relatively remote. The small communities of the region are accessible only by air or sea.

Navigation through the area is limited to the summer and fall seasons due to the presence of sea ice for the majority of the year. The reliable ice free season is normally June through October, with ice likely to be encountered in May and November. Navigation is normally not possible for most vessels from December through April.

The closest communities to the survey area are Stebbins (pop. 571 in 2018), St. Michael (pop. 415 in 2018), and Unalkaleet (pop. 697 in 2018). Nome (pop. 3,866 in 2018) is the hub community for the region, with daily flights to Anchorage (weather permitting).

Transient traffic consists mostly of barges that bring supplies to the nearby communities. Local vessel traffic is mostly skiffs engaged in subsistence activities or travel between communities.

The area is relatively shallow (14 m on the west end to 10.2 m on the east end) and has a gradual slope towards shore. The seafloor of the area is largely featureless but has occasional linear ice scours. 

Bathymetric data collection was carried out in September of 2020 under project OPR-R385-KR-20, with final processing and reporting carried out from October 2020 through January 2021. Work was completed concurrently with five other sheets in SE Norton Sound, and done in accordance with the Hydrographic Survey Project Instructions (April 2020) and the NOS Hydrographic Surveys Specifications and Deliverables (HSSD), March 2019 edition.</ns2:discussion><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">63.8546275</ns2:latitude><ns2:longitude hemisphere="W">160.964452222</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">63.9323958333</ns2:latitude><ns2:longitude hemisphere="W">161.326843889</ns2:longitude></ns2:northWest></ns2:limits><ns2:comments/></ns1:areaDescription><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete 8840 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>All waters in sheets 4 - 7</ns2:waterDepth><ns2:requiredCoverage>320 m Set Line Spacing (Reference HSSD Section 5.2.2.4 Option A). Run lines perpendicular to shore. All significant shoals or features found in waters less than 20 m deep shall be developed to complete coverage standards. The requirement to verify or disprove all charted depths falling between sounding lines and shallower than adjacent surveyed soundings is waived.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:comments/><ns2:results deviation="true"><ns2:discussion>Coverage requirements were met. The following notes are provided for additional clarification.

Approximately 9,242 LNM were acquired project-wide, exceeding the requirement by 402 LNM. The excess of about 4% was collected to compensate for inefficiencies incidental to the execution of data collection such as crossline mileage that exceeded requirements, data acquired on run-ins or run-outs, and excess overlap, if any. LNM quantities do not include transit or calibration data, or mileage that does not meet HSSD specifications.

Splits on charted soundings were not required. No significant shoals were found requiring development to Complete MBES standards.</ns2:discussion></ns2:results></ns1:surveyCoverage></ns1:areaSurveyed><ns1:metadata><ns1:assignment>Contractor</ns1:assignment><ns1:registryMetadata><ns2:sublocality>Approach to Unalakleet</ns2:sublocality><ns2:registryInstructions>na</ns2:registryInstructions><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:sheetID>5</ns2:sheetID><ns2:registryNumber>H13374</ns2:registryNumber></ns1:registryMetadata><ns1:surveyMetadata><ns2:datesOfSurvey><ns2:start>2020-09-09</ns2:start><ns2:end>2020-09-10</ns2:end></ns2:datesOfSurvey><ns2:projectType>Navigable Area</ns2:projectType><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:year>2020</ns2:year><ns2:chiefOfParty>Thomas Morino</ns2:chiefOfParty><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><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone><ns2:PIDate>2020-04-14</ns2:PIDate><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes></ns1:surveyMetadata><ns1:projectMetadata><ns2:generalLocality>Norton Sound</ns2:generalLocality><ns2:fieldUnit>Terrasond</ns2:fieldUnit><ns2:name>Norton Sound, AK</ns2:name><ns2:number>OPR-R385-KR-20</ns2:number></ns1:projectMetadata></ns1:metadata></ns1:descriptiveReport>