<?xml version="1.0" encoding="UTF-8"?>
<ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2013/01/DescriptiveReport" xmlns:ns2="http://Pydro.com/2013/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-D302-KR-13</ns2:number><ns2:name>Coastal Virginia</ns2:name><ns2:generalLocality>Coastal Virginia</ns2:generalLocality><ns2:fieldUnit>Leidos (formerly SAIC)</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12560</ns2:registryNumber><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>13 NM East of Sand Shoal Inlet</ns2:sublocality><ns2:stateOrTerritory>Virginia</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2013</ns2:year><ns2:chiefOfParty>Charles F. Holloway</ns2:chiefOfParty><ns2:projectType>Basic Hydrographic Survey</ns2:projectType><ns2:PIDate>2012-04-06</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-08-06</ns2:start><ns2:end>2013-10-04</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks>Contract: DG133C-08-CQ-0003

Contractor: Leidos 221 Third Street, Newport, RI 02840 USA.
Subcontractors: Divemasters, Inc., 15 Pumpshire Road, Toms River, NJ 08753; Rotator Staffing Services, 25 Kennedy Blvd., East Brunswick NJ 08816. 

Leidos Doc 14-TR-018.
</ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The area surveyed was a section of Coastal Virginia 13 NM East of Sand Shoal Inlet (Figure 1).
</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">37.3467305556</ns2:latitude><ns2:longitude hemisphere="W">75.6066333333</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">37.2476</ns2:latitude><ns2:longitude hemisphere="W">75.4319611111</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:figureNumber>1</ns2:figureNumber><ns2:caption>H12560 Survey Bounds</ns2:caption><ns2:link>file:///M:/charlie/NOAA_DELMARVA_2013/H12560/DR_Working/H12560_Figure_1.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyPurpose><ns2:discussion>The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products.  This project will cover approximately 109 square nautical miles, of which approximately 87 square nautical miles are designated critical survey area, as designated in the NOAA Hydrographic Survey Priorities (NHSP), 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>Leidos, formerly Science Applications International Corporation (SAIC), warrants only that the survey data acquired by Leidos and delivered to NOAA under Contract DG133C-08-CQ-0003 reflects the state of the sea floor in existence on the day and at the time the survey was conducted.

H12560 was surveyed in accordance with the following documents:
1. Project Instructions, OPR-D302-KR-13, dated 06 April 2012
2. Statement of Work, Hydrographic Survey Services, dated 11 April 2013
3. NOS Hydrographic Specifications and Deliverables, April 2013, released 18 April 2013 (HSSD)
</ns2:discussion><ns2:comments/></ns1:surveyQuality><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:coverageGraphic><ns2:figureNumber>2</ns2:figureNumber><ns2:caption>Final Bathymetry Coverage for H12560</ns2:caption><ns2:link>file:///M:/charlie/NOAA_DELMARVA_2013/H12560/DR_Working/H12560_Figure_2.jpg</ns2:link></ns1:coverageGraphic><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:surveyStatistics><ns2:surveyDates>2013-08-06</ns2:surveyDates><ns2:surveyDates>2013-08-07</ns2:surveyDates><ns2:surveyDates>2013-08-08</ns2:surveyDates><ns2:surveyDates>2013-08-09</ns2:surveyDates><ns2:surveyDates>2013-08-10</ns2:surveyDates><ns2:surveyDates>2013-08-11</ns2:surveyDates><ns2:surveyDates>2013-08-12</ns2:surveyDates><ns2:surveyDates>2013-08-13</ns2:surveyDates><ns2:surveyDates>2013-08-14</ns2:surveyDates><ns2:surveyDates>2013-08-15</ns2:surveyDates><ns2:surveyDates>2013-08-16</ns2:surveyDates><ns2:surveyDates>2013-08-17</ns2:surveyDates><ns2:surveyDates>2013-08-20</ns2:surveyDates><ns2:surveyDates>2013-08-21</ns2:surveyDates><ns2:surveyDates>2013-08-22</ns2:surveyDates><ns2:surveyDates>2013-10-01</ns2:surveyDates><ns2:surveyDates>2013-10-04</ns2:surveyDates><ns2:totalSurveyStats><ns2:bottomSamples>0</ns2:bottomSamples><ns2:AWOIS>1</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>35.75</ns2:SNM></ns2:totalSurveyStats><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>0</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>1026.3</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>85.1</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>0</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>1026.3</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>85.1</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>8.3</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Leidos used their ISS-2000 software on a Windows XP platform to acquire these survey data.  Survey planning and data analysis were conducted using the Leidos SABER software on Red Hat Enterprise 5 Linux platforms.  L-3 Klein 3000 side scan data were collected on a Windows XP platform using L-3 Klein’s SonarPro software.  Subsequent processing and review of the side scan data, including the generation of coverage mosaics, were accomplished using SABER.

A detailed description of the systems and vessel used to acquire and process these data is included in the Data Acquisition and Processing Report (DAPR) for OPR-D302-KR-13, previously delivered with the H12559 Descriptive Report (DR) on 16 May, 2014.  There were no variations from the equipment configuration described in the DAPR.
</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID><ns2:LOA units="feet">110</ns2:LOA><ns2:draft units="feet">9</ns2:draft></ns1:vessel><ns1:discussion>The M/V Atlantic Surveyor was used to collect multibeam sonar (RESON 7125 SV), side scan sonar (L-3 Klein 3000), and sound speed data during twenty-four hours per day survey operations.

A detailed description of the vessel used is included in Section A of the Data Acquisition and Processing Report (DAPR).</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>Seabat 7125 SV</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>L-3 Klein</ns2:manufacturer><ns2:model>3000</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS/MV 320</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>Probeacon</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Rolls Royce </ns2:manufacturer><ns2:model>MVP-30</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>A detailed description of the equipment installed on each vessel is included in Section A of the Data Acquisition and Processing Report (DAPR).</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>There were 85.1 linear nautical miles of crosslines and 1026.3 linear nautical miles of main scheme lines surveyed on H12560.  This resulted in crossline mileage approximately 8.3% of the main scheme mileage which meets the requirement (Section 5.2.4.3 of the HSSD) to achieve at least eight percent for a multibeam survey using set line spacing.  The main scheme lines were orientated 22°/202° and spaced 65 meters apart.  Crosslines were oriented 90°/270° and spaced 800 meters apart.  Refer to the “Multibeam Processing Log” section within Separates I for information on the delineation of main scheme and crossline data files.

In the field, hydrographers conducted daily comparisons of main scheme to near nadir crossline data to ensure that no systematic errors were introduced and to identify potential problems with the survey system.  After the application of all correctors and completion of final processing in the office, separate two-meter CUBE PFM grids were built.  One grid contained the full valid swath (±60° from nadir) of main scheme multibeam data and the other included only the near nadir swath (±5° from nadir) crossline data.  A difference grid was then generated by subtracting the CUBE depths in the main scheme PFM from the CUBE depths in the crossline PFM.

The SABER Frequency Distribution Tool was used to analyze the difference grid.  Comparisons of all final crossing data in H12560 showed that 98.61% were within 25 centimeters.  These comparisons fall within the requirement defined in Section 5.2.4.3 of the HSSD, which states that at least 95% of the depth difference values are to be within the maximum allowable total vertical uncertainty (calculated to be between 0.520 and 0.612 meters for the water depths observed in H12560).  See Separates II for a complete discussion of the analysis and tabular results.
</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values/><ns2:discussion>The Total Propagated Uncertainty (TPU) model that Leidos has adopted had its genesis at the Naval Oceanographic Office (NAVOCEANO), and is based on the work by Rob Hare and others (“Error Budget Analysis for NAVOCEANO Hydrographic Survey Systems, Task 2 FY 01”, 2001, HSRC FY01 Task 2 Final Report).  Once the TPU model is applied to the GSF bathymetry data, each beam is attributed with the horizontal uncertainty and the vertical uncertainty at the 95% confidence level.  For specific details on the use and application of the SABER Total Propagated Uncertainty model, see Section B.1 in the DAPR.

The vertical and horizontal uncertainty values that were estimated by the TPU model for individual multibeam soundings varied little across the dataset, tending to be most affected by beam angle in the multibeam data.  During application of horizontal and vertical uncertainties to the GSF files, individual beams where either the horizontal or vertical uncertainty exceeded the maximum allowable IHO S-44 5th edition Order 1a specifications were flagged as invalid.  As a result, all individual soundings used in development of the final CUBE depth surface had modeled vertical and horizontal uncertainty values at or below the allowable IHO S-44 5th edition, Order 1a uncertainty.

During the creation of the CUBE surface, two separate vertical uncertainty surfaces are calculated by the SABER software.  One surface contains the standard deviation of all soundings that are contributing to the CUBE hypothesis (Hyp. StdDev) and the other contains the average of the vertical uncertainty of all soundings contributing to the CUBE hypothesis (Hyp. AvgTPU).  A third vertical uncertainty surface is generated from the larger value of these two uncertainties at each node and is referred to as the Hypothesis Final Uncertainty (Hyp. Final Uncertainty).  For specific details on this process see Section B.2 of the DAPR.

The final two-meter PFM CUBE surface contained final vertical uncertainties that ranged from 0.270 to 0.659 meters.  The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.520 to 0.612 meters, based on the minimum CUBE depth (11.044 meters) and maximum CUBE depth (27.204 meters).  The SABER Check PFM Uncertainty function was used to highlight all instances in the Hyp. Final Uncertainty surface where a given node exceeded the IHO Order 1a allowable vertical uncertainty for the CUBE depth at that node.  The final two-meter PFM CUBE surface contained one CUBE node with a final vertical uncertainty that exceeded IHO Order 1a allowable vertical uncertainty.  This high vertical uncertainty resulted from a small depth difference in the outer beams of adjacent swaths.  

The SABER Check PFM Uncertainty function was also run on each of the two half-meter feature PFM Hyp. Final Uncertainty surfaces.  The results are listed in Figure 3.  As expected, there are higher numbers of nodes that exceed uncertainty limits due to the smaller node resolution and the high variability of sounding depths around features.

The SABER Frequency Distribution Tool was also used to review the Hyp. Final Uncertainty surface within the two-meter grid and two half-meter resolution PFM grids.  The results show that in the two-meter PFM, 99.75% of all nodes had final uncertainties less than or equal to 0.300 meters.  In the two individual feature PFM grids, at least 99.78% of all grid nodes contained total vertical uncertainties of 0.300 meters or less.
</ns2:discussion><ns2:images><ns2:figureNumber>3</ns2:figureNumber><ns2:caption>Number of Nodes Exceeding the Allowable IHO Order1a Uncertainty in the Feature BAG Files 1 of 2 and 2 of 2</ns2:caption><ns2:link>file:///M:/charlie/NOAA_DELMARVA_2013/H12560/DR_Working/H12560_Figure_3.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>An analysis of H12560 junctions with contemporary surveys H12396, H12397, and  H12559 was performed.  Note that the Project Instructions stated that junctions should be performed on H12395 as well, however, there were no overlapping data from H12560 and this survey.  Figure 4 shows the general locality of H12560 as it relates to the sheets for which junctions were performed.  Details for H12396, H12397, and  H12559 are listed in Table 6.  See Separates II for a complete discussion of the junction results and tabular listings.  Analysis of the junction with H12561 was not conducted, as the processing efforts for this sheet were still ongoing.</ns2:discussion><ns2:images><ns2:figureNumber>4</ns2:figureNumber><ns2:caption>General Locality of H12560 with Contemporary Surveys</ns2:caption><ns2:link>file:///M:/charlie/NOAA_DELMARVA_2013/H12560/DR_Working/H12560_Figure_4.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12396</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>Leidos (formerly SAIC)</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>H12560 junctions with H12396 to the Northwest. 94.33% of the soundings differ by ±0.55 meters.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12397</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>Leidos (formerly SAIC)</ns2:fieldUnit><ns2:relativeLocation>NE</ns2:relativeLocation></ns2:survey><ns2:discussion>H12560 junctions with H12397 to the Northeast. 96.58% of the soundings differ by ±0.40 meters.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12559</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2013</ns2:year><ns2:fieldUnit>Leidos (formerly SAIC)</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>H12560 junctions with H12559 to the West. 99.35% of the soundings differ by ±0.30 meters.</ns2:discussion><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="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>On the M/V Atlantic Surveyor, the MVP-30 was used to collect sound speed profile (SSP) data.  SSP data were obtained at intervals frequent enough to meet depth accuracy requirements. Section 5.2.3.3 of the HSSD requires that if the sound speed measured at the sonar head differs by more than two meters/second from the commensurate profile data, then another cast shall be acquired.  There were times when the sound speed values exceeded the two meters/second threshold due to the local temporal and tidal variability.  During these times, several profiles were acquired and reapplied in an effort to reduce these effects.  The product of this effort resulted in the final data bearing no significant artifacts due to sound speed differences.</ns1:castFrequency><ns1:discussion>Additional information can be found in Section A.8 of the DAPR.

A total of 459 sound speed profiles were applied to online data for H12560.  All profiles that were applied for online bathymetry data collection were acquired within the bounds of the survey area.  Please refer to the DAPR for specific details regarding acquisition (Section A.8) and application (Section C.1.3) of sound speed profiles.

Confidence checks of the sound speed profile casts were conducted periodically (approximately once per week) by comparing at least two consecutive casts taken with different SV and P Smart Sensors.  Six sound speed confidence checks were conducted during H12560 and the results can be found in Separates II within the “Comparison Cast Log” section.

Sound speed profiles were obtained for four different survey purposes.  The “Sound Speed Profile Log” section of Separates II is a cumulative report detailing each cast associated with H12560.  The log is separated by the purpose of the applied cast; with individual tables for “Used for MB” (online bathymetry), “Used for Comparison”, “Used for Lead Line”, and “Used for Closing”.  Additionally, in a separate folder on the delivery drive (H12560/Data/Processed/SVP/CARIS_SSP), there are four CARIS SSP files (.svp).  These files contain concatenated SSP data that have been formatted for use in CARIS.  The CARIS SSP files are designated based on the purpose of the cast and their filenames match the tables within the &quot;Sound Speed Profile Log&quot;.  All sound speed profile files are delivered with the H12560 delivery data and are broken out into sub-folders, which correspond to the purpose of each cast.</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>Coverage Analysis</ns2:title><ns2:discussion>The Project Instructions specified coverage requirements in the survey area as “(1) 200% Side Scan Sonar (SSS) with concurrent Set Line Spacing, Multibeam (MBES) and Backscatter, or (2) 200% SSS with concurrent Vertical Beam Echosounder (VBES), or (3) Object Detection MBES with Backscatter”.  Leidos choose to meet the coverage requirements with 200% side scan with concurrent set line spacing multibeam.  To achieve this coverage the M/V Atlantic Surveyor used a towed L-3 Klein 3000 side scan sonar set to a 75-meter range and a main scheme line spacing of 65 meters.  This survey scenario provided a consistent 150-meter side scan imagery swath and up to 20 meters of side scan overlap between adjacent lines within each 100% coverage and resulting multibeam coverage.

The SABER Gapchecker routine was used to flag bathymetry data gaps exceeding the allowable limit of three contiguous nodes.  Additionally, the entire surface was visually scanned for holidays at various points during the data processing effort.  Additional survey lines were run to fill any holidays that were detected.  A final review of the CUBE Depth surface in the two-meter grid showed that valid depths exist in 100% of the nodes and there were no areas where three or more nodes sharing adjacent sides lacked data.

All grids were examined for the number of soundings contributing to the chosen CUBE hypotheses for each node by running SABER’s Frequency Distribution Tool on the Hypothesis Number of Soundings (Hyp # Soundings) surface of the PFM grid.  The Hyp # Soundings surface reports the number of soundings that were used to compute the chosen hypothesis.  Analysis of the H12560 two-meter PFM grid revealed that 99.74% of all nodes contained three or more soundings; satisfying the requirements for set line spacing surveys, as specified in Section 5.2.2.3 of the HSSD.

Analysis of the two half-meter PFM grids showed a minimum of 95.74% of all individual nodes contained five or more soundings to meet object detection coverage (HSSD Section 5.2.2.1).</ns2:discussion><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>In accordance with the April 2013 NOS HSSD and the Project Instructions, Leidos collected multibeam backscatter with all GSF data acquired by the RESON 7125 SV.  The multibeam settings were checked to ensure acceptable quality standards were met and to avoid any acoustic saturation of the backscatter data.  The multibeam backscatter data acquired by each system were written to the GSF in real-time by ISS-2000 and are delivered in the final GSF files for each sheet.
</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Extended Attribute Files V5-2.</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12560_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">11.044</ns2:min><ns2:max units="meters">27.204</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12560_MB_50cm_MLLW_1of2</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">21.070</ns2:min><ns2:max units="meters">23.177</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12560_MB_50cm_MLLW_2of2</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">20.168</ns2:min><ns2:max units="meters">21.626</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12560_ss_1_100</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12560_ss_2_100</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:discussion>A PFM CUBE Depth surface was used to assess and document multibeam survey coverage.  The CUBE depth is populated with either the node’s chosen hypothesis or the depth of a feature or designated sounding set by the hydrographer, which overrides the chosen hypothesis.  The range of CUBE depths in H12560 was from 11.044 meters, 0.270-meter uncertainty (36 feet) to 27.204 meters, 0.288-meter uncertainty (89 feet).  Section 5.2.2.3 of the HSSD requires a four-meter grid resolution for depths ranging from zero meters to 40 meters for set line spacing surveys.  Due to the range of depths encountered on this project, Leidos requested and was granted permission to deliver all final grids at the higher two-meter node resolution.  Therefore, final CUBE surfaces for H12560 were generated at two-meter grid node resolution.  Over significant features, CUBE surfaces were generated at half-meter grid node resolution to meet the object detection specifications defined in Section 5.2.2.1 of the HSSD.  Two significant features were identified in H12560 and two half-meter resolution PFM grids were generated to cover these features.  Data within the half-meter resolution CUBE PFM grids also remain in the two-meter CUBE PFM grid.

The final gridded bathymetry data are delivered as Bathymetric Attributed Grids (BAG).  The BAG files were exported from CUBE PFM grids as detailed in Section B.2.4 of the DAPR.

As of the date of delivery of H12560, CARIS does not support version 1.5.1 BAGs with optional surfaces. Therefore, BAG version 1.1.0 files are delivered.  Since the BAG version 1.1.0 files only contain two surfaces, the standard CUBE Depth and Final Hyp. Uncertainty, BAGs will be delivered with the additional surfaces delivered as supplemental non-standard BAG files.  These additional BAG files were generated through the same process as the standard BAG files.  The version 1.1.0 BAG format only allows for a Depth surface and an Uncertainty surface.  Therefore, each of the non-standard BAG files were created with the CUBE Depth values populating the Depth surface of the BAG and each of the additional group surfaces listed below populating the Uncertainty surface of the BAG.

Please note when reviewing these additional, non-standard version 1.1.0 BAG files the file name designates the layer that populates the Uncertainty layer of the BAG (Figure 5).  Please also note that when displayed the two layers of the BAG remain named Depth and Uncertainty.  These non-standard BAGs are provided for review purposes only and are not intended to be used as archival products.  These additional surfaces are referred to as Elevation Solution Group surfaces and Node Group surfaces.

Note that by definition, BAG files contain elevations not depths however; many software packages display a BAG elevation surface as a depth (positive values indicating water depth).

The Elevation Solution Group is made up of the following three surfaces:

·	shoal elevation - the elevation value of the least-depth measurement selected from the sub-set of measurements that contributed to the elevation solution.
·	number of soundings - the number of elevation measurements selected from the sub-set of measurements that contributed to the elevation solution.
·	stddev - the standard deviation computed from all elevation values which contributed to any hypothesis within the node. Note that the stddev value is computed from all measurements contributing to the node, whereas shoal elevation and number of soundings relate only to the chosen elevation solution.

The Node Group is made up of the following two surfaces:

·	hypothesis strength - the CUBE computed strength of the chosen hypothesis.
·	number of hypotheses - the CUBE computed number of hypotheses.
</ns1:discussion><ns1:images><ns2:figureNumber>5</ns2:figureNumber><ns2:caption>Summary of Non-standard H12560 BAG Files</ns2:caption><ns2:link>file:///M:/charlie/NOAA_DELMARVA_2013/H12560/DR_Working/H12560_Figure_5.jpg</ns2:link></ns1:images><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>Side Scan Coverage Analysis</ns2:title><ns2:discussion>For all details regarding side scan data processing, see Section B.3 of the DAPR.  The Project Instructions required (1) 200% Side Scan Sonar (SSS) with concurrent Set Line Spacing Multibeam (MBES) and Backscatter, or (2) 200% SSS with concurrent Vertical Beam Echosounder (VBES), or (3) Object Detection MBES with Backscatter.  Leidos chose to meet the coverage requirements with 200% side scan with concurrent set line spacing multibeam.  The 200% side scan coverage was verified by generating two separate 100% coverage mosaics at one-meter cell size resolution as specified in Section 8.3.1 of the HSSD.  The first and second 100% coverage mosaics were independently reviewed using tools in SABER to verify data quality and swath coverage.  Both coverage mosaics are determined to be complete and sufficient to meet the requirements contained within the Project Instructions.  The mosaics are delivered as TIFF (.tif) images with accompanying world files (.tfw).

·	H12560_ss_1_100_mosaic
·	H12560_ss_2_100_mosaic

Side scan sonar contacts were investigated and confirmed using SABER Contact Review.  All side scan sonar contacts and accompanying images are delivered in the Side Scan Sonar Contacts S-57 file.
</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>No vertical or horizontal controls were established, recovered, or occupied during data acquisition for OPR-D302-KR-13, which includes H12560.  Therefore a Horizontal and Vertical Control Report was not required.
</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>Duck, NC</ns2:stationName><ns2:stationID>8651370</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>8651370_verified_07102013_10062013.tid</ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>D302KR2013CORP.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted xsi:nil="true"></ns2:dateSubmitted><ns2:dateReceived xsi:nil="true"></ns2:dateReceived></ns2:finalTides><ns2:discussion>No final tide note was provided by the NOAA Center for Operational Oceanographic Products and Services (CO-OPS).  Leidos is not required to have a final tide note from CO-OPS for H12560 however, a final tide note has been provided by Leidos in Appendix I.

The Project Instructions specified NOAA tide station 8651370 Duck, NC as the source for water level correctors.  A full explanation of the tide zone assessment is detailed in Section C.4 of the DAPR.  For H12560, 8651370 Duck, NC was the source of all final verified water level heights for determining correctors to soundings.  All data for H12560 were contained within two tide zones (SA54 and SA55) which were provided from NOAA.

Leidos did not revise the delivered tide zones for tide station 8651370 Duck, NC as the water level zoning parameters in the file D302KR2013CORP.zdf, provided by National Ocean Service (NOS) were deemed adequate for the application of observed verified water levels.  As a result, they were accepted as final and applied to all H12560 bathymetry data.
</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/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>UTM Zone 18, North</ns2:projection><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Driver, VA (289 kHz)</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>Annapolis, MD (301 kHz)</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>New Bern, NC (294 kHz)</ns2:name></ns2:USCGStations><ns2:discussion>Please refer to the DAPR for details regarding all antenna and transducer offsets.

Horizontal positioning of the multibeam transducer by the POS/MV was verified by frequent comparison checks against an independent DGPS system.  During survey data acquisition, the ISS-2000 real-time system provided a continuous view of the positioning comparison between the POS/MV and the Trimble DGPS.  An alarm was triggered within ISS-2000 if the comparisons were not within an acceptable range.  Any soundings with total horizontal uncertainties exceeding the maximum allowable IHO S-44 5th edition Order 1a specifications were flagged as invalid and therefore not used in the CUBE Depth calculations.  Daily positioning confidence checks for H12560 were conducted several times throughout the day and a daily value is presented as a table within Separates I, “Daily Positioning Confidence Checks”.  Daily positioning confidence checks for the M/V Atlantic Surveyor were within 0.61 meters.
</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>The chart comparisons were conducted using the Leidos SABER software to view the BSB raster charts with overlain data for H12560 such as the CUBE gridded surface, selected soundings, contacts, and features.  Charting recommendations for depths follow Section 5.1.2 of the HSSD where depths and uncertainties are to be rounded by standard arithmetic rounding (round half up) and accompanying chart depth units are rounded using NOAA cartographic rounding (0.75 round up).  All CUBE depths and uncertainty values are provided to millimeter precision.

For ENC comparisons, a combination of Jeppesen’s dKart Inspector, SevenCs’ SeeMyDENC, and CARIS’ EasyView were used in conjunction with SABER.

United States Coast Guard (USCG) District 5 Local Notice to Mariners publications were reviewed for changes subsequent to the date of the Hydrographic Survey Project Instructions and before the end of survey (as specified in Section 8.1.4 of the HSSD).  The Notice to Mariners reviewed were from week 27/13 (02 July 2013) until week 41/13 (08 October 2013).</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12221</ns2:number><ns2:kapp>558</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>8</ns2:edition><ns2:editionDate>2014-02</ns2:editionDate><ns2:LNMDate>2014-04-29</ns2:LNMDate><ns2:NMDate>2014-04-26</ns2:NMDate></ns2:chart><ns2:discussion>Chart 12221 covers the survey area west of 075° 29’ 00.00”W.

There are no federally maintained channels within H12560 on this chart.

The charted 60-foot depth curves were generally found to be in agreement with the H12560 survey data.

CUBE depths within sheet H12560 were generally within ±3 feet of the charted depths.

There were no charted soundings or features not specifically assigned as an AWOIS item within H12560 on this chart.

The AWOIS item on this chart is discussed in Section D.1.3.

All new uncharted features found, assigned AWOIS items, and charted feature updates are documented in the Final Feature File (S-57).
</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12200</ns2:number><ns2:kapp>526</ns2:kapp><ns2:scale>419706</ns2:scale><ns2:edition>50</ns2:edition><ns2:editionDate>2011-07</ns2:editionDate><ns2:LNMDate>2014-04-29</ns2:LNMDate><ns2:NMDate>2014-04-26</ns2:NMDate></ns2:chart><ns2:discussion>Chart 12200 covers the entire survey area.

There are no federally maintained channels within H12560 on this chart.

The charted 10-fathom depth curves were generally found to be in agreement with the H12560 survey data.

CUBE depths within sheet H12560 were generally within ±1 fathom of the charted depths.

There were no charted soundings or features not specifically assigned as an AWOIS item within H12560 on this chart.

The AWOIS item on this chart is discussed in Section D.1.3.

All new uncharted features found, assigned AWOIS items, and charted feature updates are documented in the Final Feature File (S-57).
</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US5VA12M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>22</ns2:edition><ns2:updateApplicationDate>2012-04-06</ns2:updateApplicationDate><ns2:issueDate>2014-02-26</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Chart US5VA12M covers the survey area west of 075° 29’ 00.00”W.

There are no federally maintained channels within H12560 on this chart.

The charted 18.2-meter depth curve is generally in agreement with the H12560 survey data.

CUBE depths within sheet H12560 were generally within ±1 meter of the charted depths.

There were no charted soundings or features not specifically assigned as an AWOIS item within H12560 on this chart.

The AWOIS item on this chart is discussed in Section D.1.3.

All new uncharted features found, assigned AWOIS items, and charted feature updates are documented in the Final Feature File (S-57).
</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US3DE01M</ns2:name><ns2:scale>419706</ns2:scale><ns2:edition>14</ns2:edition><ns2:updateApplicationDate>2013-04-24</ns2:updateApplicationDate><ns2:issueDate>2014-04-28</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Chart US3DE01M covers the entire survey area.

There are no federally maintained channels within H12560 on this chart.

The charted 18.2-meter depth curve is generally in agreement with the H12560 survey data.

CUBE depths within sheet H12560 were generally within ±1 meter of the charted depths.

There were no charted soundings or features not specifically assigned as an AWOIS item within H12560 on this chart.

The AWOIS item on this chart is discussed in Section D.1.3.

All new uncharted features found, assigned AWOIS items, and charted feature updates are documented in the Final Feature File (S-57).
</ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="Investigated"><ns2:discussion>All assigned and information AWOIS item updates are included in the Final Feature File (S-57).

AWOIS 959 was not found.  The 500-meter search radius was investigated with 200% side scan and resulting multibeam coverage.  No features and two non-significant contacts were found inside the search area.  Leidos determined the contacts were not AWOIS 959.</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="Investigated"><ns2:discussion>See the S-57 Final Feature File for all the details and recommendations regarding new uncharted features investigated.  </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="None Exist"><ns2:discussion>No bottom samples were required for this survey.</ns2:discussion></ns2:results><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/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Investigated"><ns2:discussion>Junction analysis with prior contemporary surveys H12396 (2012), H12397 (2012), and H12559 (2013) were conducted and the results are presented in Section B.2.3 of this Report.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>Within H12560 there was one USCG maintained Aid to Navigation (ATON), Hog Island Lighted Buoy 12.  This ATON is not included in the S-57 Final Feature file as called for in the HSSD.

The Feature Correlator Sheet for the ATON is presented as a JPEG file in the Multimedia folder, named by the feature number (H12560_Feature_004).

ATON Hog Island Lighted Buoy 12 (Fl R 2.5s) was compared to the United States Coast Guard Light List Volume II Atlantic Coast, updated through LNM week 19/14.  It was found to be serving its intended purpose.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><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:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features 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>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:issue><ns2:title>Designated Soundings</ns2:title><ns2:discussion>No designated soundings were set for H12560.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Final Feature S-57 File</ns2:title><ns2:discussion>Included with the H12560 delivery is the S-57 Final Feature File, H12560_FFF.000.  Details on how this file was generated and quality controlled can be found in Section B.2.6 of the DAPR.  The S-57 feature file delivered for H12560 contains millimeter precision for the value of sounding (VALSOU) attribute.  As specified in Section 8.2 of the HSSD, the S-57 feature file is in the WGS84 datum and is unprojected with all depth units in meters.  All of the features found in H12560 are retained within the S-57 Final Feature File.

Feature Correlator Sheets were exported as image files (.jpg) and are included in the S-57 Final Feature File under the NOAA Extended Attribute field “images” where applicable.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Side Scan Sonar Contacts S-57 File</ns2:title><ns2:discussion>Included with the H12560 delivery is the Side Scan Sonar Contact S-57 File, H12560_SSCon.000.  Details on how this file was generated and quality controlled can be found in Section B.2.6 of the DAPR.  As specified in Section 8.2 of the HSSD, the S-57 feature file is in the WGS84 datum and is unprojected with all depth units in meters.</ns2:discussion><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, 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>Charles F. Holloway</ns2:approverName><ns2:approverTitle>Lead Hydrographer</ns2:approverTitle><ns2:approvalDate>2014-05-23</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Descriptive Report, H12559</ns2:reportName><ns2:reportDateSent>2014-05-16</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName><ns2:reportDateSent>2014-05-16</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>