<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2014/02/DescriptiveReport" xmlns:ns2="http://Pydro.com/2014/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-Q191-KR-13</ns2:number><ns2:name>Krenitzin Islands, Alaska</ns2:name><ns2:generalLocality>Krenitzin Islands</ns2:generalLocality><ns2:fieldUnit>Fugro Pelagos, Inc.</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12547</ns2:registryNumber><ns2:sheetID>5</ns2:sheetID><ns2:registryInstructions>The Hydrographic Sheet should be accompanied by this form, filled in as completely as possible, when the sheet is forwarded to the Office.</ns2:registryInstructions><ns2:sublocality>Vicinity of Battery Point</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2013</ns2:year><ns2:chiefOfParty>Dean Moyles</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2013-05-15</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-07-03</ns2:start><ns2:end>2013-07-27</ns2:end></ns2:datesOfSurvey><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:horizontalCoordinateSystem zone="3N">UTM</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><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. Revisions and notes in red were generated during office processing. The processing branch concurs with all information and recommendations in the DR unless otherwise noted. Page numbering may be interrupted or non-sequential. All pertinent records for this survey, including the Descriptive Report, are archived at the National Geophysical Data Center (NGDC) and can be retrieved via http://www.ngdc.noaa.gov/.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>H12547 is located in the Vicinity of Battery Point.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">54.10778</ns2:latitude><ns2:longitude hemisphere="E">165.78833</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">53.97861</ns2:latitude><ns2:longitude hemisphere="E">166.02</ns2:longitude></ns2:southEast></ns2:limits><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><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><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of this work is to provide NOAA with modern and accurate hydrographic survey data for the area  in the Vicinity of Battery Point.  The survey covered 23.37 square nautical miles of critical survey area as designated in the NOAA Hydrographic Survey Priorities, 2012 edition. </ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="false"><ns2:discussion>Survey Coverage was in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12547 Survey Limits</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/H12547%20Survey%20Limits.png</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>Ocean Pioneer</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>236.12</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>10.9</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>D2</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>244.28</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>12.37</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>480.41</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>23.24</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>4.84</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>4</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>23.37</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2013-07-03</ns2:surveyDates><ns2:surveyDates>2013-07-04</ns2:surveyDates><ns2:surveyDates>2013-07-05</ns2:surveyDates><ns2:surveyDates>2013-07-15</ns2:surveyDates><ns2:surveyDates>2013-07-16</ns2:surveyDates><ns2:surveyDates>2013-07-17</ns2:surveyDates><ns2:surveyDates>2013-07-21</ns2:surveyDates><ns2:surveyDates>2013-07-22</ns2:surveyDates><ns2:surveyDates>2013-07-23</ns2:surveyDates><ns2:surveyDates>2013-07-24</ns2:surveyDates><ns2:surveyDates>2013-07-27</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>Ocean Pioneer</ns2:hullID><ns2:LOA units="feet">205</ns2:LOA><ns2:draft units="feet">14</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>D2</ns2:hullID><ns2:LOA units="feet">29</ns2:LOA><ns2:draft units="feet">3</ns2:draft></ns1:vessel><ns1:discussion>Due to an inoperable davit, production for vessel R2 was limited for the OPR-Q191-KLR-13 survey. The last day of survey for vessel R2 was JD 181.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer> Applanix </ns2:manufacturer><ns2:model>POS M/V v4 </ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer> Applied Micro-Systems </ns2:manufacturer><ns2:model>SV&amp;P  </ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer> OceanScience</ns2:manufacturer><ns2:model>UCTD</ns2:model><ns2:type>Conductivity, Temperature and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer> Reson</ns2:manufacturer><ns2:model>7101</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer> Reson</ns2:manufacturer><ns2:model>SVP70</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>WaterLOG H3611 (Radar Water Level Sensors) were installed on the port and starboard gunwales of M/V Ocean Pioneer to obtain a more precise static draft measurement. Samples were taken over a 10 minute period and averaged to determine the vessel’s draft. Traditional static draft measurement techniques were also employed as a substitute for the WaterLOG H3611 measurements when required.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Crosslines were planned and well distributed throughout the survey to ensure adequate quality control.  Total crossline length surveyed was 23.24 nautical miles or 4.84 percent of the total mainscheme line length.  Each crossline was compared to the entire mainscheme line plan through a 2m CUBE surface using the CARIS HIPS QC report routine. If the crossline covered an area with significantly rocky topography, the crossline was compared to a 1m CUBE surface of the entire mainscheme line plan.

The majority of the QC Reports fall well within the required accuracy specifications.  However, several crosslines run by survey vessels Ocean Pioneer and D2 in the vicinity of Battery Point contain beams in the QC report that fall below the 95% confidence level due to significantly rocky topography as illustrated in the crossline profile from H12547. Good conformity was still seen between the mainscheme lines and the crosslines. </ns2:discussion><ns2:images><ns2:caption>H12547 Crossline Profile</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Priority_5_Profile%20of%202P5B03-TIE01.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.1</ns2:measured><ns2:zoning units="meters">0.2</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Ocean Pioneer</ns2:hullID><ns2:measuredCTD units="meters/second">1.633</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.250</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>D2</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2.509</ns2:measuredMVP><ns2:surface units="meters/second">0.250</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>The majority of the data fell within IHO Order 1a accuracy specifications.    Nodes that exceeded the allowable specifications were located in rough or rapidly changing topography or areas where the outer beams of the coverage boundaries were the single contributor to the surface.   Despite the higher uncertainty values in these areas, agreement between adjacent lines and co-linearity between soundings was good.  

Note: The percentage of nodes within IHO Oder 1a, were computed by CARIS using the Surface QC Report utility and are as follows:

CUBE Surface Uncertainty Report  
Surface Depth Range (m) % of nodes within IHO Order 1a
H12547-1m_final        0 - 20      97.05%
H12547-2m_final      18 - 40      99.69%
H12547-4m_final      36 - 80      99.98%
H12547-8m_final      72 - 160   100.00%

As illustrated in the uncertainty errors graphic, the uncertainty is generally lowest near the sonar nadir beams and increases toward the outside of each swath. This is expected and primarily a result of the sonar’s device model used within CARIS HIPS for TPU calculations.  In general, total propagated uncertainty varies proportionally to water depth.  Outer beams also have higher uncertainty values as a function of the bottom-detection algorithms within the sonar.  Data met project specifications.</ns2:discussion><ns2:images><ns2:caption>H12547 Uncertainty</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Priority_5_H12547_uncertainty.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12547 Uncertainty Errors</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Priority_5_H12547_Uncertainty_Errors.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>TVU values exceed IHO budgets in nearshore areas with higher frequency than usual. In the DAPR, section B, the surveyor indicates that the following values were entered into the CARIS 'Compute TPU' box: Measured Tidal Uncertainty: 0.1m and Tidal Zoning Uncertainty: 0.2m. It is also indicated that these values were based on the HSSD 2012 which itself states that &quot;An estimate for a typical processing error is 0.10 m at the 95% confidence level....&quot; and ...&quot;Estimates for typical errors associated with tidal zoning are 0.20 m at the 95% confidence level.&quot; Since CARIS expects these values to be input at the 68% CI level, the surveyor has effectively doubled the TVU associated with tides. This doubling of the tidal constituent of TVU is consistent with frequency with which the TVU budget was exceeded in nearshore areas.

In review - and without any re-evaluation of TVU values based on the above findings - the number of nodes in the 1m surface meeting IHO order 1a TVU budget was found to be 95.25%. This acceptable percentage disagrees with the documented uncertainty report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>The surveys are in agreement along their common borders.  The conformity between H12547 and the bordering survey areas (H12545 and H12546) was inspected during processing, using CARIS HIPS’ Subset Editor routine and finalized BASE Surfaces. A difference surfaces was also created to compare the 4-meter surface from H12547 and the junction with the 5-meter surface from H11712 (2007). The data were well within the IHO Order 1a allowable error.</ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H11712</ns2:registryNumber><ns2:scale>10000</ns2:scale><ns2:year>2007</ns2:year><ns2:fieldUnit>Fugro Pelagos, Inc.</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>A difference surface was created to compare the 4-meter surface from H12547 and the junction with the 5-meter surface from H11712 (2007), confirming that approximately 82.56% of the nodes agree to within +/-0.50m.  The remaining 17.44% were in areas with irregular bottom topography, areas with dynamic sand waves, or were on the outer edges of the swath at the coverage boundaries.  The data were well within the IHO Order 1a allowable error.</ns2:discussion><ns2:images><ns2:caption>H12547 Junctions with H11712</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/H11712_Junction_With_H12547.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference Surface H12547 vs. H11712</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Diff_Surf_H12547-H11712_Overview_Annotated.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference Surface Statistics H12547 vs. H11712</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Diff_Surf_Statistics_H12547-H11712_Ogive.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>In addition to junction H11712 given in Table 8, junctions with 1:40,000 2013 surveys H12545 (East) and H12546 (South) should also be listed. Despite their absence from Table 8, analysis was performed by the field for all junctioning surveys. However, note that the method used by the hydrographer for junction analysis was to review soundings and grids in subset mode and visually identify agreement. The office reviewer has used the standard NOAA junction review methodology of analyzing the mean and standard deviation of the vertical differences between overlapping, adjacent surfaces. The result of this analysis shows excellent agreement between survey areas. The mean difference and standard deviation between H12547 and H12545 was 0.07m (+/-0.41m @95%CI);  the mean difference and standard deviation between H12547 and H12546 was 0.17m  (+/-0.58m @95% CI).</ns2:comment></ns2:branchComment></ns2:comments></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>Bottom-Detection Artifacts</ns2:title><ns2:discussion>Dependent on sediment type, at the 200kHz frequency, the Reson SeaBat 7125 sonar system sometimes displayed bottom-detection artifacts near nadir of the multibeam swath. The bottom detection algorithm in the Reson 7125 may have been affected by the time spreading of the signal return due to sediment penetration close to nadir. To mitigate these effects, the sonar pulse length was kept at low settings during acquisition and the artifacts were monitored closely during data processing to ensure all data met IHO Order 1a specifications.</ns2:discussion><ns2:images><ns2:caption>Bottom-Detection Artifacts</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/P5-7125-200kHz_bta.png</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Kelp</ns2:title><ns2:discussion>Along coastal regions of the survey, an abundance of kelp was observed during data acquisition.  Due to data quality and safety issues, there may be some areas where survey operations were halted, thus not achieving the 4 fathom survey limit.  In addition to this, during data processing every effort was made to flag the kelp as rejected data wherever the CUBE BASE surface included the kelp as part of the seafloor.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Sound Speed Refraction Errors</ns2:title><ns2:discussion>Sound speed refraction errors were seen in the outer beams of the swaths of survey lines that were run in deeper water. However, line overlap was sufficient, and the affected soundings were rejected in CARIS HIPS’ Subset Editor routine to ensure the CUBE surface met IHO Order 1a specifications.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Note that in addition to the sound speed refraction errors noted by the field, during office review a number of irregularities were found with the field's compliance with the HSSD in terms of addressing sound speed sensor value differences, application of sound speed correction, and documentation of sound speed profiler confidence checks.</ns2:comment></ns2:branchComment></ns2:comments></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Sound speed measurements were conducted and applied as discussed in the Corrections to Echo Soundings section of the DAPR.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Data Density</ns2:title><ns2:discussion>The NOS Hydrographic Surveys Specifications and Deliverables, April 2012, requires 95% of all nodes to be populated with at least five soundings. Survey H12547 met these project specifications.

Density requirements for H12547 were achieved with at least 99.70% of finalized surface nodes containing five or more soundings.  Nodes that failed to meet the allowable specifications were located in rough or rapidly changing topography or areas where the outer beams of the coverage boundaries were the single contributor to the surface.

CUBE Surface Density Report  
Surface Depth Range (m) % of nodes within HSSD 2012
H12547-1m_final        0 - 20      99.71%
H12547-2m_final      18 - 40      99.97%
H12547-4m_final      36 - 80      99.94%
H12547-8m_final      72 - 160    99.94%

Detection requirements were met by minimizing vessel speed when necessary, using sonar range scales appropriate to the water depth to maximize ping rates, and maximizing swath overlap. These variables were adjusted in real-time by the online acquisition crew based on the WinFrog QC and coverage displays. The shipboard processing crew provided feedback after preliminary processing and coverage creation in CARIS HIPS and In-fills were run as necessary.</ns2:discussion><ns2:images><ns2:caption>H12547 Data Density</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/Priority_5_H12547_Data_Density.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><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:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Towed Side Scan Sonar (SSS) operations were not required by this contract, but the backscatter and beam imagery snippet data from all multibeam systems were logged and are stored in the s7k files.  All beam imagery snippet data was logged in the 7028 record of the s7k file for the project.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>Version 5.3.2</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12547_1m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">143</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_1m_final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_2m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">143</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_2m_final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_4m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">143</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_4m_final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">36</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_8m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">143</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12547_8m_final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">72</ns2:min><ns2:max units="meters">160</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>The surfaces have been reviewed where noisy data, or 'fliers' are incorporated into the gridded solution causing the surface to be shoaler than the true seafloor. Where these spurious soundings cause the gridded surface to be shoaler than the reliably measured seabed by greater than the maximum allowable TVU at that depth, the noisy data have been rejected and the surface recomputed.

The NOAA CUBE parameters mandated in HSSD were used for the creation of all CUBE BASE surfaces in Survey H12547.
</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical and horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>Discrete Zoning</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Unalaska, Dutch Harbor</ns2:stationName><ns2:stationID>9462620</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>King Cove</ns2:stationName><ns2:stationID>9459881</ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>Broad Bight</ns2:stationName><ns2:stationID>9462676</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>SE Tigalda Island</ns2:stationName><ns2:stationID>9462705</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Green Bight</ns2:stationName><ns2:stationID>9462786</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9462676.tid  </ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9462705.tid  </ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9462786.tid  </ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>OPR-Q191-KR-13_Zoning_20131008.zfd  </ns2:fileName><ns2:status>Preliminary</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2013-10-24</ns2:dateSubmitted><ns2:dateReceived>2013-10-31</ns2:dateReceived></ns2:finalTides><ns2:discussion>On October 08, 2013, John Oswald and Associates (JOA) issued verified tidal data and zoning for OPR-Q191-KR-13.  All sounding data was then re-merged using CARIS HIPS and SIPS tide routine. JOA verified tidal data were used for all final Navigation BASE surfaces and S-57 Feature files.  It should be noted that the tidal data applied to OPR-Q191-KR-13 is JOA verified and not CO-OPs verified. JOA are currently in the WALI verification process, which is pending,  awaiting CO-OPs approval.  Since the timeframe for CO-OPs verification is unknown, FPI were given approval, by our COTR, to submit the data with the JOA verified tides and zoning applied.

</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>JOA zoning model was approved as final by CO-OPS. Tide Note is appended to this report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>NAD83</ns2:horizontalDatum><ns2:projection>3N</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>Broad Bight</ns2:HVCRSiteID><ns2:stationID>BB_E</ns2:stationID></ns2:userInstalledStations><ns2:userInstalledStations><ns2:HVCRSiteID>SE Tigalda Island</ns2:HVCRSiteID><ns2:stationID>TI_N</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion> For real-time DGPS corrections, a CSI MBX-3 unit was tuned to the Cold Bay, Alaska USCG DGPS site. The unit output differentially corrected positions at 1 Hz to the (POS MV) 320 V4 where it was integrated with inertial data, and a position for the top-center of the IMU  generated. This position was logged concurrently with the bathymetry from WinFrog and the POS file using Fugro Pelagos PosMvLogger. It was later corrected for offsets to the multibeam echosounder (MBES) by CARIS HIPS in post-processing.

Final positioning was done using post-processed kinematic (PPK) methods. Applanix POSPac MMS v5.4 software was used in conjunction with the POS files and local 1Hz base station data to generate a higher accuracy position, which was applied in processing to replace the real-time position records. </ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Cold Bay DGPS Station</ns2:name></ns2:USCGStations><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16531</ns2:number><ns2:kapp>1</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>7</ns2:edition><ns2:editionDate>2002-02</ns2:editionDate><ns2:LNMDate>2013-10-01</ns2:LNMDate><ns2:NMDate>2013-09-28</ns2:NMDate></ns2:chart><ns2:discussion>The Raster chart was downloaded from NOAA’s Office of Coast Survey website on October 9, 2013.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.  

Sounding agreement between surveyed soundings on sheet H12547 and spot soundings displayed on Raster chart 16531 varied between 1 and 7 fathoms.  Generally, the surveyed data in the vicinity of the charted spot soundings from Raster chart 16531 agree to within 1 to 2 fathoms. However, the largest discrepancy found was 7 fathoms. 
  
The Hydrographer recommends that soundings within the survey limits of H12547 supersede all prior survey and charted depths.</ns2:discussion><ns2:images><ns2:caption>Chart Comparison H12547 vs. 16531</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/H12547_vs_16531.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US3AK61M</ns2:name><ns2:scale>300000</ns2:scale><ns2:edition>16</ns2:edition><ns2:updateApplicationDate>2011-01-12</ns2:updateApplicationDate><ns2:issueDate>2013-06-24</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>The ENCs were downloaded from NOAA’s Office of Coast Survey website on October 9, 2013. Thus, the issue dates displayed in the table above are more recent than the dates in the Project Instructions.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.  

Generally, the surveyed data in the vicinity of the charted spot soundings from the ENC US3AK61M agreed to within 1 to 5 meters.  

Although the ENC displays the spot soundings in meters, the contours are displayed in fathoms. The surveyed data for sheet H12547 shows contours that generally agree with the contour trends from ENC US3AK61M. 

The Hydrographer recommends that soundings within the survey limits of H12547 supersede all prior survey and charted depths.</ns2:discussion><ns2:images><ns2:caption>Chart Comparison H12547 vs. US3AK61M</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/H12547_vs_US3AK61M.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Chart 18520 is a 1:300,000 scale chart that also contains the surveyed area, but was not used for chart comparison purposes.</ns2:comment></ns2:branchComment></ns2:comments></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US4AK6FM</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>8</ns2:edition><ns2:updateApplicationDate>2011-04-28</ns2:updateApplicationDate><ns2:issueDate>2013-05-02</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths. 
 
Sounding agreement between surveyed soundings on sheet H12547 and spot soundings displayed on ENC US4AK6FM varied between 1 meter and 5 meters.  

Although the ENC displays the spot soundings in meters, the contours are displayed in fathoms. The surveyed data for sheet H12547 shows contours that generally agree with the contour trends from ENC US4AK6FM. 

The Hydrographer recommends that soundings within the survey limits of H12547 supersede all prior survey and charted depths.</ns2:discussion><ns2:images><ns2:caption>Chart Comparison H12547 vs. US4AK6FM</ns2:caption><ns2:link>file:///M:/OPRQ191KR13/Surveys/H12547/Report/Original/Support%20Files/H12547_vs_US4AK6FM.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="None Exist"><ns2:discussion>No AWOIS items exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:AWOISItems><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:chartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No Danger to Navigation Reports were submitted for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><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:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion xsi:nil="true"></ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur"><ns2:comment>Bottom Samples were acquired in accordance with the Project Instructions and the HSSD.</ns2:comment></ns2:branchComment></ns2:comments></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Limited shoreline verification was assigned in the Project Instructions, including the instruction to verify all features with asgnmt attributed 'Assigned' regardless if it is located inshore of the Navigable Area Limit Line. In email with the COTR, this requirement was eased to allow the hydrographer discretion in selecting safe, navigationally significant features for field verification. See Branch Comment (note in red) under D.2.1.</ns2:comment></ns2:branchComment></ns2:comments></ns1:shoreline><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:ATONS><ns2:results investigated="None Exist"><ns2:discussion>Aids to navigation (ATONs) do not exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>Overhead features do not exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>Submarine features do not exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><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:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><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:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>There is no present or planned construction or dredging within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:issue><ns2:title>Final Feature File</ns2:title><ns2:discussion>Charted features that fell inshore of the 4-fathom contour (NALL) were not investigated and have been noted with a “Not Addressed” comment in the “descrp” attribute of the final features file.  Features that fell within the survey limits were addressed and attributed appropriately.  This file contains the object and metadata with extended attributes as required in the Specifications and Deliverables (April 2012). 

All features, including ones from the NOAA assigned feature file, that were within the geographical bounds of H12547 are included in the “H12547_Field_Features.000” file.

Note: Since CARIS Notebook and Bathy DataBASE were unable to export to S-57 with the parameters outlined in section 8.2 of the HSSD 2012, an additional text file with the required meta information was sent to accompany the S-57 file. </ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The office reviewer added 18 features to the Final Feature File (FFF) that had been attributed 'Assigned' by the field, but not incorporated into the FFF. Also note that, though the Project Instructions indicate that the hydrographer is required to investigate all features whose asgnmt attribute is 'Assigned,' there is guidance from the COTR allowing the hydrographer discretion to verify the navigational significance of these features, and that the safety of the vessel and crew would not be compromised by the investigation. See Branch Comment (note in red) under D.2.1.
</ns2:comment></ns2:branchComment></ns2:comments></ns2:issue><ns2:comments/></ns1:otherResults><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:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><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: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 and Specifications Deliverables Manual, Field Procedures Manual, Standing and 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:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Dean Moyles</ns2:approverName><ns2:approverTitle>Senior Hydrographer (ACSM Cert. No. 226) </ns2:approverTitle><ns2:approvalDate>2013-11-04</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName><ns2:reportDateSent>2013-11-04</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Horizontal and Vertical Control Report</ns2:reportName><ns2:reportDateSent>2013-11-04</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package</ns2:reportName><ns2:reportDateSent>2013-11-04</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>MAR-P-001-R2 MBES Acquisition Procedures</ns2:reportName><ns2:reportDateSent>2013-11-04</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>DAC-P-010-R3 MBES Processing Procedures</ns2:reportName><ns2:reportDateSent>2013-11-04</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>