<?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:dataAcquisitionAndProcessing><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:images><ns2:caption>Backscatter mosaic for H13419</ns2:caption><ns2:link>SupportFiles\Backscatter_mosaic.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Backscatter calibration values</ns2:caption><ns2:link>SupportFiles\backscatter_cal_values.jpg</ns2:link></ns2:images><ns2:discussion>Raw backscatter data were stored in the .all file for Kongsberg systems. All backscatter were processed to GSF files and a floating point mosaic was created by the field unit via Fledermaus FMGT 7.9.0 . See Figure 11 for a greyscale representation of the complete mosaic. A relative backscatter calibration was performed by the field unit via a backscatter calibration site in order to bring the survey systems on each of the launches into alignment. See Figure 12 for a table of the calibration values entered into the Processing Settings within FMGT. Approximate inter-calibration corrections for offsets between sonar systems were applied to the mosaic.</ns2:discussion></ns2:results></ns1:backscatter><ns1:dataProcessing><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:surfaces><ns1:surface><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13419_MB_VR_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:depthRange><ns2:min units="meters">0.8</ns2:min><ns2:max units="meters">139.2</ns2:max></ns2:depthRange><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13419_MB_VR_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:depthRange><ns2:min units="meters">0.8</ns2:min><ns2:max units="meters">139.2</ns2:max></ns2:depthRange><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter></ns1:surface><ns1:comments/><ns1:discussion>The NOAA CUBE parameters defined in the HSSD were used for the creation of all CUBE surfaces for H13419. The surfaces have been reviewed where noisy data, or &quot;fliers&quot; are incorporated into the gridded solutions causing the surface to be shoaler or deeper than the true sea floor. Where these spurious soundings cause the gridded surface to vary from the reliably measured seabed by greater than the maximum allowable Total Vertical Uncertainty at that depth, the noisy data have been rejected by the hydrographer and the surface recomputed.

Flier Finder, part of the QC Tools package within HydrOffice, was used to assist the search for spurious soundings following gross cleaning. Flier Finder was run iteratively until all remaining flagged fliers were deemed to be valid aspects of the surface.
</ns1:discussion></ns1:surfaces><ns1:drSoftware><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:featureObjectCatalog>NOAA Profile Version 2021</ns1:featureObjectCatalog><ns1:bathySoftware deviation="true"><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:name>HIPS and SIPS</ns1:name><ns1:version>11.3</ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>QPS</ns1:manufacturer><ns1:name>Fledermaus</ns1:name><ns1:version>7.9.0</ns1:version></ns1:imagerySoftware></ns1:drSoftware></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:equipmentAndVessels><ns1:comments/><ns1:equipment><ns1:comments/><ns1:majorSystem><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 2040</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 19plus V2</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</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 RESON</ns2:manufacturer><ns2:model>SVP 71</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>All launches utilize the Kongsberg EM 2040 MBES, a POS M/V v5 system for position and attitude, SVP 71 surface sound speed sensors, and Sea-Bird SBE 19plus v2 CTDs for conductivity, temperature, and depth casts.</ns1:discussion></ns1:equipment><ns1:discussion>Refer to the OPR-P358-FA-21 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><ns2:branchComment><ns2:comment>The following values HVFs for Vessels 2805 and 2808 differ from what is reported in the DAPR: 2805 static draft : -0.622m, 2805 static draft uncertainty: 0.010m, 2808 static draft: -0.631m, and 2808 static draft uncertainty: 0.030m.</ns2:comment></ns2:branchComment></ns1:comments><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:vessel><ns2:hullID>2805</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.6</ns2:LOA></ns1:vessel><ns1:vessel><ns2:hullID>2807</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.6</ns2:LOA></ns1:vessel><ns1:vessel><ns2:hullID>2808</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.6</ns2:LOA></ns1:vessel></ns1:vessels></ns1:equipmentAndVessels><ns1:qualityControl><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:soundSpeedMethods><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:castFrequency>Casts were conducted at a minimum of one every four hours during launch acquisition. Casts were conducted more frequently in areas where the influx of freshwater had an effect on the speed of sound in the water column and when there was a change in surface sound speed greater than two meters per second. All sound speed methods were used as detailed in the DAPR.</ns1:castFrequency></ns1:soundSpeedMethods><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:junctions><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:junctions><ns1:additionalQualityControl><ns2:issue><ns2:images><ns2:caption>Holiday in H13419 where coverage could not be obtained due to thick ice. </ns2:caption><ns2:link>SupportFiles\Holiday_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday in H13419 where the least depth of an offshore feature could not be obtained</ns2:caption><ns2:link>SupportFiles\Holiday_3.jpg</ns2:link></ns2:images><ns2:title>Holidays</ns2:title><ns2:discussion>H13419 data were reviewed in CARIS HIPS and SIPS for holidays in accordance with Section 5.2.2.3 of the HSSD. Two holidays which meet the definition described in the HSSD for complete coverage were identified via HydrOffice QC Tools Holiday Finder tool. This tool automatically scans the surface for holidays as defined in the HSSD and was run in conjunction with a visual inspection of the surface by the hydrographer.

Reasonable attempts were made to cover all gaps in coverage in icy areas. One holiday was left on the north side of Suprise Inlet where it was deemed unsafe to obtain complete coverage due to ice as seen in Figure 7. 

One holiday was left in the south side of Surprise Inlet on a rocky feature. Multibeam coverage could not be obtained, as the least depth of the feature was shoaler than the minimum safe depth for the launches and ice present in the area created additional navigational hazards.  Due to time constraints, the feature was not observed at a different tide and the least depth was not obtained.  The holiday can be seen in Figure 8.
</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:images><ns2:caption>H13419 allowable uncertainty statistics
</ns2:caption><ns2:link>SupportFiles\H13419_MB_VR_MLLW.QAv6.tvu_qc.png</ns2:link></ns2:images><ns2:title>NOAA Allowable Uncertainty</ns2:title><ns2:discussion>The surface was analyzed using the HydrOffice QC Tools Grid QA feature to determine compliance with specifications. Overall, over 99.5% of nodes within the surface meet NOAA Allowable Uncertainty specifications for H13419 (Figure 9).</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:images><ns2:caption>H13419 data density statistics</ns2:caption><ns2:link>SupportFiles\H13419_MB_VR_MLLW.QAv6.density.png</ns2:link></ns2:images><ns2:title>Density</ns2:title><ns2:discussion>The surface was analyzed using the HydrOffice QC Tools Grid QA feature to determine compliance with specifications. Density requirements for H13419 were achieved with at least 99.5% of surface nodes containing five or more soundings as required by HSSD Section 5.2.2.3 (Figure 10).
</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl><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: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>In addition to the usual a priori estimates of uncertainty via device models for vessel motion and ERTDM, real-time and post-processed uncertainty sources were also incorporated into the depth estimates of survey H13419. Real-time uncertainties were provided via EM 2040 MBES data and Applanix Delayed Heave RMS. Following post-processing of the real-time vessel motion, recomputed uncertainties of vessel roll, pitch, gyro and navigation were applied in CARIS HIPS and SIPS via a Smoothed Best Estimate of Trajectory (SBET) RMS file generated in Applanix POSPac.</ns2:discussion><ns2:values><ns2:soundSpeedUncertainty><ns2:hullID>2805</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.5</ns2:surface><ns2:measuredXBT xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2807</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.5</ns2:surface><ns2:measuredXBT xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2808</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.5</ns2:surface><ns2:measuredXBT xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:tideUncertainty><ns2:zoning units="meters">0.13</ns2:zoning><ns2:measured xsi:nil="true"/><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod></ns2:tideUncertainty></ns2:values><ns2:comments/></ns1:uncertainty><ns1:crosslines><ns2:topic><ns2:images><ns2:caption>Overview of H13419 crosslines</ns2:caption><ns2:link>SupportFiles\XL_Overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H13419 crossline and mainscheme difference statistics</ns2:caption><ns2:link>SupportFiles\H13419_Crossline_Comparison.png</ns2:link></ns2:images><ns2:discussion>Crosslines were collected, processed and compared in accordance with Section 5.2.4.2 of the HSSD. To evaluate crosslines, a surface generated via data strictly from mainscheme lines and a surface generated via data strictly from crosslines were created. From these two surfaces, a difference surface (mainscheme - crosslines = difference surface) was generated (Figure 5). Statistics show the mean difference between the depths derived from mainscheme data and crossline data was 0.05 meters (with mainscheme being shoaler) and 95% of nodes falling within 0.69 meters (Figure 6). For the respective depths, the difference surface was compared to the allowable NOAA uncertainty standards. In total, 99% of the depth differences between H13419 mainscheme and crossline data were within allowable NOAA uncertainties. 
</ns2:discussion></ns2:topic><ns2:comments/></ns1:crosslines></ns1:qualityControl></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1: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, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1: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:statements><ns1:signingPersonnel><ns2:approverTitle>Commanding Officer</ns2:approverTitle><ns2:approvalDate>2021-08-16</ns2:approvalDate><ns2:approverName>CAPT John Lomnicky</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2021-08-16</ns2:approvalDate><ns2:approverName>LT Shelley Devereaux</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approvalDate>2021-08-16</ns2:approvalDate><ns2:approverName>Simon Swart</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approvalDate>2021-08-16</ns2:approvalDate><ns2:approverName>Colin Schmidt</ns2:approverName></ns1:signingPersonnel></ns1:approvalSheet><ns1:verticalAndHorizontalControl><ns1:horizontalControl><ns2:WAAS used="true"><ns2:discussion>During real-time acquisition, all platforms received correctors from the Wide Area Augmentation System (WAAS) for increased accuracies similar to USCG DGPS stations. WAAS and SBETs were the sole methods of positioning for H13419 as no DGPS stations were available for real-time horizontal control.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:DGPS used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:comments/><ns2:projection>Projected UTM 6</ns2:projection><ns2:PPK used="true"><ns2:discussion>Vessel kinematic data were post-processed using Applanix POSPac processing software and RTX positioning methods described in the DAPR. Smoothed Best Estimate of Trajectory (SBET) and associated error (RMS) data were applied to all MBES data in CARIS HIPS and SIPS.</ns2:discussion><ns2:baseStations/><ns2:comments/><ns2:methodsUsed>RTX</ns2:methodsUsed></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum></ns1:horizontalControl><ns1:verticalControl><ns2:tideStations/><ns2:VDATUM_or_constantSep used="true"><ns2:discussion>ERS methods were used as the final means of reducing H13419 to MLLW for submission.</ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-P358-FA-21_PWS_ERTDM21-1_NAD83-MLLW</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via ERTDM</ns2:methodsUsed><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:comments/><ns2:standard_or_ERZT used="false" xsi:nil="true"/></ns1:verticalControl><ns1:discussion> Per Section 5.2.2.1.3 of the 2020 Field Procedures Manual no Horizontal and Vertical Control Report has been generated for H13419.</ns1:discussion><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:additionalResults><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: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: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:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures><ns1:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>3D rendering of Surprise Inlet in sheet 13419 with a 300% exaggeration. Three terminal moraines are visible.</ns2:caption><ns2:link>SupportFiles\moraine.jpg</ns2:link></ns2:images><ns2:discussion>Three terminal moraines were observed in surprise inlet and can be seen in the 3D rendering of the surface in Figure 15.</ns2:discussion></ns2:results></ns1:abnormalSeafloorEnviroCond><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:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>H13419 bottom sample locations</ns2:caption><ns2:link>SupportFiles\bottom_sample_locations.jpg</ns2:link></ns2:images><ns2:discussion>3 bottom samples were acquired in accordance with the Project Instructions for survey H13419.  All bottom samples were entered in the H13419 Final Feature File. See Figure 14 for a graphical overview of sample locations. </ns2:discussion></ns2:results></ns1:bottomSamples><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: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:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>Areas where shoaling in Harrian Fiord is farther offshore than reported.</ns2:caption><ns2:link>SupportFiles\Glacier_Shoaling.jpg</ns2:link></ns2:images><ns2:discussion>The 10 fathom contour at the toe of Harriman Glacier is farther offshore than depicted on the chart.  On the north side of the fiord near the glacier, the NALL was reached where a 53 fathom sounding was previously charted. Similarly, the NALL was reached near a 55 fathom sounding and a 39 fathom sounding on the south side of the fiord (Figure 13). Land now extends out to apporximately where the 10 fathom contour was previously charted. The NALL was defined by 3.5 meter depth or a quarter mile safety buffer from the glacier in all areas. The extent of this shoal was not surveyed directly in front of the glacier due to the quarter mile safety buffer</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:charts><ns2:ENC><ns2:updateApplicationDate>2021-03-29</ns2:updateApplicationDate><ns2:edition>5</ns2:edition><ns2:issueDate>2018-07-12</ns2:issueDate><ns2:scale>50000</ns2:scale><ns2:name>US5AK27M</ns2:name></ns2:ENC><ns2:comments/></ns1:charts><ns1:methods><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:chartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion> The shoal reported on the chart near the terminus of Surprise Glacier was observed and is narrower than reported.  Deeper water was present between the shoal and the toe of the glacier.  The NALL was reached due to ice and a minimum depth of the shoal was not obtained.  Large icebergs were observed on the shoal.</ns2:discussion></ns2:results></ns1:chartedFeatures><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:metadata><ns1:registryMetadata><ns2:sublocality>Harriman Fiord</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>2</ns2:sheetID><ns2:registryNumber>H13419</ns2:registryNumber></ns1:registryMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:surveyMetadata><ns2:datesOfSurvey><ns2:start>2021-03-23</ns2:start><ns2:end>2021-03-24</ns2:end></ns2:datesOfSurvey><ns2:projectType>Navigable Area</ns2:projectType><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:year>2021</ns2:year><ns2:chiefOfParty>CAPT John Lomnicky</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 6N, 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>2021-02-24</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>Prince William Sound, AK</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Fairweather (S220)</ns2:fieldUnit><ns2:number>OPR-P358-FA-21</ns2:number><ns2:name>Prince William Sound, AK</ns2:name></ns1:projectMetadata></ns1:metadata><ns1:areaSurveyed><ns1:surveyLimits><ns2:comments/><ns2:results deviation="true"><ns2:images><ns2:caption>Areas where the NALL was defined by the prescence of ice</ns2:caption><ns2:link>SupportFiles\NALL_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area near Surprise Glacier where the NALL was defined by prescence of ice</ns2:caption><ns2:link>SupportFiles\NALL_2.jpg</ns2:link></ns2:images><ns2:discussion>Data were acquired to the survey limits in accordance with the requirements in the Project Instructions and the 2020 NOS Hydrographic Surveys Specifications and Deliverables (HSSD). Coverage acquired in H13419 is shown in Figure 1. In all areas where the 3.5 meter depth contour or the sheet limits were not met, the Navigable Area Limit Line (NALL) was defined as the inshore limit of bathymetry due to the risks of maneuvering the survey vessels within one quarter mile of active glaciers or in areas of thick ice. Examples of these areas are seen in Figures 2 and 3.</ns2:discussion></ns2:results></ns1:surveyLimits><ns1:surveyPurpose><ns2:topic><ns2:discussion>Prince William Sound has 3,800 miles of coastline, supporting the fishing, oil, and tourism industries. This project will provide modern bathymetric data to the Prince William Sound region, primarily focusing on areas left unsurveyed due to significant glacial retreat. The area has experienced increased tour boat and cruise ship traffic in recent years. In 2019, the Port of Valdez estimated almost 20,000 passengers aboard cruise ships with the numbers expected to increase.

As the area is becoming more popular, there is greater vessel traffic near the unmapped glacier faces. Most of these glacier areas have not been surveyed since the 1990s with sedimentation potentially changing the submerged glacial moraines. Conducting a modern bathymetric survey in this area will address Seabed 2030 data gaps, identify hazards and changes to the seafloor, provide critical data for updating National Ocean Service (NOS) nautical charting products and improve maritime safety. 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:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>Data acquired in H13419 meet multibeam echo sounder (MBES) coverage requirements for complete coverage, as required by the HSSD. This includes crosslines (see Section B.2.1), NOAA allowable uncertainty (see Section B.2.10), and density requirements (see Section B.2.11).
</ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption> H13419 survey coverage overlaid onto Chart 16711</ns2:caption><ns2:link>SupportFiles\Survey_Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:comments/><ns2:results deviation="true"><ns2:discussion>The entirety of H13419 was acquired with complete coverage, meeting the requirements listed above and in the HSSD. See Figure 4 for an overview of coverage.</ns2:discussion></ns2:results></ns1:surveyCoverage><ns1:areaDescription><ns2:images><ns2:caption>H13419 sheet limits (in blue) overlaid onto Chart 16711</ns2:caption><ns2:link>SupportFiles\Survey_limits.jpg</ns2:link></ns2:images><ns2:discussion>The survey area is located in Harriman Fiord, AK</ns2:discussion><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">60.9714837222</ns2:latitude><ns2:longitude hemisphere="W">148.298780528</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">61.0648643056</ns2:latitude><ns2:longitude hemisphere="W">148.442847722</ns2:longitude></ns2:northWest></ns2:limits><ns2:comments/></ns1:areaDescription><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>2805</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>0.87</ns2:XL_MBES_SBES><ns2:MS_MBES>28.55</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>2807</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>2.85</ns2:XL_MBES_SBES><ns2:MS_MBES>20.25</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>2808</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>2.30</ns2:XL_MBES_SBES><ns2:MS_MBES>34.90</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>6.02</ns2:XL_MBES_SBES><ns2:percentXLLNM>7.19</ns2:percentXLLNM><ns2:MS_MBES>83.70</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 xsi:nil="true"></ns2:discussion><ns2:surveyDates>2021-03-23</ns2:surveyDates><ns2:surveyDates>2021-03-24</ns2:surveyDates><ns2:comments/><ns2:totalSurveyStats><ns2:bottomSamples>3</ns2:bottomSamples><ns2:diveOps>0</ns2:diveOps><ns2:SNM>4.13</ns2:SNM><ns2:DP>0</ns2:DP><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints></ns2:totalSurveyStats></ns1:surveyStatistics></ns1:areaSurveyed></ns1:descriptiveReport>