<?xml version="1.0" encoding="UTF-8"?>
<ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport"
    xmlns:ns2="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport http://svn.pydro.noaa.gov/2015/02/DR.xsd">
    <ns1:metadata>
        <ns1:projectMetadata>
            <ns2:number>OPR-K371-KR-15</ns2:number>
            <ns2:name/>
            <ns2:generalLocality>Gulf of Mexico</ns2:generalLocality>
            <ns2:fieldUnit>Leidos</ns2:fieldUnit>
        </ns1:projectMetadata>
        <ns1:registryMetadata>
            <ns2:registryNumber>H12730</ns2:registryNumber>
            <ns2:sheetID>4</ns2:sheetID>
            <ns2:registryInstructions/>
            <ns2:sublocality>25 NM SE of Sabine Pass</ns2:sublocality>
            <ns2:stateOrTerritory>Louisiana</ns2:stateOrTerritory>
            <ns2:country>United States</ns2:country>
            <ns2:scale>40000</ns2:scale>
        </ns1:registryMetadata>
        <ns1:surveyMetadata>
            <ns2:year>2015</ns2:year>
            <ns2:chiefOfParty>Paul L. Donaldson</ns2:chiefOfParty>
            <ns2:projectType>Basic Hydrographic Survey</ns2:projectType>
            <ns2:PIDate>2015-04-09</ns2:PIDate>
            <ns2:datesOfSurvey>
                <ns2:start>2015-12-01</ns2:start>
                <ns2:end>2015-12-15</ns2:end>
            </ns2:datesOfSurvey>
            <ns2:equipmentTypes>
                <ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment>
                <ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment>
                <ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment>
            </ns2:equipmentTypes>
            <ns2:acquisition>
                <ns2:units>meters</ns2:units>
            </ns2:acquisition>
            <ns2:horizontalCoordinateSystem zone="15N">Universal Transverse Mercator
                (UTM)</ns2:horizontalCoordinateSystem>
            <ns2:timeZone>UTC</ns2:timeZone>
            <ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier>
            <ns2:titlesheetRemarks>
                <ns2:fieldRemarks>EA-133C-14-CQ_0033.
                    
                    Contractor: Leidos, 221 Third Street, Newport, RI 02840 USA.
                    
                    Subcontractors: Divemasters, Inc., 15 Pumpshire Road, Toms River, NJ 08753 and OARS, 8705 Shoal Creek Blvd, Suite 109, Austin, TX 78757.
                    
                    Leidos Doc 16-TR-024.
                    
                    All times were recorded in UTC.
                    
                    Data were collected in UTM Zone 15</ns2:fieldRemarks>
                <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 the Gulf of Mexico SE of Sabine Pass, LA (Figure 1)</ns2:discussion>
            <ns2:limits>
                <ns2:northWest>
                    <ns2:latitude hemisphere="N">29.37682</ns2:latitude>
                    <ns2:longitude hemisphere="W">093.63581</ns2:longitude>
                </ns2:northWest>
                <ns2:southEast>
                    <ns2:latitude hemisphere="N">29.30201</ns2:latitude>
                    <ns2:longitude hemisphere="W">093.45312</ns2:longitude>
                </ns2:southEast>
            </ns2:limits>
            <ns2:images/>
            <ns2:images>
                <ns2:caption>Outline of area surveyed as part of H12827.</ns2:caption>
                <ns2:link>file:///SupportFiles/H12730_Figure_1.jpg</ns2:link>
            </ns2:images>
            <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 NOS Hydrographic Survey Specifications and Deliverables (HSSD).</ns2:discussion>
            </ns2:results>
            <ns2:comments/>
        </ns1:surveyLimits>
        <ns1:surveyPurpose>
            <ns2:discussion>The purpose of this survey is to update existing NOS nautical charts.  This project is located in a highly trafficked critical area south of the Louisiana coast as designated in the 2012 NOAA Hydrographic Survey Priorities.</ns2:discussion>
            <ns2:comments/>
        </ns1:surveyPurpose>
        <ns1:surveyQuality>
            <ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy>
            <ns2:discussion>Leidos warrants only that the survey data acquired by Leidos and delivered to NOAA under Contract EA-133C-14-CQ-0033 reflects the state of the sea floor in existence on the day and at the time the survey was conducted.
                
                H12730 was surveyed in accordance with the following documents:
                1.	Project Instructions, OPR-K371-KR-15, dated 09 April 2015
                2.	NOS Hydrographic Survey Specifications and Deliverables (HSSD), May 2015
                3.	OPR-K371-KR-15 Statement of Work, dated 09 January 2015</ns2:discussion>
            <ns2:comments/>
        </ns1:surveyQuality>
        <ns1:surveyCoverage>
            <ns2:coverageRequirement>
                <ns2:waterDepth>All waters in survey area.</ns2:waterDepth>
                <ns2:requiredCoverage>Either A) Complete MBES with backscatter, OR B) 100% SSS with concurrent set line spacing with MBES with backscatter.  Note: Complete MBES is sufficient for both determination of least depth identified with SSS and for disproving a feature - 100% SSS is sufficient to disprove a feature. Refer to Section 6.1.2 of the HSSD to confirm proper SSS acquisition parameters.  Gaps in SSS coverage should be treated as gaps in MBES coverage and addressed accordingly.</ns2:requiredCoverage>
            </ns2:coverageRequirement>
            <ns2:results deviation="false">
                <ns2:discussion>Leidos chose to achieve the coverage requirement using 100% side scan sonar with concurrent set line spacing multibeam echo-sounder with backscatter.  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>Final Bathymetry Coverage for H12730</ns2:caption>
            <ns2:link>file:///SupportFiles/H12730_Figure_2.jpg</ns2:link>
        </ns1:coverageGraphic>
        <ns1:surveyStatistics>
            <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>1048.87</ns2:MS_MBES_SSS>
                            <ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
                            <ns2:XL_MBES_SBES>84.35</ns2:XL_MBES_SBES>
                            <ns2:XL_lidar>0</ns2:XL_lidar>
                        </ns2:statistics>
                    </ns2:vessel>
                    <ns2:vessel>
                        <ns2:hullID>2802</ns2:hullID>
                        <ns2:statistics>
                            <ns2:MS_SBES>0</ns2:MS_SBES>
                            <ns2:MS_MBES>8.58</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>82.03</ns2:MS_MBES_SSS>
                            <ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
                            <ns2:XL_MBES_SBES>0</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></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>1048.87</ns2:MS_MBES_SSS>
                    <ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
                    <ns2:XL_MBES_SBES>84.35</ns2:XL_MBES_SBES>
                    <ns2:XL_lidar>0</ns2:XL_lidar>
                    <ns2:percentXLLNM>8.04</ns2:percentXLLNM>
                </ns2:totalLNM>
            </ns2:LNM>
            <ns2:totalSurveyStats>
                <ns2:bottomSamples>7</ns2:bottomSamples>
                <ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints>
                <ns2:DP>0</ns2:DP>
                <ns2:diveOps>0</ns2:diveOps>
                <ns2:SNM>41.65</ns2:SNM>
            </ns2:totalSurveyStats>
            <ns2:surveyDates>2015-12-01</ns2:surveyDates>
            <ns2:surveyDates>2015-12-02</ns2:surveyDates>
            <ns2:surveyDates>2015-12-03</ns2:surveyDates>
            <ns2:surveyDates>2015-12-04</ns2:surveyDates>
            <ns2:surveyDates>2015-12-05</ns2:surveyDates>
            <ns2:surveyDates>2015-12-06</ns2:surveyDates>
            <ns2:surveyDates>2015-12-07</ns2:surveyDates>
            <ns2:surveyDates>2015-12-08</ns2:surveyDates>
            <ns2:surveyDates>2015-12-10</ns2:surveyDates>
            <ns2:surveyDates>2015-12-15</ns2:surveyDates>
            <ns2:discussion xsi:nil="true"/>
            <ns2:comments/>
        </ns1:surveyStatistics>
    </ns1:areaSurveyed>
    <ns1:dataAcquisitionAndProcessing>
        <ns1:equipmentAndVessels>
            <ns1:discussion>Leidos used their ISS-2000 software on a Windows 7 platform to acquire these survey data.  Survey planning and data analysis were conducted using the Leidos SABER software on Red Hat Enterprise 6 Linux platforms.  L-3 Klein 3000 side scan data were collected on a Windows 7 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-K371-KR-15, delivered on 12 February 2016.  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 Seabat 8101 ER), 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 DAPR.</ns1:discussion>
                <ns1:comments/>
            </ns1:vessels>
            <ns1:equipment>
                <ns1:majorSystem>
                    <ns2:manufacturer>RESON</ns2:manufacturer>
                    <ns2:model>Seabat 8101 ER</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>Brooke Ocean Technology</ns2:manufacturer>
                    <ns2:model>MVP-30</ns2:model>
                    <ns2:type>Sound Speed System</ns2:type>
                </ns1:majorSystem>
                <ns1:discussion xsi:nil="true"/>
                <ns1:comments/>
            </ns1:equipment>
            <ns1:comments/>
        </ns1:equipmentAndVessels>
        <ns1:qualityControl>
            <ns1:crosslines>
                <ns2:discussion>There were 84.35 linear nautical miles of crosslines and 1048.87 linear nautical miles of mainscheme lines surveyed on H12730.  This resulted in crossline mileage of approximately 8.04% of the mainscheme mileage which meets the requirement (Section 5.2.4.3 of the 2015 HSSD) to achieve at least four percent for a complete coverage multibeam survey.  H12730 requirements were for complete coverage based on the 2015 HSSD and set line spacing in the 2014 HSSD.  Leidos was granted permission from NOAA (correspondence email dated 26 October 2015) to deliver H12730 data to the 2015 HSSD version after survey operations had already commenced; therefore, crossline survey plans were made to the 2014 HSSD requirement of eight percent.   
                    
                    The mainscheme lines were orientated 90°/270° and spaced 80 meters apart.  Crosslines were oriented 0°/180° and spaced 975 meters apart.  Refer to the “Multibeam Processing Log” section within Separates I for information on the delineation of mainscheme and crossline data files.
                    
                    In the field, hydrographers conducted daily comparisons of mainscheme to near nadir crossline data to ensure that no systematic errors were introduced, and to identify potential problems with the survey systems.  After the application of all correctors and completion of final processing in the office, separate one-meter grids were built.  One grid contained the full valid swath (±60° from nadir) of mainscheme multibeam and the other included only the near nadir swath (±5° from nadir) crossline data.  Difference grids were then generated by subtracting one grid from the other.
                    
                    The SABER Frequency Distribution Tool was used to analyze the difference grids.  All comparisons fell 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.  Figure 3 summarizes the comparison results.  See Separates II for a complete discussion of the analysis and tabular results.</ns2:discussion>
                <ns2:images>
                    <ns2:caption>Summary of Crossing Analysis</ns2:caption>
                    <ns2:link>file:///SupportFiles/H12730_Figure_3.jpg</ns2:link>
                </ns2:images>
                <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.  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. AvgTPE).  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.  For specific details on this process see Section B.2 of the DAPR.
                    
                    The final one-meter PFM CUBE surface contained final vertical uncertainties that ranged from 0.470 to 1.235 meters.  The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.516 to 0.545 meters, based on the minimum CUBE depth (9.792 meters) and maximum CUBE depth (16.723 meters).  The SABER Check PFM Uncertainty function was used to highlight all instances in the Hypothesis Final Uncertainty surface where a given node exceeded the IHO Order 1a allowable vertical uncertainty for the CUBE depth at that node.  The final one-meter PFM CUBE surface contained 110 individual CUBE nodes with final vertical uncertainties that exceeded IHO Order 1a allowable vertical uncertainty.  The nodes that exceed the IHO Order 1a allowable vertical uncertainty for the CUBE depth are primarily located around features where there is a high variability in the depth soundings.  There were four nodes where the uncertainty was high resulting from lines that were re-run due to gaps in the CUBE surface.
                    
                    The SABER Frequency Distribution Tool was used to review the Hypothesis Final Uncertainty surface within the final one-meter PFM grid.  The results show that in the final one-meter PFM grid, 99.99% of all nodes had final uncertainties less than or equal to 0.500 meters.</ns2:discussion>
            </ns1:uncertainty>
            <ns1:junctions>
                <ns2:discussion>An analysis of H12730 junctions with contemporary surveys was performed.  Figure 4 shows the general locality of H12730 as it relates to the contemporary sheets for which junction analysis was performed.  Table 6 provides details for each contemporary sheet junction analysis performed.  See Separates II for a complete discussion of the junction results and tabular listings.  Note that analysis of the junction with H12731 was not conducted, as at the time of this delivery, Leidos had not begun data acquisition of H12731.</ns2:discussion>
                <ns2:images>
                    <ns2:caption>General Locality of H12730 with Contemporary Surveys</ns2:caption>
                    <ns2:link>file:///SupportFiles/H12730_Figure_4.jpg</ns2:link>
                </ns2:images>
                <ns2:comments/>
                <ns2:junction>
                    <ns2:survey>
                        <ns2:registryNumber>>H10804</ns2:registryNumber>
                        <ns2:scale>20000</ns2:scale>
                        <ns2:year>1999</ns2:year>
                        <ns2:fieldUnit>John E. Chance and Associates</ns2:fieldUnit>
                        <ns2:relativeLocation>W</ns2:relativeLocation>
                    </ns2:survey>
                    <ns2:discussion>H12730 junctions with H10804 to the west; 96.86% of the comparisons agreed within ±0.50 meters.</ns2:discussion>
                    <ns2:comments/>
                </ns2:junction>
                <ns2:junction>
                    <ns2:survey>
                        <ns2:registryNumber>H10948</ns2:registryNumber>
                        <ns2:scale>20000</ns2:scale>
                        <ns2:year>2000</ns2:year>
                        <ns2:fieldUnit>Fugro GeoServices, Inc.</ns2:fieldUnit>
                        <ns2:relativeLocation>SW</ns2:relativeLocation>
                    </ns2:survey>
                    <ns2:discussion>H12730 junctions with H10948 to the southwest; 98.38% of the comparisons agreed within ±0.65 meters.</ns2:discussion>
                    <ns2:comments/>
                </ns2:junction>
                <ns2:junction>
                    <ns2:survey>
                        <ns2:registryNumber>H12728</ns2:registryNumber>
                        <ns2:scale>40000</ns2:scale>
                        <ns2:year>2015</ns2:year>
                        <ns2:fieldUnit>Leidos</ns2:fieldUnit>
                        <ns2:relativeLocation>N</ns2:relativeLocation>
                    </ns2:survey>
                    <ns2:discussion>H12730 junctions with H12728 to the north; 98.42% of the comparisons agreed within ±0.18 meters.</ns2:discussion>
                    <ns2:comments/>
                </ns2:junction>
            </ns1:junctions>
            <ns1:sonarQCChecks>
                <ns2:results deviation="false">
                    <ns2:discussion>Sonar system quality control checks were conducted as detailed in Section A.5, Multibeam Systems and Operations, 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>Exist</ns2:title>
                        <ns2:discussion>During localized weather events, an artifact resulting from a difference in water levels between the survey area and the water level gauge was observed in the multibeam CUBE surface.  The artifact generally ranged between 10 to 20 centimeters when present (Figure 5).  The occasional vertical offsets observed within H12730 were within the IHO Order 1a allowable vertical and horizontal uncertainty for these water depths.</ns2:discussion>
                        <ns2:images>
                            <ns2:caption>CUBE Depth Delta Resulting From Local Weather Events</ns2:caption>
                            <ns2:link>file:///SupportFiles/H12730_Figure_5.jpg</ns2:link>
                        </ns2:images>
                        <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.
                    
                    All sound speed profiles that were applied for online bathymetry data collection were acquired within one kilometer of the bounds of the survey area.  Please refer to the DAPR for specific details regarding acquisition (Section A.7) and application (Section C.1.3) of sound speed profiles.
                    
                    Confidence checks of the sound speed profile casts were conducted by comparing at least two consecutive casts taken with different SVP Smart Sensors.  Five sound speed confidence checks were conducted during H12730 and the results can be found in Separates II within the “Comparison Cast Log” section.
                    
                    Sound speed profiles have been provided in CARIS format (.svp) and are named based on the purpose of the casts.  There were four distinct purposes for SSP casts and each concatenated SSP file is located in a separate folder on the delivery drive (H12730/Data/Processed/SVP/CARIS_SSP).  There are four files for the MVP sound speed data.  All individual sound speed profile files are also delivered with the H12730 data and are broken out into sub-folders, which correspond to the purpose of each cast.</ns1:castFrequency>
                <ns1:discussion xsi:nil="true"/>
                <ns1:comments/>
            </ns1:soundSpeedMethods>
            <ns1:coverageEquipmentAndMethods>
                <ns2:results deviation="false">
                    <ns2:discussion>All equipment and survey methods are detailed in the DAPR.</ns2:discussion>
                </ns2:results>
                <ns2:comments/>
                </ns1:coverageEquipmentAndMethods>
            <ns1:additionalQualityControl>
                <ns2:issue>
                    <ns2:title>Coverage Analysis</ns2:title>
                    <ns2:discussion>Leidos chose to achieve the coverage requirement using 100% side scan sonar with concurrent set line spacing multibeam echo-sounder with backscatter.  To achieve this coverage, the M/V Atlantic Surveyor used a towed L-3 Klein 3000 side scan sonar set to a 50-meter range scale.  Mainscheme line spacing was 80 meters, which insured 100% side scan coverage.  
                        
                        Both the Project Instructions and the HSSD stated that 100% side scan was insufficient to disprove a charted feature.  Therefore, Leidos reviewed the BSB and ENC charts and completed an additional 100% side scan coverage, and resulting multibeam coverage over common charted objects not found during survey in order to verify disproval.  A radius was determined from the Project Instructions, which stated, “In the case of the unassigned offshore oil platforms within the survey area, should the field unit observe that the feature is not visible, then a formal disproval is required.  For the purposes of disproval, charted features labeled with a "PA" will have a search radius of 160 meters, a "PD" will have a search radius of 240 meters, and all other features without a position qualifier will have a search radius of 80 meters.”
                        
                        Backscatter data were acquired for all water depths.
                        
                        The SABER Gapchecker routine was used to flag multibeam data gaps within the CUBE surface.  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 of the one-meter PFM containing all multibeam showed that there were a few areas where a three by three node gap exists.  These gaps resulted from one of two reasons, the holiday line data was offset slightly from the original line due to vessel line following or the swath width of the holiday lines were reduced compared to the original line due to water level differences.  One instance of a three by three node gap, 29° 21’ 20.97”N 093° 35’ 44.17”W, exists on a crossline where data were turned off, and additional crossline data were not needed, as the crossline percentage requirement had already been met.
                        
                        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 for the one-meter PFM.  The Hyp # Soundings surface reports the number of soundings that were used to compute the chosen hypothesis.  Analysis of the H12730 final one-meter PFM grid revealed that 87.59% of all nodes contained five or more soundings; satisfying the requirements for complete coverage surveys, as specified in Section 5.2.2.2 of the HSSD.</ns2:discussion>    
                </ns2:issue>
            </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 HSSD and Project Instructions, Leidos collected multibeam backscatter with all GSF data acquired by the RESON Seabat 8101 ER.  The multibeam settings used were checked to ensure acceptable quality standards were met and to avoid any acoustic saturation of the backscatter data.  The multibeam backscatter data acquired were written to the GSF in real-time by ISS-2000 and are delivered in the final GSF files for this sheet.  Backscatter was not processed by Leidos.</ns2:discussion>
            </ns2:results>
            <ns2:comments/>
        </ns1:backscatter>
        <ns1:dataProcessing>
            <ns1:drSoftware>
                <ns1:bathySoftware deviation="true">
                    <ns1:manufacturer>Leidos</ns1:manufacturer>
                    <ns1:name>SABER</ns1:name>
                    <ns1:version>5.2.0.14.13</ns1:version>
                </ns1:bathySoftware>
                <ns1:imagerySoftware deviation="true">
                    <ns1:manufacturer>Leidos</ns1:manufacturer>
                    <ns1:name>SABER</ns1:name>
                    <ns1:version>5.2.0.14.13</ns1:version>
                </ns1:imagerySoftware>
                <ns1:featureObjectCatalog>NOAA Extended Atribute File V5-2.</ns1:featureObjectCatalog>
                <ns1:discussion>The primary data processing software used for both bathymetry and imagery was SABER.  There were no software configuration changes after the DAPR was submitted.</ns1:discussion>
                <ns1:comments/>
            </ns1:drSoftware>
            <ns1:surfaces>
                <ns1:surface>
                    <ns2:surfaceName>H12730_MB_1m_MLLW</ns2:surfaceName>
                    <ns2:surfaceType>BAG</ns2:surfaceType>
                    <ns2:resolution units="meters">1</ns2:resolution>
                    <ns2:depthRange>
                        <ns2:min units="meters">9.792</ns2:min>
                        <ns2:max units="meters">16.723</ns2:max>
                    </ns2:depthRange>
                    <ns2:surfaceParameter>N/A</ns2:surfaceParameter>
                    <ns2:purpose>Complete Coverage</ns2:purpose>
                </ns1:surface>
                <ns1:surface>
                    <ns2:surfaceName>H12730_ss_1_100_mosaic</ns2:surfaceName>
                    <ns2:surfaceType>SSS Mosaic (.tif;.tfw)</ns2:surfaceType>
                    <ns2:resolution units="meters">1</ns2:resolution>
                    <ns2:depthRange>
                        <ns2:min units="meters">0</ns2:min>
                        <ns2:max units="US Survey feet">0</ns2:max>
                    </ns2:depthRange>
                    <ns2:surfaceParameter>N/A</ns2:surfaceParameter>
                    <ns2:purpose>100% SSS</ns2:purpose>
                </ns1:surface>
                <ns1:surface>
                    <ns2:surfaceName>H12730_ss_2_100_mosaic</ns2:surfaceName>
                    <ns2:surfaceType>SSS Mosaic (.tif;.tfw)</ns2:surfaceType>
                    <ns2:resolution units="meters">1</ns2:resolution>
                    <ns2:depthRange>
                        <ns2:min units="meters">0</ns2:min>
                        <ns2:max units="meters">0</ns2:max>
                    </ns2:depthRange>
                    <ns2:surfaceParameter>N/A</ns2:surfaceParameter>
                    <ns2:purpose>200% SSS Charted Object Disproval</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 H12730 was from 9.792 meters (32.126 feet, 0.480-meter uncertainty) to 16.723 meters (54.865 feet, 0.480-meter uncertainty).  Section 5.2.2.2 of the HSSD requires a one-meter grid resolution for depths ranging from zero meters to 20 meters for Complete Coverage.  
                    
                    The final gridded bathymetry data are delivered as Bathymetric Attributed Grids (BAG).  The BAG file was exported from the CUBE PFM grid as detailed in Section B.2.5 of the DAPR</ns1:discussion>
            </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 100% side scan coverage with concurrent set line spacing MBES with backscatter.  Both the Project Instructions and the HSSD stated that 100% side scan was insufficient to disprove a charted feature. Therefore, 100% side scan coverage was collected and verified for the entire survey area, and an additional 100% coverage was collected over charted objects that were not found to verify disproval.  Leidos generated 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), refer to Table 7.
                        
                        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; for specifics refer to Section D.2.13.</ns2:discussion>
                </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-K371-KR-15, which includes H12730.  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>Calcasieu Pass, LA</ns2:stationName>
                        <ns2:stationID>8768094</ns2:stationID>
                    </ns2:NWLONGauges>
                </ns2:tideStations>
                <ns2:correctorFiles>
                    <ns2:waterLevels>
                        <ns2:fileName>8768094_verified_09222015_to_12202015.tid</ns2:fileName>
                        <ns2:status>Verified Observed</ns2:status>
                    </ns2:waterLevels>
                    <ns2:waterLevels>
                        <ns2:fileName>K371KR2015CORP.zdf</ns2:fileName>
                        <ns2:status>Final</ns2:status>
                   </ns2:waterLevels>
                <ns2:finalTides>
                    <ns2:dateSubmitted>1957-08-13</ns2:dateSubmitted>
                    <ns2:dateReceived>1957-08-15</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 H12730 however, a final tide note has been provided by Leidos in Appendix I.
                            
                            The Tides Statement of Work specified NOAA tide station 8768094 Calcasieu Pass, LA as the source for water level correctors for OPR-K371-KR-15.  A full explanation of the tide zone assessment is detailed in Section C.4 of the DAPR.  For H12730, 8768094 Calcasieu Pass, LA was the source of all final verified water level heights for determining correctors to soundings.  All data for H12730 were contained within three tide zones (WGM72, WGM407, and WGM81) which were provided from NOAA.
                            
                            Leidos did not revise the delivered tide zones for tide station 8768094 Calcasieu Pass, LA as the water level zoning parameters in the file K371KR2015CORP.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 H12730 bathymetry data.  
                            
                            Leidos was notified on 14 January 2016 that an adjustment to the observed verified tide correctors posted on the CO-OPS website were changed due to an adjustment of the sensor elevation during maintenance of the sensor.  This change modified the observed verified correctors from September 2015 through December 2015.  Leidos downloaded these changes and applied the updated verified tides to all data within H12730.</ns2:discussion>
                <ns2:comments/>
            </ns2:correctorFiles>
            </ns2:standard_or_ERZT>
            <ns2:VDATUM_or_constantSep used="false">
                <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 15</ns2:projection>
            <ns2:PPK used="true">
                <ns2:methodsUsed>Smart Base</ns2:methodsUsed>
                <ns2:baseStations/>
                <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>English Turn, LA (293 kHz)</ns2:name>
            </ns2:USCGStations>
                <ns2:USCGStations>
                    <ns2:name>Angleton, TX (301 kHz)</ns2:name>
                </ns2:USCGStations>
                <ns2:USCGStations>
                    <ns2:name>Aransas Pass, TX (304 kHz)</ns2:name>
                </ns2:USCGStations>
                <ns2:discussion>Please refer to the DAPR for details regarding all antenna and transducer offsets.
                    
                    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 were not used in the CUBE Depth calculations.</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 H12730 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).  
                    
                    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 8 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 36/15 (09 September 2015) until week 10/16 (09 March 2016).
                    
                    H12730 data meet data accuracy standards and bottom coverage requirements.  Recommend updating the common areas of all charts using data from this survey.  Charting recommendations for all features are provided in the S-57 Final Feature File.</ns2:discussion>
                <ns2:comments/>
            </ns1:methods>
            <ns1:charts>
                <ns2:rasterChart>
                    <ns2:chart>
                        <ns2:number>11341</ns2:number>
                        <ns2:kapp>124</ns2:kapp>
                        <ns2:scale>80000</ns2:scale>
                        <ns2:edition>44</ns2:edition>
                        <ns2:editionDate>2013-03</ns2:editionDate>
                        <ns2:LNMDate>2016-02-16</ns2:LNMDate>
                        <ns2:NMDate>2016-02-20</ns2:NMDate>
                    </ns2:chart>
                    <ns2:discussion>Chart 11341 covers the entire H12730 survey area.
                        
                        CUBE depths within sheet H12730 agreed with the charted depths across most of the survey area and were generally within ±3 feet of the charted depths.  There were discrete areas where the depths varied as much as 11 feet such as in 29° 20’ 43.17”N 093° 33’ 31.87”W.
                        
                        The charted 30-foot depth curve around a 28 foot sounding centered in approximately 29° 18’ 47.34”N 093° 34’ 52.51”W was found to have depths between 32 to 35 feet.
                        
                        Additional charted objects such as submarine pipelines and platforms are discussed in the sections below. 
                        
                        All new uncharted features found, and updates to charted features, are documented in the Final Feature File (S-57).</ns2:discussion>
                </ns2:rasterChart>
                <ns2:ENC>
                    <ns2:chart>
                        <ns2:name>US4LA10M</ns2:name>
                        <ns2:scale>700000</ns2:scale>
                        <ns2:edition>7</ns2:edition>
                        <ns2:updateApplicationDate>2011-05-02</ns2:updateApplicationDate>
                        <ns2:issueDate>2014-11-13</ns2:issueDate>
                        <ns2:preliminary>false</ns2:preliminary>
                    </ns2:chart>
                    <ns2:discussion>In the area of survey H12827, Electronic Navigation Chart (ENC)
                        US2AK92M coincides with Chart 16005, therefore a comparison between H12827
                        and US2AK92M is equivalent to the preceding comparison with Chart
                        16005.</ns2:discussion>
                    <ns2:comments/>
                </ns2:ENC>
                <ns2:ENC>
                    <ns2:chart>
                        <ns2:name>US4LA10M</ns2:name>
                        <ns2:scale>80000</ns2:scale>
                        <ns2:edition>10</ns2:edition>
                        <ns2:updateApplicationDate>2014-11-03</ns2:updateApplicationDate>
                        <ns2:issueDate>2016-01-21</ns2:issueDate>
                        <ns2:preliminary>false</ns2:preliminary>
                    </ns2:chart>
                    <ns2:discussion>ENC US4LA10M covers the H12730 survey area, east of 093° 34’ 00.63”W. 
                        
                        CUBE depths within sheet H12730 agreed with the charted depths across most of the survey area and were generally within ±1 meter of the charted depths.  There were discrete areas where the depths varied as much as 3 meters such as in 29° 20’ 42.64”N 093° 33’ 32.35”W.
                        
                        Additional charted objects such as submarine pipelines and platforms are discussed in the sections below. 
                        
                        All new uncharted features found, and updates to charted features, are documented in the Final Feature File (S-57).</ns2:discussion>
                </ns2:ENC>
                <ns2:ENC>
                    <ns2:chart>
                        <ns2:name>US4TX71M</ns2:name>
                        <ns2:scale>80000</ns2:scale>
                        <ns2:edition>27</ns2:edition>
                        <ns2:updateApplicationDate>2016-02-05</ns2:updateApplicationDate>
                        <ns2:issueDate>2016-02-05</ns2:issueDate>
                        <ns2:preliminary>false</ns2:preliminary>
                    </ns2:chart>
                    <ns2:discussion>ENC US4TX71M covers the H12730 survey area, west of 093° 34’ 00.63”W. 
                        
                        The charted 9.1-meter depth curve around an 8.5 meter sounding centered in approximately 29° 18’ 45.56”N 093° 34’ 53.02”W was found to have depths between 9.8 to 10.7  meters.
                        
                        Additional charted objects such as submarine pipelines and platforms are discussed in the sections below. 
                        
                        All new uncharted features found, and updates to charted features, are documented in the Final Feature File (S-57.</ns2:discussion>
                </ns2:ENC>      
                <ns2:comments/>
            </ns1:charts>
            <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="Investigated">
                    <ns2:discussion>One charted obstruction was located just outside the statement of work area in 29° 21’ 15.00”N 093° 38’ 00.00”W.  The charted obstruction was covered with 200% side scan sonar and resulting multibeam over a radius of at least 160 meters.  No obstruction was found.</ns2:discussion>
                </ns2:results>
                <ns2:comments/>
            </ns1:chartedFeatures>
            <ns1:unchartedFeatures>
                <ns2:results investigated="Investigated">
                    <ns2:discussion>See the S-57 Final Feature File (FFF) 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: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>There were no Danger to Navigation Reports (DTON) submitted for H12730.  Per guidance from AHB (via email correspondence 20 January 2016), exposed pipelines should not to be submitted as DTONs but as Feature Reports, in S-57 format.  Leidos submitted two Feature Reports in S-57 format to AHB, which AHB forwarded to the Office of Coast Surveys Navigation Manager.  Feature Report 1 contained a seep located at the junction of two charted pipelines.  Feature Report 2 contained 15 sections of exposed pipeline of various lengths.  These sections are represented by PIPSOL Features 10, 11, 15, 24-30, 33, and 34 in the S-57 FFF.</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>In accordance with both the Project Instructions and Section 7.1 of the HSSD, bottom characteristics were obtained for H12730.  Bottom characteristics were acquired at the seven locations proposed in the Project Reference File (PRF) by NOAA.  Leidos did not modify any bottom sample locations from the locations provided by NOAA.  Bottom characteristics collected during H12730 are included in the H12730 S-57 FFF, H12730.FFF.000, within the Seabed Area (SBDARE) object and are classified according to the requirements set forth in Appendix H of the HSSD</ns2:discussion>
                </ns2:results>
            </ns1:bottomSamples>
        </ns1:chartComparison>
        <ns1:additionalResults>
            <ns1:shoreline>
                <ns2:results investigated="None Exist">
                    <ns2:discussion>All features within the Composite Source File (CSF) were resolved.  There were no assigned features inshore of the NALL.</ns2:discussion>
                </ns2:results>
                <ns2:comments/>
            </ns1:shoreline>
            <ns1:priorSurveys>
                <ns2:results investigated="Investigated">
                    <ns2:discussion>Junction analysis with prior surveys H10804, H10948, and H12728 (collected in 1999, 2000, and 2015) was conducted, and the results are presented in Section B.2.4 of this Data Report and Separates II</ns2:discussion>
                </ns2:results>
                <ns2:comments/>
            </ns1:priorSurveys>
            <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: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="Investigated">
                    <ns2:discussion>Nineteen pipeline (PIPSOL) objects are delivered in the S-57 FFF to represent sections of pipelines found within the bounds of H12730, utilizing both multibeam and side scan data.  Additional charted pipelines fall within the survey coverage; however, the multibeam and side scan data do not show evidence of them.</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="Investigated">
                    <ns2:discussion>Five platforms were found within the bounds of H12730 all of which were charted.  In addition, five charted platforms were not found; an area with a radius of at least 80 meters was covered by 200% side scan and resulting multibeam.  The latest 11341 raster chart only has four of the five covered platforms remaining on the chart.  In addition, three charted platforms on ENC USTX71M were removed from both 11341 and 11332 raster charts prior to survey.  These three charted platforms were covered by 100% side scan sonar and resulting multibeam.  There was no evidence of the platforms existence in the side scan or multibeam data and no platforms were visible above the waterline.  See the S-57 FFF, H12730.FFF.000, Offshore Platform (OFSPLF) objects, for details and charting recommendations on each platform.</ns2:discussion>
                </ns2:results>
                <ns2:comments/>
            </ns1:platforms>
            <ns1:significantFeatures>
                <ns2:results investigated="None Exist">
                    <ns2:discussion>No significant features as defined in Section 8.1.4 of the HSSD exist within the H12730 survey area.</ns2:discussion>
                </ns2:results>
            </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>Designated soundings were used to help better preserve the shallowest sounding relative to the computed depth surface.  Separate flags exist in the Generic Sensor Format (version 3.06) for designated soundings and features.  All depths flagged as features and designated soundings override the CUBE best estimate of the depth in the final BAG files.  Both the designated soundings and features flags as defined within GSF are mapped to the same HDCS flag when ingested into CARIS (PD_DEPTH_DESIGNATED_MASK).
                        
                        Eleven designated soundings were set for H12730 to preserve the least depth on non-significant objects.  The difference between the least depth of these objects and the CUBE depth was more than one-half the maximum allowable total vertical uncertainty at that depth.  An individual Correlator Sheet for designated soundings and correlated side scan contacts are presented as JPEG files in the Multimedia folder and are named by the feature numbers (Figure 6).</ns2:discussion>
                    <ns2:images>
                        <ns2:caption>List of Designated Soundings set within H12730</ns2:caption>
                        <ns2:link>file:///SupportFiles/H12730_Figure_6.jpg</ns2:link>
                    </ns2:images>
                    <ns2:comments/>
                </ns2:issue>
                <ns2:comments/>
                <ns2:issue>
                    <ns2:title>Final Feature S-57 File</ns2:title>
                    <ns2:discussion>Included with H12730 delivery is the S-57 FFF, H12730.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 FFF delivered for H12730 contains millimeter precision for the value of sounding (VALSOU) attribute.  As specified in Section 8.2 of the HSSD, the S-57 FFF is in the WGS84 datum and is unprojected with all depth units in meters.  All significant, and recommended for charting, features found in H12730 are included within the S-57 FFF.
                        
                        In accordance with the HSSD, Leidos addressed all assigned objects within the bounds of H12730 from the provided CSF S-57 file in the S-57 FFF.  Additionally, all charted objects, derived from the largest scale ENC, are addressed within the S-57 FFF.  Note that positions of the objects from the ENC retain the full extents for that object; and therefore some objects extend beyond the H12730 sheet bounds.
                        
                        For each feature contained in the FFF (S-57), the Feature Correlator Sheet was exported as an image file (.jpg) and is included in the S-57 FFF under the NOAA Extended Attribute field “images”.</ns2:discussion>
                    <ns2:comments/>
                </ns2:issue>
                <ns2:issue>
                    <ns2:title>Side Scan Sonar Contacts S-57 File</ns2:title>
                    <ns2:discussion>Included with the H12730 delivery is the Side Scan Sonar Contact S-57 File, H12730.SSCon.000.  Details on how this file was generated and quality controlled can be found in Section B.3.5 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.  
                        
                        All side scan contacts are retained within the Side Scan Sonar Contact S-57 File.  For each contact included in this S-57 file, a JPEG image of the side scan contact is included under the NOAA Extended Attribute field “images”.</ns2:discussion>
                    <ns2:comments/>
                </ns2:issue>
            </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 BAG files, 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, Project Instructions, and the OPR-K371-KR-15 Statement of Work.  These data are adequate to supersede charted data in their common areas.  This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey>
            <ns1:additionalInfo xsi:nil="true"/>
        </ns1:statements>
        <ns1:signingPersonnel>
            <ns2:approverName>Paul L. Donaldson</ns2:approverName>
            <ns2:approverTitle>Chief Hydrographer</ns2:approverTitle>
            <ns2:approvalDate>2016-03-30</ns2:approvalDate>
        </ns1:signingPersonnel>
        <ns1:additionalReports>
            <ns2:reportName>OPR-K371-KR-15_DAPR.pdf</ns2:reportName>
            <ns2:reportDateSent>2016-02-12</ns2:reportDateSent>
        </ns1:additionalReports>
        <ns1:additionalReports>
            <ns2:reportName>OPR-K371-KR-15_Coast Pilot Review Report.pdf</ns2:reportName>
            <ns2:reportDateSent>2016-02-12</ns2:reportDateSent>
        </ns1:additionalReports>
        <ns1:additionalReports>
            <ns2:reportName>H12727_DR.pdf</ns2:reportName>
            <ns2:reportDateSent>2016-02-12</ns2:reportDateSent>
        </ns1:additionalReports>
        <ns1:additionalReports>
            <ns2:reportName>H12728_DR.pdf</ns2:reportName>
            <ns2:reportDateSent>2016-02-26</ns2:reportDateSent>
        </ns1:additionalReports>
        <ns1:additionalReports>
            <ns2:reportName>H12729_DR.pdf</ns2:reportName>
            <ns2:reportDateSent>2016-03-24</ns2:reportDateSent>
        </ns1:additionalReports>
    </ns1:approvalSheet>
</ns1:descriptiveReport>
