<?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:metadata><ns1:projectMetadata><ns2:number>OPR-D304-FH-15</ns2:number><ns2:name>Approaches to Chesapeake Bay</ns2:name><ns2:generalLocality>Approaches to Chesapeake Bay</ns2:generalLocality><ns2:fieldUnit>NOAA Ship FERDINAND R. HASSLER</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12843</ns2:registryNumber><ns2:sheetID>5</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>13 Miles East of Sheep House Hill</ns2:sublocality><ns2:stateOrTerritory>North Carolina</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>LCDR Briana J. Welton, NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-07-24</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-08-05</ns2:start><ns2:end>2015-10-18</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>Survey H12843 was conducted in the Chesapeake Bay, with a sublocality of 13 Miles East of Sheep House Hill as shown in Figure 1.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">36.5950265556</ns2:latitude><ns2:longitude hemisphere="W">75.6955230556</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">36.4240038056</ns2:latitude><ns2:longitude hemisphere="W">75.5935755556</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12843 survey limits</ns2:caption><ns2:link>SupportFiles\H12843_Area_Surveyed.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey Limits were extended to the East to include the portion of H12842.  Survey H12842 was opened, but only a small amount of acquisition was conducted on the sheet and was then merged into H12843 for processing efficiency.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><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 the Bureau of Ocean Energy Management (BOEM) research in the area.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete Multibeam with Backscatter</ns2:requiredCoverage></ns2:coverageRequirement><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:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Survey layout for OPR-D304-FH-15 over raster chart 12200.</ns2:caption><ns2:link>SupportFiles\H12843_Coverage_Overview.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S250</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>1026.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>57.0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>1026.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>57.0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>5.5</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>8</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>51.0</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-08-05</ns2:surveyDates><ns2:surveyDates>2015-08-06</ns2:surveyDates><ns2:surveyDates>2015-08-13</ns2:surveyDates><ns2:surveyDates>2015-08-14</ns2:surveyDates><ns2:surveyDates>2015-08-18</ns2:surveyDates><ns2:surveyDates>2015-08-20</ns2:surveyDates><ns2:surveyDates>2015-08-21</ns2:surveyDates><ns2:surveyDates>2015-08-22</ns2:surveyDates><ns2:surveyDates>2015-08-27</ns2:surveyDates><ns2:surveyDates>2015-08-28</ns2:surveyDates><ns2:surveyDates>2015-09-03</ns2:surveyDates><ns2:surveyDates>2015-09-09</ns2:surveyDates><ns2:surveyDates>2015-10-18</ns2:surveyDates><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:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><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:vessels><ns1:vessel><ns2:hullID>S250</ns2:hullID><ns2:LOA units="meters">37.7</ns2:LOA><ns2:draft units="meters">3.77</ns2:draft></ns1:vessel><ns1:images><ns2:caption>NOAA Ship FERDINAND R. HASSLER</ns2:caption><ns2:link>SupportFiles\Hassler_stern_bow_clean.png</ns2:link></ns1:images><ns1:discussion>NOAA Ship FERDINAND R. HASSLER (S250), shown in Figure 3, acquired all surveyed soundings during operation for H12843</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V 320 V5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Hemisphere</ns2:manufacturer><ns2:model>MBX-4</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML</ns2:manufacturer><ns2:model>MicroCTD</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Brooke Ocean</ns2:manufacturer><ns2:model>MVP-200</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>RESON</ns2:manufacturer><ns2:model>SVP-70</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea Bird</ns2:manufacturer><ns2:model>SBE 19+</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>A geographic plot of crosslines is shown in Figure 4. It should be noted that crossline coverage did not reach the eastern extent of the survey area, leaving the six easternmost mainscheme lines without a crossline.  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.45 meters and 0.80 meters. The statistical analysis of the differences between the mainscheme and crossline surfaces is sown in Figure 5. The average difference between the surfaces is -0.04 meters with a standard deviation of 0.08 meters; Ninety-five percent of nodes agree within +/- 0.16 meters of the mean.</ns2:discussion><ns2:images><ns2:caption>Location of crosslines for H12843.</ns2:caption><ns2:link>SupportFiles\H12843_XL_MS_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12843 crossline difference statistics: mainscheme minus crossline. </ns2:caption><ns2:link>SupportFiles\H12843_MS-XL.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.01</ns2:measured><ns2:zoning units="meters">0.102</ns2:zoning><ns2:tideMethod>VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S250</ns2:hullID><ns2:measuredCTD units="meters/second">1.0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1.0</ns2:measuredMVP><ns2:surface units="meters/second">0.5</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Two tidal models were available for water level corrections associated with survey H12843. 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 H12843 were reduced to MLLW via VDatum. This model functioned as a gridded separation model for GPS tide computations with a 0.102 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: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:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>Two prior surveys to the north junctions with H12843. See Figure 7 for further information.</ns2:discussion><ns2:images><ns2:caption>H12843 Junction Survey</ns2:caption><ns2:link>SupportFiles\H12843_Junction_Location.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12306</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2011</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>Survey H12843 junctions with survey H12306 with nodes overlapping approximately 20 to 150 meters to the north (See Figure 8). The minimum and maximum depth difference between the two surveys is -2.09 meters and 1.59 meters respectively. Of the greater than one hundred and eighteen thousand overlapping nodes, the average difference is -0.03 meters with a standard deviation of 0.35 meters; Ninety-five percent of the differenced surface nodes are within +/- 0.72 meters of the mean, as shown in Figure 9.</ns2:discussion><ns2:images><ns2:caption>Area of overlap between H12843 and H12306.</ns2:caption><ns2:link>SupportFiles\H12843-H12306_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics for H12843 and H12306.</ns2:caption><ns2:link>SupportFiles\H12843-H12306_Difference.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12341</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2011</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>Survey H12843 junctions with survey H12341 with nodes overlapping approximately 30 to 230 meters to the north. The junction was made using the provided survey outlines from the Project Instructions. There are two gaps in data between the two junction surveys that are not covered by side scan data, as shown in the red boxes in Figure 10. The minimum and maximum depth difference between the two surveys is -1.58 meters and 1.57 meters respectively. Of the greater than one hundred and eighteen thousand (118,000) overlapping nodes, the average difference is -0.02 meters with a standard deviation of 0.32 meters; Ninety-five percent of the differenced surface nodes are within +/- 0.64 meters of the mean, as shown in Figure 11.</ns2:discussion><ns2:images><ns2:caption>Area of overlap between H12843 and H12341.</ns2:caption><ns2:link>SupportFiles\H12843-H12341_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics for H12843 and H12341.</ns2:caption><ns2:link>SupportFiles\H12843-H12341_Difference.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Sound Speed Errors</ns2:title><ns2:discussion>Refraction issues due to environmental conditions exist in survey H12843. As shown in Figure 12, the likely culprit was the very steep below-layer gradient which moved up and down in the water by about 10 meters per second which were very present on data collected between DN217-226 (See Figure 13). 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.

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 DN226 and 227 do not exhibit the extreme refraction issues seen on the earlier days. 

To mitigate the impacts of refraction on data that was already collected, the hydrographer utilized Subset Editor in CARIS HIPS/SIPS to further eliminate poor data. This did not eliminate all instances of refraction in H12843. 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:images><ns2:caption>Sound speed measurements related to H12843.</ns2:caption><ns2:link>SupportFiles\H12843_AllSVP.tif</ns2:link></ns2:images><ns2:images><ns2:caption>Sound speed measurements on from DN217-226.</ns2:caption><ns2:link>SupportFiles\H12843_217-226SVP.tif</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>A total of 484 sound speed measurements were taken within the boundaries of H12843 (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 1 hour (for DN 230, 232, 233, and 234), 2 hours (DN 246, 252, and 291), and 4 hours (DN 217, 218, 225, 226, 239, and 240).</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:images><ns2:caption>H12843 sound speed profile locations.</ns2:caption><ns2:link>SupportFiles\H12843_SV_cast_locations.png</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>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 H12843. 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 plug-ins 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.
H12843_S250_Port_400kHz | 4m resolution mosaic | Absorption Coefficient = 100dB/km
H12843_S250_Stbd_400kHz | 4m resolution mosaic | Absorption Coefficient = 100dB/km</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_3</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12843_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">14.08</ns2:min><ns2:max units="meters">30.20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12843_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">14.08</ns2:min><ns2:max units="meters">20.00</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12843_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">13.93</ns2:min><ns2:max units="meters">28.21</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12843_MB_2m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18.00</ns2:min><ns2:max units="meters">28.21</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>Gaps in data coverage (holidays) do exist in the 1-meter finalized surface (See Figures 15-16). These gaps in coverage are due to poor overlap in the outerbeams. The holidays occur in flat areas and the hydrographer believes that they do not pose a risk to surface navigation.</ns1:discussion><ns1:images><ns2:caption>Example of holiday in the 1-meter finalized surface. </ns2:caption><ns2:link>SupportFiles\H12843_1m_Holiday_2.png</ns2:link></ns1:images><ns1:images><ns2:caption>Example of holiday in the 1-meter finalized surface</ns2:caption><ns2:link>SupportFiles\H12843_1m_Holiday_3.png</ns2:link></ns1:images><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>Data Density</ns2:title><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 17 and 18).</ns2:discussion><ns2:images><ns2:caption>Data density for the 1-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12843_MB_1m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Data density for the 2-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12843_MB_2m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Total Vertical Uncertainty Analysis</ns2:title><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 only one node failed to meet TVU specifications (See Figures 19 and 20). In addition, a custom layer was created for the finalized surfaces submitted in correlation with H12843. 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:images><ns2:caption>Total vertical uncertainty analysis for 1-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12843_MB_1m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>Total vertical uncertainty analysis for 2-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\H12843_MB_2m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Designated Soundings</ns2:title><ns2:discussion>Within the limits of H12843, two (2) soundings are flagged as designated.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><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:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="false"><ns2:tideStations/><ns2:correctorFiles/><ns2:finalTides><ns2:dateSubmitted xsi:nil="true"></ns2:dateSubmitted><ns2:dateReceived xsi:nil="true"></ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>VDatum</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>2015_D304_VDatum_NAD83_MLLW</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>All soundings submitted for H12843 has been reduced to MLLW using documented VDatum techniques.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>UTM Zone 18N.</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>DUCK 3, Duck, NC</ns2:HVCRSiteID><ns2:stationID>NCDU</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>LOYOLA, Virginia Beach, VA</ns2:HVCRSiteID><ns2:stationID>LS03</ns2:stationID></ns2:CORSStations></ns2:baseStations><ns2:discussion>Single Base processing was the primary method used for 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 H12843 and are used to reduce acquired soundings to MLLW via HSD Operations Branch provided separation model.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Driver, VA (289 kHz)</ns2:name></ns2:USCGStations><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>Interpolation of SBETs</ns2:title><ns2:discussion>On occasion, SBET altitude spikes compromised the data's TVU. In these instances, Pydro's POSPAC Automated QC tool was used to interpolate the SBET (See Figure 21 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 H12843:
DN218 Starboard lines using interpolated_2015_218_S250S_b.sbet
DN225 Starboard lines using interpolated_2015_225_S250S_b.sbet</ns2:discussion><ns2:images><ns2:caption>Example of SBET interpolation for 2015_225_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\H12843_InterpolatedSBET.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Base Station Outages</ns2:title><ns2:discussion>Throughout acquisition of H12843 the preferred base station used for single base processing was DUCK. During acquisition there was an outage of the DUCK station, requiring the use of an alternate station. LS03 was used, with ship to station distance ranging from 149km to 183km. Though LS03 was far outside the recommended base station range, the SBET that used LS03 was only applied on data acquired during DN 218. A vertical offset ranging from 0.3-0.5 meters can be seen in the data for line 2209 (Figures 22 and 23) due to an SBET that has periods of poor quality vertical solutions. The oscillations in the vertical solution are within the TVU specifications for the depth of the area.</ns2:discussion><ns2:images><ns2:caption>The 2-meter combined surface affected by offset.</ns2:caption><ns2:link>file:///Q:/2015/OPR-D304-FH-15_Approaches_to_Chesapeake/Surveys/H12843/Descriptive_Report/SupportFiles/SBET_Offset_Overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>DN 218, line 2209 offset shown in subset editor.</ns2:caption><ns2:link>file:///Q:/2015/OPR-D304-FH-15_Approaches_to_Chesapeake/Surveys/H12843/Descriptive_Report/SupportFiles/SBET_Offset.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><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><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12207</ns2:number><ns2:kapp>548</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>24</ns2:edition><ns2:editionDate>2014-07</ns2:editionDate><ns2:LNMDate>2016-03-22</ns2:LNMDate><ns2:NMDate>2016-04-02</ns2:NMDate></ns2:chart><ns2:discussion>A comparison was performed with Chart 12207 (1:80,000) using depths derived from a 2-meter combined surface. Most charted soundings agree within 3-4 feet of H12843 surveyed depths, with exception of the areas shown below in Figure 24.</ns2:discussion><ns2:images><ns2:caption>Chart 12207 comparison.</ns2:caption><ns2:link>file:///G:/OPR-D304-FH-15/H12843/Separates/Descriptive_Report/Report/SupportFiles/H12843_ChartComp.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4NC32M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>24</ns2:edition><ns2:updateApplicationDate>2014-07-01</ns2:updateApplicationDate><ns2:issueDate>2016-04-02</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></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 2-meter finalized surface from survey H12843. The depth differences range from -6.22 to 5.91 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.16 meters, shown in Figure 25. In general, surveyed depths were deeper than charted. Figure 26 shows a surface created by interpolating the differenced point cloud between the ENC and surveyed depths. Negative values indicate areas where surveyed depths are deeper than charted.</ns2:discussion><ns2:images><ns2:caption>ENC US4NC32M comparison.</ns2:caption><ns2:link>SupportFiles\H12843-US4NC32M.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface between ENC US4NC32M and H12842.</ns2:caption><ns2:link>SupportFiles\H12843-US4NC32M_Diff.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> One new wreck was identified with data collected for survey H12843. See the final feature file for further information.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No Danger to Navigation Reports were submitted for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Six (6) bottom samples were acquired for this survey though one sample did not result in a return after three attempts therefore was not submitted. A total of five (5) bottom samples have been submitted in the final feature file. See final feature file for more information.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>No Significant Features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>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:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>LCDR Briana Welton, NOAA</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2016-05-27</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>LT Nicholas Morgan, NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2016-05-27</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>PS Tyanne Faulkes</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approvalDate>2016-05-27</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>