<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2017 sp2 (x64) (http://www.altova.com) by iss2000 (Leidos, Inc.) -->
<dr:descriptiveReport xmlns="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:dr="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport file:///M:/charlie/NOAA_Louisiana_2016/XML_Schema/DR.xsd">
	<dr:metadata>
		<dr:projectMetadata>
			<number>OPR-K371-KR-16</number>
			<name>Alex T. Bernier</name>
			<generalLocality>Gulf of Mexico</generalLocality>
			<fieldUnit>Leidos</fieldUnit>
		</dr:projectMetadata>
		<dr:registryMetadata>
			<registryNumber>H12876</registryNumber>
			<sheetID>2</sheetID>
			<registryInstructions/>
			<sublocality>33 NM South Southeast of Sabine Pass</sublocality>
			<stateOrTerritory>Louisiana</stateOrTerritory>
			<country>United States</country>
			<scale>40000</scale>
		</dr:registryMetadata>
		<dr:surveyMetadata>
			<year>2016</year>
			<chiefOfParty>Alex T. Bernier</chiefOfParty>
			<projectType>Basic Hydrographic Survey</projectType>
			<PIDate>2016-05-12</PIDate>
			<datesOfSurvey>
				<start>2016-06-18</start>
				<end>2016-09-28</end>
			</datesOfSurvey>
			<equipmentTypes>
				<soundingEquipment>Multibeam Echo Sounder</soundingEquipment>
				<imageryEquipment>Side Scan Sonar</imageryEquipment>
				<imageryEquipment>Multibeam Echo Sounder Backscatter</imageryEquipment>
			</equipmentTypes>
			<acquisition>
				<units>meters</units>
			</acquisition>
			<horizontalCoordinateSystem zone="15N"/>
			<timeZone>UTC</timeZone>
			<verifier>Atlantic Hydrographic Branch</verifier>
			<titlesheetRemarks>
				<fieldRemarks>Contract: EA-133C-14-CQ-0033/T-0002.
Contractor: Leidos, 221 Third Street, Newport, RI 02840 USA. 
Subcontractors: Divemasters, Inc., 15 Pumpshire Road, Toms River, NJ 08753; OARS, 8705 Shoal Creek Blvd, Suite 109, Austin, TX 78757. 
Leidos Doc 17-TR-003
All times were recorded in UTC. 
Data were collected in UTM Zone 15.</fieldRemarks>
				<branchRemarks/>
			</titlesheetRemarks>
		</dr:surveyMetadata>
		<dr:assignment>Contractor</dr:assignment>
	</dr:metadata>
	<dr:areaSurveyed>
		<dr:areaDescription>
			<discussion>The area surveyed was a section of the Gulf of Mexico south southeast of Sabine Pass, LA (Figure 1).</discussion>
			<limits>
				<northWest>
					<latitude hemisphere="N">29.23249</latitude>
					<longitude hemisphere="W">093.63325</longitude>
				</northWest>
				<southEast>
					<latitude hemisphere="N">29.15772</latitude>
					<longitude hemisphere="W">093.44042</longitude>
				</southEast>
			</limits>
			<images>
				<caption>H12876 Survey Bounds</caption>
				<link>file:///SupportFiles/H12876_Figure_1.jpg</link>
			</images>
			<comments/>
		</dr:areaDescription>
		<dr:surveyLimits>
			<results deviation="false">
				<discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the NOS Hydrographic Survey Specifications and Deliverables (HSSD).</discussion>
			</results>
			<comments/>
		</dr:surveyLimits>
		<dr:surveyPurpose>
			<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.</discussion>
			<comments/>
		</dr:surveyPurpose>
		<dr:surveyQuality>
			<adequacy>The entire survey is adequate to supersede previous data.</adequacy>
			<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.

H12876 was surveyed in accordance with the following documents:
1.	Project Instructions, OPR-K371-KR-16, dated 12 May 2016
2.	NOS Hydrographic Survey Specifications and Deliverables (HSSD), March 2016
3.	OPR-K371-KR-16 Statement of Work, dated 12 May 2016</discussion>
			<comments/>
		</dr:surveyQuality>
		<dr:surveyCoverage>
			<coverageRequirement>
				<waterDepth>All waters in survey area.</waterDepth>
				<requiredCoverage>Either A) Complete MBES with backscatter, OR B) 100% SSS with concurrent set line spacing 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 insufficient 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.</requiredCoverage>
			</coverageRequirement>
			<results deviation="false">
				<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.</discussion>
			</results>
			<comments/>
		</dr:surveyCoverage>
		<dr:coverageGraphic>
			<caption>Final Bathymetry Coverage for H12876</caption>
			<link>file:///SupportFiles/H12876_Figure_2.jpg</link>
		</dr:coverageGraphic>
		<dr:surveyStatistics>
			<LNM>
				<vesselLNM>
					<vessel>
						<hullID>M/V Atlantic Surveyor</hullID>
						<statistics>
							<MS_SBES>0</MS_SBES>
							<MS_MBES>0</MS_MBES>
							<MS_lidar>0</MS_lidar>
							<MS_SSS>0</MS_SSS>
							<MS_SBES_MBES>0</MS_SBES_MBES>
							<MS_MBES_SSS>1116.77</MS_MBES_SSS>
							<MS_SBES_SSS>0</MS_SBES_SSS>
							<XL_MBES_SBES>62.77</XL_MBES_SBES>
							<XL_lidar>0</XL_lidar>
						</statistics>
					</vessel>
				</vesselLNM>
				<totalLNM>
					<MS_SBES>0</MS_SBES>
					<MS_MBES>0</MS_MBES>
					<MS_lidar>0</MS_lidar>
					<MS_SSS>0</MS_SSS>
					<MS_SBES_MBES>0</MS_SBES_MBES>
					<MS_MBES_SSS>1116.77</MS_MBES_SSS>
					<MS_SBES_SSS>0</MS_SBES_SSS>
					<XL_MBES_SBES>62.77</XL_MBES_SBES>
					<XL_lidar>0</XL_lidar>
					<percentXLLNM>5.62</percentXLLNM>
				</totalLNM>
			</LNM>
			<totalSurveyStats>
				<bottomSamples>8</bottomSamples>
				<maritimeBoundaryPoints>0</maritimeBoundaryPoints>
				<DP>0</DP>
				<diveOps>0</diveOps>
				<SNM>44.23</SNM>
			</totalSurveyStats>
			<surveyDates>2016-06-18</surveyDates>
			<surveyDates>2016-06-19</surveyDates>
			<surveyDates>2016-06-20</surveyDates>
			<surveyDates>2016-06-21</surveyDates>
			<surveyDates>2016-06-22</surveyDates>
			<surveyDates>2016-06-23</surveyDates>
			<surveyDates>2016-06-24</surveyDates>
			<surveyDates>2016-06-25</surveyDates>
			<surveyDates>2016-06-26</surveyDates>
			<surveyDates>2016-06-27</surveyDates>
			<surveyDates>2016-06-28</surveyDates>
			<surveyDates>2016-08-10</surveyDates>
			<surveyDates>2016-09-28</surveyDates>
			<discussion/>
			<comments/>
		</dr:surveyStatistics>
	</dr:areaSurveyed>
	<dr:dataAcquisitionAndProcessing>
		<dr:equipmentAndVessels>
			<dr: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-16, delivered on 13 January 2017.  There were no variations from the equipment configuration described in the DAPR.</dr:discussion>
			<dr:vessels>
				<dr:vessel>
					<hullID>M/V Atlantic Surveyor</hullID>
					<LOA units="feet">110</LOA>
					<draft units="feet">9</draft>
				</dr:vessel>
				<dr:discussion>The M/V Atlantic Surveyor was used to collect multibeam sonar (RESON SeaBat 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 DAPR.</dr:discussion>
				<dr:comments/>
			</dr:vessels>
			<dr:equipment>
				<dr:majorSystem>
					<manufacturer>RESON</manufacturer>
					<model>SeaBat 7125 SV</model>
					<type>MBES</type>
				</dr:majorSystem>
				<dr:majorSystem>
					<manufacturer>L-3 Klein</manufacturer>
					<model>3000</model>
					<type>SSS</type>
				</dr:majorSystem>
				<dr:majorSystem>
					<manufacturer>Applanix</manufacturer>
					<model>POS/MV 320 V5</model>
					<type>Positioning and Attitude System</type>
				</dr:majorSystem>
				<dr:majorSystem>
					<manufacturer>Trimble</manufacturer>
					<model>Probeacon</model>
					<type>DGPS Positioning System</type>
				</dr:majorSystem>
				<dr:majorSystem>
					<manufacturer>ODIM Brooke Ocean</manufacturer>
					<model>MVP-30</model>
					<type>Sound Speed System</type>
				</dr:majorSystem>
				<dr:discussion>A detailed description of the equipment installed is included in Section A of the DAPR.</dr:discussion>
				<dr:comments/>
			</dr:equipment>
			<dr:comments/>
		</dr:equipmentAndVessels>
		<dr:qualityControl>
			<dr:crosslines>
				<discussion>There were 62.77 linear nautical miles of crosslines and 1116.77 linear nautical miles of mainscheme lines surveyed on H12876.  This resulted in crossline mileage of approximately 5.62% of the mainscheme mileage, which meets the requirement to achieve approximately four percent of mainscheme mileage for a complete coverage multibeam survey (Section 5.2.4.3 of the HSSD).  H12876 requirements were for complete coverage, Option B, based on the classifications defined in Section 5.2.2 of the HSSD; "100% side scan sonar coverage with concurrent multibeam bathymetry collection with complete coverage multibeam developments (i.e. 1m grid resolution in 0-20m depth range) of contacts and features.”  

The mainscheme lines were oriented 90°/270° and spaced 80 meters apart.  Crosslines were oriented 0°/180° and spaced 1500 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, Class 2) of mainscheme multibeam and the other included only the near nadir swath (±5° from nadir, Class 1) 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.</discussion>
				<images>
					<caption>Summary of Crossing Analysis</caption>
					<link>file:///SupportFiles/H12876_Figure_3.jpg</link>
				</images>
				<comments/>
			</dr:crosslines>
			<dr:uncertainty>
				<values/>
				<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.037 meters.  The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.531 to 0.560 meters, based on the minimum CUBE depth (13.849 meters) and maximum CUBE depth (19.469 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 102 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 were primarily located around features where there was a high variability in the depth soundings.

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.50 meters.</discussion>
				<comments/>
			</dr:uncertainty>
			<dr:junctions>
				<discussion>An analysis of H12876 junctions with contemporary surveys was performed.  Figure 4 shows the general locality of H12876 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.  At the time of this delivery, Leidos had not completed processing of H12877, H12878, and H12879.  Therefore, no final junction analyses with H12877, H12878, and H12879 were conducted.</discussion>
				<images>
					<caption>General Locality of H12876 with Contemporary Surveys</caption>
					<link>file:///SupportFiles/H12876_Figure_4.jpg</link>
				</images>
				<junction>
					<survey>
						<registryNumber>H10948</registryNumber>
						<scale>20000</scale>
						<year>2000</year>
						<fieldUnit>Fugro GeoServices, Inc.</fieldUnit>
						<relativeLocation>W</relativeLocation>
					</survey>
					<discussion>H12876 junctions with H10948 to the west; 99.06% of the comparisons agreed within ±0.50 meters.</discussion>
					<comments/>
				</junction>
				<junction>
					<survey>
						<registryNumber>H12875</registryNumber>
						<scale>40000</scale>
						<year>2016</year>
						<fieldUnit>Leidos, Inc.</fieldUnit>
						<relativeLocation>N</relativeLocation>
					</survey>
					<discussion>H12876 junctions with H12875 to the north; 99.95% of the comparisons agreed within ±0.30 meters.</discussion>
					<comments/>
				</junction>
				<comments/>
			</dr:junctions>
			<dr:sonarQCChecks>
				<results deviation="false">
					<discussion>Sonar system quality control checks were conducted as detailed in Section A.5, Multibeam Systems and Operations, of the DAPR.</discussion>
				</results>
				<comments/>
			</dr:sonarQCChecks>
			<dr:equipmentEffectiveness>
				<results deviation="false">
					<issue>
						<title>None Exist</title>
						<discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</discussion>
						<comments/>
					</issue>
				</results>
				<comments/>
			</dr:equipmentEffectiveness>
			<dr:factorsAffectingSoundings>
				<results deviation="false">
					<issue>
						<title>Exist</title>
						<discussion>Localized weather events produced a difference in water levels between the survey area and the water level gauge.  The artifact was seen in the multibeam CUBE surface and generally ranged between 10 to 20 centimeters when present (Figure 5).  Additionally, positional scatter resulting from normal DGPS variability was sometimes visible in the sounding data for discrete features with multiple passes.  Figure 6 represents small positional differences of 2 meters over a discrete object from two separate passes.  This horizontal offset was not always present as depicted in Figure 7, which shows two passes over a distinct object (represented by two colors) which align quite well (within 0.25 meters).  These occasional vertical and horizontal offsets observed within H12876 were within the IHO Order 1a allowable vertical and horizontal uncertainty for these water depths.</discussion>
						<images>
							<caption>CUBE Depth Artifact Resulting From Local Weather Events</caption>
							<link>file:///SupportFiles/H12876_Figure_5.jpg</link>
						</images>
						<images>
							<caption>DGPS Positional Variation Between Passes</caption>
							<link>file:///SupportFiles/H12876_Figure_6.jpg</link>
						</images>
						<images>
							<caption>No DGPS Positional Variation Between Multiple Passes and Multiple Headings</caption>
							<link>file:///SupportFiles/H12876_Figure_7.jpg</link>
						</images>
						<comments/>
					</issue>
				</results>
				<comments/>
			</dr:factorsAffectingSoundings>
			<dr:soundSpeedMethods>
				<dr: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 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.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.  Seven sound speed confidence checks were conducted during H12876 and the results can be found in Separates II within the “Comparison Cast Log” section.

All individual sound speed profile files are delivered with the H12876 data and are broken out into sub-folders, which correspond to the purpose of each cast.  Also, all individual sound speed profiles for H12876 have been concatenated into four separate files based on the purpose of the cast, provided in CARIS format files (.svp), and delivered under (H12876/Data/Processed/SVP/CARIS_SSP) on the delivery drive.  Refer to Separates II for more details.</dr:castFrequency>
				<dr:discussion/>
				<dr:comments/>
			</dr:soundSpeedMethods>
			<dr:coverageEquipmentAndMethods>
				<results deviation="false">
					<discussion>All equipment and survey methods are detailed in the DAPR.</discussion>
				</results>
				<comments/>
			</dr:coverageEquipmentAndMethods>
			<dr:additionalQualityControl>
				<issue>
					<title>Multibeam Coverage Analysis</title>
					<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 ensured 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 Composite Source File (CSF), BSB charts, 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.”  For the wellheads assigned in the final CSF file, coverage requirements for disproval were provided via email from NOAA on 16 June 2016 stating “If the obstruction is not found, in cases where 100% SSS with concurrent multibeam is being used as the primary coverage technique, a 50m disproval search radius using a technique described in Section 7.3.4 is necessary.”

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 instances where a three by three node gap exists.  However, these were not considered holidays in the final multibeam CUBE surface as these instances generally resulted from either the holiday line data being slightly offset from the original line due to vessel line steering, or the swath width of the holiday lines being reduced compared to the original line due to water level differences.  Two additional instances exist on crosslines where data were turned off between mainscheme swath coverage, 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 of the final one-meter CUBE PFM.  The Hyp # Soundings surface reports the number of soundings that were used to compute the chosen hypothesis.  Analysis of the H12876 final one-meter PFM grid revealed that 98.41% of all nodes contained five or more soundings; satisfying the requirements for complete coverage surveys, option B, as specified in Section 5.2.2.3 of the HSSD.</discussion>
					<comments/>
				</issue>
				<comments/>
			</dr:additionalQualityControl>
		</dr:qualityControl>
		<dr:echoSoundingCorrections>
			<dr:corrections>
				<results deviation="false">
					<discussion>All data reduction procedures conform to those detailed in the DAPR.</discussion>
				</results>
				<comments/>
			</dr:corrections>
			<dr:calibrations>
				<results deviation="false">
					<discussion>All sounding systems were calibrated as detailed in the DAPR.</discussion>
					<calibration>
						<type/>
						<date>2017-01-13</date>
						<reason/>
					</calibration>
				</results>
				<comments/>
			</dr:calibrations>
			<dr:additionalIssues>
				<comments/>
			</dr:additionalIssues>
		</dr:echoSoundingCorrections>
		<dr:backscatter>
			<results acquired="true">
				<discussion>Side Scan Coverage Analysis: For all details regarding side scan data processing, see Section B.3 of the DAPR.  Leidos chose to adhere to the coverage requirements in the Project Instructions with 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, and CSF assigned objects, to verify disproval.  Leidos generated two separate coverage mosaics at one-meter cell size resolution as specified in Section 8.2.1 of the HSSD.  The first 100% and second 100% disproval coverage mosaics were independently reviewed using tools in SABER to verify data quality and swath coverage.  The SABER Gapchecker routine was used to flag data gaps within each of the 100% side scan sonar coverage mosaics.  Additionally, the entirety of each SSS 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.  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.

Multibeam Echosounder Seafloor Backscatter: In accordance with the HSSD and Project Instructions, Leidos collected multibeam backscatter with all GSF data acquired by the RESON SeaBat 7125 SV.  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.</discussion>
			</results>
			<comments/>
		</dr:backscatter>
		<dr:dataProcessing>
			<dr:drSoftware>
				<dr:bathySoftware deviation="false">
					<dr:manufacturer>Leidos</dr:manufacturer>
					<dr:name>SABER</dr:name>
					<dr:version>5.2.0.19.02</dr:version>
				</dr:bathySoftware>
				<dr:imagerySoftware deviation="false">
					<dr:manufacturer>Leidos</dr:manufacturer>
					<dr:name>SABER</dr:name>
					<dr:version>5.2.0.19.02</dr:version>
				</dr:imagerySoftware>
				<dr:featureObjectCatalog>NOAA Extended Attribute File V5-4.</dr:featureObjectCatalog>
				<dr: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.</dr:discussion>
				<dr:comments/>
			</dr:drSoftware>
			<dr:surfaces>
				<dr:surface>
					<surfaceName>H12876_MB_1m_MLLW_Final_1of2</surfaceName>
					<surfaceType>BAG</surfaceType>
					<resolution units="meters">1</resolution>
					<depthRange>
						<min units="meters">14.764</min>
						<max units="meters">19.469</max>
					</depthRange>
					<surfaceParameter>N/A</surfaceParameter>
					<purpose>Concurrent
set line
spacing
MBES</purpose>
				</dr:surface>
				<dr:surface>
					<surfaceName>H12876_MB_1m_MLLW_Final_2of2</surfaceName>
					<surfaceType>BAG</surfaceType>
					<resolution units="meters">1</resolution>
					<depthRange>
						<min units="meters">13.849</min>
						<max units="meters">18.163</max>
					</depthRange>
					<surfaceParameter>N/A</surfaceParameter>
					<purpose>Concurrent
set line
spacing
MBES</purpose>
				</dr:surface>
				<dr:surface>
					<surfaceName>H12876_SSS_1m_100</surfaceName>
					<surfaceType>SSS Mosaic (.tif;.tfw)</surfaceType>
					<resolution units="meters">1</resolution>
					<depthRange>
						<min units="meters">0</min>
						<max units="meters">0</max>
					</depthRange>
					<surfaceParameter>N/A</surfaceParameter>
					<purpose>100% SSS</purpose>
				</dr:surface>
				<dr:surface>
					<surfaceName>H12876_SSS_Disproval</surfaceName>
					<surfaceType>SSS Mosaic (.tif;.tfw)</surfaceType>
					<resolution units="meters">1</resolution>
					<depthRange>
						<min units="meters">0</min>
						<max units="meters">0</max>
					</depthRange>
					<surfaceParameter>N/A</surfaceParameter>
					<purpose>200% SSS Charted Object Disproval</purpose>
				</dr:surface>
				<dr: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 H12876 was from 13.849 meters (45.436 feet, 0.470-meter uncertainty) to 19.469 meters (63.875 feet, 0.470-meter uncertainty).  Section 5.2.2.3 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 files were exported from the CUBE PFM grid as detailed in Section B.2.5 of the DAPR.</dr:discussion>
				<dr:comments/>
			</dr:surfaces>
			<dr:additionalDataProcessing>
				<comments/>
			</dr:additionalDataProcessing>
		</dr:dataProcessing>
	</dr:dataAcquisitionAndProcessing>
	<dr:verticalAndHorizontalControl>
		<dr:discussion>No vertical or horizontal controls were established, recovered, or occupied during data acquisition for OPR-K371-KR-16, which includes H12876.  Therefore, a Horizontal and Vertical Control Report was not required.</dr:discussion>
		<dr:verticalControl>
			<verticalDatum>Mean Lower Low Water</verticalDatum>
			<tideStations>
				<NWLONGauges>
					<stationName>Calcasieu Pass, LA</stationName>
					<stationID>8768094</stationID>
				</NWLONGauges>
			</tideStations>
			<standard_or_ERZT used="true">
				<methodsUsed>Discrete Zoning</methodsUsed>
				<correctorFiles>
					<waterLevels>
						<fileName>8768094_verified_01June16_to_04Oct16.tid</fileName>
						<status>Verified Observed</status>
					</waterLevels>
					<tideCorrectors>
						<fileName>K371KR2016CORP.zdf</fileName>
						<status>Final</status>
					</tideCorrectors>
				</correctorFiles>
				<finalTides>
					<dateSubmitted>1957-08-13</dateSubmitted>
					<dateReceived>1957-08-15</dateReceived>
				</finalTides>
				<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 H12876 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-16.  A full explanation of the tide zone assessment is detailed in Section C.4 of the DAPR.  For H12876, 8768094 Calcasieu Pass, LA was the source of all final verified water level heights for determining correctors to soundings.  All data for H12876 were contained within four tide zones (WGM398, WGM399, WGM400, and WGM401) 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 K371KR2016CORP.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 H12876 bathymetry data.</discussion>
				<comments/>
			</standard_or_ERZT>
			<VDATUM_or_constantSep used="false">
				<methodsUsed>ERS via Constant Separation Model</methodsUsed>
				<ellipsoidToChartDatumSepFile>
					<fileName/>
				</ellipsoidToChartDatumSepFile>
				<discussion/>
				<comments/>
			</VDATUM_or_constantSep>
			<comments/>
		</dr:verticalControl>
		<dr:horizontalControl>
			<horizontalDatum>North American Datum of 1983 (NAD83)</horizontalDatum>
			<projection>UTM Zone 15, North</projection>
			<PPK used="false">
				<methodsUsed>Single Base</methodsUsed>
				<baseStations/>
				<discussion/>
				<comments/>
			</PPK>
			<PPP used="false">
				<discussion/>
				<comments/>
			</PPP>
			<RTK used="false">
				<discussion/>
				<comments/>
			</RTK>
			<DGPS used="true">
				<USCGStations>
					<name>English Turn, LA (293 kHz)</name>
				</USCGStations>
				<USCGStations>
					<name>Angleton, TX (301 kHz)</name>
				</USCGStations>
				<USCGStations>
					<name>Aransas Pass, TX (304 kHz)</name>
				</USCGStations>
				<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.</discussion>
				<comments/>
			</DGPS>
			<comments/>
		</dr:horizontalControl>
		<dr:additionalIssues>
			<comments/>
		</dr:additionalIssues>
	</dr:verticalAndHorizontalControl>
	<dr:resultsAndRecommendations>
		<dr:chartComparison>
			<dr:methods>
				<discussion>The chart comparisons were conducted using the Leidos SABER software to view the BSB raster charts with overlain data for H12876 such as the CUBE 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).

For ENC comparisons, a combination of CARIS’ EasyView and SABER were used.

United States Coast Guard (USCG) District 8 Local Notice to Mariners publications were reviewed for changes subsequent to the date of the 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 22/16 (01 June 2016) until week 40/16 (05 October 2016).  Two Danger to Navigation Reports (DTONs) were submitted during survey operations and were reported in the lnm0829g2016 Local Notice to Mariners.  Specific details pertaining to the two DTONs are provided in the H12876 S-57 Final Feature File (FFF), named H12876.FFF.000.

H12876 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 found and updates to charted features, are documented in the H12876 S-57 FFF.  Additional charted objects such as submarine pipelines and platforms are discussed in later sections.</discussion>
				<comments/>
			</dr:methods>
			<dr:charts>
				<rasterChart>
					<chart>
						<number>11330</number>
						<kapp>195</kapp>
						<scale>250000</scale>
						<edition>22</edition>
						<editionDate>2013-04</editionDate>
						<LNMDate>2016-11-22</LNMDate>
						<NMDate>2016-10-29</NMDate>
					</chart>
					<discussion>Chart 11330 covers the H12876 survey area in its entirety.

CUBE depths within sheet H12876 agreed with the charted depths across most of the survey area or were generally within ±2 feet of the charted depths.</discussion>
					<comments/>
				</rasterChart>
				<rasterChart>
					<chart>
						<number>11332</number>
						<kapp>125</kapp>
						<scale>80000</scale>
						<edition>33</edition>
						<editionDate>2013-01</editionDate>
						<LNMDate>2016-11-22</LNMDate>
						<NMDate>2016-10-29</NMDate>
					</chart>
					<discussion>Chart 11332 covers the H12876 survey area north of 29° 13’ 31.12”N and west of 093° 33’ 59.72”W.

CUBE depths within sheet H12876 agreed with the charted depths across most of the survey area or were generally within ±1 foot of the charted depths.</discussion>
					<comments/>
				</rasterChart>
				<ENC>
					<chart>
						<name>US3GC02M</name>
						<scale>250000</scale>
						<edition>27</edition>
						<issueDate>2016-10-31</issueDate>
						<preliminary>false</preliminary>
						<updateApplicationDate>2014-10-27</updateApplicationDate>
					</chart>
					<discussion>ENC US3GC02M covers the H12876 survey area in its entirety. 

CUBE depths within sheet H12876 agreed with the charted depths across most of the survey area and were generally within ±1.00 meter of the charted depths.</discussion>
					<comments/>
				</ENC>
				<ENC>
					<chart>
						<name>US4TX71M</name>
						<scale>80000</scale>
						<edition>29</edition>
						<issueDate>2016-10-28</issueDate>
						<preliminary>false</preliminary>
						<updateApplicationDate>2016-10-28</updateApplicationDate>
					</chart>
					<discussion>ENC US4TX71M covers the H12876 survey area north of 29° 13’ 30.80”N and west of 093° 34’ 00.63”W. 

CUBE depths within sheet H12876 agreed with the charted depths across most of the survey area and were generally within ±1.00 meter of the charted depths.</discussion>
					<comments/>
				</ENC>
				<comments/>
			</dr:charts>
			<dr:maritimeBoundary>
				<results investigated="None Exist">
					<discussion>No Maritime Boundary Points were assigned for this survey.</discussion>
				</results>
				<comments/>
			</dr:maritimeBoundary>
			<dr:chartedFeatures>
				<results investigated="Investigated">
					<discussion>A charted obstruction PA fell within the H12876 survey bounds but was not found during survey.  See the H12876 S-57 FFF for details and recommendations regarding this charted feature.

A wreck and obstruction were charted within the survey area as a result of DTONs submitted for H12876 during survey operations (Section D.1.6).  The details resulting from final processing of the data, and recommendations, are captured in the H12876 S-57 FFF.</discussion>
				</results>
				<comments/>
			</dr:chartedFeatures>
			<dr:unchartedFeatures>
				<results investigated="Investigated">
					<discussion>See the H12876 S-57 FFF for all the details and recommendations regarding new uncharted features investigated.</discussion>
				</results>
				<comments/>
			</dr:unchartedFeatures>
			<dr:DTONS>
				<results reportSubmitted="true">
					<numberSubmitted>2</numberSubmitted>
					<report>
						<title>H12876_DTON01.000</title>
						<dateSubmitted>2016-07-01</dateSubmitted>
					</report>
					<report>
						<title>H12876_DTON02.000</title>
						<dateSubmitted>2016-07-01</dateSubmitted>
					</report>
					<discussion>There were two Danger to Navigation Reports (DTON_01 and DTON_02) submitted for H12876 by Leidos in S-57 format to the Atlantic Hydrographic Branch (AHB), which were subsequently submitted to the Nautical Data Branch (NDB)/Marine Chart Division (MCD) as a single submission on 05 July 2016 (H12876_DtoNs_1and2.zip).  A copy of the AHB verification email and AHB DTON report, in PDF format, submitted to the NDB/MCD for DTON_1-2 are included in a sub-directory within Appendix II of this Data Report.  Figure 8 provides a list of DTONs and their associated Feature number and object class in the H12876 S-57 FFF.

Leidos also submitted nine individual DTONs for exposed pipelines in S-57 format (titled H12876_DTON_03 through H12876_DTON_11) to AHB on 22 July 2016, of which AHB forwarded eight of the nine exposed pipelines to the Office of Coast Surveys Navigation Manager.  On 20 January 2017, Leidos submitted an additional Feature Report for two separate individual sections of exposed pipelines.  Figure 9 provides a list of exposed pipelines forwarded to AHB, and their associated Feature number and object class in the H12876 S-57 FFF.</discussion>
					<images>
						<caption>DTON Feature Numbers</caption>
						<link>file:///SupportFiles/H12876_Figure_8.jpg</link>
					</images>
					<images>
						<caption>Exposed Pipelines Submitted to AHB</caption>
						<link>file:///SupportFiles/H12876_Figure_9.jpg</link>
					</images>
				</results>
				<comments/>
			</dr:DTONS>
			<dr:shoalAndHazardousFeatures>
				<results investigated="None Exist">
					<discussion>There were no significant shoals or hazardous features within the area covered by H12876 other than those discussed in Section D.1.6.</discussion>
				</results>
				<comments/>
			</dr:shoalAndHazardousFeatures>
			<dr:channels>
				<results investigated="None Exist">
					<discussion>There were no channels within the area covered by H12876.</discussion>
				</results>
				<comments/>
			</dr:channels>
			<dr:bottomSamples>
				<results investigated="Investigated">
					<discussion>In accordance with both the Project Instructions and Section 7.2.2 of the HSSD, bottom characteristics were obtained for H12876.  Bottom characteristics were acquired at the eight locations, five of which were assigned in the Project Reference File (PRF) by NOAA.  Leidos did not modify any bottom sample locations from the locations proposed by NOAA in the PRF.  Three additional bottom samples were collected after review of the side scan data indicated a change in reflectivity.  Bottom characteristics collected during H12876 are included in the H12876 S-57 FFF within the Seabed Area (SBDARE) object and classified according to the requirements set forth in Appendix H of the HSSD.</discussion>
				</results>
				<comments/>
			</dr:bottomSamples>
		</dr:chartComparison>
		<dr:additionalResults>
			<dr:shoreline>
				<results investigated="None Exist">
					<discussion>All features within the CSF were resolved.  There were no assigned features inshore of the NALL.</discussion>
				</results>
				<comments/>
			</dr:shoreline>
			<dr:priorSurveys>
				<results investigated="Investigated">
					<discussion>Junction analysis with prior surveys H10948 and H12875 (collected in 2000 and 2016, respectfully) were conducted, and the results are presented in Section B.2.3 of this Data Report and Separates II.</discussion>
				</results>
				<comments/>
			</dr:priorSurveys>
			<dr:ATONS>
				<results investigated="None Exist">
					<discussion>There were no aids to navigation that fell within the H12876 survey area.</discussion>
				</results>
				<comments/>
			</dr:ATONS>
			<dr:overheadFeatures>
				<results investigated="None Exist">
					<discussion>There were no overhead features within the H12876 survey area.</discussion>
				</results>
				<comments/>
			</dr:overheadFeatures>
			<dr:submarineFeatures>
				<results investigated="Investigated">
					<discussion>Sixteen pipeline (PIPSOL) objects are delivered in the H12876 S-57 FFF to represent sections of pipeline found within the bounds of H12876.  Six pipeline objects are delivered as point objects identified as exposed pipelines within multibeam data.  Three pipeline objects are delivered as line objects identified as exposed pipelines, utilizing both multibeam and side scan data.  Seven pipeline objects are line objects depicting charted buried pipelines of which evidence of existence was observed in the side scan data only.  See Section D.1.6 for additional information.  Additional charted pipelines fall within the survey coverage; however, the multibeam and side scan data do not show evidence of them.</discussion>
				</results>
				<comments/>
			</dr:submarineFeatures>
			<dr:ferryRoutesAndTerminals>
				<results investigated="None Exist">
					<discussion>No ferry routes or terminals exist within the H12876 survey area.</discussion>
				</results>
				<comments/>
			</dr:ferryRoutesAndTerminals>
			<dr:platforms>
				<results investigated="Investigated">
					<discussion>There were no assigned offshore platform objects in the CSF, OPR-K371-KR-16_CSF_Version2.000, provided on 16 June 2016, which fell within the H12876 survey area.  However, there were five charted platforms within the H12876 SOW area associated with assigned obstructions (wellhead) within the OPR-K371-KR-16_CSF_Version2.000 file.

In addition, a separate charted platform, charted in 29° 10’ 05.20”N, 093° 28’ 25.27”W, was not found during survey operations.  An area with a radius of at least 80 meters was covered by 200% side scan and resulting 100% multibeam.  There was no evidence of the charted platforms existence in the side scan or multibeam data and no platforms were visible above the waterline in this charted position.  However, a platform (identification placard stating “APAWC-314A OCS-G-14273”) was found to exist approximately 280-meters south-southeast from the charted platform, and in the position of a separate assigned obstruction (wellhead) within the CSF.  The platform found (“APAWC-314A OCS-G-14273”) is represented by Feature 24 in the H12876 S-57 FFF  

See the H12876 S-57 FFF Offshore Platform (OFSPLF) objects, for details and charting recommendations for each platform.</discussion>
				</results>
				<comments/>
			</dr:platforms>
			<dr:significantFeatures>
				<results investigated="None Exist">
					<discussion>During data acquisition on H12876 there were intermittent local weather events which produced increased winds and sea state (see section B.2.6).  Occasionally during the localized weather events the water levels within the survey area differed slightly (10 to 20 centimeters) from the provided tide zone time and range ratios compared to the gauge at Calcasieu Pass, LA.  However, the vertical offsets observed were within the IHO Order 1a allowable vertical and horizontal uncertainty for the H12876 water depths.

No abnormal seafloor or environmental conditions, as defined in Section 8.1.4 of the HSSD, exist within the H12876 survey area.</discussion>
				</results>
				<comments/>
			</dr:significantFeatures>
			<dr:constructionOrDredging>
				<results investigated="None Exist">
					<discussion>No construction or dredging exists for the H12876 survey.</discussion>
				</results>
				<comments/>
			</dr:constructionOrDredging>
			<dr:newSurveyRecommendation>
				<results recommended="false">
					<discussion>No new survey recommendations are made for the area surrounding the H12876 survey area.</discussion>
				</results>
				<comments/>
			</dr:newSurveyRecommendation>
			<dr:otherResults>
				<issue>
					<title>Designated Soundings</title>
					<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 sounding and feature flags, as defined within GSF, are mapped to the same HDCS flag when ingested into CARIS (PD_DEPTH_DESIGNATED_MASK).

No GSF designated sounding flags were set for H12876.  Only GSF feature flags were set on significant features within H12876, and all information is contained in the H12876 S-57 FFF.</discussion>
					<comments/>
				</issue>
				<issue>
					<title>Final Feature S-57 File</title>
					<discussion>Included with the H12876 delivery is the S-57 FFF, H12876.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 H12876 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 H12876 are included within the S-57 FFF.

In accordance with the HSSD, Leidos addressed all assigned objects within the bounds of H12876 from the provided CSF S-57 file in the H12876 S-57 FFF.  

For each feature contained in the H12876 S-57 FFF, a 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”.</discussion>
					<comments/>
				</issue>
				<issue>
					<title>Side Scan Sonar Contacts S-57 File</title>
					<discussion>Included with the H12876 delivery is the Side Scan Sonar Contact S-57 File, H12876.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.  

Side scan sonar contacts were investigated and confirmed using SABER Contact Review.  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”.</discussion>
					<comments/>
				</issue>
				<issue>
					<title>Coast Pilot Review Report</title>
					<discussion>A Coast Pilot Review Report for OPR-K371-KR-16 was not required per guidance from the NOAA COR (see 06 June 2016 email in Appendices II Supplemental Survey Records and Correspondence).  The Coast Pilot was reviewed for the port of call and areas frequently transited, and no changes are recommended.</discussion>
					<comments/>
				</issue>
				<issue>
					<title>Assigned Wellheads</title>
					<discussion>On 16 June 2016, NOAA delivered OPR-K371-KR-16_CSF_Version2.000 which contained nineteen wellhead features within the H12876 survey bounds requiring investigation (See Appendix II).  All wellhead locations were covered in accordance with Section 7.3.4 of the HSSD with a minimum of 200% side scan data and resulting multibeam data.  A minimum of a 50-meter disproval search radius was covered as specified in the correspondence dated 16 June 2016.  No wellheads were found at eighteen of the nineteen assigned locations surveyed as part of H12876.  Within the search radius of one of the CSF assigned wellhead feature locations (29° 09’ 56.59”N, 093° 28’ 27.06”W) an uncharted platform (identification placard stating “APAWC-314A OCS-G-14273”) was found.  The platform found (“APAWC-314A OCS-G-14273”) is represented by Feature 24 in the H12876 S-57 FFF.</discussion>
					<comments/>
				</issue>
				<comments/>
			</dr:otherResults>
			<dr:insetRecommendation>
				<results recommended="false">
					<discussion>No inset recommendations are made for the area covered by the H12876 survey.</discussion>
				</results>
				<comments/>
			</dr:insetRecommendation>
		</dr:additionalResults>
	</dr:resultsAndRecommendations>
	<dr:approvalSheet>
		<dr:statements>
			<dr: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.</dr:supervision>
			<dr: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.</dr:approval>
			<dr: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-16 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.  Previously submitted deliverables for OPR-K371-KR-16 are provided in the table below.</dr:adequacyOfSurvey>
			<dr:additionalInfo/>
		</dr:statements>
		<dr:signingPersonnel>
			<approverName>Alex T. Bernier</approverName>
			<approverTitle>Lead Hydrographer</approverTitle>
			<approvalDate>2017-02-03</approvalDate>
		</dr:signingPersonnel>
		<dr:additionalReports>
			<reportName>OPR-K371-KR-16_DAPR.pdf</reportName>
			<reportDateSent>2017-01-13</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12875_DR.pdf</reportName>
			<reportDateSent>2017-01-13</reportDateSent>
		</dr:additionalReports>
	</dr:approvalSheet>
</dr:descriptiveReport>
