<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:approvalSheet><ns1:signingPersonnel><ns2:approvalDate>2016-05-26</ns2:approvalDate><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approverName>LCDR Briana Welton, NOAA</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2016-05-26</ns2:approvalDate><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approverName>LT Nicholas Morgan, NOAA</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2016-05-26</ns2:approvalDate><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approverName>PS Tyanne Faulkes</ns2:approverName></ns1:signingPersonnel><ns1:statements><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><ns1:supervision>Field operations for this hydrographic survey were conducted under the direct supervision of the then Chief of Party, Commander Marc S. Moser, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision></ns1:statements></ns1:approvalSheet><ns1:dataAcquisitionAndProcessing><ns1:qualityControl><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="false"><ns2:issue><ns2:comments/><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results></ns1:equipmentEffectiveness><ns1:coverageEquipmentAndMethods><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl><ns1:crosslines><ns2:comments/><ns2:images><ns2:caption>H12839 MBES crossline data overlaid on mainscheme data, shown in grey.</ns2:caption><ns2:link>SupportFiles\H12839_MS-XL_Geographic.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12839 crossline difference statistics: mainscheme minus crossline.</ns2:caption><ns2:link>SupportFiles\H12839_MS-XL.png</ns2:link></ns2:images><ns2:discussion>A geographic plot of crosslines is shown in Figure 4. Crosslines were filtered to remove soundings greater than 45 degrees from nadir. To evaluate crossline agreement, two 2-meter surfaces were created: one from crossline depths, the other from mainscheme depths. These two surfaces were differenced using CARIS HIPS/SIPS. The 2.6 million nodes have a difference value range from -0.89 meters and 1.84 meters. The statistical analysis of the differences between the mainscheme and crossline surfaces is shown in Figure 5. The average difference between the surfaces is 0.06 meters with a standard deviation of 0.09 meters; Ninety-five percent of nodes agree within +/- 0.17 meters of the mean.</ns2:discussion></ns1:crosslines><ns1:soundSpeedMethods><ns1:images><ns2:caption>H12839 sound speed profile locations.</ns2:caption><ns2:link>SupportFiles\H12839_SV_Locations.png</ns2:link></ns1:images><ns1:castFrequency>A total of 484 sound speed measurements were taken within the boundaries of H12839 (See Figure 14). These sound speed measurements were collected using the MVP-200 approximately every 30 minutes. Comparisons were made by the survey watch to assess sound speed variation in the water column. 

Sound speed corrections were applied in CARIS HIPS/SIPS using Nearest in Distance Within Time (NIDWT) of every 4 hours for the entire survey. </ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Sound speed measurements related to H12839.</ns2:caption><ns2:link>SupportFiles\H12839_Refraction_1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Ray tracing analysis.</ns2:caption><ns2:link>SupportFiles\H12839_Refraction_2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example of two sound speed profiles from DN217 which were taken 18 minutes apart.</ns2:caption><ns2:link>SupportFiles\H12839_Refraction_3.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example where the surface shows signs of refraction in H12839.</ns2:caption><ns2:link>SupportFiles\H12839_Refraction_4.png</ns2:link></ns2:images><ns2:images><ns2:caption>Subset of refraction data.</ns2:caption><ns2:link>SupportFiles\H12839_Refraction_5.png</ns2:link></ns2:images><ns2:discussion>Refraction issues due to environmental conditions exist in survey H12839. As shown in Figure 9, the likely culprit was the mid-water column thermocline which resides between 10 and 20 meters. This thermocline saw sound speed variations of up to 30 meters per second. 

A ray tracing uncertainty analysis was performed to help identify casts that exceeded the allowance for refraction as defined in Section 5.2.3.4 Error Budget Analysis for Depths (See Figure 10). The blue lines in the graph are consecutive cast comparisons and the red dots are the allowable vertical error due to refraction. In cases where the blue line exceeds the red dots, those are examples of where the estimations show the allowable refraction error is being exceeded. As we can see, refraction issues are present on data collected between DN217 to DN220 and DN235 to DN236. Sound speed casts were taken at a very frequent rate, yet refraction still was an issue, because it was believed that the sound speed variability in nature, specifically, the survey lines may have crossed a significant below-layer sound speed gradient. An example from DN217 shows two profiles which were taken only 18 minutes apart, yet the estimated outerbeam refraction error is 0.658m (See Figure 11). 

A number of methods were used to mitigate the refraction. Initially the sonars were being operated using its entire 140 degree swath. After an in port in Norfolk, VA the hydrographer instituted two changes: the use of Cast-Time to model these refraction issues and the decrease in swath width. This change most likely is the reason why data from DN238 and 239 do not exhibit the extreme refraction issues seen on the earlier days.

To mitigate the impacts of refraction on data that was already collected, a number of methods were used. First, lines from DN217, DN219, and DN220 were filtered to 66 degrees on the port side for port lines and 66 degrees on the starboard side for starboard lines. Filtered lines were then inspected by the hydrographer to ensure they did not cause holidays or remove data from the tops of shoals or features. In areas this did occur, data was re-accepted by the hydrographer in subset editor. Secondly the hydrographer utilized Subset Editor in CARIS HIPS/SIPS to further eliminate poor data (See Figures 12 and 13). 

This did not eliminate all instances of refraction in H12839. Though the data does not meet allowable error budget for refraction, the surfaces do meet the Total Vertical Uncertainty requirements (See Section B.5.4 Total Vertical Uncertainty Analysis in this report for more information).  </ns2:discussion><ns2:title>Sound Speed Errors</ns2:title></ns2:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:sonarQCChecks><ns2:comments/><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results></ns1:sonarQCChecks><ns1:junctions><ns2:comments/><ns2:images><ns2:caption>Junction associated with survey H12839.</ns2:caption><ns2:link>SupportFiles\H12839_Junctions_1.png</ns2:link></ns2:images><ns2:discussion>One contemporary survey, to the west, junctions with H12839. See Figure 7 for further information.</ns2:discussion><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Difference surface statistics for H12839 and H12840.</ns2:caption><ns2:link>SupportFiles\H12839-H12840.png</ns2:link></ns2:images><ns2:discussion>Survey H12839 junctions with its contemporary survey H12840. Nodes overlap approximately 200 meters to the west. The minimum and maximum depth difference between the two surveys is -1.07 meters and 1.14 meters respectively. Of the greater than 505 thousand overlapping nodes, the average difference is 0.14 meters with a standard deviation of 0.09 meters; Ninety-five percent of the differenced surface nodes are within +/- 0.17 meters of the mean, as shown in Figure 8.</ns2:discussion><ns2:survey><ns2:scale>40000</ns2:scale><ns2:relativeLocation>W</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship FERDINAND R. HASSLER</ns2:fieldUnit><ns2:year>2015</ns2:year><ns2:registryNumber>H12840</ns2:registryNumber></ns2:survey></ns2:junction></ns1:junctions><ns1:uncertainty><ns2:comments/><ns2:images><ns2:caption>Sources of error data applied during CARIS processing.</ns2:caption><ns2:link>SupportFiles\H12839_uncertainty_source.png</ns2:link></ns2:images><ns2:discussion>Two tidal models were available for water level corrections associated with survey H12839. A discrete tide zone file, produced by CO-OPS for project OPR-B304-FH-15, was provided to the field unit. Additionally, a vertical datum transformation (VDatum) model was delivered to the field unit in the project instructions. All data for survey H12839 were reduced to MLLW via VDatum. This model functioned as a gridded separation model for GPS tide computations with a 0.081 meter uncertainty. Final TPU calculations are derived from the following sources: VDatum separation model, sound velocity (MVP and surface sound velocimeter), HVF uncertainties, and SBET post processed uncertainty. Error data sources applied through CARIS processing software are listed in Figure 6.</ns2:discussion><ns2:values><ns2:tideUncertainty><ns2:tideMethod>VDATUM</ns2:tideMethod><ns2:zoning units="meters">0.102</ns2:zoning><ns2:measured units="meters">0.01</ns2:measured></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>S250</ns2:hullID><ns2:measuredCTD units="meters/second">1</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values></ns1:uncertainty></ns1:qualityControl><ns1:dataProcessing><ns1:surfaces><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/><ns1:surface><ns2:depthRange><ns2:max units="meters">42.38</ns2:max><ns2:min units="meters">23.55</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:surfaceName>H12839_MB_2m_MLLW</ns2:surfaceName><ns2:resolution units="meters">2</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType></ns1:surface><ns1:surface><ns2:depthRange><ns2:max units="meters">40.00</ns2:max><ns2:min units="meters">23.55</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:surfaceName>H12839_MB_2m_MLLW_Final</ns2:surfaceName><ns2:resolution units="meters">2</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType></ns1:surface><ns1:surface><ns2:depthRange><ns2:max units="meters">42.30</ns2:max><ns2:min units="meters">23.56</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H12839_MB_4m_MLLW</ns2:surfaceName><ns2:resolution units="meters">4</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType></ns1:surface><ns1:surface><ns2:depthRange><ns2:max units="meters">42.30</ns2:max><ns2:min units="meters">36.00</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H12839_MB_4m_MLLW_Final</ns2:surfaceName><ns2:resolution units="meters">4</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType></ns1:surface></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Data density of the 2-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12839_MB_2m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Data density of the 4-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12839_MB_4m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:discussion>A density analysis was run to calculate the number of soundings per surface node. The results determined that 99.9% of all nodes contained five or more soundings which meets the data density specifications (See Figures 15 and 16).</ns2:discussion><ns2:title>Data Density</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Total vertical uncertainty analysis for 2-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12839_MB_2m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>Total vertical uncertainty analysis for 4-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12839_MB_4m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:discussion>Pydro's Finalized CSAR QA tool was used to calculate the percentage of nodes which meet total vertical uncertainty (TVU) specifications. The resulting statistical analysis yielded 99.9% nodes both surfaces meet TVU specifications (See Figures 17 and 18). In addition, a custom layer was created for the finalized surfaces submitted in correlation with H12839. The layer was derived from the difference between the calculated uncertainties of individual nodes and the allowable uncertainty at the coupled node. </ns2:discussion><ns2:title>Total Vertical Uncertainty Analysis</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:discussion>Within the limits of H12839, one (1) sounding is flagged as designated. </ns2:discussion><ns2:title>Designated Soundings</ns2:title></ns2:issue></ns1:additionalDataProcessing><ns1:drSoftware><ns1:featureObjectCatalog>NOAA Profile V_5_3</ns1:featureObjectCatalog><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:version xsi:nil="true"></ns1:version><ns1:name xsi:nil="true"></ns1:name></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:version xsi:nil="true"></ns1:version><ns1:name xsi:nil="true"></ns1:name></ns1:imagerySoftware><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware></ns1:dataProcessing><ns1:echoSoundingCorrections><ns1:corrections><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results></ns1:corrections><ns1:calibrations><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:discussion>Backscatter was logged in RESON datagram 7008 snippets record in the raw .s7k files. The .s7k file also holds the navigation record and bottom detections for all lines of survey H12839. The files were paired with the CARIS HDCS data, imported, and processed using Fledermaus Geocoder Toolbox (FMGT). The FMGT projects and backscatter mosaic imagery is included in the field submission. The processed mosaic is formated as a geo-referenced tiff image per specifications. The following information is provided as metadata for the processing branch:

Backscatter data processing and mosaicing performed in Fledermaus FMGT version 7.4.4b using Reson De-TVG plugins where appropriate.
Backscatter data has a histogram range of 10 to -70dB
Backscatter data is provided in separate layers broken down by survey vessel hull number and sonar operating frequency.
	H12839_S250_Port_400kHz	|	4m resolution mosaic	|	Absorption Coefficient = 100dB/km
	H12839_S250_Stbd_400kHz	|	4m resolution mosaic	|	Absorption Coefficient = 100dB/km</ns2:discussion></ns2:results></ns1:backscatter><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:equipment><ns1:majorSystem><ns2:model>7125</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>POS M/V 320 V5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>MBX-4</ns2:model><ns2:manufacturer>Hemisphere</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>MicroCTD</ns2:model><ns2:manufacturer>AML</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>MVP-200</ns2:model><ns2:manufacturer>Brooke Ocean</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SVP-70</ns2:model><ns2:manufacturer>RESON</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SBE 19+</ns2:model><ns2:manufacturer>Sea Bird</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:vessels><ns1:images><ns2:caption>NOAA Ship FERDINAND R. HASSLER</ns2:caption><ns2:link>SupportFiles\Hassler_stern_bow_clean.png</ns2:link></ns1:images><ns1:vessel><ns2:LOA units="meters">37.7</ns2:LOA><ns2:hullID>S250</ns2:hullID><ns2:draft units="meters">3.77</ns2:draft></ns1:vessel><ns1:discussion>NOAA Ship FERDINAND R. HASSLER (S250), shown in Figure 3, acquired all surveyed soundings during operation for H12839</ns1:discussion><ns1:comments/></ns1:vessels><ns1:comments/></ns1:equipmentAndVessels></ns1:dataAcquisitionAndProcessing><ns1:areaSurveyed><ns1:areaDescription><ns2:comments/><ns2:images><ns2:caption>H12839 Survey Limits</ns2:caption><ns2:link>SupportFiles\H12839_SurveyLayout.png</ns2:link></ns2:images><ns2:discussion>Survey H12839 was conducted in the Chesapeake Bay, with a sublocality of 36 miles East of Currituck Beach as shown in Figure 1.</ns2:discussion><ns2:limits><ns2:southEast><ns2:longitude hemisphere="W">75.2163720833</ns2:longitude><ns2:latitude hemisphere="N">36.1990133333</ns2:latitude></ns2:southEast><ns2:northWest><ns2:longitude hemisphere="W">75.3081897222</ns2:longitude><ns2:latitude hemisphere="N">36.5001421111</ns2:latitude></ns2:northWest></ns2:limits></ns1:areaDescription><ns1:surveyCoverage><ns2:comments/><ns2:results deviation="false"><ns2:discussion>Survey coverage was in accordance with the requirements listed above and in the HSSD.</ns2:discussion></ns2:results><ns2:coverageRequirement><ns2:requiredCoverage>Complete Multibeam with Backscatter</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area</ns2:waterDepth></ns2:coverageRequirement></ns1:surveyCoverage><ns1:surveyStatistics><ns2:comments/><ns2:totalSurveyStats><ns2:diveOps>0</ns2:diveOps><ns2:DP>0</ns2:DP><ns2:SNM>80.2</ns2:SNM><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:bottomSamples>8</ns2:bottomSamples></ns2:totalSurveyStats><ns2:discussion>Mainscheme survey lines were run with a dual-head multibeam echosounder. Linear nautical miles were calculated using statistics from the port head.</ns2:discussion><ns2:LNM><ns2:totalLNM><ns2:MS_MBES>1112.7</ns2:MS_MBES><ns2:percentXLLNM>6.5</ns2:percentXLLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:XL_MBES_SBES>71.8</ns2:XL_MBES_SBES></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_MBES>1112.7</ns2:MS_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:XL_MBES_SBES>71.8</ns2:XL_MBES_SBES></ns2:statistics><ns2:hullID>S250</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:surveyDates>2015-07-30</ns2:surveyDates><ns2:surveyDates>2015-07-31</ns2:surveyDates><ns2:surveyDates>2015-08-05</ns2:surveyDates><ns2:surveyDates>2015-08-07</ns2:surveyDates><ns2:surveyDates>2015-08-08</ns2:surveyDates><ns2:surveyDates>2015-08-10</ns2:surveyDates><ns2:surveyDates>2015-08-11</ns2:surveyDates><ns2:surveyDates>2015-08-18</ns2:surveyDates><ns2:surveyDates>2015-08-19</ns2:surveyDates><ns2:surveyDates>2015-08-20</ns2:surveyDates><ns2:surveyDates>2015-08-23</ns2:surveyDates><ns2:surveyDates>2015-08-24</ns2:surveyDates></ns1:surveyStatistics><ns1:surveyQuality><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy></ns1:surveyQuality><ns1:coverageGraphic><ns2:caption>Survey layout for OPR-D304-FH-15 over raster chart 12200.</ns2:caption><ns2:link>SupportFiles\H12839_ProjectLayout.png</ns2:link></ns1:coverageGraphic><ns1:surveyLimits><ns2:comments/><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results></ns1:surveyLimits><ns1:surveyPurpose><ns2:comments/><ns2:discussion>The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products.  In addition, this project will improve the chart for traffic navigating the Atlantic Ocean Channel and will support Bureau of Ocean Energy Management (BOEM) research in the area.</ns2:discussion></ns1:surveyPurpose></ns1:areaSurveyed><ns1:metadata><ns1:surveyMetadata><ns2:chiefOfParty>LCDR Briana J. Welton, NOAA</ns2:chiefOfParty><ns2:year>2015</ns2:year><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone><ns2:horizontalCoordinateSystem zone="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:titlesheetRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:PIDate>2015-10-19</ns2:PIDate><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:datesOfSurvey><ns2:start>2015-07-30</ns2:start><ns2:end>2015-08-24</ns2:end></ns2:datesOfSurvey><ns2:projectType>Navigable Area</ns2:projectType></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:registryMetadata><ns2:scale>40000</ns2:scale><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:registryNumber>H12839</ns2:registryNumber><ns2:stateOrTerritory>North Carolina</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:sublocality>36 Miles East of Currituck Beach</ns2:sublocality><ns2:sheetID>1</ns2:sheetID></ns1:registryMetadata><ns1:projectMetadata><ns2:number>OPR-D304-FH-15</ns2:number><ns2:generalLocality>Approaches to Chesapeake Bay</ns2:generalLocality><ns2:name>Approaches to Chesapeake Bay</ns2:name><ns2:fieldUnit>NOAA Ship FERDINAND R. HASSLER</ns2:fieldUnit></ns1:projectMetadata></ns1:metadata><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:maritimeBoundary><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results></ns1:maritimeBoundary><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion> One new obstruction was identified with 100% multibeam data. See FFF for more information.</ns2:discussion></ns2:results></ns1:unchartedFeatures><ns1:charts><ns2:comments/><ns2:ENC><ns2:comments/><ns2:images><ns2:caption>ENC US3DE01M comparison.</ns2:caption><ns2:link>SupportFiles\H12839-US3DE01M.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface between ENC US3DE01M and H12839.</ns2:caption><ns2:link>SupportFiles\H12839-US3DE01M_2.png</ns2:link></ns2:images><ns2:chart><ns2:scale>419706</ns2:scale><ns2:updateApplicationDate>2016-01-28</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2016-01-28</ns2:issueDate><ns2:edition>17</ns2:edition><ns2:name>US3DE01M</ns2:name></ns2:chart><ns2:discussion>ENC soundings were extracted from the S-57 file and used to create an interpolated .csar surface. The interpolated surface was then differenced with the 4-meter finalized surface from survey H12839. The depth differences range from -12.87 to 11.25 meters. The high depth differences were determined to be the result of coarse resolution soundings extracted from the ENC. All other depth differences mirrored RNC depth differences, with a mean difference value of 0.19 meters, shown in Figure 22. In general, surveyed soundings were deeper than charted. Figure 23 shows a surface created by interpolating the differenced point cloud between the ENC and surveyed soundings. Negative values indicate areas where surveyed soundings are deeper than charted.</ns2:discussion></ns2:ENC><ns2:ENC><ns2:comments/><ns2:images><ns2:caption>ENC US4NC31M comparison.</ns2:caption><ns2:link>SupportFiles\H12839-US4NC31M.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface between ENC US4NC31M and H12839.</ns2:caption><ns2:link>SupportFiles\H12839-US4NC31M_2.png</ns2:link></ns2:images><ns2:chart><ns2:scale>80000</ns2:scale><ns2:updateApplicationDate>2014-10-09</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2016-03-07</ns2:issueDate><ns2:edition>18</ns2:edition><ns2:name>US4NC31M</ns2:name></ns2:chart><ns2:discussion>ENC soundings were extracted from the S-57 file and used to create an interpolated .csar surface. The interpolated surface was then differenced with the 4-meter finalized surface from survey H12839. The depth differences range from -5.27 to 3.86 meters. The high depth differences were determined to be the result of coarse resolution soundings extracted from the ENC. All other depth differences mirrored RNC depth differences, with a mean difference value of -1.20 meters, shown in Figure 24. In general, surveyed soundings were deeper than charted. Figure 25 shows a surface created by interpolating the differenced point cloud between the ENC and surveyed soundings. Negative values indicate areas where surveyed soundings are deeper than charted.</ns2:discussion></ns2:ENC><ns2:rasterChart><ns2:comments/><ns2:images><ns2:caption>Chart 12200 comparison.</ns2:caption><ns2:link>SupportFiles\H12839_Chart12200_Comp.png</ns2:link></ns2:images><ns2:chart><ns2:editionDate>2014-05</ns2:editionDate><ns2:scale>419706</ns2:scale><ns2:number>12200</ns2:number><ns2:edition>51</ns2:edition><ns2:LNMDate>2016-02-27</ns2:LNMDate><ns2:NMDate>2016-02-23</ns2:NMDate><ns2:kapp>526</ns2:kapp></ns2:chart><ns2:discussion>A comparison was performed with Chart 12200 (1:419,706) using soundings derived from a 4-meter combined surface, shown in Figure 20. Most charted depths agree within 1-2 fathoms of H12839 surveyed soundings, with exception of the southeast portion of the survey. </ns2:discussion></ns2:rasterChart><ns2:rasterChart><ns2:comments/><ns2:images><ns2:caption>Chart 12204 comparison.</ns2:caption><ns2:link>SupportFiles\H12839_Chart12204_Comp.png</ns2:link></ns2:images><ns2:chart><ns2:editionDate>2012-12</ns2:editionDate><ns2:scale>80000</ns2:scale><ns2:number>12204</ns2:number><ns2:edition>38</ns2:edition><ns2:LNMDate>2016-02-27</ns2:LNMDate><ns2:NMDate>2016-02-23</ns2:NMDate><ns2:kapp>527</ns2:kapp></ns2:chart><ns2:discussion>A comparison was performed with Chart 12204 (1:80,000) using soundings derived from a 4-meter combined surface. Most charted depths agree within 2-3 feet of H12839 surveyed soundings, with exception of the area shown below in Figure 21. </ns2:discussion></ns2:rasterChart></ns1:charts><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results></ns1:chartedFeatures><ns1:DTONS><ns2:comments/><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No Danger to Navigation Reports were submitted for this survey.</ns2:discussion></ns2:results></ns1:DTONS><ns1:channels><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results></ns1:channels><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Eight (8) bottom samples were acquired for this survey. See final feature file for more information.</ns2:discussion></ns2:results></ns1:bottomSamples><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:methods><ns2:comments/><ns2:discussion>The hydrographer has compared a sounding plot from the surveyed area to the charted soundings. There are no charted contours to compare.</ns2:discussion></ns1:methods></ns1:chartComparison><ns1:additionalResults><ns1:insetRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results></ns1:insetRecommendation><ns1:constructionOrDredging><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results></ns1:constructionOrDredging><ns1:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results></ns1:submarineFeatures><ns1:ATONS><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>ATONs were observed during H12839 survey operations. These aids were deemed to serve their intended purposes. No positioning was performed in the field or required from the project instructions.</ns2:discussion></ns2:results></ns1:ATONS><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:priorSurveys><ns2:comments/><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Prior survey comparisons exist for this survey, but were not investigated.</ns2:discussion></ns2:results></ns1:priorSurveys><ns1:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:significantFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Significant Features exist for this survey.</ns2:discussion></ns2:results></ns1:significantFeatures><ns1:newSurveyRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results></ns1:newSurveyRecommendation><ns1:shoreline><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>A limited shoreline investigation was required by the project instructions but no shoreline coincides with H12839.</ns2:discussion></ns2:results></ns1:shoreline></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:verticalAndHorizontalControl><ns1:discussion>All vertical and horizontal control activities conducted during the course of this survey are fully addressed in the following sections. No separate HVCR is submitted.</ns1:discussion><ns1:verticalControl><ns2:comments/><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>2015_D304_VDatum_NAD83_MLLW</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>VDatum</ns2:methodsUsed><ns2:discussion>All soundings submitted for H12839 has been reduced to MLLW using documented VDatum techniques.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false"><ns2:comments/><ns2:finalTides><ns2:dateReceived xsi:nil="true"></ns2:dateReceived><ns2:dateSubmitted xsi:nil="true"></ns2:dateSubmitted></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:correctorFiles/><ns2:tideStations/></ns2:standard_or_ERZT><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum></ns1:verticalControl><ns1:additionalIssues><ns2:comments/><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Example of SBET interpolation for 2015_222_S250S. The anomalous data on the left has been edited in POSPAC AutoQC and the resultant SBET is seen on the right.</ns2:caption><ns2:link>SupportFiles\H12839_BeforeAfterSBET.png</ns2:link></ns2:images><ns2:discussion>On occasion, the SBET altitude exhibited spikes which compromised the data's ability to meet TVU specifications. In these instances, the hydrographer utilized tools in Pydro's POSPAC Automated QC tool to interpolate the SBET (See Figure 19 for an example). The interpolated SBET was exported out of the POSPAC Automated QC tool, opened in POSPAC MMS, and exported again to ensure the SBET was in the correct datum (NAD83). The new SBET contains the prefix &quot;interpolated&quot; for easy identification.

The following SBETs were interpolated for H12839:
DN219 Starboard lines using interpolated_2015_219_S250S_b.sbet
DN222 Starboard lines using interpolated_2015_222_S250S.sbet and 2015_222_S250S_b.sbet </ns2:discussion><ns2:title>Interpolation of SBETs</ns2:title></ns2:issue></ns1:additionalIssues><ns1:horizontalControl><ns2:comments/><ns2:RTK used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:PPP used="false" xsi:nil="true"/><ns2:PPK used="true"><ns2:comments/><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:discussion>Single Base processing was the primary method used for Post Processed Kinematics (PPK) processing of Applanix TrueHeave data for Smooth Best Estimate of Trajectory (SBET) production. SBET files have been loaded for all lines for survey H12839 and are used to reduce acquired soundings to MLLW via HSD Operations Branch provided separation model.</ns2:discussion><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>DUCK 3, Duck, NC</ns2:HVCRSiteID><ns2:stationID>NCDU</ns2:stationID></ns2:CORSStations></ns2:baseStations></ns2:PPK><ns2:projection>UTM Zone 18N</ns2:projection><ns2:DGPS used="true"><ns2:comments/><ns2:USCGStations><ns2:name>Driver, VA (289 kHz)</ns2:name></ns2:USCGStations><ns2:discussion>DGPS was used for real-time positioning during acquisition. All lines submitted are corrected using post-processed horizontal solutions.</ns2:discussion></ns2:DGPS></ns1:horizontalControl></ns1:verticalAndHorizontalControl></ns1:descriptiveReport>