<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2016 sp1 (x64) (http://www.altova.com) by iss2000 (Leidos) -->
<dr:descriptiveReport xmlns:xi="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes" xmlns:dr="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport file:///C:\Program%20Files\Pydro64\Lib\site-packages\HSTP\xmlDR\schemas\final_2015_02\DR.xsd">
	<dr:metadata>
		<dr:projectMetadata>
			<number>OPR-K371-KR-15</number>
			<name>Alex T. Bernier</name>
			<generalLocality>Gulf of Mexico</generalLocality>
			<fieldUnit>Leidos</fieldUnit>
		</dr:projectMetadata>
		<dr:registryMetadata>
			<registryNumber>H12838</registryNumber>
			<sheetID>5</sheetID>
			<registryInstructions/>
			<sublocality>29 NM South of Calcasieu 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>2015-08-21</PIDate>
			<datesOfSurvey>
				<start>2016-04-24</start>
				<end>2016-06-18</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-001/M0001.

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-026.

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 of Calcasieu Pass, LA (Figure 1).</discussion>
			<limits>
				<northWest>
					<latitude hemisphere="N">29.304647</latitude>
					<longitude hemisphere="W">093.455459</longitude>
				</northWest>
				<southEast>
					<latitude hemisphere="N">29.252108</latitude>
					<longitude hemisphere="W">093.255495</longitude>
				</southEast>
			</limits>
			<images>
				<caption>H12838 Survey Bounds</caption>
				<link>file:///SupportFiles/H12838_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.

H12838 was surveyed in accordance with the following documents:
1.	Project Instructions, OPR-K371-KR-15, dated 21 August 2015
2.	NOS Hydrographic Survey Specifications and Deliverables (HSSD), May 2015
3.	OPR-K371-KR-15 Statement of Work, dated 21 August 2015
</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 H12838</caption>
			<link>file:///SupportFiles/H12838_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>807.25</MS_MBES_SSS>
							<MS_SBES_SSS>0</MS_SBES_SSS>
							<XL_MBES_SBES>34.13</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>807.25</MS_MBES_SSS>
					<MS_SBES_SSS>0</MS_SBES_SSS>
					<XL_MBES_SBES>34.13</XL_MBES_SBES>
					<XL_lidar>0</XL_lidar>
					<percentXLLNM>4.23</percentXLLNM>
				</totalLNM>
			</LNM>
			<totalSurveyStats>
				<bottomSamples>5</bottomSamples>
				<maritimeBoundaryPoints>0</maritimeBoundaryPoints>
				<DP>0</DP>
				<diveOps>0</diveOps>
				<SNM>31.97</SNM>
			</totalSurveyStats>
			<surveyDates>2016-04-24</surveyDates>
			<surveyDates>2016-04-25</surveyDates>
			<surveyDates>2016-04-26</surveyDates>
			<surveyDates>2016-04-27</surveyDates>
			<surveyDates>2016-04-28</surveyDates>
			<surveyDates>2016-04-29</surveyDates>
			<surveyDates>2016-05-01</surveyDates>
			<surveyDates>2016-05-02</surveyDates>
			<surveyDates>2016-05-03</surveyDates>
			<surveyDates>2016-05-04</surveyDates>
			<surveyDates>2016-05-05</surveyDates>
			<surveyDates>2016-06-06</surveyDates>
			<surveyDates>2016-06-18</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 sonar data were collected on a Windows 7 platform using L-3 Klein’s SonarPro software.  Subsequent processing and review of the side scan sonar 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) revision 1 for OPR-K371-KR-15, delivered on 11 August 2016.  There were no variations from the equipment configuration described in the DAPR Rev 1.

</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 Rev 1.

</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 V4
and
POS/MV 320 V5</model>
					<type>Positioning and Attitude System</type>
				</dr:majorSystem>
				<dr:majorSystem>
					<manufacturer>Trimble</manufacturer>
					<model>Probeacon</model>
					<type>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 Rev 1.</dr:discussion>
				<dr:comments/>
			</dr:equipment>
			<dr:comments/>
		</dr:equipmentAndVessels>
		<dr:qualityControl>
			<dr:crosslines>
				<discussion>There were 34.13 linear nautical miles of crosslines and 807.25 linear nautical miles of mainscheme lines surveyed on H12838.  This resulted in crossline mileage of approximately 4.23% 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.  H12838 requirements were for complete coverage based on the classifications defined in Section 5.2.2 of the 2015 HSSD (“…100% side scan sonar coverage with set line spacing bathymetry and complete coverage multibeam developments of significant contacts”).

The mainscheme lines were orientated 90°/270° and spaced 80 meters apart.  Crosslines were oriented 0°/180° and generally spaced 1950 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.
</discussion>
				<images>
					<caption>Summary of Crossing Analysis</caption>
					<link>file:///SupportFiles/H12838_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 Generic Sensor Format (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 Rev 1.

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 Rev 1.

The final one-meter PFM CUBE surface contained final vertical uncertainties that ranged from 0.470 to 0.933 meters.  The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.516 to 0.551 meters, based on the minimum CUBE depth (9.826 meters) and maximum CUBE depth (17.828 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 36 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.

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.43% of all nodes had final uncertainties less than or equal to 0.480 meters.  </discussion>
				<comments/>
			</dr:uncertainty>
			<dr:junctions>
				<discussion>An analysis of H12838 junctions with contemporary surveys was performed.  Figure 4 shows the general locality of H12838 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.    </discussion>
				<images>
					<caption>General Locality of H12838 with Contemporary Surveys</caption>
					<link>file:///SupportFiles/H12838_Figure_4.jpg</link>
				</images>
				<junction>
					<survey>
						<registryNumber>H10890</registryNumber>
						<scale>20000</scale>
						<year>1999</year>
						<fieldUnit>C and C Technologies, Inc.</fieldUnit>
						<relativeLocation>E</relativeLocation>
					</survey>
					<discussion>H12838 junctions with H10890 to the east; 98.35% of the comparisons agreed within ±0.40 meters.     </discussion>
					<comments/>
				</junction>
				<junction>
					<survey>
						<registryNumber>H10891</registryNumber>
						<scale>20000</scale>
						<year>1999</year>
						<fieldUnit>C and C Technologies, Inc.</fieldUnit>
						<relativeLocation>E</relativeLocation>
					</survey>
					<discussion>H12838 junctions with H10891 to the east; 96.90% of the comparisons agreed within ±0.30 meters  </discussion>
					<comments/>
				</junction>
				<junction>
					<survey>
						<registryNumber>H12730</registryNumber>
						<scale>40000</scale>
						<year>2015</year>
						<fieldUnit>Leidos</fieldUnit>
						<relativeLocation>N</relativeLocation>
					</survey>
					<discussion>H12838 junctions with H12730 to the north; 95.82% of the comparisons agreed within ±0.30 meters.  </discussion>
					<comments/>
				</junction>
				<junction>
					<survey>
						<registryNumber>H12731</registryNumber>
						<scale>40000</scale>
						<year>2016</year>
						<fieldUnit>Leidos</fieldUnit>
						<relativeLocation>N</relativeLocation>
					</survey>
					<discussion>H12838 junctions with H12731 to the north; 96.49% 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 Rev 1.</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>During localized weather events, an artifact resulting from a difference in water levels between the survey area and the water level gauge (Calcasieu Pass, LA) was observed in the multibeam CUBE surface.  The artifact generally ranged between 10 to 30 centimeters when present (Figure 5).  In addition, some of these adverse weather conditions resulted in a visible heave artifact in the final CUBE surface of H12838.  The occasional vertical offsets and heave artifacts observed within H12838 were within the IHO Order 1a allowable vertical and horizontal uncertainty for these water depths.</discussion>
						<images>
							<caption>CUBE Depth Delta and Heave Artifact Resulting From Local Weather Events</caption>
							<link>file:///SupportFiles/H12838_Figure_5.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 that were applied for online bathymetry data collection were acquired within 250 meters of the bounds of the survey area.  Please refer to the DAPR Rev 1 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 Smart SV and P sensors.  Seven sound speed confidence checks were conducted during H12838 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 H12838 data and are broken out into sub-folders, which correspond to the purpose of each cast.  Also, all individual sound speed profiles for H12838 have been concatenated into four separate files based on the purpose of the cast, provided in CARIS format files (.svp), and delivered under (H12838/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 Rev 1.</discussion>
				</results>
				<comments/>
			</dr:coverageEquipmentAndMethods>
			<dr:additionalQualityControl>
				<issue>
					<title>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 sonar was insufficient to disprove a charted feature.  Therefore, Leidos reviewed the BSB and ENC charts and completed an additional 100% side scan sonar coverage with resulting multibeam coverage over common charted objects not found during survey in order to verify disproval.  A search radius for each charted feature disproval 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 data gaps within each of the 100% side scan sonar coverage mosaics, as well as the multibeam CUBE surface.  Additionally, the entirety of each SSS and MBES 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 each 100% side scan sonar coverage mosaic showed that there were no holidays, as defined by Section 5.2.2.2 of the HSSD to be three by three nodes in the surface at the required one-meter resolution (see Section B.5.3 for more details).  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.  These gaps 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.  One additional instance of a three by three node gap, 29° 16’ 56.93”N 093° 22’ 16.16”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.

The one-meter PFM (containing all multibeam) was 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 H12838 final one-meter PFM grid revealed that 98.55% 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.</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 Rev 1.</discussion>
				</results>
				<comments/>
			</dr:corrections>
			<dr:calibrations>
				<results deviation="false">
					<discussion>All sounding systems were calibrated as detailed in the DAPR Rev 1.</discussion>
					<calibration>
						<type/>
						<date>2016-04-08</date>
						<reason/>
					</calibration>
				</results>
				<comments/>
			</dr:calibrations>
			<dr:additionalIssues>
				<comments/>
			</dr:additionalIssues>
		</dr:echoSoundingCorrections>
		<dr:backscatter>
			<results acquired="true">
				<discussion>In accordance with the HSSD and Project Instructions, Leidos collected multibeam echo-sounder 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.14.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.14.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 Rev 1 was submitted.</dr:discussion>
				<dr:comments/>
			</dr:drSoftware>
			<dr:surfaces>
				<dr:surface>
					<surfaceName>H12838_MB_1m_MLLW</surfaceName>
					<surfaceType>BAG</surfaceType>
					<resolution units="meters">1</resolution>
					<depthRange>
						<min units="meters">9.826</min>
						<max units="meters">17.828</max>
					</depthRange>
					<surfaceParameter>N/A</surfaceParameter>
					<purpose>Concurrent set line spacing MBES</purpose>
				</dr:surface>
				<dr:surface>
					<surfaceName>H12838_ss_1_100_mosaic</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>Complete Coverage (100% SSS)</purpose>
				</dr:surface>
				<dr:surface>
					<surfaceName>H12838_ss_2_100_mosaic</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 (see Section D.2.11 for details of the GSF feature and designated sounding flags).  The range of CUBE depths in H12838 was from 9.826 meters (32.237 feet, 0.470-meter uncertainty) to 17.828 meters (58.491 feet, 0.558-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 a Bathymetric Attributed Grid (BAG).  The BAG file was exported from the CUBE PFM grid as detailed in Section B.2.5 of the DAPR Rev 1.</dr:discussion>
				<dr:comments/>
			</dr:surfaces>
			<dr:additionalDataProcessing>
				<issue>
					<title>Side Scan Sonar Coverage Analysis</title>
					<discussion>For all details regarding side scan sonar data processing, see Section B.3 of the DAPR Rev 1.  The Project Instructions required 100% side scan sonar 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 sonar coverage was collected and verified for the entire survey area, and an additional 100% side scan sonar 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.  A final review of each 100% side scan sonar coverage mosaic showed that there were no holidays, as defined by Section 5.2.2.2 of the HSSD to be three by three nodes in the surface at the required one-meter resolution.  Both coverage mosaics are determined to be complete and sufficient to meet the requirements contained within the Project Instructions, and the HSSD.  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.</discussion>
					<comments/>
				</issue>
				<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-15, which includes H12838.  Therefore, a Horizontal and Vertical Control Report was not required.</dr:discussion>
		<dr:verticalControl>
			<verticalDatum>Mean Lower Low Water</verticalDatum>
			<standard_or_ERZT used="true">
				<methodsUsed>Discrete Zoning</methodsUsed>
				<tideStations>
					<NWLONGauges>
						<stationName>Calcasieu Pass, LA</stationName>
						<stationID>8768094</stationID>
					</NWLONGauges>
				</tideStations>
				<correctorFiles>
					<waterLevels>
						<fileName>8768094_verified_01April16_to_30June16.tid</fileName>
						<status>Verified Observed</status>
					</waterLevels>
					<tideCorrectors>
						<fileName>K371KR2015CORP.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 H12838 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 Rev 1.  For H12838, 8768094 Calcasieu Pass, LA was the source of all final verified water level heights for determining correctors to soundings.  All data for H12838 were contained within three tide zones (WGM400, WGM401, and WGM407) 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 H12838 bathymetry data.  

</discussion>
				<comments/>
			</standard_or_ERZT>
			<VDATUM_or_constantSep used="false">
				<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>Smart 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 Rev 1 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 H12838 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 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 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 16/16 (20 April 2016) until week 27/16 (06 July 2016).

H12838 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.
</discussion>
				<comments/>
			</dr:methods>
			<dr:charts>
				<rasterChart>
					<chart>
						<number>11341</number>
						<kapp>124</kapp>
						<scale>80000</scale>
						<edition>44</edition>
						<editionDate>2013-03</editionDate>
						<LNMDate>2016-07-19</LNMDate>
						<NMDate>2016-07-16</NMDate>
					</chart>
					<discussion>Chart 11341 covers the H12838 survey area west of 093° 19’ 00.88”W.

CUBE depths within sheet H12838 agreed with the charted depths across most of the survey area and were generally within ±5 feet of the charted depths.  There were discrete areas where the depths varied as much as 10 feet such as in 29° 15’ 46.26”N 093° 24’ 35.26”W.

The charted dangerous wreck labeled PA in approximately 29° 16’ 30.35”N 093° 20’ 35.87”W was not found.  A search radius of at least 160 meters was covered by 200% side scan and resulting 100% multibeam coverage around this position.  See Section D.1.4 for more details.

The charted 53-foot dangerous wreck labeled Wk in approximately 29° 15’ 37.08”N 093° 20’ 08.90”W was found with a CUBE depth of 53.550 feet in 29° 15’ 37.08”N 093° 20’ 08.90”W (Feature 03, DTON 01).  See Sections D.1.6 for more details.

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).

</discussion>
					<comments/>
				</rasterChart>
				<rasterChart>
					<chart>
						<number>11344</number>
						<kapp>123</kapp>
						<scale>80000</scale>
						<edition>40</edition>
						<editionDate>2014-08</editionDate>
						<LNMDate>2016-07-19</LNMDate>
						<NMDate>2016-07-16</NMDate>
					</chart>
					<discussion>Chart 11344 covers the H12838 survey area east of 093° 21’ 00.47”W.

CUBE depths within sheet H12838 agreed with the charted depths across most of the survey area and were generally within ±3 feet of the charted depths.

The charted dangerous wreck labeled PA in approximately 29° 16’ 29.98”N 093° 20’ 36.25”W was not found.  A search radius of at least 160 meters was covered by 200% side scan and resulting 100% multibeam coverage around this position.  See Section D.1.4 for more details.

The charted 53-foot dangerous wreck labeled Wk in approximately 29° 15’ 37.08”N 093° 20’ 08.90”W was found with a CUBE depth of 53.550 feet in 29° 15’ 37.08”N 093° 20’ 08.90”W (Feature 03, DTON 01).  See Sections D.1.6 for more details.

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).
</discussion>
					<comments/>
				</rasterChart>
				<ENC>
					<chart>
						<name>US4LA10M</name>
						<scale>80000</scale>
						<edition>10</edition>
						<issueDate>2016-07-21</issueDate>
						<preliminary>false</preliminary>
						<updateApplicationDate>2014-11-03</updateApplicationDate>
					</chart>
					<discussion>ENC US4LA10M covers the H12838 survey area, west of 093° 21’ 00.53”W. 

CUBE depths within sheet H12838 agreed with the charted depths across most of the survey area and were generally within ±2 meter of the charted depths. 

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).

</discussion>
					<comments/>
				</ENC>
				<ENC>
					<chart>
						<name>US4LA14M</name>
						<scale>80000</scale>
						<edition>16</edition>
						<issueDate>2016-07-22</issueDate>
						<preliminary>false</preliminary>
						<updateApplicationDate>2012-09-05</updateApplicationDate>
					</chart>
					<discussion>ENC US4LA14M covers the H12838 survey area, east of 093° 21’ 00.53”W. 

CUBE depths within sheet H12838 agreed with the charted depths across most of the survey area and were generally within ±2 meter of the charted depths.

The charted dangerous wreck with least depth unknown in 29° 16’ 29.21”N 093° 20’ 36.29”W (from ENC) or 29° 16’ 29.21”N 093° 20’ 36.30”W (from CSF) was not found.  A search radius of at least 160 meters was covered by 200% side scan and resulting 100% multibeam coverage around these positions.  See Section D.1.4 for more details.

The charted 16.1-meter dangerous wreck in 29° 15’ 37.10”N 093° 20’ 08.90”W was found with a CUBE depth of 16.322 meters in 29° 15’ 37.08”N 093° 20’ 08.90”W (Feature 03, DTON 01).  See Sections D.1.6 for more details.

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).

</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>There was one charted dangerous Wreck PA within the survey bounds of H12838 in 29° 16’ 29.21”N 093° 20’ 36.29”W (from ENC) or 29° 16’ 29.21”N 093° 20’ 36.30”W (from CSF) which was not found.  A search radius of at least 160 meters was covered by 200% side scan and 100% multibeam around these positions.  There were no significant contacts or features identified within the coverage of the search radius.  This charted dangerous Wreck PA falls on raster charts 11341 and 11344, as well as ENC US4LA14M, and is recommended to be deleted from all charts as stated in the H12838 S-57 Final Feature File (FFF).</discussion>
				</results>
				<comments/>
			</dr:chartedFeatures>
			<dr:unchartedFeatures>
				<results investigated="Investigated">
					<discussion>See the S-57 Final Feature File (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>H12838_DTON01.000</title>
						<dateSubmitted>2016-07-12</dateSubmitted>
					</report>
					<report>
						<title>H12838_DTON02.000</title>
						<dateSubmitted>2016-07-13</dateSubmitted>
					</report>
					<discussion>Leidos submitted two Danger to Navigation Reports (DTON) in S-57 format to the Atlantic Hydrographic Branch (AHB) for H12838.  AHB did not submit DTON02 to the Nautical Data Branch (NDB)/Marine Chart Division (MCD), but rather submitted a Navigation Manager Report to the to the Office of Coast Surveys (OCS) Navigation Manager.  AHB did submit DTON01 to MCD.  Copies of the AHB verification email and AHB DTON report, in PDF format, submitted to the Nautical Data Branch (NDB)/Marine Chart Division (MCD) are included in a sub-directory within Appendix II of this Data Report.  Also included is the Navigation Manager Report, which AHB submitted for DTON02.  Figure 6 provides a list of DTONs and their associated Feature number and object class in the H12838 S-57 FFF.</discussion>
					<images>
						<caption>DTON Feature Numbers</caption>
						<link>file:///SupportFiles/H12838_Figure_6.jpg</link>
					</images>
				</results>
				<comments/>
			</dr:DTONS>
			<dr:shoalAndHazardousFeatures>
				<results investigated="None Exist">
					<discussion>All hazardous features were discussed in Sections D.1.1 and D.1.2 for each chart, Section D.1.6, and the H12838 S-57 Final Feature File (FFF).</discussion>
				</results>
				<comments/>
			</dr:shoalAndHazardousFeatures>
			<dr:channels>
				<results investigated="None Exist">
					<discussion>There were no channels within the area covered by H12838. </discussion>
				</results>
				<comments/>
			</dr:channels>
			<dr:bottomSamples>
				<results investigated="Investigated">
					<discussion>In accordance with both the Project Instructions and Section 7.1 of the HSSD, bottom characteristics were obtained for H12838.  Bottom characteristics were acquired at the five 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 H12838 are included in the H12838 S-57 FFF, H12838.FFF.000, within the Seabed Area (SBDARE) object and are 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 Composite Source File (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 H10890, H10891, H12730, and H12731 (collected in 1999, 2015, 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 area of H12838. </discussion>
				</results>
				<comments/>
			</dr:ATONS>
			<dr:overheadFeatures>
				<results investigated="None Exist">
					<discussion>There were no overhead features within the H12838 survey area.</discussion>
				</results>
				<comments/>
			</dr:overheadFeatures>
			<dr:submarineFeatures>
				<results investigated="Investigated">
					<discussion>One pipeline (PIPSOL) object is delivered in the S-57 FFF (Feature 02) to represent a section of exposed pipeline found, utilizing both multibeam and side scan sonar data, within the bounds of H12838.  See Section D.1.6 for additional information.  Additional charted pipelines fall within the H12838 survey coverage; however, the multibeam and side scan sonar 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 H12838 survey area.</discussion>
				</results>
				<comments/>
			</dr:ferryRoutesAndTerminals>
			<dr:platforms>
				<results investigated="Investigated">
					<discussion>Eight platforms are charted within the bounds of H12838 and all eight were not found; an area with a radius of at least 80 meters was covered by 200% side scan sonar and 100% multibeam for each charted platform.  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, H12838.FFF.000, Offshore Platform (OFSPLF) objects, for details and charting recommendations on each platform.</discussion>
				</results>
				<comments/>
			</dr:platforms>
			<dr:significantFeatures>
				<results investigated="Investigated">
					<discussion>During data acquisition on H12838, intermittent adverse weather conditions and sea state were observed, in many cases causing the survey to be suspended due to the achievable data quality.  Many of these localized weather events caused an observed offset between the survey area and the water level gauge located at Calcasieu Pass, LA.  The adverse weather conditions also resulted in heave artifacts visible in the final CUBE surface of H12838.  However, the vertical offsets and heave artifacts observed were within the IHO Order 1a allowable vertical and horizontal uncertainty for the H12838 water depths.  See Section B.2.6 for more information regarding the water level offsets and heave artifacts.

No other significant features as defined in Section 8.1.4 of the HSSD exist within the H12838 survey area.</discussion>
				</results>
				<comments/>
			</dr:significantFeatures>
			<dr:constructionOrDredging>
				<results investigated="None Exist">
					<discussion>No construction or dredging exists for the H12838 survey.</discussion>
				</results>
				<comments/>
			</dr:constructionOrDredging>
			<dr:newSurveyRecommendation>
				<results recommended="false">
					<discussion>No new survey recommendations are made for the area covered by the H12838 survey.</discussion>
				</results>
				<comments/>
			</dr:newSurveyRecommendation>
			<dr:insetRecommendation>
				<results recommended="false">
					<discussion>No inset recommendations are made for the area covered by the H12838 survey.</discussion>
				</results>
				<comments/>
			</dr:insetRecommendation>
			<dr:otherResults>
				<issue>
					<title>Designated Soundings</title>
					<discussion>Designated soundings are used to help better preserve the shallowest sounding relative to the computed depth surface.  Separate flags exist in the GSF (version 3.06) for designated soundings and features.  All depths flagged as either a feature or a designated sounding in the GSF override the CUBE best estimate of the depth in the final BAG file.  Both the designated sounding and feature flags as defined within GSF are mapped to the same Hydrographic Data Cleaning System (HDCS) flag when ingested into CARIS (PD_DEPTH_DESIGNATED_MASK).  Note that there were only three feature flags set within the H12838 data and no GSF “designated soundings” were set.  Therefore, there are only three overrides to the CUBE best estimate of the depth for H12838, all of which are also presented in the S-57 FFF, H12838.FFF.000.</discussion>
					<comments/>
				</issue>
				<issue>
					<title>Final Feature S-57 File</title>
					<discussion>Included with the H12838 delivery is the S-57 FFF, H12838.FFF.000.  Details on how this file was generated and quality controlled can be found in Section B.2.6 of the DAPR Rev 1.  The S-57 FFF delivered for H12838 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 H12838 are included within the S-57 FFF.

In accordance with the HSSD, Leidos addressed all assigned objects within the bounds of H12838 from the provided CSF S-57 file in the delivered H12838 S-57 FFF.  Additionally, several charted objects, derived from the largest scale ENCs, were disproven by the results of this survey, and are addressed within the delivered H12838 S-57 FFF.  

For each feature contained in the FFF (S-57), 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 H12838 delivery is the Side Scan Sonar Contact S-57 File, H12838.SSCon.000.  Details on how this file was generated and quality controlled can be found in Section B.3.5 of the DAPR Rev 1.  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”.

</discussion>
					<comments/>
				</issue>
				<comments/>
			</dr:otherResults>
		</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>The BAG file, 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-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 any deficiencies noted in the Descriptive Report.  Previously submitted deliverables for OPR-K371-KR-15 are provided in the table below.  Note that there were no sea turtle sightings and therefore there is no associated deliverable listed.</dr:adequacyOfSurvey>
			<dr:additionalInfo/>
		</dr:statements>
		<dr:signingPersonnel>
			<approverName>Alex T. Bernier</approverName>
			<approverTitle>Lead Hydrographer</approverTitle>
			<approvalDate>2016-08-29</approvalDate>
		</dr:signingPersonnel>
		<dr:additionalReports>
			<reportName>OPR-K371-KR-15_DAPR.pdf</reportName>
			<reportDateSent>2016-02-12</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>OPR-K371-KR-15_Coast Pilot Review Report.pdf</reportName>
			<reportDateSent>2016-02-12</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12727_DR.pdf</reportName>
			<reportDateSent>2016-02-12</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12728_DR.pdf</reportName>
			<reportDateSent>2016-02-26</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12729_DR.pdf</reportName>
			<reportDateSent>2016-03-24</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12730_DR.pdf</reportName>
			<reportDateSent>2016-03-30</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>OPR-K371-KR-15_DAPR_rev1.pdf</reportName>
			<reportDateSent>2016-08-11</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>H12731_DR.pdf</reportName>
			<reportDateSent>2016-08-11</reportDateSent>
		</dr:additionalReports>
		<dr:additionalReports>
			<reportName>OPR-K371-KR-15_Marine_Mammal_Observation_Log.pdf</reportName>
			<reportDateSent>2016-08-29</reportDateSent>
		</dr:additionalReports>
	</dr:approvalSheet>
</dr:descriptiveReport>
