<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-R300-KR-16</ns2:number><ns2:name>Etolin Strait</ns2:name><ns2:generalLocality>Bering Sea</ns2:generalLocality><ns2:fieldUnit>TerraSond Limited</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12949</ns2:registryNumber><ns2:sheetID>6</ns2:sheetID><ns2:registryInstructions>Registry Instructions</ns2:registryInstructions><ns2:sublocality>4 NM East of Cape Corwin</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2016</ns2:year><ns2:chiefOfParty>Andrew Orthmann</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2016-07-20</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2016-07-17</ns2:start><ns2:end>2016-08-05</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="3">WGS84</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific 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>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>A navigable area survey (H12949) was conducted in the area 4 NM East of Cape Corwin, Alaska, in accordance with the NOAA, National Ocean Service, Statement of Work (SOW), OPR-R300-KR-16, dated July 15th, 2016 and Hydrographic Survey Project Instructions dated July 20th, 2016.  Hydrographic survey data was acquired from July 17th through August 5th, 2016. Tidal data was collected from mid-June through late September, 2016. Note that this survey area was part of a modification to the original task order (work instructions dated May 12th) and added four additional survey sheets to the four previously assigned.
			
						An additional contract modification, &quot;Mod2&quot;, issued February 17th, 2017, extended the deliverables submission deadline to March 13th, 2017, due to delays associated with issuance of the final TCARI tide grid.
			
			The survey area is located at the south approach to Etolin Strait, a navigable passage off of the southwest Alaska coast. Nunivak Island lies to the west, with Nelson Island and mainland Alaska to the east. This relatively remote region of the Arctic is covered or heavily influenced by sea ice for a large portion of the year, presenting a limited ice-free season with open navigable water from approximately June through October. 
			
			Vessel traffic in the region primarily consists of barges serving nearby communities or transiting through the area to other points along Alaska's west and north coasts, bringing fuel and supplies, as well as some freighter traffic. Nunivak Island provides some of the only protection available for vessels transiting Alaska's southwest coast, a region that frequently experiences inclement weather and poor sea conditions. Traffic is relatively sparse, but has been increasing in recent years along with economic and scientific interest in the Arctic.
			
			Nearby communities are small and primarily subsistence-based. The region is not connected to the road system and communities depend on air services for connections to Bethel and on to Anchorage. No facilities exist nearby for supporting, or servicing larger vessels, with Bethel (approximately 200 NM transit) and Nome (approximately 250 NM transit) the closest port options for fueling, or limited services. During this survey--which utilized a 105' research vessel--Bethel was used for resupply, largely due to a more protected transit route. However, larger or deeper drafted vessels may favor Nome.
		
			TerraSond conducted multibeam echosounder (MBES) and side scan sonar (SSS) operations in the area in accordance with the project instructions, which specified areas requiring complete coverage (100% SSS with concurrent complete coverage MBES), and areas requiring set-spaced MBES-only. Other requirements included tidal data collection and bottom sampling.
			</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">60.087031</ns2:latitude><ns2:longitude hemisphere="W">165.686708</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">59.816436</ns2:latitude><ns2:longitude hemisphere="W">165.299453</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Survey extents and overview.</ns2:caption><ns2:link>SupportFiles\1_H12949_SurveyExtents.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey Limits were acquired in accordance with the requirements in the Project Instructions and the HSSD, with any exceptions noted below.
				
				1. Survey extents were modified on the north side from the extents provided in the Project Reference File (PRF) with the Project Instructions: In the set-spaced area only, H12949 was extended north into the area originally assigned under H12948 by approximately 2.7 km. This was done to optimize line planning to facilitate operations prior to commencement of survey operations. This made H12949 slightly larger in area (and H12948 slightly smaller). Regardless, the affected area received survey to identical specifications.
				
				Survey limits for both the 2 km wide corridor (requiring full coverage) and the set-spaced areas were achieved. Note the far western &quot;corner&quot; of the survey area, approximately 60-02-40.5 N, 165-37-09.9 W received coverage under a concurrent adjacent survey, H12868. 
				
				The specified inshore limit of hydrography (farthest offshore of either the 4 m depth contour, or the line defined by the distance seaward from the MHW line, which is equivalent to 0.8 mm at the scale of the largest scale nautical chart), was not encountered in this survey area.</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. The project (of which this survey sheet is one of eight separate, adjacent sheets) covered approximately 570 SNM of seafloor, all Priority 2 area as identified in the 2012 NOAA Hydrographic Survey Priorities document. There is an emerging need to provide modern hydrography in the Arctic to update nautical chart products. 
			
			In this project area, east of Nunivak Island, deep-draft traffic is operating in relatively shoal areas that have not been surveyed in over 100 years. A 600' chemical tanker (Champion Ebony) grounded on an uncharted shoal in this survey area on June 24th, 2016, just days before survey operations were scheduled to commence. Fortunately, no discharge occurred, but the incident emphasized the need for chart updates in the area. Refer to the concurrent survey H12950 for more information on the grounding incident.
			
			Survey data from this project is intended to supersede all prior survey data in the common area and support larger scale nautical chart products.</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 defined survey corridor</ns2:waterDepth><ns2:requiredCoverage>Full coverage: 100% Side Scan Sonar with concurrent Multibeam and Backscatter</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All survey areas outside of defined survey corridor</ns2:waterDepth><ns2:requiredCoverage>Set-spaced MBES: 500 m set line spacing Multibeam and Backscatter</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Coverage requirements were met for all areas. Lead Hydrographer's notes applicable to coverage review are as follows.
				
				Full coverage (corridor) area:
				
				Full coverage was achieved in the defined survey corridor. Coverage in the corridor area conforms with HSSD requirements described in Section 5.2.2.3, Option B: 100% SSS coverage with concurrent MBES.
				
				* In a few cases, SSS data shows small along-track gaps. These were examined and filled with MBES data to ensure full coverage, sometimes re-accepting high quality soundings that were auto-rejected during the MBES filtering process.
				
				* A large gap in SSS coverage at the south end of the corridor area caused by early termination of SSS data logging, approximately centered at 59-49-52 N, 165-27-55 W received SSS coverage primarily under the neighboring survey to the south, H12950. A small portion of a gap remained, which was successfully filled with MBES data.
				
				Set-spacing area:
				
				MBES-only data was acquired at 500 m spacing in all assigned areas outside the corridor to set-spacing standards.
				
				SSS was not collected in the set-spaced areas.
				
				Splits:
				
				Bathymetric line splits were not acquired to investigate charted depths because charted depths shoaler than survey depths did not fall between two survey lines given the scale of the affected chart. 
				
				Two dedicated splits were acquired in the south portion of the corridor area to develop seafloor mounds that were visible between lines in SSS data. In other areas rejected data was re-accepted when it was of high quality to better develop shoaler areas between lines. However, in other areas, shoals, contours, and significant deeps were adequately defined by the mainscheme lines and no further splits were necessary.
				</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Survey overview showing coverage.</ns2:caption><ns2:link>SupportFiles\2_H12949_Coverage.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>116</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>97</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>19</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>88</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>59</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>13</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>204</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>157</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>32</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>8.9</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>5</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>66</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2016-07-17</ns2:surveyDates><ns2:surveyDates>2016-07-18</ns2:surveyDates><ns2:surveyDates>2016-07-19</ns2:surveyDates><ns2:surveyDates>2016-07-21</ns2:surveyDates><ns2:surveyDates>2016-07-26</ns2:surveyDates><ns2:surveyDates>2016-07-29</ns2:surveyDates><ns2:surveyDates>2016-08-05</ns2:surveyDates><ns2:discussion xsi:nil="true"></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>Qualifier 105</ns2:hullID><ns2:LOA units="meters">32</ns2:LOA><ns2:draft units="meters">1.8</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>ASV-CW5</ns2:hullID><ns2:LOA units="meters">5.5</ns2:LOA><ns2:draft units="meters">0.5</ns2:draft></ns1:vessel><ns1:discussion>The Qualifier 105 (Q105) is a 32 m aluminum hull vessel owned and operated by Support Vessels of Alaska. The Q105 acquired all multibeam data and provided housing and facilities for on-site data processing. The vessel also collected bottom samples, deployed BMPG tide gauges, and deployed/recovered the ASV-CW5 vessel.
				
				The ASV-CW5 (C-Worker 5) is a 5.5 m aluminum hull Autonomous Surface Vessel (ASV) owned and operated by ASV Global. The ASV was operated in an unmanned, but monitored mode, collecting SSS and MBES data in close proximity to the Q105.
				
				Refer to the DAPR for vessel photos, offset diagrams, and more information on vessel operations.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Teledyne Reson</ns2:manufacturer><ns2:model>Seabat 7101</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POSMV 320 V5</ns2:model><ns2:type>Positioning and Attitude</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POSMV 320 V4</ns2:model><ns2:type>Positioning and Attitude</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>Rapid SVT 200Bar</ns2:model><ns2:type>Sound Speed Profiler</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne Oceanscience</ns2:manufacturer><ns2:model>RapidCAST</ns2:model><ns2:type>Sound Speed Profiler Deployment System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>5700</ns2:model><ns2:type>Base Station</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer><ns2:model>SBE 26+</ns2:model><ns2:type>Submerged Tide Gauge</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>DAA (YSI - Xylem)</ns2:manufacturer><ns2:model>WaterLOG H-350XL</ns2:model><ns2:type>Vented Tide Gauge</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>MinosX with Xchange Sensors</ns2:model><ns2:type>Conductivity and Temperature Gauges</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>EdgeTech</ns2:manufacturer><ns2:model>4200-MP</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:discussion>Details on equipment specifications, configurations, quality control methodology, and methods of operation are described in the DAPR.</ns1:discussion><ns1:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>SAR:  Edgetech 4200 Side Scan Sonar was also used for data acquisition as part of H12949.</ns2:comment></ns2:branchComment></ns1:comments></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Crosslines were acquired in accordance with the requirements described in Section 5.2.4.3 of the 2016 HSSD. Effort was made to ensure crosslines had good temporal and geographic distribution, were run so as to enable maximal nadir-to-nadir comparisons, and percent of mainscheme LNM requirements were achieved (4% for complete coverage areas, and 8% for set-spacing coverage areas). Since the complete coverage areas utilized SSS, and therefore, had minimal MBES swath overlap in many locations, the higher standard of 8% was assumed (and achieved) sheet-wide.
				
				Crosslines were conducted with both vessels to ensure there was ample overlap for inter-vessel comparisons, with each vessel crossing the other's mainscheme lines. Since the two vessels worked in close proximity and ran parallel lines, crosslines were usually collected in sets, with one vessel on each adjacent line.
				
				In this area, crosslines were conducted concurrently with bottom sampling, usually during the transit between sample locations. Therefore, crosslines do not always intersect mainscheme lines at right angles. However, in all cases, crosslines have ample data for nadir-to-nadir and nadir-to-outer beam comparisons.
				
				The crossline analysis was conducted using CARIS HIPS “QC Report” routine. Every crossline was selected and run through the process, which calculated the depth difference between each accepted crossline sounding and a QC BASE (CUBE-type, 1 m resolution) surface’s depth layer created from the mainscheme data. QC BASE surfaces were created with the same parameters used for 1 m surfaces as the final surfaces, with the important distinction that the QC BASE surfaces did not include crosslines so as to not bias the QC report results. Differences in depth were grouped by beam number and statistics computed, which included the percentage of soundings with differences from the BASE surface falling within IHO Order 1. When at least 95% of the sounding differences exceed IHO Order 1, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.” A 5% (or less) failure rate was considered acceptable since this approach compares soundings to a surface, instead of a surface to a surface.
				
				Results: Agreement between the BASE surfaces and crossline soundings is excellent. All crossline comparisons pass with 95% (or more) of soundings comparing to within IHO Order 1.
				
				Refer to Separate II: Digital Data for the detailed Crossline QC Reports.</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.038</ns2:measured><ns2:zoning units="meters">0.148</ns2:zoning><ns2:tideMethod>TCARI</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Qualifier 105</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0.401</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>ASV-CW5</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0.401</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>All soundings were assigned a horizontal and vertical value for estimated total propagated uncertainty (TPU). Refer to the DAPR for more detail concerning the parameters and methods used for computation of sounding uncertainty. 
				
				Note that fixed tide error values (0.038 m measured, 0.148 m zoning) entered during TPU computation were project-wide error averages for tide zones that were ignored by CARIS during TPU computation in favor of real-time tide error estimates loaded coincident with the TCARI model. Therefore, these static error estimates for tide zoning error did not affect final TPU computations.
				
				Real-time error estimates for attitude, positioning, and tide were used over fixed error estimates defined in the HVF. Exceptions, if they exist, are listed in Section B.3 of this report.
				
				The BASE surfaces were finalized in CARIS HIPS, so that the final uncertainty value for each grid cell is the greater of either standard deviation or uncertainty. The uncertainty layer of each final surface was then examined for areas of uncertainty that exceeded IHO Order 1. Uncertainty for the surfaces ranged from 0.21 m to 0.54 m for the 2 m surface and 0.13 m to 0.59 m for the 4 m surface.
				
				The vast majority of grid cells have uncertainty values within IHO Order 1. Few exceeded IHO Order 1. Highest uncertainties were found in areas of varying bottom topography such as slopes and near bottom features and sandwaves where high standard deviations are caused by the wide depth ranges of soundings contributing to each grid cell, outer edges of multibeam swathes without adjacent line overlap, and areas exhibiting sound speed or motion artifact error. Despite elevated TPU values for these grid cells, the data is within specifications.</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>
				This survey junctions with three contemporary surveys -- H12868, H12948, and H12950 -- which were conducted concurrently with this survey as part of the overall project, OPR-R300-KR-16.
				
				Difference surface methodology was used for the junction comparison. The depth layer from 2 m resolution CUBE surfaces from each survey were differenced from each other in CARIS HIPS, resulting in a difference surface. Values were extracted and statistics generated to quantify agreement. Any areas of significant disagreement, generally those exceeding IHO Order 1, were investigated to determine the cause.
				</ns2:discussion><ns2:images><ns2:caption>Survey junctions with this sheet.</ns2:caption><ns2:link>SupportFiles\4_H12949_Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12868</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>TerraSond</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent, averaging 0.028 m, with a standard deviation of 0.104 m, with differences falling in a range of -0.362 to 0.415 m. None exceed IHO Order 1.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12948</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>TerraSond</ns2:fieldUnit><ns2:relativeLocation>NE</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent, averaging 0.044 m, with a standard deviation of 0.091 m, with differences falling in a range of -0.351 to 0.351 m. None exceed IHO Order 1.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12950</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>TerraSond</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent, averaging 0.004 m, with a standard deviation of 0.165 m, with differences falling in a range of -0.678 to 0.488 m. Few exceed IHO Order 1. The few exceeding IHO Order 1 were investigated and the cause determined to be a tidal bust. Only isolated or small groupings of grid cells in the difference surface failed to meet specifications, rather than the entire line.</ns2:discussion><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Echosounder confidence checks consisting of bar checks, lead lines, and inter-vessel acoustic comparisons were undertaken on this project. Results were good, with agreement averaging 0.009 m for bar checks, 0.190 m for lead lines, and 0.059 m for inter-vessel acoustic comparisons . Refer to the bar check, lead line, and echosounder depth comparison logs available in Separate I: Acquisition and Processing Logs for specific results. Refer to the project DAPR for more information regarding QC checks methodology.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>7101 Beam Pattern</ns2:title><ns2:discussion>A distinct beam pattern was obvious in the data set in certain areas, with a fuzziness or “horn” like features on both sides of nadir on multibeam swaths, coinciding with the bottom detection shift from phase to amplitude detection. The pattern is common with Reson 8101/7101 multibeam echosounders in certain bottom types. Power and range settings were adjusted in acquisition to minimize the issue, with little effect. However, the “horns,” which can be as great as 0.20 m in height, appear to be largely ignored by the CUBE algorithm during surface creation, with minimal effect on the final surfaces.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>7101 Errant Pings</ns2:title><ns2:discussion>Errant or bad pings is evident periodically in the multibeam swath data. This occurred regularly on both 7101 systems. The issue manifests itself as a single ping, or swath, that is skewed (or rolled) from the seafloor at an angle. The cause is unknown, but does not correlate to any spikes in attitude data. These were normally removed manually during swath edit review, resulting in small along-track gaps as viewed in swath editor plan view. However, since only single pings were affected and ping rates were high (generally 10 or more per second), there is no significant detrimental effect on data density. Unrejected errant pings in the dataset may remain, but do not have significant detrimental effect on final surface quality. </ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Sound Speed Error</ns2:title><ns2:discussion>A general downward or upward across-track cupping in multibeam data, indicative of sound speed error, is present sporadically in the data set. The sound speed error adversely affected outer beams by up to 0.20 m in places. To minimize the error, sound speed profiles were collected every 2 hours during multibeam operations, and filters were used in processing to remove the outermost beams. The effect of sound speed error on final surfaces is relatively minor, normally not exceeding 0.10 m, and is within specifications.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Motion Artifact</ns2:title><ns2:discussion>Motion artifact is occasionally visible in the final multibeam surfaces. This is the result of uncompensated effects of motion, particularly due to roll. The primary contributer was motion induced on the survey vessels by poor sea states (often 1.5 m or greater), a common and unavoidable condition in this highly exposed area. A survey-grade Applanix POSMV 320 was used for motion compensation, but residual error within the manufacturer specifications for the system remains nonetheless. The problem was addressed in processing by identifying lines with the greatest error and iteratively applying more aggressive outer beam filters, in some instances rejecting beams greater than 55 degrees either side of nadir. No adjustments to line spacing were made in acquisition to compensate for the rejected outer beam data because complete MBES coverage was not required. Following the additional filtering, the effect on the final surface is normally 0.25 m or less, which is within specifications. 
						
						Note that the ASV-CW5, at 3.5 m in length was a much smaller survey platform than the Q105 at 32 m in length, and therefore, experienced greater induced motion at the same sea states, resulting in more motion artifact for lines run simultaneously.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Tide Error</ns2:title><ns2:discussion>Periodic vertical offsets or “busts,” indicative of tide error, is present sporadically in the data set. The majority of lines show good matchup with crosslines or adjacent lines, but busts of up to 0.4 m are occasionally present and attributable primarily to tide error.</ns2:discussion><ns2:images><ns2:caption>Example tide error. Crossline 0546-Q105-218-F34XL2 (cyan) is offset vertically from intersecting mainscheme lines by up to 0.40 m. Final 2 m surface is shown as light blue.</ns2:caption><ns2:link>SupportFiles\5_TideBustExample.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>2 hours</ns1:castFrequency><ns1:discussion>Sound speed profiles, or casts, were acquired aboard the Q105 while underway with an Oceanscience RapidCAST system, which utilized a Valeport sound speed profiler. The interval between subsequent casts was normally 2 hours. The sound speed sensor was lowered as close as possible to the seafloor, and then retracted to the vessel and downloaded. When surveying lines covering widely varying water depths, casts were favored in the deeper portions to ensure the entire water column was captured.
				
				The ASV-CW5 vessel was not equipped to collect sound speed profiles. Instead, the profile data collected aboard the Q105 was used to correct all ASV-CW5 data. This was possible because the ASV-CW5 worked simultaneously and in close proximity (usually within 200 - 800 m) of the Q105 at all times.
				
				Up and down portions of the profiles were averaged and a combined profile at a standardized 0.10 m depth increment was output to CARIS SVP format with time and position. Sound speed profiles were applied with the “nearest in distance within time” method in CARIS HIPS, with time set to 2 hours. Exceptions, if they occurred, are listed in section B.3 of this report.
				</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>
					Refer to the DAPR, section B.2.4 &quot;Data Coverage and Density,&quot; for details on the equipment, software, and methodology used to meet object detection, coverage, and data density requirements.
					</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="true"><ns2:discussion>Corrections applied to echo soundings are detailed in the project DAPR. No deviations occurred, except as described below. Note that despite exceptions, affected data is within specifications.
					
					Sound speed exception: The following lines required correction for sound speed that was different than the project standard of nearest in distance within 2 hours.
					
					Nearest in distance within 3 hours
					
					0383-Q105-203-F4FS06_-_0002
					
					SMRMSG real-time error exception: SMRMSG files could not be loaded to the following lines. Therefore, real-time error estimates were not available for post-processed attitude data during TPU computation. Static error estimates from the HVF were used instead.
					
					0316-ASV-208-F4FS04_-_0001
					0316-ASV-208-F4FS04_-_0002
					0317-ASV-208-F3FS17_-_0001
					0317-ASV-208-F3FS17_-_0002
					
					</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>Calibrations were undertaken as described in the DAPR. No deviations occurred.</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>Multibeam backscatter was logged at all times during this survey, but not processed. Raw DB and XTF files, submitted with the survey deliverables, contain the backscatter records.</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>V5.4</ns1:featureObjectCatalog><ns1:discussion>
				There were no software configuration changes after the DAPR was submitted.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12949_MB_4m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Set-spaced MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12949_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</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12949_SSS_1m_100-F1</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS, block F1</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12949_SSS_1m_100-F2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS, block F2</ns2:purpose></ns1:surface><ns1:discussion>The final depth information for this survey was submitted as two CARIS BASE surfaces (CSAR format) and two georeferenced SSS mosaic images which best represented the seafloor at the time of the 2016 survey. The surfaces and images were created from fully processed data with all final corrections applied. 
				
				MBES Data:
				
				The MBES surfaces were created using NOAA CUBE parameters and resolutions in conformance with the 2016 HSSD. Corridor (full coverage) area surfaces were generated in accordance with section 5.2.2.3 (Complete Coverage) while the set-spacing area surface was generated in accordance with section 5.2.2.4 (Set Line Spacing). Surfaces were finalized, and designated soundings were applied where applicable. Horizontal projection was selected as UTM Zone 3 North, WGS84. 
				
				Non-finalized versions of the CSAR surfaces are also included. These do not have the _Final designation in the filename.
				
				File names for final surfaces was done in accordance with section 8.3.2 (Bathymetric Data) of the 2016 HSSD for MBES data. 
				
				SSS Data:
				
				SSS mosaics were exported from SonarWiz as georeferenced TIFF images at 1 m resolution. These are projected as WGS84 UTM Zone 3N. A world file (.TFW) accompanies each TIFF image to provide the georeferencing.
				
				SSS filenames are as specified in section 8.2.1, with the addition of an area or block designation at the end of filenames. Singular SSS images for this survey was not practical due to extremely large GeoTIFF file sizes that would result from combined images. Therefore, images were created by survey block, and the block name added as a suffix to the filenames. 
				
				For this survey, block &quot;F1&quot; denoted the north half of the corridor area, while &quot;F2&quot; the south half of the corridor area.
				
				Supplementary Data:
				
				A CARIS HOB file was submitted (H12949_FFF.HOB) with the survey deliverables as well. The final feature file (FFF) contains meta-data and other data not readily represented by the final surfaces, including DTONs that were submitted previously during the course of the survey, if applicable, and bottom samples.
				
				A CARIS HOB file containing SSS contacts was NOT submitted because no significant contacts (not already adequately captured in the MBES surfaces) were found. Many small contacts were observed in deeper portions of this survey area, but did not meet criteria for significance. Significant contacts were those identified in the SSS record as having height above the seafloor of 1 m, or greater, in depths less than 20 m, and heights of 10%, or greater, of water depth in depths 20 m and deeper. The 10% allowance is an exception granted for this project by NOAA (see correspondence) to the 5% requirement described in the 2016 HSSD. In this area, contacts were more common in deep water than in shallow water, and this exception was made to limit the number of contacts requiring multibeam development in deeper water, and therefore, facilitate the survey of additional areas over performing multibeam developments. This was considered acceptable given that vessels of 20 m draft are extremely unlikely to attempt transiting this area given its shoal approaches.
				
				Each object is encoded with mandatory S-57 attributes, additional attributes, and NOAA Extended Attributes (V#5.4).</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:subordinateGauges><ns2:stationName>Nelson Island</ns2:stationName><ns2:stationID>9466298</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Eastern Nunivak Island</ns2:stationName><ns2:stationID>9466012</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Kipnuk</ns2:stationName><ns2:stationID>9465953</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Offshore South Nunivak</ns2:stationName><ns2:stationID>9465683</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:correctorFiles><ns2:tideCorrectors><ns2:fileName>r300kr2016_rev.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2016-11-17</ns2:dateSubmitted><ns2:dateReceived>2017-01-26</ns2:dateReceived></ns2:finalTides><ns2:discussion>In addition to the subordinate tide station installed to support the project, submerged BMPG (bottom mounted pressure gauges) were also deployed throughout the survey area to capture zoning characteristics. These zoning gauges were used for QC purposes only. All data has been submitted to CO-OPS.
				
				A final TCARI grid covering the survey area was issued on January 13th, 2017. However, the grid file was revised and reissued (filename &quot;r300kr2016_rev.tc&quot;) on January 26th, 2017. This revised grid &quot;r300kr2016_rev.tc&quot; demonstrated better results in general, and was applied to all data.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false" xsi:nil="true"/><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>WGS84</ns2:horizontalDatum><ns2:projection>UTM Zone 3N</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>0056</ns2:HVCRSiteID><ns2:stationID>Toksook Bay</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>The project base continuously logged GPS data at 1 Hz and was utilized to post-process position data in Applanix POSPac MMS software. The Continually Operating Reference Station (CORS) site at Mekoryuk, station ID &quot;AB08,&quot; was used for preliminary post-processing in the field, quality control checks for the project base station, and for final positions in rare instances where the project base station experienced outages. All real-time positions for both vessels were replaced in processing with post-processed kinematic (PPK) solutions, with few exceptions (noted if applicable earlier in this report).
				
				Quality control confidence checks were performed at least weekly on the survey vessels as well as the base station position. RMS error estimates for positioning results were very good, with RMS error estimated at 0.10 m (or better). Refer to the project DAPR for additional details on quality control checks and results.
				
				WAAS was used for real-time corrections in the field, but was replaced in post-processing with the PPK solution, as described in the DAPR.
				
				Note: Final positions are WGS84 (instead of NAD83) per Section 2.1 of the 2016 HSSD, which was the governing guidance during the time of field operations.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>The chart comparison was performed by examining all Raster Navigational Charts (RNCs) and Electronic Navigational Charts (ENCs) that intersect the survey area. The latest editions available at the time of the review (February 10th, 2017) were used.
				
				The chart comparison was accomplished by overlaying the finalized BASE surfaces with shoal-biased soundings, and a final feature file on the charts in CARIS HIPS. The general agreement between charted soundings and survey soundings was then examined and a more detailed comparison was undertaken for any shoals, or other dangerous features. In areas where a large scale chart overlapped with a small scale chart, only the larger scale chart was examined. Results are shown in the following sections.
				
				It is recommended that in all cases of disagreement this survey supersedes charted data.
				
				USCG Notice to Mariners (NM) and USCG Local Notice to Mariners (LNM) were checked for updates affecting the area. None were found that were issued subsequent to issuance date of the project instructions, nor prior to the completion of operations that affect the survey area.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16006</ns2:number><ns2:kapp>2411</ns2:kapp><ns2:scale>1534076</ns2:scale><ns2:edition>37</ns2:edition><ns2:editionDate>2015-12</ns2:editionDate><ns2:LNMDate>2017-01-17</ns2:LNMDate><ns2:NMDate>2017-01-21</ns2:NMDate></ns2:chart><ns2:discussion>This survey fully intersects only a small number of charted soundings. Overall sounding agreement is good, within 1 fathom, with exceptions noted below:
					
					1. Depth in the vicinity of charted 8 fathom sounding at 59-58-53 N, 165-29-53 W was found to be approximately 10.5 to 11 fathoms. However, the charted sounding is on the edge of survey coverage. Therefore, it is recommended the 8 fathom sounding remain as charted.
					
					 Agreement was also examined for significant trends. None was noted except as follows:
					 
					 1. The 10 fathom contour is charted significantly further east (up to 6.8 km) than its actual location.
					 
					See included figure that shows soundings from this survey overlaid on chart 16006.
					</ns2:discussion><ns2:images><ns2:caption>Soundings from this survey overlaid on chart 16006. Survey soundings (orange) are shown in fathoms and feet. Charted soundings (black) are shown in fathoms and fractional fathoms.</ns2:caption><ns2:link>SupportFiles\6_H12949_ChartCompare.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US2AK95M</ns2:name><ns2:scale>1534076</ns2:scale><ns2:edition>4</ns2:edition><ns2:updateApplicationDate>2016-08-29</ns2:updateApplicationDate><ns2:issueDate>2016-08-29</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>The same differences observed for the RNC apply to the ENC.</ns2:discussion><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>There are no charted features labeled PA, ED, PD, or Rep. within the survey extents.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features were found during this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No DTONs were found during this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or hazardous features exist in the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist in the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Bottom samples were collected for this survey. 
					
					8 sample locations were assigned in the Project Reference File (PRF) supplied with the Work Instructions. 
					
					Samples were obtained at 5 of the 8 assigned locations. At 3 locations samples could not be obtained despite a minimum of 3 attempts at the location, with each attempt returning a closed sampler indicating seafloor contact, but no sample.
					
					Unsuccessful samples were at the following locations:
					
					60-01-59.035 N, 165-33-37.396 W
					60-00-10.260 N, 165-27-51.488 W
					59-52-41.806 N, 165-29-51.081 W
					
					Successful samples returned a variety of seabed types, ranging from fine sand to pebbles, shells, and cobbles.
					
					Samples were not retained. However, photos were taken of most samples prior to discarding. Bottom characteristics were encoded as SBDARE objects in the FFF, with any applicable photos in the accompanying &quot;multimedia&quot; directory, with the survey deliverables. Unsuccessful samples are encoded as SBDARE objects with NATSUR = &quot;Unknown&quot; per the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>This survey did not intersect shoreline, and shoreline investigation was not assigned.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Comparison with prior surveys was not required. However, Junction analysis, described previously in this report, was undertaken for overlapping contemporary surveys.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No ATONs were observed in the survey area, and none were assigned for investigation.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features existed within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>There are no submarine features of special note.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>Ferry routes and terminals do not exist within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>Platforms do not exist within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>Any significant features and conditions encountered have been described previously.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No construction or dredging was occurring within the survey extents, nor are there any known future plans for construction or dredging in the survey area.</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 are recommended in this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new chart insets are recommended in this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>Field operations contributing to the completion of survey H12949 were conducted under my direct supervision with frequent personal checks of progress, integrity, and adequacy.</ns1:supervision><ns1:approval>This report, digital data, and all other accompanying records are approved. All records are respectfully submitted and forwarded for final review.</ns1:approval><ns1:adequacyOfSurvey>The survey data was collected in accordance with the project Work Instructions and Statement of Work, and meets or exceeds the requirements set in the 2016 NOS Hydrographic Surveys and Specifications Deliverables (HSSD) document. This data is adequate to supersede charted data in common areas. This survey is complete and no additional work is required with the exception of any deficiencies, if any, noted in this Descriptive Report. 
			
			The Data Acquisition and Processing Report (DAPR) and Horizontal and Vertical Control Report (HVCR) were submitted concurrently with this report and the survey deliverables. Other significant required reports or data packages submitted separately but not already described are listed below.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName><ns2:approverTitle>TerraSond Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2017-03-05</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Coast Pilot Review (OPR-R300-KR-16_Coast Pilot Review Report)</ns2:reportName><ns2:reportDateSent>2017-02-13</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>NCEI Sound Speed Data</ns2:reportName><ns2:reportDateSent>2016-12-20</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Trained Marine Mammal Observers Logsheet</ns2:reportName><ns2:reportDateSent>2016-11-21</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Marine Mammal Observation Logs</ns2:reportName><ns2:reportDateSent>2016-11-17</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Tides and Water Levels Package and Reports (one for each project tide station)</ns2:reportName><ns2:reportDateSent>2016-10-21</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>