<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:dataAcquisitionAndProcessing><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw Backscatter data were logged as .7k files for Teledyne RESON 7125 data. Kongsberg EM710 stores the backscatter data in the .all file. The data have been sent to the Pacific Hydrographic Branch for processing. One line per vessel per day of acquisition was processed by the field unit for quality control.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:qualityControl><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:discussion>H12972 data were reviewed in CARIS HIPS and SIPS for holidays in accordance with Section 5.2.2.3 of the HSSD. Eleven holidays which meet the 3 by 3 node definition were identified via Pydro QC Tools Holiday Finder tool. This tool automatically scans finalized surfaces for holidays as defined in the HSSD and was run in conjunction with a visual inspection of all surfaces by the Hydrographer. Three holidays were in shoal and/or rocky areas that were deemed unsafe to navigate, or the hydrographer was not able to reach due to heavy seas (Figure 17). Two of the holidays is a result of incomplete coverage (Figure 18). Six holidays are from acoustic shadowing from a rock in a downward sloping area in close proximity to shore, as seen in Figure 19. This shadow is formed due to a rapid drop in the seafloor in conjunction with poor geometry from the sonar head. These areas were investigated in CARIS Subset Editor to verify that the least depths were found (Figure 20). 

Although numerous apparent holidays were flagged by Holiday Finder, all were examined and many were determined to be from areas where an adjoining finalized surfaces covered the gap (e.g., a holiday in the 2 meter finalized surface was covered by the 1 meter finalized surface due to the area being shoaler than the depth range for the 1 meter surface) as shown in Figure 21. </ns2:discussion><ns2:images><ns2:caption>Holidays unable to be addressed due to weather and/or unsafe conditions.</ns2:caption><ns2:link>SupportFiles\H12972_Hazardous_Holidays.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example of holiday due to incomplete coverage.</ns2:caption><ns2:link>SupportFiles\missed_holiday_2808_DN305.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example of holiday due to acoustic shadowing.</ns2:caption><ns2:link>SupportFiles\H12972_Steap_Holiday_1m.png</ns2:link></ns2:images><ns2:images><ns2:caption>Acoustic shadow holiday viewed in CARIS HIPS and SIPS subset editor.</ns2:caption><ns2:link>SupportFiles\H12972_1m_Holiday_Subsest.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example of an apparent holiday in the 2 meter finalized surface which is covered by the 1 meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12972_Apparant_Holiday2m.png</ns2:link></ns2:images><ns2:comments/><ns2:title>Holidays</ns2:title></ns2:issue><ns2:issue><ns2:discussion>To verify that all data meets the accuracy specifications as stated in HSSD Section 5.1.3, a child layer titled “NOAA_Allowable_1” was created for each of the 1 meter, 2 meter, 4 meter, and 8 meter (72-100m) and &quot;NOAA_Allowable_2&quot; for the 8 meter (100-208m), and 16 meter finalized surfaces using the equations stated in Section C. 2.1 of the DAPR. These surfaces were then analyzed using the Pydro QC Tools  Grid QA feature to determine what percentage of each surface meets specifications. Figure 22 shows an overview of the NOAA Allowable Uncertainty layers for all surfaces. Figure 23 shows the corresponding statistics for each individual surface. Overall, 97.21% of nodes with all surfaces meet or exceed NOAA Allowable Uncertainty specifications for H12972. For individual graphs per surface of density requirements, see the Standards and Compliance Review located in Appendix II.</ns2:discussion><ns2:images><ns2:caption>H12972 NOAA Allowable Uncertainty overview.</ns2:caption><ns2:link>SupportFiles\H12972_NOAAness_overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12972 NOAA Allowable Uncertainty statistics.</ns2:caption><ns2:link>SupportFiles\H12972_NOAAness.png</ns2:link></ns2:images><ns2:comments/><ns2:title>NOAA Allowable Uncertainty</ns2:title></ns2:issue><ns2:issue><ns2:discussion>Finalized surfaces were analyzed using the Pydro QC Tools Grid QA feature and the results are shown in Figure 25. Density requirements for H12972 were achieved with at least 98.35% of finalized surface nodes containing five or more soundings as required by HSSD Section 5.2.2.3. The few nodes that did not meet density requirements are due to sparse data in the outer beams, especially near steep slopes and rocky areas where acoustic shadowing occurred, and at the edges of the survey limits as shown in Figure 24. For individual graphs (per surface) of density requirements, see the Standards and Compliance Review located in Appendix II.
</ns2:discussion><ns2:images><ns2:caption>H12972 density overview.</ns2:caption><ns2:link>SupportFiles\H12972_Density_overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12972 density statistics.</ns2:caption><ns2:link>SupportFiles\H12972_density.png</ns2:link></ns2:images><ns2:comments/><ns2:title>Density</ns2:title></ns2:issue></ns1:additionalQualityControl><ns1:junctions><ns2:discussion>H12972 junctions with two adjacent surveys from this project, H12971 and H12973, as shown in Figure 8. Data overlap between H12972 and each adjacent survey was achieved. These areas of overlap between surveys were reviewed with CARIS HIPS and SIPS through surface differencing (at equal resolutions) to assess surface agreement. The junctions with H12972 are within the NOAA allowable uncertainty in their areas of overlap. For all junctions with H12972, a negative difference indicates H12972 was shoaler, and a positive difference indicates H12972 was deeper.
</ns2:discussion><ns2:images><ns2:caption>Overview of H12972 surveys.</ns2:caption><ns2:link>SupportFiles\H12972_H12971_H12973_Junctions_Overview.png</ns2:link></ns2:images><ns2:comments/><ns2:junction><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the 16 meter combined surface from H12972 and the 16 meter combined surface from H12971. The statistical analysis of the difference surface shows a mean of 0.15 meters with 95% of all nodes having a maximum deviation of +/- 3.54 meters, as seen in Figure 10. A detailed graphical overview can be seen in Figure 9. In addition, a comparison surface was created between the difference surface and the NOAA allowable uncertainty (See Figure 11). It was found that 98.58% of nodes are within NOAA allowable uncertainty (Figure 12). The largest differences are located on the eastern and western extremes, as well as in the middle of the junction in relatively rocky areas, as seen in Figure 11.</ns2:discussion><ns2:images><ns2:caption>Difference surface between H12972 (blue) and junctioning survey H12971 (pink).</ns2:caption><ns2:link>SupportFiles\H12972_H12971_16m_Difference.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12972 and H12971 (16 meter surface).</ns2:caption><ns2:link>SupportFiles\H12972_H12971_Junction_Statistics.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface compliance with regard to NOAA allowable uncertainty between H12972 (blue) and junctioning survey H12971 (pink).</ns2:caption><ns2:link>SupportFiles\H12972_H12971_16m_NOAAness.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12972 and H12971 showing percentage of nodes meeting NOAA allowable uncertainty.</ns2:caption><ns2:link>SupportFiles\H12971_H12972_NOAAness_statistics.png</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>N</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit><ns2:scale>20000</ns2:scale><ns2:registryNumber>H12971</ns2:registryNumber><ns2:year>2016</ns2:year></ns2:survey></ns2:junction><ns2:junction><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the 16 meter base surface from H12972 and the 16 meter base surface from H12973. The statistical analysis of the difference surface shows a mean of 0.31 meters with 95% of all nodes having a maximum deviation of +/- 4.45 meters, as seen in Figure 14. A detailed graphical overview can be seen in Figure 13. In addition, a comparison surface was created between the difference surface and the NOAA allowable uncertainty (See Figure 15). It was found that 99.34% of nodes are within NOAA allowable uncertainty (Figure 16). The largest differences are located on the eastern and western side of the junction in relatively rocky areas, as seen in Figure 15.</ns2:discussion><ns2:images><ns2:caption>Difference surface between H12972 (steel blue) and junctioning survey H12973 (brown).</ns2:caption><ns2:link>SupportFiles\H12972_H12973_16m_Difference.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12972 and H12973 (16 meter surface).</ns2:caption><ns2:link>SupportFiles\H12972_H12973_Junction_Statistics.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface compliance with regard to NOAA allowable uncertainty between H12972 (blue) and junctioning survey H12973 (brown).</ns2:caption><ns2:link>SupportFiles\H12972_H12973_16m_NOAAness.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12972 and H12973 showing percentage of nodes meeting NOAA allowable uncertainty.</ns2:caption><ns2:link>SupportFiles\H12972_H12973_NOAAness.png</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>S</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit><ns2:scale>40000</ns2:scale><ns2:registryNumber>H12973</ns2:registryNumber><ns2:year>2016</ns2:year></ns2:survey></ns2:junction></ns1:junctions><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:uncertainty><ns2:discussion>In addition to the usual a priori estimates of uncertainty provided via device models for vessel motion, discrete zoning tides, ERZT, and Poor Man’s VDatum (PMVD), real-time and post-processed uncertainty sources were also incorporated into the depth estimates of survey H12972. Real-time uncertainties were provided via EM710 and Teledyne RESON 7125 MBES data, Applanix Delayed Heave RMS, and TCARI tides. 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:comments/><ns2:values><ns2:tideUncertainty><ns2:zoning units="meters">0</ns2:zoning><ns2:measured units="meters">0</ns2:measured><ns2:tideMethod>TCARI</ns2:tideMethod></ns2:tideUncertainty><ns2:tideUncertainty><ns2:zoning units="meters">0.1</ns2:zoning><ns2:measured units="meters">0</ns2:measured><ns2:tideMethod>ERS via PMVD</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S220</ns2:hullID><ns2:surface units="meters/second">0.5</ns2:surface><ns2:measuredCTD units="meters/second">N/A</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>280x (all launches)</ns2:hullID><ns2:surface units="meters/second">0.5</ns2:surface><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values></ns1:uncertainty><ns1:crosslines><ns2:discussion>Crosslines were collected, processed and compared in accordance with Section 5.2.4.3 of the HSSD. To evaluate crosslines, a 16 meter CUBE surface using strictly mainscheme lines, and a 16 meter CUBE surface using strictly crosslines were created. From these two surfaces, a difference surface (mainscheme - crosslines = difference surface) was generated at a 16 meter resolution (Figure 4), and is submitted in the Separates II Digital Data folder. Statistics show the mean difference between the depths derived from mainscheme and crosslines was -0.09 meters (with mainscheme being shoaler) and 95% of nodes falling within +/- 3.66 meters (Figure 5). For the respective depths, the difference surface was compared to the allowable NOAA uncertainty standards (Figure 6). In total, 98.73% of the depth differences between H12972 mainscheme and crossline data were within allowable NOAA uncertainties (Figure 7). </ns2:discussion><ns2:images><ns2:caption>Overview of H12972 crosslines.</ns2:caption><ns2:link>SupportFiles\H12972_XL_Diff_Image.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>H12972 crossline and mainscheme difference statistics.</ns2:caption><ns2:link>SupportFiles\H12972_Crosslines_Diff_16m_Stats.png</ns2:link></ns2:images><ns2:images><ns2:caption>Depth differences between H12972 mainscheme and crossline data as compared to NOAA allowable uncertainty standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\H12972_XL_NOAAness_image.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Crossline surface statistics showing percentage of nodes meeting NOAA allowable uncertainty.</ns2:caption><ns2:link>SupportFiles\NOAAness_XL.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:soundSpeedMethods><ns1:comments/><ns1:castFrequency>Casts were conducted at a minimum of one every 4 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. MVP casts on S220 were conducted at an average interval of 17 minutes as recommended by Pydro’s CastTime software, which determines optimum cast frequency based on the observed sound speed variations from previous casts. All sound speed methods were used as detailed in the DAPR.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:soundSpeedMethods><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings></ns1:qualityControl><ns1:equipmentAndVessels><ns1:equipment><ns1:comments/><ns1:discussion>The equipment was installed on the survey platforms as follows: S220 utilizes the Kongsberg EM710 MBES, SVP 70 surface sound speed sensors, and Rolls Royce MVP for conductivity, temperature, and depth (CTD) casts. All launches utilize Teledyne RESON 7125 SV1 MBES, SVP71 surface sound speed sensors, and Sea-Bird Electronics 19plus CTD casts. Additionally, Launch 2806 is equipped with the Velodyne VLP-16 Lidar for shoreline feature acquisition. </ns1:discussion><ns1:majorSystem><ns2:model>7125 SV1</ns2:model><ns2:type>MBES</ns2:type><ns2:manufacturer>Teledyne RESON</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>EM710</ns2:model><ns2:type>MBES</ns2:type><ns2:manufacturer>Kongsberg</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>19Plus</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>MVP 200</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:manufacturer>Rolls Royce</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>SVP 70</ns2:model><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>Teledyne RESON</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>SVP 71</ns2:model><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>Teledyne RESON</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>POS/MV V4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type><ns2:manufacturer>Applanix </ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>VLP-16</ns2:model><ns2:type>Lidar System</ns2:type><ns2:manufacturer>Velodyne</ns2:manufacturer></ns1:majorSystem></ns1:equipment><ns1:vessels><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:vessel><ns2:hullID>2805</ns2:hullID><ns2:LOA units="meters">8.64</ns2:LOA><ns2:draft units="meters">1.12</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2806</ns2:hullID><ns2:LOA units="meters">8.64</ns2:LOA><ns2:draft units="meters">1.12</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2808</ns2:hullID><ns2:LOA units="meters">8.64</ns2:LOA><ns2:draft units="meters">1.12</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>S220</ns2:hullID><ns2:LOA units="meters">70.4</ns2:LOA><ns2:draft units="meters">8.64</ns2:draft></ns1:vessel></ns1:vessels><ns1:discussion>Refer to the OPR-O393-FA-16 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:bathySoftware deviation="true"><ns1:version>9.1.7</ns1:version><ns1:name>HIPS and SIPS</ns1:name><ns1:manufacturer>Teledyne CARIS</ns1:manufacturer></ns1:bathySoftware><ns1:comments/><ns1:featureObjectCatalog>NOAA Extended Attribute Files V_5_4</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:imagerySoftware deviation="true"><ns1:version>5.4</ns1:version><ns1:name>Fledermaus FMGT</ns1:name><ns1:manufacturer>QPS</ns1:manufacturer></ns1:imagerySoftware></ns1:drSoftware><ns1:surfaces><ns1:comments/><ns1:discussion>In order to prevent visual data gaps between the finalized surfaces, a waiver to extend the 1, 2, 4, 8, and 16 meter surface depths and not submit a 32 meter surface was granted by the Hydrographic Surveys Division Operations Branch, and is located in Appendix II. The modified surface depth ranges are shown in Table 11. All finalized surface depth ranges were extended deeper by 6 times the surface resolution. To determine how much to expand the depth range, the largest gap in coverage that could be found was measured in CARIS HIPS and SIPS subset editor. The distance of the gap was divided by the resolution of the surface that would cover the gap to determine how many multiples of that resolution it would take to cover that gap. This number was then doubled to ensure that all gaps would be covered resulting in the extension of the surfaces by 6 times their resolution. 

Additionally, a waiver to extend the 1 meter surface depth shallower to include data collected at high tide above Mean Lower Low Water, i.e. negative numbers, was granted by HSD OPs and is located in Appendix II. The approved 1 meter finalized surface range was -3m to 26m. All surfaces still meet the density and NOAA uncertainty requirements for their expanded ranges as defined by the HSSD.

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 be shoaler or deeper than 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 v3, part of the QC Tools package within Pydro, was used to assist the search for spurious soundings following gross cleaning. This allowed Flier Finder to accurately and quickly identify gross fliers, but Flier Finder incorrectly flagged dynamic aspects of the seafloor such as steep drop offs and rocky areas as fliers resulting in hundreds of false positives. At this point, the hydrographer ceased using the tool and returned to manual cleaning for these dynamic regions of seafloor.</ns1:discussion><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_1m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_1m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">26</ns2:max><ns2:min units="meters">-3</ns2:min></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_2m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:resolution units="meters">2</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_2m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">52</ns2:max><ns2:min units="meters">18</ns2:min></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:resolution units="meters">2</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_4m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:resolution units="meters">4</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_4m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">104</ns2:max><ns2:min units="meters">36</ns2:min></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:resolution units="meters">4</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_8m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:resolution units="meters">8</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_8m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">208</ns2:max><ns2:min units="meters">72</ns2:min></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:resolution units="meters">8</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_16m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_16m</ns2:surfaceParameter><ns2:resolution units="meters">16</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:surfaceName>H12972_MB_16m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">640</ns2:max><ns2:min units="meters">144</ns2:min></ns2:depthRange><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceParameter>NOAA_16m</ns2:surfaceParameter><ns2:resolution units="meters">16</ns2:resolution></ns1:surface></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/><ns2:issue><ns2:discussion>Data acquisition and processing notes are included in the acquisition and processing logs, and additional processing such as final tide and sound speed application are noted in the H12972 Data Log spreadsheet. All data logs are submitted digitally in the Separates I folder. 
</ns2:discussion><ns2:comments/><ns2:title>Data Logs</ns2:title></ns2:issue><ns2:issue><ns2:discussion>The TCARI grid provided by HSD OPS was misaligned with the shoreline due to an error in georeferencing the grid (see Figure 26). This caused some areas not covered by the grid to use extrapolated tidal data, however this issue did not prevent the use of ERZT and was resolved with the application of an updated PMVD model. See Appendix II for a copy of this correspondence. </ns2:discussion><ns2:images><ns2:caption>Misalignment of the TCARI grid observed in Project OPR-O393-FA-16. The most significant differences occurred in H12971, as shown.</ns2:caption><ns2:link>SupportFiles\Re_ O393 Behm Canal PMVD.bmp</ns2:link></ns2:images><ns2:comments/><ns2:title>Misalignment of the TCARI Grid</ns2:title></ns2:issue></ns1:additionalDataProcessing></ns1:dataProcessing><ns1:echoSoundingCorrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations></ns1:echoSoundingCorrections></ns1:dataAcquisitionAndProcessing><ns1:areaSurveyed><ns1:surveyStatistics><ns2:surveyDates>2016-10-18</ns2:surveyDates><ns2:surveyDates>2016-10-24</ns2:surveyDates><ns2:surveyDates>2016-10-26</ns2:surveyDates><ns2:surveyDates>2016-10-27</ns2:surveyDates><ns2:surveyDates>2016-10-29</ns2:surveyDates><ns2:surveyDates>2016-10-31</ns2:surveyDates><ns2:surveyDates>2016-11-01</ns2:surveyDates><ns2:surveyDates>2016-11-02</ns2:surveyDates><ns2:totalSurveyStats><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>3</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>20.15</ns2:SNM><ns2:bottomSamples>0</ns2:bottomSamples></ns2:totalSurveyStats><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S220</ns2:hullID><ns2:statistics><ns2:XL_MBES_SBES>6.73</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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:MS_SBES>0</ns2:MS_SBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>22.48</ns2:MS_MBES></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2805</ns2:hullID><ns2:statistics><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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:MS_SBES>0</ns2:MS_SBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>65.50</ns2:MS_MBES></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2806</ns2:hullID><ns2:statistics><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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:MS_SBES>0</ns2:MS_SBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>43.43</ns2:MS_MBES></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2808</ns2:hullID><ns2:statistics><ns2:XL_MBES_SBES>6.56</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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:MS_SBES>0</ns2:MS_SBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>49.63</ns2:MS_MBES></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:XL_MBES_SBES>13.28</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>7.34</ns2:percentXLLNM><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>181.03</ns2:MS_MBES></ns2:totalLNM></ns2:LNM></ns1:surveyStatistics><ns1:areaDescription><ns2:discussion>The survey area is located in Behm Canal within the sub locality of Neets Bay.</ns2:discussion><ns2:comments/><ns2:images><ns2:caption> H12972 sheet limits (in blue) overlaid onto Chart 17422.</ns2:caption><ns2:link>SupportFiles\H12972_Coverage.png</ns2:link></ns2:images><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">55.8403472222</ns2:latitude><ns2:longitude hemisphere="W">131.826002778</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">55.7842888889</ns2:latitude><ns2:longitude hemisphere="W">131.498183333</ns2:longitude></ns2:southEast></ns2:limits></ns1:areaDescription><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>The entirety of H12972 was acquired with complete coverage, meeting the requirements listed above and in the HSSD. See Figure 3 for an overview of coverage. </ns2:discussion></ns2:results><ns2:comments/><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete coverage MBES with backscatter</ns2:requiredCoverage></ns2:coverageRequirement></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12972 survey coverage (16m surface) overlaid onto Chart 17422.</ns2:caption><ns2:link>SupportFiles\H12972_Coverage_Data.png</ns2:link></ns1:coverageGraphic><ns1:surveyQuality><ns2:discussion>Data acquired in H12972 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). Additional compliance statistics can be found in the Standards and Compliance Review located in Appendix II of this report.</ns2:discussion><ns2:comments/><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy></ns1:surveyQuality><ns1:surveyPurpose><ns2:discussion>This project will support safe navigation through the acquisition and processing of hydrographic survey data for updating National Ocean Service (NOS) nautical charts and by the identification and dissemination of dangers to navigation as identified during the course of survey operations. Survey H12972 addresses 18 SNM of navigationally significant waters in accordance with the National Hydrographic Survey Priorities, 2012 Edition.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired to the survey limits, as shown in Figure 1, in accordance with the requirements in the Project Instructions and the March 2016 NOS Hydrographic Surveys Specifications and Deliverables (HSSD).  In all areas where the 4 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 vessel in close proximity to the steep and rocky shoreline. An example of such an area is shown in Figure 2.</ns2:discussion><ns2:images><ns2:caption>H12972 Example of an area not acquired to the 4m Depth Curve due to inshore limit of safe navigation.</ns2:caption><ns2:link>SupportFiles\H12972_Inshore_Sheet_Limits.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits></ns1:areaSurveyed><ns1:metadata><ns1:assignment>NOAA</ns1:assignment><ns1:registryMetadata><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:scale>40000</ns2:scale><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:sheetID>2</ns2:sheetID><ns2:sublocality>Neets Bay</ns2:sublocality><ns2:registryNumber>H12972</ns2:registryNumber></ns1:registryMetadata><ns1:projectMetadata><ns2:number>OPR-O393-FA-16</ns2:number><ns2:name>Southeast Alaska, Behm Canal</ns2:name><ns2:generalLocality>Behm Canal</ns2:generalLocality><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit></ns1:projectMetadata><ns1:surveyMetadata><ns2:horizontalCoordinateSystem zone="9N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:projectType>Navigable Area</ns2:projectType><ns2:titlesheetRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed
with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold red italic text. The
processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered
preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products. All pertinent
records for this survey, including the DR, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://
www.ncei.noaa.gov/.</ns2:branchRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:chiefOfParty>CDR Mark Van Waes, NOAA</ns2:chiefOfParty><ns2:PIDate>2016-10-14</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2016-10-18</ns2:start><ns2:end>2016-11-02</ns2:end></ns2:datesOfSurvey><ns2:year>2016</ns2:year><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone></ns1:surveyMetadata></ns1:metadata><ns1:resultsAndRecommendations><ns1:additionalResults><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to Navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>No significant features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>H12972 survey limits extended to the NALL (see Section A.1) and all features within these limits were addressed and attributed in the H12972 Final Feature File. All features inshore of the NALL were attributed in the Final Feature File with the description of “Not Addressed” and remarks of “Retain as charted, not investigated due to being inshore of NALL” as per HSSD Section 7.3.1. Annotations, information, and diagrams collected on DP forms and boat sheets during field operations are scanned and included in the Separates I Detached Positions folder.
</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline></ns1:additionalResults><ns1:chartComparison><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:charts><ns2:rasterChart><ns2:discussion>The charted soundings and contours of Chart 17422 are identical to those found on ENC US4AK43M. As such, all discussions regarding comparisons between surveyed soundings and charted depths are covered under the ENC US4AK43M discussion below. </ns2:discussion><ns2:chart><ns2:number>17422</ns2:number><ns2:LNMDate>2017-02-07</ns2:LNMDate><ns2:edition>10</ns2:edition><ns2:kapp>2730</ns2:kapp><ns2:NMDate>2017-02-11</ns2:NMDate><ns2:scale>79334</ns2:scale><ns2:editionDate>2015-03</ns2:editionDate></ns2:chart><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:discussion>Soundings from H12972 are in a general disagreement with charted depths on ENC US4AK43M in deeper parts of the survey area and on some nearshore slopes (Figure 27), but agree with charted depths on ENC US4AK43M within 3-5 fathoms in the shallower regions of H12972. 

To more accurately visualize trends within these differences, a 16 meter TIN surface was interpolated from the ENC sounding layer. This surface was then differenced with a corresponding 16 meter surface from H12972 and visualized in Figure 28. In this difference surface red colors indicate H12972 was shoaler than the ENC US4AK43M, green colors indicate agreement, and blue colors indicate H12972 was deeper than ENC US4AK43M. Statistical analysis of the difference surface shows a mean of 25.04 m, with H12972 being deeper and 95% of all nodes having a maximum deviation of +/- 59.19 meters, as shown in Figure 29. Most of the differences indicate that H12972 is deeper than US4AK43M, particularly in the deeper areas of the survey where the charted depths are widely spaced and surveyed soundings are more dense. 

Contours from H12972 are in a general agreement with charted contours on ENC US4AK43M as shown in Figure 30. The largest differences are seen near the shoreline, where the 10 fathom contour is inshore of the previously charted contour (Figure 31). To facilitate electronic navigation, the hydrographer recommends the addition of contours at 20 and 30 fathoms (Figure 32). </ns2:discussion><ns2:chart><ns2:edition>4</ns2:edition><ns2:updateApplicationDate>2017-01-10</ns2:updateApplicationDate><ns2:name>US4AK43M</ns2:name><ns2:scale>79334</ns2:scale><ns2:issueDate>2017-01-10</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:images><ns2:caption>Nearshore sounding discrepancy between H12972/US4AK43M.</ns2:caption><ns2:link>SupportFiles\nearshore sounding discprenacies.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface between H12972 and interpolated TIN surface from US4AK43M.</ns2:caption><ns2:link>SupportFiles\H12972_16m_Combinded-Tin_Difference_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12972 and interpolated TIN surface from US4AK43M.</ns2:caption><ns2:link>SupportFiles\H12972_16m_Combined-Tin_Difference_Stats.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of H12972 contour comparison with US4AK43M.</ns2:caption><ns2:link>SupportFiles\H12972_Contour_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>Inshore contour discrepancy H12972.</ns2:caption><ns2:link>SupportFiles\H12972_Inshore_Contours.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12972 proposed additional contours.</ns2:caption><ns2:link>SupportFiles\Contour_proposal.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:discussion>An uncharted shoal was observed during acquisition, prompting one Danger to Navigation Report to be submitted on 11/23/2016 (Figure 34). The DTON lies adjacent to a 15 fathom sounding and is outside of the charted 10 fathom contour. Small fishing vessels were observed in the area and appear to use the nearby islands for shelter during inclement weather.</ns2:discussion><ns2:numberSubmitted>1</ns2:numberSubmitted><ns2:images><ns2:caption>Overview of DTON found in the northwestern head of Neats Bay.</ns2:caption><ns2:link>SupportFiles\DTON.png</ns2:link></ns2:images><ns2:report><ns2:dateSubmitted>2016-11-23</ns2:dateSubmitted><ns2:title>H12972 Danger to Navigation Report</ns2:title></ns2:report></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The DTON has been applied to the chart. The DTON report was not submitted by the field and is not attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:bottomSamples><ns2:results investigated="None Exist"><ns2:discussion>No bottom samples were required for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey other than those addressed in the Dangers to Navigation section above.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> A reported 6 fathom sounding from 2007, south of Clam Island was disproved by MBES, as seen in Figure 33. The observed depth at the reported 6 fathom sounding was 44 fathoms. </ns2:discussion><ns2:images><ns2:caption>Reported 6 fm sounding was disproven by MBES.</ns2:caption><ns2:link>SupportFiles\Clam_island.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>Survey H12972 has 23 new features that are addressed in the H12972 Final Feature File. Of these features, there are 9 Buoys (3 submitted as Detached Positions), 6 Piles, 2 Dolphins, 5 new positions of Underwater/Awash Rocks, and 1 new Underwater Rock which was submitted as a DTON, see Section D.1.6.  </ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:methods><ns2:discussion>A comparison was performed between survey H12972 and Chart 17422 as well as ENC US4AK43M using CARIS HIPS and SIPS sounding and contour layers derived from the 16 meter combined surface. The contours and soundings were overlaid on the charts to assess differences between the surveyed soundings and charted depths. ENCs were compared to a 16 meter combined grid by extracting all soundings from the chart and creating an interpolated TIN surface which could be differenced with the combined surface from H12972.

All data from H12972 should supersede charted data. In general, surveyed soundings disagree with the charted depths. A full discussion of the disagreements follows below.
</ns2:discussion><ns2:comments/></ns1:methods><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels></ns1:chartComparison></ns1:resultsAndRecommendations><ns1:verticalAndHorizontalControl><ns1:horizontalControl><ns2:comments/><ns2:PPK used="true"><ns2:discussion>Vessel kinematic data were post-processed using Applanix POSPac processing software and Single Base 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. 

For further details regarding the processing and quality control checks performed, see the H12972 POSPAC Processing Logs spreadsheet located in the Separates folder. See also the OPR-393-FA-16 Horizontal and Vertical Control Report (HVCR), submitted under separate cover.</ns2:discussion><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:comments/><ns2:baseStations><ns2:userInstalledStations><ns2:stationID>ANDY</ns2:stationID><ns2:HVCRSiteID>9677</ns2:HVCRSiteID></ns2:userInstalledStations></ns2:baseStations></ns2:PPK><ns2:horizontalDatum>World Geodetic System 1984 (WGS84)</ns2:horizontalDatum><ns2:DGPS used="true"><ns2:discussion>Differential correctors from the US Coast Guard beacon at Annette Island, AK was used in real-time for acquisition when not otherwise noted in the acquisition logs, and were the sole method of positioning of detached positions (DP).</ns2:discussion><ns2:USCGStations><ns2:name>Annette Island, AK - 323 kHz (100 BPS)</ns2:name></ns2:USCGStations><ns2:comments/></ns2:DGPS><ns2:projection>UTM Zone 9 North</ns2:projection><ns2:RTK used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:verticalControl><ns2:VDATUM_or_constantSep used="true"><ns2:discussion>ERS methods were used as the final means of reducing H12972 to MLLW for submission. Data were initially reduced via traditional tidal means until an ERZT separation model could be calculated. This empirically derived model was then checked for consistency and compared to the Poor Man's VDatum (PMVD) separation model provided with the Project Instructions. The PMVD separation model was then vertically shifted such that the average difference between these two separation models is zero. This vertical shift de-biases the PMVD separation model, correcting for local offsets that cannot be effectively modeled by the PMVD. In areas where the PMVD model did not have sufficient coverage, such as near shore areas, the ERZT separation model was appended to the PMVD model creating the composite ERZT/PMVD separation model listed above and used to reduce H12972 to MLLW. For further information see the ERS Capability Memo, submitted under separate cover.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The ERS Capability Memo is attached</ns2:comment></ns2:branchComment></ns2:comments><ns2:methodsUsed>ERS via Poor Mans VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>O393FA2016_PMVD_EPSG6338_WGS84-MLLW_Composite.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile></ns2:VDATUM_or_constantSep><ns2:tideStations><ns2:NWLONGauges><ns2:stationID>9450460</ns2:stationID><ns2:stationName>Ketchikan</ns2:stationName></ns2:NWLONGauges></ns2:tideStations><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:comments/><ns2:standard_or_ERZT used="true"><ns2:discussion>Initial reduction of acquired data to MLLW was accomplished via traditional tidal means using the Tidal Constituent And Residual Interpolation (TCARI) grid provided by Hydrographic Surveys Division - Operations Branch (HSD-OPS). Following the successful application of SBETs and computation of an Ellipsoidally Referenced Zone Tide (ERZT) separation model, ERS methods were used for reducing data to MLLW. 

After final tides were received, the final TCARI grids were applied to the data and used for reducing features to MLLW. The TCARI grid provided by HSD OPS was misaligned with the shoreline due to an error in georeferencing the grid. See section B.5.4 for more information. 

</ns2:discussion><ns2:finalTides><ns2:dateSubmitted>2016-11-03</ns2:dateSubmitted><ns2:dateReceived>2016-11-15</ns2:dateReceived></ns2:finalTides><ns2:correctorFiles><ns2:tideCorrectors><ns2:status>Final</ns2:status><ns2:fileName>0393FA2016_Verified.tc</ns2:fileName></ns2:tideCorrectors><ns2:waterLevels><ns2:status>Final Approved</ns2:status><ns2:fileName>9450460.tid</ns2:fileName></ns2:waterLevels></ns2:correctorFiles><ns2:comments><ns2:branchComment><ns2:comment>The Tide Note is attached.</ns2:comment></ns2:branchComment></ns2:comments><ns2:methodsUsed>TCARI</ns2:methodsUsed></ns2:standard_or_ERZT></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>2017-03-01</ns2:reportDateSent><ns2:reportName>Chief Survey Technician</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2017-04-17</ns2:reportDateSent><ns2:reportName>Horizontal and Vertical Control Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2017-04-17</ns2:reportDateSent><ns2:reportName>Coast Pilot Report</ns2:reportName></ns1:additionalReports><ns1:signingPersonnel><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approverName>CDR Mark Van Waes, NOAA</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approverName>LT Bart Buesseler, NOAA</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approverName>HCST Douglas Bravo</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approverName>HAST Roger Stillick</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Assistant Sheet Manager</ns2:approverTitle><ns2:approverName>HAST Rebekah Gossett</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Assistant Sheet Manager</ns2:approverTitle><ns2:approverName>HST Hannah Marshburn</ns2:approverName><ns2:approvalDate>2017-04-21</ns2:approvalDate></ns1:signingPersonnel><ns1:statements><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Field Procedures Manual, Project Instructions, and all HSD Technical Directives, except as noted in this Descriptive Report. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required unless otherwise noted herein.</ns1:adequacyOfSurvey></ns1:statements></ns1:approvalSheet></ns1:descriptiveReport>