<?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:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:comments/><ns2:discussion>A comparison of soundings was accomplished by overlaying the latest edition of the largest scale NOS charts and ENCs onto the final BASE surfaces in CARIS HIPS. An additional check was conducted by gridding the ENC sounding data and differencing the ENC *.csar files against the H12885 *.csar files. The general agreement between the charted soundings and H12885 soundings is noted in the Charts section. A more detailed comparison was undertaken for any charted shoals or other dangerous features and is discussed in the Shoals and Hazardous Features section. </ns2:discussion></ns1:methods><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>There were seven charted features within the limits of H12885. A list of the charted features are as follows: 

Wreck with label “Wk PA” charted in the general vicinity of 43-59-15N 069-11-25W on charts 13301, and 13302. This item was assigned in the Composite Source File (CSF) with the following SORIND: US,US,graph,Chart 13301; refer to the Final Feature File (FFF) for more information on the results and S57 encoding.

Rock with label “Rk 1 Ft rep” charted in the general vicinity of 43-58-21N 069-11-31W on chart 13301. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13301; refer to the FFF for more information on the results and S57 encoding. 

Wreck with label “Wk” charted in the general vicinity of 43-58-36N 069-11-14W on chart 13301. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13301; refer to the FFF for more information on the results and S57 encoding.

Rock with label “Rep PA Rk” charted in the general vicinity of 43-59-40N 069-07-35W on charts 13301, 13302, 13303, and 13305. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13305; refer to the FFF for more information on the results and S57 encoding. 

Wreck with label “Wk” charted in the general vicinity of 43-59-28N 069-04-20W on charts 13303, and 13305. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13305; refer to the FFF for more information on the results and S57 encoding.

Rock with label “PD Rk” charted in the general vicinity of 43-59-40N 069-03-38W on charts 13303, and 13305. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13305; refer to the FFF for more information on the results and S57 encoding. 

Rock with label “Rep Rk” charted in the general vicinity of 44-00-59N 069-03-57W on charts 13302, 13303, and 13305. This item was assigned in the CSF with the following SORIND: US,US,graph,Chart 13305; refer to the FFF for more information on the results and S57 encoding. </ns2:discussion></ns2:results></ns1:chartedFeatures><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>Sample of difference surface of H12885 and ENC</ns2:caption><ns2:link>Support Files\Sample of difference surface of H12885 and ENC.png</ns2:link></ns2:images><ns2:discussion>A comparison of soundings was accomplished by overlaying the latest edition of the largest scale NOS charts and ENCs onto the final BASE surfaces in CARIS HIPS. An additional check was conducted by gridding the ENC sounding data and differencing the ENC *.csar files against the H12885 *.csar files. The results from this method highlight areas that differed and warranted extra attention. A unique color range pallet was developed to highlight these areas, for example, if the agreement was +/- 5 feet, the difference surface was colored green. Areas greater than +/- 5 feet were colored orange. Red was used for extreme differences.

The following are shoal features that differed, but did not warrant a danger to navigation submittal. Other Shoals and Hazardous Features exist in the survey area and were submitted as dangers to navigation; a total of 22 dangers were submitted to AHB and PHB. 

The item is a charted, 28-foot sounding in the general vicinity of (44-00-22 N) (069-03-52 W). Survey H12885 had a survey depth of 19 feet in that general location. Due to its location, no danger to navigation was submitted.

Survey H12885 revealed a new shoal with a survey depth of 13 feet in the general vicinity of (43-59-24 N) (069-05-18 W). Due to its location, no danger to navigation was submitted.

The item is a charted, 10-foot sounding in the general vicinity of (43-58-33 N) (069-04-08 W). Survey H12885 revealed a survey depth of 3 feet in that general location. Due to its location, no danger to navigation was submitted.

The item is a charted, 14-foot sounding in the general vicinity of (43-58-35 N) (069-04-26 W). Survey H12885 revealed a survey depth of 10 feet in that general location. Due to its location, no danger to navigation was submitted.

The item is a charted, 15-foot sounding in the general vicinity of (43-58-24 N) (069-07-11 W). Survey H12885 had a survey depth of 25.9 feet in that general location, but revealed a depth of 16 feet, 66 meters to the south. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 16-foot sounding in the general vicinity of (43-58-49 N) (069-07-19 W). Survey H12885 had a survey depth of 50 feet in that general location, but revealed a depth of 18 feet, 75 meters to the southeast. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 22-foot sounding in the general vicinity of (43-58-56 N) (069-06-58 W). Survey H12885 had a survey depth of 53 feet in that general location, but revealed a depth of 22 feet, 96 meters to the south. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 8-foot sounding in the general vicinity of (43-57-27 N) (069-05-58 W). Survey H12885 had a survey depth of 6 feet in that general location. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 15-foot sounding in the general vicinity of (43-57-32 N) (069-05-49 W). Survey H12885 had a survey depth of 12 feet in that general location. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 27-foot sounding in the general vicinity of (43-58-48 N) (069-04-01 W). Survey H12885 had a survey depth of 56 feet in that general location, but revealed a depth of 24 feet, 74 meters to the southwest. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 21-foot sounding in the general vicinity of (44-01-01 N) (069-02-25 W). Survey H12885 had a survey depth of 45 feet in that general location, but revealed a depth of 22 feet, 105 meters to the southwest. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 27-foot sounding in the general vicinity of (44-00-11 N) (069-05-45 W). Survey H12885 had a survey depth of 43 feet in that general location but revealed a depth of 27 feet, 119 meters to the southwest. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 21-foot sounding in the general vicinity of (43-58-31 N) (069-10-04 W). Survey H12885 had a survey depth of 17 feet in that general location.

The item is a charted, 46-foot sounding in the general vicinity of (44-00-02 N) (069-06-04 W). Survey H12885 had a survey depth of 37 feet in that general location.

The item is a charted, 7-foot sounding in the general vicinity of (44-00-58 N) (069-02-07 W). Survey H12885 had a survey depth of 3 feet in that general location.

The item is a charted, 28-foot sounding in the general vicinity of (43-58-56 N) (069-03-41 W). Survey H12885 had a survey depth of 45.6 feet in that general location, but revealed a depth of 24 feet, 102 meters to the southeast. The Hydrographer recommends a repositioning of the shoal.

Survey H12885 revealed a survey depth of 7 feet in the general vicinity of (43-58-49 N) (069-05-05 W). Due to its location and proximity to the shoreline, no danger to navigation was submitted.

The item is a charted, 19-foot sounding in the general vicinity of (43-58-52 N) (069-05-09 W). Survey H12885 had a survey depth of 12 feet in that general location. Due to its location, no danger to navigation was submitted.

The item is a charted, 11-foot sounding in the general vicinity of (43-58-15 N) (069-05-49 W). Survey H12885 had a survey depth of 37.4 feet in that general location, but revealed a depth of 20 feet, 58 meters to the south. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 10-foot sounding in the general vicinity of (43-58-10 N) (069-05-56 W). Survey H12885 had a survey depth of 6 feet in that general location. Due to its location, no danger to navigation was submitted.

The item is a charted, 13-foot sounding in the general vicinity of (43-57-36 N) (069-05-31 W). Survey H12885 had a survey depth of 11 feet in that general location. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 22-foot sounding in the general vicinity of (43-59-23 N) (069-06-23 W). Survey H12885 had a survey depth of 47 feet in that general location, but revealed a depth of 24 feet, 96 meters to the north. The Hydrographer recommends a repositioning of the shoal.

The item is a charted, 11-foot sounding in the general vicinity of (44-00-52 N) (069-02-22 W). Survey H12885 had a survey depth of 24 feet in that general location.

The item is a charted, 25-foot sounding in the general vicinity of (43-57-54 N) (069-05-13 W). Survey H12885 had a survey depth of 40 feet in that general location, but revealed a depth of 17 feet, 69 meters to the west. 

</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results></ns1:unchartedFeatures><ns1:charts><ns2:comments/><ns2:ENC><ns2:comments/><ns2:chart><ns2:edition>6</ns2:edition><ns2:name>US5ME19</ns2:name><ns2:scale>40000</ns2:scale><ns2:updateApplicationDate>2016-01-19</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2016-02-06</ns2:issueDate></ns2:chart><ns2:discussion>Chart information displayed is based on OPR-A366-KR-16 Project Instructions, however the charts used for final comparison were downloaded on 8 December 2016.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.

Sounding agreement between the H12885 BASE surface depths (surveyed depths) and the charted soundings for all applicable ENC charts was within (+/-) 1 meter. Since the survey area was ensonified with 100% multibeam coverage, discrepancies between charted and surveyed depths were discovered; special attention was given to charted and surveyed depths with a difference greater than 2 meters.

Contours in the area were adequate, but the 100% multibeam coverage established discrepancies between charted and observed contours and require revision from the high-resolution data.   

The item is a charted, 29.8-meter sounding in the general vicinity of (43-54-58 N) (069-11-11 W). Survey H12885 had a survey depth of 46.0 meters in that general location, but revealed a depth of 28.1 meters, 120 meters to the east.

The item is a charted, 14.6-meter sounding in the general vicinity of (43-56-15 N) (069-12-07 W). Survey H12885 had a survey depth of 22.6 meters in that general location.

The item is a charted, 7.6-meter sounding in the general vicinity of (43-56-18 N) (069-12-23 W). Survey H12885 had a survey depth of 10.9 meters in that general location.

The item is a charted, 10-meter sounding in the general vicinity of (43-56-30 N) (069-11-57 W). Survey H12885 had a survey depth of 16.2 meters in that general location.

The item is a charted, 33-meter sounding in the general vicinity of (43-56-00 N) (069-09-34 W). Survey H12885 had a survey depth of 39 meters in that general location.

The item is a charted, 2.4-meter sounding in the general vicinity of (43-56-57 N) (069-11-39 W). Survey H12885 had a survey depth of 6.5 meters in that general location.

The item is a charted, 17.3-meter sounding in the general vicinity of (43-57-04 N) (069-11-11 W). Survey H12885 had a survey depth of 22 meters in that general location.

The item is a charted, 31-meter sounding in the general vicinity of (43-57-01 N) (069-09-16 W). Survey H12885 had a survey depth of 34 meters in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 33-meter sounding in the general vicinity of (43-56-47 N) (069-09-00 W). Survey H12885 had a survey depth of 36 meters in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 29.5-meter sounding in the general vicinity of (43-57-18 N) (069-09-13 W). Survey H12885 had a survey depth of 32 meters in that general location, but revealed a depth of 28.6 meters, 205 meters to the east.

The item is a charted, 9.4-meter sounding in the general vicinity of (43-57-29 N) (069-11-19 W). Survey H12885 had a survey depth of 13.9 meters in that general location.

The item is a charted, 14.6-meter sounding in the general vicinity of (43-57-21 N) (069-11-16 W). Survey H12885 had a survey depth of 17.6 meters in that general location.

The item is a charted, 20.4-meter sounding in the general vicinity of (43-57-19 N) (069-11-00 W). Survey H12885 had a survey depth of 24.4 meters in that general location.

The item is a charted, 13.4-meter sounding in the general vicinity of (43-57-15 N) (069-10-41 W). Survey H12885 had a survey depth of 15.8 meters in that general location, but revealed a depth of 14.1 meters, 73 meters to the west.

The item is a charted, 27.4-meter sounding in the general vicinity of (43-57-37 N) (069-09-17 W). Survey H12885 had a survey depth of 30.9 meters in that general location.

The item is a charted, 10.3-meter sounding in the general vicinity of (43-57-55 N) (069-11-18 W). Survey H12885 had a survey depth of 13.6 meters in that general location.

The item is a charted, 16.4-meter sounding in the general vicinity of (43-58-01 N) (069-10-32 W). Survey H12885 had a survey depth of 19.9 meters in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 21-meter sounding in the general vicinity of (43-57-57 N) (069-10-02 W). Survey H12885 had a survey depth of 24.6 meters in that general location.

The item is a charted, 21-meter sounding in the general vicinity of (43-58-04 N) (069-09-47 W). Survey H12885 had a survey depth of 24.4 meters in that general location.

The item is a charted, 16.4-meter sounding in the general vicinity of (43-58-10 N) (069-09-37 W). Survey H12885 had a survey depth of 24.8 meters in that general location.

The item is a charted, 9.4-meter sounding in the general vicinity of (43-58-26 N) (069-10-31 W). Survey H12885 had a survey depth of 14.1 meters in that general location, but revealed a depth of 9.1 meters, 95 meters to the southwest.

The item is a charted, 10.3-meter sounding in the general vicinity of (43-58-26 N) (069-10-19 W). Survey H12885 had a survey depth of 15.2 meters in that general location, but revealed a depth of 9.3 meters, 191 meters to the northeast.

The LiDAR item is a charted, 0.6-meter sounding in the general vicinity of (43-57-81 N) (069-12-01 W). Survey H12885 had a survey depth of 3.0 meters in that general location, but revealed a depth of 2.4 meters, 15 meters to the southeast.

The Hydrographer recommends that soundings within the survey limits of H12885 supersede all prior survey and charted depths.</ns2:discussion></ns2:ENC><ns2:ENC><ns2:comments/><ns2:chart><ns2:edition>11</ns2:edition><ns2:name>US5ME21</ns2:name><ns2:scale>40000</ns2:scale><ns2:updateApplicationDate>2016-01-26</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2016-02-06</ns2:issueDate></ns2:chart><ns2:discussion>Chart information displayed is based on OPR-A366-KR-16 Project Instructions, however the charts used for final comparison were downloaded on 8 December 2016.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.

Sounding agreement between the H12885 BASE surface depths (surveyed depths) and the charted soundings for all applicable ENC charts was within (+/-) 1 meter. Since the survey area was ensonified with 100% multibeam coverage, discrepancies between charted and surveyed depths were discovered; special attention was given to charted and surveyed depths with a difference greater than 2 meters.

Contours in the area were adequate, but the 100% multibeam coverage established discrepancies between charted and observed contours and require revision from the high-resolution data.

The item is a charted, 35-meter sounding in the general vicinity of (43-56-32 N) (069-07-14 W). Survey H12885 had a survey depth of 40 meters in that general location, but revealed a depth of 36 meters, 81 meters to the southwest.

The item is a charted, 36-meter sounding in the general vicinity of (43-56-40 N) (069-06-51 W). Survey H12885 had a survey depth of 42 meters in that general location, but revealed shoaling to the east of the charted sounding.

The item is a charted, 11.8-meter sounding in the general vicinity of (43-58-19 N) (069-08-49 W). Survey H12885 had a survey depth of 17.8 meters in that general location, but revealed a depth of 12.9 meters, 44 meters to the north.

The item is a charted, 24.6-meter sounding in the general vicinity of (43-58-10 N) (069-08-34 W). Survey H12885 had a survey depth of 27.7 meters in that general location.

The item is a charted, 24.6-meter sounding in the general vicinity of (43-58-07 N) (069-07-49 W). Survey H12885 had a survey depth of 32.6 meters in that general location, but revealed shoaling to the northwest of the charted sounding.

The item is a charted, 21.9-meter sounding in the general vicinity of (43-58-14 N) (069-07-35 W). Survey H12885 had a survey depth of 40.2 meters in that general location.

The item is a charted, 11.8-meter sounding in the general vicinity of (43-58-11 N) (069-07-22 W). Survey H12885 had a survey depth of 19.6 meters in that general location, but revealed a depth of 9.6 meters, 90 meters to the northwest.

The item is a charted, 4.5-meter sounding in the general vicinity of (43-58-24 N) (069-07-12 W). Survey H12885 had a survey depth of 7.7 meters in that general location, but revealed a depth of 4.8 meters, 63 meters to the southwest.

The item is a charted, 21-meter sounding in the general vicinity of (43-58-10 N) (069-07-01 W). Survey H12885 had a survey depth of 29.5 meters in that general location, but revealed a depth of 19.3 meters, 123 meters to the northwest.

The item is a charted, 15.5-meter sounding in the general vicinity of (43-58-27 N) (069-07-42 W). Survey H12885 had a survey depth of 20.2 meters in that general location, but revealed shoaling to the northwest of the charted sounding.

The item is a charted, 10.3-meter sounding in the general vicinity of (43-58-02 N) (069-06-40 W). Survey H12885 had a survey depth of 17.8 meters in that general location, but revealed a depth of 13.9 meters, 55 meters to the northwest.

The item is a charted, 10.6-meter sounding in the general vicinity of (43-58-37 N) (069-06-36 W). Survey H12885 had a survey depth of 18.7 meters in that general location, b but revealed shoaling to the south of the charted sounding.

The item is a charted, 10.3-meter sounding in the general vicinity of (43-57-50 N) (069-05-26 W). Survey H12885 had a survey depth of 17.9 meters in that general location.

The item is a charted, 10.6-meter sounding in the general vicinity of (43-58-30 N) (069-04-56 W). Survey H12885 had a survey depth of 16.6 meters in that general location, but revealed a depth of 7.2 meters, 100 meters to the south.

The item is a charted, 18.5-meter sounding in the general vicinity of (43-58-20 N) (069-04-33 W). Survey H12885 had a survey depth of 11.9 meters in that general location.

The item is a charted, 27.7-meter sounding in the general vicinity of (43-58-36 N) (069-06-13 W). Survey H12885 had a survey depth of 38.5 meters in that general location.

The item is a charted, 7.6-meter sounding in the general vicinity of (43-57-54 N) (069-05-13 W). Survey H12885 had a survey depth of 12.2 meters in that general location, but revealed a depth of 5.2 meters, 68 meters to the west.

The item is a charted, 6.4-meter sounding in the general vicinity of (43-58-24 N) (069-08-35 W). Survey H12885 had a survey depth of 11.9 meters in that general location, but revealed a depth of 5.1 meters, 109 meters to the northeast.

The Hydrographer recommends that soundings within the survey limits of H12885 supersede all prior survey and charted depths.</ns2:discussion></ns2:ENC><ns2:ENC><ns2:comments/><ns2:chart><ns2:edition>12</ns2:edition><ns2:name>US5ME22</ns2:name><ns2:scale>40000</ns2:scale><ns2:updateApplicationDate>2016-01-26</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2016-02-06</ns2:issueDate></ns2:chart><ns2:discussion>Chart information displayed is based on OPR-A366-KR-16 Project Instructions, however the charts used for final comparison were downloaded on 8 December 2016.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.

Sounding agreement between the H12885 BASE surface depths (surveyed depths) and the charted soundings for all applicable ENC charts was within (+/-) 1 meter. Since the survey area was ensonified with 100% multibeam coverage, discrepancies between charted and surveyed depths were discovered; special attention was given to charted and surveyed depths with a difference greater than 2 meters.

Contours in the area were adequate, but the 100% multibeam coverage established discrepancies between charted and observed contours and require revision from the high-resolution data.   

The item is a charted, 4.5-meter sounding in the general vicinity of (43-58-59 N) (069-09-44 W). Survey H12885 had a survey depth of 8.9 meters in that general location.

The item is a charted, 0.6-meter sounding in the general vicinity of (43-59-01 N) (069-09-39 W). Survey H12885 had a survey depth of 5.9 meters in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 2.1-meter sounding in the general vicinity of (43-59-06 N) (069-10-07 W). Survey H12885 had a survey depth of 5.6 meters in that general location, but revealed a depth of 4.8 meters, 20 meters to the east.

The item is a charted, 22.8-meter sounding in the general vicinity of (43-58-53 N) (069-07-08 W). Survey H12885 had a survey depth of 31.2 meters in that general location, but revealed a depth of 17.9 meters, 117 meters to the southwest.

The item is a charted, 24.6-meter sounding in the general vicinity of (43-59-02 N) (069-07-00 W). Survey H12885 had a survey depth of 30.1 meters in that general location, but revealed a depth of 17.3 meters, 72 meters to the east.

The item is a charted, 20.4-meter sounding in the general vicinity of (43-58-58 N) (069-06-08 W). Survey H12885 had a survey depth of 28.9 meters in that general location.

The item is a charted, 11.8-meter sounding in the general vicinity of (43-59-22 N) (069-06-46 W). Survey H12885 had a survey depth of 16.8 meters in that general location, but revealed a depth of 11.5 meters, 112 meters to the north.

The item is a charted, 27.7-meter sounding in the general vicinity of (43-58-45 N) (069-03-13 W). Survey H12885 had a survey depth of 34.5 meters in that general location, but revealed a depth of 16 meters, 98 meters to the northwest.

The item is a charted, 11.5-meter sounding in the general vicinity of (44-00-56 N) (069-01-52 W). Survey H12885 had a survey depth of 23.4 meters in that general location, but revealed a depth of 11.4 meters, 63 meters to the south.

The item is a charted, 16.7-meter sounding in the general vicinity of (44-00-00 N) (069-05-55 W). Survey H12885 had a survey depth of 20.2 meters in that general location, but revealed a depth of 17.6 meters, 120 meters to the southeast.

The item is a charted, 17.6-meter sounding in the general vicinity of (43-59-51 N) (069-06-00 W). Survey H12885 had a survey depth of 19.8 meters in that general location, but revealed a depth of 17.4 meters, 141 meters to the southwest.

The item is a charted, 10-meter sounding in the general vicinity of (43-59-58 N) (069-05-20 W). Survey H12885 had a survey depth of 14.6 meters in that general location, but revealed a depth of 10.6 meters, 62 meters to the west.

The item is a charted, 24.6-meter sounding in the general vicinity of (43-59-16 N) (069-06-55 W). Survey H12885 had a survey depth of 29.5 meters in that general location, but revealed a depth of 22.1 meters, 74 meters to the southeast.

The item is a charted, 17.3-meter sounding in the general vicinity of (44-01-08 N) (069-01-43 W). Survey H12885 had a survey depth of 25.5 meters in that general location, but revealed a depth of 16.6 meters, 103 meters to the east.

The item is a charted, 18.8-meter sounding in the general vicinity of (43-59-29 N) (069-05-54 W). Survey H12885 had a survey depth of 35 meters in that general location.

The item is a charted, 9.4-meter sounding in the general vicinity of (43-59-00 N) (069-05-55 W). Survey H12885 had a survey depth of 19.8 meters in that general location, but revealed a depth of 10.8 meters, 85 meters to the south.

The item is a charted, 2.7-meter sounding in the general vicinity of (43-58-47 N) (069-06-45 W). Survey H12885 had a survey depth of 12.1 meters in that general location, but revealed a depth of 7.9 meters, 15 meters to the southeast.

The item is a charted, 5.7-meter sounding in the general vicinity of (43-59-59 N) (069-05-01 W). Survey H12885 had a survey depth of 8.3 meters in that general location, but revealed a depth of 4.8 meters, 26 meters to the south.

The item is a charted, 7.6-meter sounding in the general vicinity of (44-00-37 N) (069-02-22 W). Survey H12885 had a survey depth of 15.2 meters in that general location, but revealed a depth of 8.4 meters, 62 meters to the west.

The item is a charted, 12.8-meter sounding in the general vicinity of (44-00-30 N) (069-02-24 W). Survey H12885 had a survey depth of 17.1 meters in that general location.

The item is a charted, 17-meter sounding in the general vicinity of (44-00-39 N) (069-01-55 W). Survey H12885 had a survey depth of 21.3 meters in that general location, but revealed a depth of 14.4 meters, 46 meters to the northeast.

The item is a charted, 23.7-meter sounding in the general vicinity of (43-59-04 N) (069-01-44 W). Survey H12885 had a survey depth of 36.8 meters in that general location, but revealed a depth of 24.4 meters, 90 meters to the south.

The item is a charted, 9.7-meter sounding in the general vicinity of (43-59-13 N) (069-02-47 W). Survey H12885 had a survey depth of 17.1 meters in that general location, but revealed a depth of 14.6 meters, 33 meters to the northwest.

The item is a charted, 21.6-meter sounding in the general vicinity of (43-58-45 N) (069-03-37 W). Survey H12885 had a survey depth of 24.8 meters in that general location, but revealed a depth of 17.6 meters, 134 meters to the east.

The LiDAR item is a charted, 1.2-meter sounding in the general vicinity of (43-58-47 N) (069-08-28 W). Survey H12885 had a survey depth of 7.2 meters in that general location.

The LiDAR item is a charted, 0.3-meter sounding in the general vicinity of (43-59-30 N) (069-04-22 W). Survey H12885 had a survey depth of 3.3 meters in that general location.

The LiDAR item is a charted, 0.9-meter sounding in the general vicinity of (43-59-24 N) (069-04-41 W). Survey H12885 had a survey depth of 3.6 meters in that general location.

The Hydrographer recommends that soundings within the survey limits of H12885 supersede all prior survey and charted depths.</ns2:discussion></ns2:ENC><ns2:rasterChart><ns2:comments/><ns2:chart><ns2:edition>21</ns2:edition><ns2:LNMDate>2016-02-02</ns2:LNMDate><ns2:NMDate>2016-02-20</ns2:NMDate><ns2:kapp>2033</ns2:kapp><ns2:editionDate>2015-04</ns2:editionDate><ns2:scale>40000</ns2:scale><ns2:number>13301</ns2:number></ns2:chart><ns2:discussion>Chart information displayed is based on OPR-A366-KR-16 Project Instructions, however the charts used for final comparison were downloaded on 8 December 2016.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.

Sounding agreement between the H12885 BASE surface depths (surveyed depths) and the charted soundings for all applicable Raster charts was within (+/-) 3 feet. Since the survey area was ensonified with 100% multibeam coverage, discrepancies between charted and surveyed depths were discovered and special attention was given to charted and surveyed depths with a difference greater than 5 feet.

Contours in the area were adequate, but the 100% multibeam coverage established discrepancies between charted and observed contours and require revision from the high-resolution data.

The item is a charted, 98-foot sounding in the general vicinity of (43-54-58 N) (069-11-11 W). Survey H12885 had a survey depth of 150 feet in that general location, but revealed a depth of 92 feet, 118 meters to the east.

The item is a charted, 48-foot sounding in the general vicinity of (43-56-15 N) (069-12-07 W). Survey H12885 had a survey depth of 74 feet in that general location, but revealed a depth of 48 feet, 131 meters to the northeast.

The item is a charted, 25-foot sounding in the general vicinity of (43-56-18 N) (069-12-23 W). Survey H12885 had a survey depth of 36 feet in that general location, but revealed a depth of 25 feet, 160 meters to the southwest.

The item is a charted, 33-foot sounding in the general vicinity of (43-56-30 N) (069-11-57 W). Survey H12885 had a survey depth of 53 feet in that general location, but revealed a depth of 33 feet, 94 meters to the northwest.

The item is a charted, 107 foot sounding in the general vicinity of (43-56-00 N) (069-09-34 W). Survey H12885 had a survey depth of 127 feet in that general location, but revealed a depth of 95 feet 153 meters to the northwest.

The item is a charted, 8-foot sounding in the general vicinity of (43-56-57 N) (069-11-39 W). Survey H12885 had a survey depth of 21 feet in that general location.

The item is a charted, 57-foot sounding in the general vicinity of (43-57-04 N) (069-11-11 W). Survey H12885 had a survey depth of 72 feet in that general location, but revealed a depth of 57 feet, 124 meters to the west.

The item is a charted, 101-foot sounding in the general vicinity of (43-57-01 N) (069-09-16 W). Survey H12885 had a survey depth of 112 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 107-foot sounding in the general vicinity of (43-56-47 N) (069-09-00 W). Survey H12885 had a survey depth of 117 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 104-foot sounding in the general vicinity of (43-57-01 N) (069-08-57 W). Survey H12885 had a survey depth of 114 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 97-foot sounding in the general vicinity of (43-57-18 N) (069-09-13 W). Survey H12885 had a survey depth of 104 feet in that general location, but revealed a depth of 94 feet, 206 meters to the east.

The item is a charted, 108-foot sounding in the general vicinity of (43-57-03 N) (069-08-32 W). Survey H12885 had a survey depth of 116 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 114-foot sounding in the general vicinity of (43-56-31 N) (069-07-14 W). Survey H12885 had a survey depth of 130 feet in that general location, but revealed a depth of 117 feet, 76 meters to the southwest.

The item is a charted, 31-foot sounding in the general vicinity of (43-57-29 N) (069-11-19 W). Survey H12885 had a survey depth of 45 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 48-foot sounding in the general vicinity of (43-57-21 N) (069-11-16 W). Survey H12885 had a survey depth of 58 feet in that general location, but revealed a depth of 48 feet, 169 meters to the northwest.

The item is a charted, 67-foot sounding in the general vicinity of (43-57-19 N) (069-11-00 W). Survey H12885 had a survey depth of 80 feet in that general location, but revealed a depth of 62 feet, 168 meters to the west.

The item is a charted, 44-foot sounding in the general vicinity of (43-57-15 N) (069-10-41 W). Survey H12885 had a survey depth of 53 feet in that general location, but revealed a depth of 46 feet, 75 meters to the west.

The item is a charted, 90-foot sounding in the general vicinity of (43-57-37 N) (069-09-16 W). Survey H12885 had a survey depth of 101 feet in that general location, but revealed a depth of 76 feet, 176 meters to the west.

The item is a charted, 34-foot sounding in the general vicinity of (43-57-55 N) (069-11-17 W). Survey H12885 had a survey depth of 44 feet in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 60-foot sounding in the general vicinity of (43-57-50 N) (069-10-32 W). Survey H12885 had a survey depth of 69 feet in that general location, but revealed a depth of 64 feet, 98 meters to the east.

The item is a charted, 54-foot sounding in the general vicinity of (43-58-01 N) (069-10-32 W). Survey H12885 had a survey depth of 65 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 69-foot sounding in the general vicinity of (43-57-57 N) (069-10-02 W). Survey H12885 had a survey depth of 81 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 69-foot sounding in the general vicinity of (43-58-04 N) (069-09-47 W). Survey H12885 had a survey depth of 79 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 54-foot sounding in the general vicinity of (43-58-10 N) (069-09-37 W). Survey H12885 had a survey depth of 81 feet in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 31-foot sounding in the general vicinity of (43-58-26 N) (069-10-31 W). Survey H12885 had a survey depth of 47 feet in that general location, but revealed a depth of 27 feet, 100 meters to the west.

The item is a charted, 34-foot sounding in the general vicinity of (43-58-26 N) (069-10-19 W). Survey H12885 had a survey depth of 50 feet in that general location, but revealed a depth of 30 feet, 191 meters to the northeast.

The item is a charted, 11-foot sounding in the general vicinity of (43-58-30 N) (069-09-26 W). Survey H12885 had a survey depth of 41 feet in that general location, but revealed a depth of 7 feet, 54 meters to the east.

The item is a charted, 15-foot sounding in the general vicinity of (43-58-58 N) (069-09-43 W). Survey H12885 had a survey depth of 33 feet in that general location, but revealed a depth of 15 feet, 85 meters to the north.

The item is a charted, 2-foot sounding in the general vicinity of (43-59-01 N) (069-09-39 W). Survey H12885 had a survey depth of 12 feet in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 7-foot sounding in the general vicinity of (43-59-06 N) (069-10-07 W). Survey H12885 had a survey depth of 13 feet in that general location, but revealed shoaling to the northwest of the charted sounding.

The item is a charted, 21-foot sounding in the general vicinity of (43-58-23 N) (069-08-36 W). Survey H12885 had a survey depth of 40 feet in that general location, but revealed a depth of 23 feet, 111 meters to the northwest.

The item is a charted, 39-foot sounding in the general vicinity of (43-58-18 N) (069-08-50 W). Survey H12885 had a survey depth of 60 feet in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 81-foot sounding in the general vicinity of (43-58-10 N) (069-08-35 W). Survey H12885 had a survey depth of 91 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 81-foot sounding in the general vicinity of (43-58-07 N) (069-07-49 W). Survey H12885 had a survey depth of 107 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 39-foot sounding in the general vicinity of (43-58-11 N) (069-07-22 W). Survey H12885 had a survey depth of 65 feet in that general location, but revealed a depth of 26 feet, 81 meters to the north.

The item is a charted, 69-foot sounding in the general vicinity of (43-58-09 N) (069-07-03 W). Survey H12885 had a survey depth of 96 feet in that general location, but revealed a depth of 63 feet, 92 meters to the northwest.

The item is a charted, 51-foot sounding in the general vicinity of (43-58-27 N) (069-07-42 W). Survey H12885 had a survey depth of 68 feet in that general location, but revealed a depth of 45 feet, 64 meters to the northwest.

The item is a charted, 75-foot sounding in the general vicinity of (43-58-53 N) (069-07-08 W). Survey H12885 had a survey depth of 102 feet in that general location, but revealed a depth of 58 feet, 124 meters to the southwest.

The item is a charted, 81-foot sounding in the general vicinity of (43-59-03 N) (069-07-01 W). Survey H12885 had a survey depth of 100 feet in that general location, but revealed a depth of 56 feet, 104 meters to the east.

The LiDAR item is a charted, 2-foot sounding in the general vicinity of (43-57-47 N) (069-12-01 W). Survey H12885 had a survey depth of 8 feet in that general location.

The Hydrographer recommends that soundings within the survey limits of H12885 supersede all prior survey and charted depths.</ns2:discussion></ns2:rasterChart><ns2:rasterChart><ns2:comments/><ns2:chart><ns2:edition>14</ns2:edition><ns2:LNMDate>2016-02-02</ns2:LNMDate><ns2:NMDate>2016-02-20</ns2:NMDate><ns2:kapp>2156</ns2:kapp><ns2:editionDate>2015-04</ns2:editionDate><ns2:scale>40000</ns2:scale><ns2:number>13303</ns2:number></ns2:chart><ns2:discussion>Chart information displayed is based on OPR-A366-KR-16 Project Instructions, however the charts used for final comparison were downloaded on 8 December 2016.

Given that the survey area was ensonified with 100% multibeam coverage, discrepancies were discovered between the charted and surveyed depths.

Sounding agreement between the H12885 BASE surface depths (surveyed depths) and the charted soundings for all applicable Raster charts was within (+/-) 3 feet. Since the survey area was ensonified with 100% multibeam coverage, discrepancies between charted and surveyed depths were discovered; special attention was given to charted and surveyed depths with a difference greater than 5 feet.

Contours in the area were adequate, but the 100% multibeam coverage established discrepancies between charted and observed contours and require revision from the high-resolution data.

The item is a charted, 108-foot sounding in the general vicinity of (43-57-03 N) (069-08-32 W). Survey H12885 had a survey depth of 116 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 114-foot sounding in the general vicinity of (43-56-31 N) (069-07-14 W). Survey H12885 had a survey depth of 130 feet in that general location, but revealed a depth of 117 feet, 86 meters to the southwest.

The item is a charted, 118-foot sounding in the general vicinity of (43-56-40 N) (069-06-51 W). Survey H12885 had a survey depth of 139 feet in that general location, but revealed shoaling to the east of the charted sounding.

The item is a charted, 80-foot sounding in the general vicinity of (43-57-45 N) (069-08-38 W). Survey H12885 had a survey depth of 99 feet in that general location, but revealed a depth of 84 feet, 64 meters to the south.

The item is a charted, 66-foot sounding in the general vicinity of (43-57-26 N) (069-08-38 W). Survey H12885 had a survey depth of 86 feet in that general location, but revealed a depth of 66 feet, 79 meters to the west. It should be noted that the position of the sounding on the overlapping chart 13301 is positioned correctly.

The item is a charted, 21-foot sounding in the general vicinity of (43-58-24 N) (069-08-35 W). Survey H12885 had a survey depth of 38 feet in that general location, but revealed a depth of 23 feet, 107 meters to the northwest.

The item is a charted, 81-foot sounding in the general vicinity of (43-58-10 N) (069-08-35 W). Survey H12885 had a survey depth of 91 feet in that general location, but revealed no shoaling near the charted sounding.

The item is a charted, 81-foot sounding in the general vicinity of (43-58-07 N) (069-07-49 W). Survey H12885 had a survey depth of 107 feet in that general location, but revealed shoaling to the north of the charted sounding.

The item is a charted, 72-foot sounding in the general vicinity of (43-58-14 N) (069-07-34 W). Survey H12885 had a survey depth of 132 feet in that general location, but revealed shoaling to the east of the charted sounding.

The item is a charted, 39-foot sounding in the general vicinity of (43-58-11 N) (069-07-22 W). Survey H12885 had a survey depth of 64 feet in that general location, but revealed a depth of 26 feet, 80 meters to the northwest.

The item is a charted, 69-foot sounding in the general vicinity of (43-58-10 N) (069-07-01 W). Survey H12885 had a survey depth of 96 feet in that general location, but revealed a depth of 63 feet, 116 meters to the northwest.

The item is a charted, 51-foot sounding in the general vicinity of (43-58-27 N) (069-07-42 W). Survey H12885 had a survey depth of 69 feet in that general location, but revealed a depth of 45 feet, 70 meters to the northwest.

The item is a charted, 31-foot sounding in the general vicinity of (43-58-46 N) (069-07-00 W). Survey H12885 had a survey depth of 41 feet in that general location.

The item is a charted, 75-foot sounding in the general vicinity of (43-58-54 N) (069-07-07 W). Survey H12885 had a survey depth of 105 feet in that general location, but revealed a depth of 58 feet, 152 meters to the southwest.

The item is a charted, 81-foot sounding in the general vicinity of (43-59-04 N) (069-06-59 W). Survey H12885 had a survey depth of 99 feet in that general location, but revealed a depth of 56 feet, 59 meters to the southeast.

The item is a charted, 34-foot sounding in the general vicinity of (43-58-03 N) (069-06-39 W). Survey H12885 had a survey depth of 59 feet in that general location, but revealed a depth of 45 feet, 49 meters to the northwest.

The item is a charted, 35-foot sounding in the general vicinity of (43-58-38 N) (069-06-36 W). Survey H12885 had a survey depth of 62 feet in that general location, but revealed a depth of 35 feet, 63 meters to the south.

The item is a charted, 21-foot sounding in the general vicinity of (43-58-43 N) (069-06-55 W). Survey H12885 had a survey depth of 46 feet in that general location, but revealed a depth of 27 feet, 41 meters to the west.

The item is a charted, 67-foot sounding in the general vicinity of (43-59-00 N) (069-06-07 W). Survey H12885 had a survey depth of 95 feet in that general location, but revealed a depth of 62 feet, 132 meters to the west.

The item is a charted, 39-foot sounding in the general vicinity of (43-59-23 N) (069-06-44 W). Survey H12885 had a survey depth of 66 feet in that general location, but revealed a depth of 38 feet, 86 meters to the northwest.

The item is a charted, 34-foot sounding in the general vicinity of (43-57-50 N) (069-05-25 W). Survey H12885 had a survey depth of 59 feet in that general location, but revealed a depth of 36 feet, 163 meters to the southwest.

The item is a charted, 61-foot sounding in the general vicinity of (43-58-20 N) (069-04-32 W). Survey H12885 had a survey depth of 39 feet in that general location.

The item is a charted, 91-foot sounding in the general vicinity of (43-58-46 N) (069-03-12 W). Survey H12885 had a survey depth of 115 feet in that general location, but revealed a depth of 52 feet, 108 meters to the west.

The item is a charted, 38-foot sounding in the general vicinity of (44-00-57 N) (069-01-50 W). Survey H12885 had a survey depth of 94 feet in that general location, but revealed a depth of 32 feet, 150 meters to the southwest.

The item is a charted, 55-foot sounding in the general vicinity of (44-00-00 N) (069-05-54 W). Survey H12885 had a survey depth of 66 feet in that general location, but revealed a depth of 58 feet, 111 meters to the southeast.

The item is a charted, 58-foot sounding in the general vicinity of (43-59-51 N) (069-05-58 W). Survey H12885 had a survey depth of 65 feet in that general location, but revealed a depth of 57 feet, 157 meters to the southwest.

The item is a charted, 33-foot sounding in the general vicinity of (43-59-57 N) (069-05-19 W). Survey H12885 had a survey depth of 46 feet in that general location, but revealed a depth of 34 feet, 80 meters to the west.

The item is a charted, 81-foot sounding in the general vicinity of (43-59-17 N) (069-06-54 W). Survey H12885 had a survey depth of 98 feet in that general location, but revealed a depth of 72 feet, 95 meters to the southeast.

The item is a charted, 91-foot sounding in the general vicinity of (43-58-36 N) (069-06-12 W). Survey H12885 had a survey depth of 127 feet in that general location, but revealed a depth of 92 feet, 169 meters to the southwest.

The item is a charted, 57-foot sounding in the general vicinity of (44-01-10 N) (069-01-42 W). Survey H12885 had a survey depth of 90 feet in that general location, but revealed a depth of 54 feet, 96 meters to the southeast.

The item is a charted, 31-foot sounding in the general vicinity of (43-59-01 N) (069-05-53 W). Survey H12885 had a survey depth of 47 feet in that general location, but revealed a depth of 35 feet, 97 meters to the south.

The item is a charted, 9-foot sounding in the general vicinity of (43-58-48 N) (069-06-45 W). Survey H12885 had a survey depth of 43 feet in that general location, but shoaling to either side.

The item is a charted, 19-foot sounding in the general vicinity of (43-59-59 N) (069-05-00 W). Survey H12885 had a survey depth of 28 feet in that general location, but revealed a depth of 16 feet, 49 meters to the southwest.

The item is a charted, 56-foot sounding in the general vicinity of (44-00-40 N) (069-01-55 W). Survey H12885 had a survey depth of 47 feet in that general location.

The item is a charted, 44-foot sounding in the general vicinity of (44-00-18 N) (069-01-46 W). Survey H12885 had a survey depth of 35 feet in that general location.

The item is a charted, 78-foot sounding in the general vicinity of (43-59-06 N) (069-01-43 W). Survey H12885 had a survey depth of 115 feet in that general location, but revealed a depth of 80 feet, 90 meters to the south.

The item is a charted, 32-foot sounding in the general vicinity of (43-59-14 N) (069-02-45 W). Survey H12885 had a survey depth of 54 feet in that general location, but revealed a depth of 48 feet, 62 meters to the west.

The LiDAR item is a charted, 4-foot sounding in the general vicinity of (43-58-47 N) (069-08-27 W). Survey H12885 had a survey depth of 21 feet in that general location, but revealed a depth of 4 feet, 57 meters to the southeast. It should be noted that the charted sounding is correct on chart 13301.

The LiDAR item is a charted, 1-foot sounding in the general vicinity of (43-59-30 N) (069-04-20 W). Survey H12885 had a survey depth of 8 feet in that general location. 

The Hydrographer recommends that soundings within the survey limits of H12885 supersede all prior survey and charted depths.</ns2:discussion></ns2:rasterChart></ns1:charts><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Samples were taken with a Van Veen grab sampler and positions and information were recorded with WinFrog Multibeam and CARIS Notebook 3.1. Samples retrieved were analyzed and then encoded with the appropriate S-57 attributes. Positions and descriptions of bottom samples for survey H12885 are found in the “H12885_FFF.000” file. 

No SBDARE items were in the CSF, therefore were not investigated during field operations. Bottom samples were conducted in accordance with the project instructions and HSSD 2016. All 18 samples were discarded after the sample information was recorded.</ns2:discussion></ns2:results></ns1:bottomSamples><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:DTONS><ns2:comments/><ns2:results reportSubmitted="true"><ns2:report><ns2:dateSubmitted>2016-09-12</ns2:dateSubmitted><ns2:title>H12885_DTON_Report_1</ns2:title></ns2:report><ns2:report><ns2:dateSubmitted>2016-09-12</ns2:dateSubmitted><ns2:title>H12885_DTON_Report_2</ns2:title></ns2:report><ns2:report><ns2:dateSubmitted>2016-09-12</ns2:dateSubmitted><ns2:title>H12885_DTON_Report_3</ns2:title></ns2:report><ns2:report><ns2:dateSubmitted>2017-01-30</ns2:dateSubmitted><ns2:title>H12885_DTON_Report_4</ns2:title></ns2:report><ns2:numberSubmitted>22</ns2:numberSubmitted><ns2:discussion>Dangers to Navigation are included in the Final Features File and have images associated with them. The Dangers to Navigation files listed above were submitted to MCD via AHB and PHB are included in Appendix II.</ns2:discussion></ns2:results></ns1:DTONS><ns1:maritimeBoundary><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No maritime boundary exists for this survey.</ns2:discussion></ns2:results></ns1:maritimeBoundary></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Limited shoreline verification was conducted using the composite source file (CSF) . All features with the attribute ‘asgnmt’ were address and can be found in the final feature file (FFF).</ns2:discussion></ns2:results></ns1:shoreline><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:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>AIS Traffic Ferry Routes Running from Rockland to Vinalhaven</ns2:caption><ns2:link>Support Files\AIS Traffic Ferry Routes Run from Rockland to Vinalhaven.png</ns2:link></ns2:images><ns2:discussion>The Rockland Ferry Terminal services the islands of Matinicus, North Haven, and Vinalhaven. H12885 encompassed part of the routes out of Rockland and vicinity for these island ferry runs, and was surveyed with 100% MB coverage. H12885 had numerous dangers to navigation and shoal features, but none hinder the existing ferry routes. </ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:ATONS><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>There were no Aids to Navigation (ATONs) specifically assigned for this project, but all ATONs within the survey limits were verified and serve their intended purpose.</ns2:discussion></ns2:results></ns1:ATONS><ns1:priorSurveys><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results></ns1:priorSurveys><ns1:otherResults><ns2:comments/><ns2:issue><ns2:comments/><ns2:discussion>Fugro conducted limited shoreline verification using the CSF. All features with the Assigned attribute were addressed in accordance with the HSSD 2016. There were a total of 386 assigned features (which included the Charted Features) in the CSF provided by NOAA. All features were addressed as required with S-57 attribution and recorded in the H12885 FFF to best represent the features at chart scale.

FFF features that do not exist or were determined to be a duplicate were given a “delete”value in the “descrp” attribute. Features that were positioned incorrectly were also given the “delete” value in the “descrp” attribute, and a new feature with a “new” value in the “descrp” attribute was added in its correct location. The “primsec” field was used to distinguish deleted features from newly positioned features. For survey H12885, most of the assigned features were verified or identified in the LiDAR bathy data or ortho-mosaic. These items were labelled with “LiDAR investigations” in the “Special Feature Type” attribute. The TECSOU field was populated with the “found by multi-beam attribute” for any feature verified by multibeam.

If an assigned feature was not submerged and within 2 mm at survey scale, the position of that assigned feature was retained and only the VALSOU or ELEVAT attributes were updated. To determine the VALSOU or ELEVAT for features investigated by LiDAR, the National VDatum software developed by NOAA was used to reduce LiDAR data to MLLW. LiDAR data was then clipped to the extents of each of the survey priorities and overlaid with Fugro-acquired ortho-imagery and assigned CSF features. The LiDAR grid was then used to determine the VALSOU attribute using the height or depth on the actual features and not the height or depth of the corresponding assigned CSF features. In order to determine which features should be considered islets, a difference surface corresponding to mean high water (MHW) was created for all survey priorities. Islet elevations were derived by taking the difference between the highest SHOALS topo point and the MHW grid. See the NOS HSSD 2016, Appendix F. WATLEV Attribution encoding guidelines were used for determining points above and below MHW.

To the reviewer: some automated routines that check grid agreement to a feature file (such as HydrOffice QC Tools VALSOU Check) may reveal flags suggesting a positional error; this is because some of the charted features in this survey have depths with little or no height off the bottom, and so automated routines may not be able to distinguish the node-match from the surrounding seafloor.

The final S-57 file for this project is called “H12885_FFF.000”. This file contains the object and metadata S-57 objects as required in the HSSD 2016. </ns2:discussion><ns2:title>Final Feature File</ns2:title></ns2:issue></ns1:otherResults><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:constructionOrDredging><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>There is no present or planned construction or dredging within the survey limits.</ns2:discussion></ns2:results></ns1:constructionOrDredging><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>Existing Cable Area in H12885</ns2:caption><ns2:link>Support Files\Existing Cable Area in H12885.png</ns2:link></ns2:images><ns2:images><ns2:caption>Coverage of Cable Area in H12885</ns2:caption><ns2:link>Support Files\Data of Cable Area in H12885.png</ns2:link></ns2:images><ns2:discussion>The only submarine feature within the limits of H12885 was an existing cable area, which was located within the charted Cable Area. The majority of the charted Cable Area within the limits of H12885 were surveyed with 100% MB coverage. A cable trench cannot be seen in the final surfaces. Refer to the following graphics.</ns2:discussion></ns2:results></ns1:submarineFeatures><ns1:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>Overhead features do not exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures><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: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:additionalResults></ns1:resultsAndRecommendations><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-A366-KR-16</ns2:number><ns2:generalLocality>Penobscot Bay</ns2:generalLocality><ns2:name>Penobscot Bay, ME</ns2:name><ns2:fieldUnit>Fugro Pelagos, Inc.</ns2:fieldUnit></ns1:projectMetadata><ns1:surveyMetadata><ns2:projectType>Navigable Area</ns2:projectType><ns2:year>2016</ns2:year><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts.
All separates are filed with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office
processing are shown in bold red italic text. The processing branch maintains the DR as a field unit product, therefore,
all information and recommendations within the body of the DR are considered preliminary unless otherwise noted. The
final disposition of surveyed features is represented in the OCS nautical chart update products. All pertinent records for
this survey, including the DR, are archived at the National Centers for Envitronmental Information (NCEI) and can be
retrieved via http://www.ncei.noaa.gov/.</ns2:branchRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:soundingEquipment>LiDAR SHOALS-1000T</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:imageryEquipment>Prosilica GX3300</ns2:imageryEquipment></ns2:equipmentTypes><ns2:horizontalCoordinateSystem zone="19N">UTM</ns2:horizontalCoordinateSystem><ns2:PIDate>2016-05-06</ns2:PIDate><ns2:chiefOfParty>Dean Moyles</ns2:chiefOfParty><ns2:datesOfSurvey><ns2:start>2016-07-11</ns2:start><ns2:end>2016-09-29</ns2:end></ns2:datesOfSurvey></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment><ns1:registryMetadata><ns2:country>United States</ns2:country><ns2:sublocality>Spaulding Island to Mosquito Island</ns2:sublocality><ns2:scale>20000</ns2:scale><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:stateOrTerritory>Maine</ns2:stateOrTerritory><ns2:registryNumber>H12885</ns2:registryNumber></ns1:registryMetadata></ns1:metadata><ns1:verticalAndHorizontalControl><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>Interp_ITRF00_to_MLLW</ns2:fileName><ns2:fileName>Interp_ITRF00_to_MHW</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:discussion>Additional information discussing the vertical control for this survey can be found in the accompanying HVCR.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Portland, ME</ns2:stationName><ns2:stationID>8418150</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Bar Harbor, ME</ns2:stationName><ns2:stationID>8413320</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:standard_or_ERZT used="true"><ns2:comments/><ns2:correctorFiles><ns2:tideCorrectors><ns2:status>Final</ns2:status><ns2:fileName>A366KR2016_FINAL.tc</ns2:fileName></ns2:tideCorrectors><ns2:waterLevels><ns2:status>Verified Observed</ns2:status><ns2:fileName>8418150_Portland_Verified</ns2:fileName></ns2:waterLevels><ns2:waterLevels><ns2:status>Verified Observed</ns2:status><ns2:fileName>8413320_Bar Harbor_Verified</ns2:fileName></ns2:waterLevels></ns2:correctorFiles><ns2:finalTides><ns2:dateReceived>2016-12-12</ns2:dateReceived><ns2:dateSubmitted>2016-11-16</ns2:dateSubmitted></ns2:finalTides><ns2:discussion>Additional information discussing the vertical control for this survey can be found in the accompanying HVCR.</ns2:discussion><ns2:methodsUsed>TCARI</ns2:methodsUsed></ns2:standard_or_ERZT><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:projection>UTM (Zone 19N)</ns2:projection><ns2:DGPS used="false" xsi:nil="true"/><ns2:PPK used="true"><ns2:comments/><ns2:discussion>Real-time corrections for both the vessels and aircraft, the POS M/V and A/V were configured to accept Fugro’s Marinestar G2 corrections. Marinestar G2 service is a real-time GPS and GLObal Navigation Satellite System (GLONASS) Precise Point Positioning (PPP) service providing refined satellite ‘clock and orbit’ data to any GNSS receiver with a valid subscription. Signals on the L-band with corrections are broadcasted by geo-stationary satellites and are received by the integrated GNSS/L-band antenna. The unit outputs corrected positions at 1 Hz to the POS units where they are integrated with inertial data, and a position for the top-center of the IMU is generated, providing a horizontal accuracy of 10 cm and a vertical accuracy of 15 cm. 

This position was logged concurrently with the bathymetry from WinFrog and the POS file using Fugro Pelagos PosMvLogger for the Westerly. For the multibeam data, the real-time solution was used for the final positioning and no post-processing was required. 

Processed LiDAR point positions for the SHOALS and VQ-820-G LiDAR sensors were derived relative to the ITRF00 ellipsoid using a Post Processed Kinematic (PPK) solution during GNSS post-processing, which used aircraft positioning data and final LiDAR point positions. These positions were then reduced to MLLW using a VDatum model created for the survey area by Fugro. For each flight, a Kinematic GPS (KGPS) navigation solution was processed in Applanix POSPac software. GPS data from the airplane and ground control base stations were input into a POSPac project and post-processed to obtain an optimal inertially-aided KGPS navigation solution. 

Fugro’s installed base station in Rockland was only intended to be a backup and was not used in the smartbase network.

Refer to the OPR-A366-KR-16 DAPR for additional details.</ns2:discussion><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>Augusta, ME</ns2:HVCRSiteID><ns2:stationID>MEOW</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>Waldo, ME </ns2:HVCRSiteID><ns2:stationID>MEWA</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>Penobscot, ME</ns2:HVCRSiteID><ns2:stationID>PNB6</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>Bar Harbor, ME</ns2:HVCRSiteID><ns2:stationID>BARH</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>Truro, MA</ns2:HVCRSiteID><ns2:stationID>MATU</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>U New Hampshire, NH</ns2:HVCRSiteID><ns2:stationID>NHUN</ns2:stationID></ns2:CORSStations><ns2:userInstalledStations><ns2:HVCRSiteID>Rockland, ME</ns2:HVCRSiteID><ns2:stationID>RKD16P</ns2:stationID></ns2:userInstalledStations></ns2:baseStations></ns2:PPK><ns2:horizontalDatum>ITRF2000 (WGS84: G1150)</ns2:horizontalDatum><ns2:RTK used="false" xsi:nil="true"/><ns2:comments/><ns2:PPP used="false" xsi:nil="true"/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:discussion>Multibeam vertical control for OPR-A366-KR-16 was provided by way of a Tidal Constituent And Residual Interpolation (TCARI) grid based on verified tide data from Portland (8418150), and Bar Harbor (8413320), ME. 

During field operations, all sounding data were initially reduced to MLLW using a combination of preliminary and verified tidal data along with a zone definition file (ZDF) that was based on tidal data from the Portland, ME station. This station is owned and operated by NOAA’s National Ocean Service (NOS) through the Center for Operational Oceanographic Products and Services (CO-OPS). Preliminary and verified tidal data was assembled by CO-OPS and accessed through NOAA’s Tides&amp;Currents website (http://tidesandcurrents.noaa.gov/). A cumulative file for the gauge in use was updated daily by appending the new data as it became available. It should be noted that these unverified tides were used in the field for preliminary processing only.

On December 12, 2016, the final TCARI grid was acquired from CO-OPS and applied to all sounding data using the TCARI GUI (version 16.8) and merged in CARIS HIPS. Verified tidal data were used for all final CUBE Surfaces, soundings, and S-57 Feature files.


LiDAR vertical control for OPR-A366-KR-16 was GPS-derived. POS files logged during data acquisition on each flight were post-processed using Applanix POSPac SmartBase routine to create a smoothed best estimate of trajectory (SBET) file. Following creation, the SmartBase SBETs were then applied to the data in SHOALS GCS, replacing the real-time GPS navigation position with a post-processed GPS position. The separation model was created with NOAA’s VDatum v3.6. This model also allowed for topographic data to be referenced to MLLW through the use of DTM-derived interpolation. 

Data was initially referenced to the ITRF00 (WGS84) ellipsoid using the Applanix Smart Base routine. An SBET solution was processed using a network of CORS stations, with MEOW, as control. It should be noted that the LiDAR data was maintained on the ellipsoid during processing.

All depth soundings were eventually reduced to MLLW in CARIS using this Fugro-created VDatum model. Topographic heights detected by LiDAR were also related to MLLW through the same method. The model was applied to the data, using the compute GPS tides utility, and then merged. 

Additional information discussing the vertical and horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion></ns1:verticalAndHorizontalControl><ns1:areaSurveyed><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. This project area is located in a highly trafficked area and will cover approximately 96 SNM of priority 1 area, 9 SNM of priority 2 area, 2 SNM of priority 3 area, and 1 SNM of priority 4 area as identified in the 2012 NOAA Hydrographic Survey Priorities. This project is located in Penobscot Bay, ME and encompasses approximately 108 SNM of survey area.</ns2:discussion></ns1:surveyPurpose><ns1:surveyStatistics><ns2:LNM><ns2:totalLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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_MBES_SBES>45.51</ns2:XL_MBES_SBES><ns2:MS_MBES>871.84</ns2:MS_MBES><ns2:percentXLLNM>5.2</ns2:percentXLLNM><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_lidar>119.49</ns2:XL_lidar></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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_MBES_SBES>45.51</ns2:XL_MBES_SBES><ns2:MS_MBES>871.84</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics><ns2:hullID>1231991</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES_SSS>0</ns2:MS_SBES_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_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES>0</ns2:MS_MBES><ns2:MS_lidar>1984.37</ns2:MS_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_lidar>119.49</ns2:XL_lidar></ns2:statistics><ns2:hullID>N87Q</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:discussion>The area was not divided into separate surveys for LiDAR acquisition, but three smaller blocks for data management purposes. For this reason, the LiDAR survey statistics are for the entire project and not just for H12885. 

The LiDAR program was proposed and planned for 100% of the area to be flown with a five by five (or better) spot spacing. A reconnaissance coverage survey would be used from the inshore limit (4-meter) to the 8-meter water depth. The actual line spacing was based on 200% coverage to try to provide maximum coverage and data density; this resulted in doubling the anticipated mainscheme linear nautical miles. In addition to this, the LiDAR area extends to the original survey limits and not to the revised survey limits as outlined in the project instructions (the area was reduced due to the allocated and available budget). For these reasons, the percentage of LiDAR mainscheme lines to LiDAR crosslines are not within the HSSD 2016 specification.  </ns2:discussion><ns2:surveyDates>2016-08-03</ns2:surveyDates><ns2:surveyDates>2016-08-04</ns2:surveyDates><ns2:surveyDates>2016-08-07</ns2:surveyDates><ns2:surveyDates>2016-08-08</ns2:surveyDates><ns2:surveyDates>2016-08-09</ns2:surveyDates><ns2:surveyDates>2016-08-10</ns2:surveyDates><ns2:surveyDates>2016-08-11</ns2:surveyDates><ns2:surveyDates>2016-08-12</ns2:surveyDates><ns2:surveyDates>2016-08-15</ns2:surveyDates><ns2:surveyDates>2016-08-16</ns2:surveyDates><ns2:surveyDates>2016-08-18</ns2:surveyDates><ns2:surveyDates>2016-08-19</ns2:surveyDates><ns2:surveyDates>2016-08-20</ns2:surveyDates><ns2:surveyDates>2016-08-21</ns2:surveyDates><ns2:surveyDates>2016-08-22</ns2:surveyDates><ns2:surveyDates>2016-08-23</ns2:surveyDates><ns2:surveyDates>2016-08-24</ns2:surveyDates><ns2:surveyDates>2016-09-02</ns2:surveyDates><ns2:surveyDates>2016-09-03</ns2:surveyDates><ns2:surveyDates>2016-09-04</ns2:surveyDates><ns2:surveyDates>2016-09-05</ns2:surveyDates><ns2:surveyDates>2016-09-06</ns2:surveyDates><ns2:surveyDates>2016-09-07</ns2:surveyDates><ns2:surveyDates>2016-09-08</ns2:surveyDates><ns2:surveyDates>2016-09-15</ns2:surveyDates><ns2:surveyDates>2016-09-16</ns2:surveyDates><ns2:surveyDates>2016-09-17</ns2:surveyDates><ns2:surveyDates>2016-09-20</ns2:surveyDates><ns2:surveyDates>2016-09-21</ns2:surveyDates><ns2:surveyDates>2016-09-24</ns2:surveyDates><ns2:surveyDates>2016-09-25</ns2:surveyDates><ns2:surveyDates>2016-09-26</ns2:surveyDates><ns2:surveyDates>2016-09-29</ns2:surveyDates><ns2:surveyDates>2016-07-11</ns2:surveyDates><ns2:surveyDates>2016-07-12</ns2:surveyDates><ns2:surveyDates>2016-07-13</ns2:surveyDates><ns2:surveyDates>2016-07-14</ns2:surveyDates><ns2:surveyDates>2016-07-15</ns2:surveyDates><ns2:surveyDates>2016-07-16</ns2:surveyDates><ns2:surveyDates>2016-07-17</ns2:surveyDates><ns2:surveyDates>2016-07-18</ns2:surveyDates><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The following LiDAR linear mileage was calculated for this survey during office processing: LiDAR mainscheme = 1420 miles, LiDAR crosslines = 35 miles (% of LiDAR XL to LiDAR MS = 2.5%)</ns2:comment></ns2:branchComment></ns2:comments><ns2:images><ns2:caption>Proposed LiDAR Line Plan</ns2:caption><ns2:link>Support Files\Proposed LiDAR Line Plan (Original Limits).PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Actual LiDAR Line Plan</ns2:caption><ns2:link>Support Files\Actual LiDAR Line Plan (Revised Limits).PNG</ns2:link></ns2:images><ns2:totalSurveyStats><ns2:diveOps>0</ns2:diveOps><ns2:DP>0</ns2:DP><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:SNM>31.3</ns2:SNM><ns2:bottomSamples>18</ns2:bottomSamples></ns2:totalSurveyStats></ns1:surveyStatistics><ns1:coverageGraphic><ns2:caption>H12885 Survey Coverage</ns2:caption><ns2:link>Support Files\H12884_Area_Coverage.png</ns2:link></ns1:coverageGraphic><ns1:surveyCoverage><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>In addition to LiDAR, MBES was also required in 4-8 meter water depth for feature disproval.</ns2:comment></ns2:branchComment></ns2:comments><ns2:results deviation="true"><ns2:discussion>Data holidays are present in the LiDAR data due to the removal of vessels and other surface structures. A gap between the LiDAR and MB data sets exists and is due to water clarity in the area. The water clarity had a negative impact on coverage within the four to eight-meter depth range, which varied significantly both spatially and temporally across the project area. A test flight was conducted during high tide in order to eliminate the low tide timing as the issue with water clarity, due to tidal flushing. Water conditions on this test flight were consistent with those seen on the flights timed around low tide, so it was concluded that the tide level was not the cause of the poor water clarity. Though not required, since the limit for the MB was greater than an 8-meter water depth, to bridge this gap, additional nearshore lines were conducted during field operations.</ns2:discussion></ns2:results><ns2:coverageRequirement><ns2:requiredCoverage>5 by 5 meter Lidar</ns2:requiredCoverage><ns2:waterDepth>Inshore limit to 8 meters water depth</ns2:waterDepth></ns2:coverageRequirement><ns2:coverageRequirement><ns2:requiredCoverage>Complete coverage multibeam with backscatter</ns2:requiredCoverage><ns2:waterDepth>Greater than 8 meters water depth</ns2:waterDepth></ns2:coverageRequirement></ns1:surveyCoverage><ns1:surveyQuality><ns2:comments/><ns2:discussion>Additional discussions regarding survey quality or data quality can be found in the Quality Control and Additional Results sections of this XML DR.</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy></ns1:surveyQuality><ns1:areaDescription><ns2:limits><ns2:southEast><ns2:longitude hemisphere="W">69.99519</ns2:longitude><ns2:latitude hemisphere="N">43.89024</ns2:latitude></ns2:southEast><ns2:northWest><ns2:longitude hemisphere="W">69.27089</ns2:longitude><ns2:latitude hemisphere="N">44.03404</ns2:latitude></ns2:northWest></ns2:limits><ns2:discussion>H12885 (Sheet ID 1) is located in Penobscot Bay, ME and encompasses approximately 31.3 SNM of Spaulding Island to Mosquito Island.  </ns2:discussion><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:comments/><ns2:results deviation="true"><ns2:images><ns2:caption>H12885 Sheet 1 Limits</ns2:caption><ns2:link>Support Files\H12885_Limits.png</ns2:link></ns2:images><ns2:discussion>The survey limits were revised to encompass the additional LiDAR data that was collected during field acquisition and were submitted as the final outlines following field operations. It should be noted that the limits were extended only to capture the extra LiDAR data and that the multibeam (MB) collection concluded at the survey limits as outlined in the project instructions.</ns2:discussion></ns2:results></ns1:surveyLimits></ns1:areaSurveyed><ns1:approvalSheet><ns1:signingPersonnel><ns2:approvalDate>2017-02-08</ns2:approvalDate><ns2:approverTitle>Senior Hydrographer (ACSM Cert. No. 226)</ns2:approverTitle><ns2:approverName>Dean Moyles</ns2:approverName></ns1:signingPersonnel><ns1:statements><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Standing and 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>As Chief of Party, Field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</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:statements><ns1:additionalReports><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName><ns2:reportDateSent>2017-02-07</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Horizontal and Vertical Control Report</ns2:reportName><ns2:reportDateSent>2017-02-07</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Coast Pilot Report</ns2:reportName><ns2:reportDateSent>2016-12-20</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet><ns1:dataAcquisitionAndProcessing><ns1:dataProcessing><ns1:additionalDataProcessing><ns2:comments/><ns2:issue><ns2:comments/><ns2:discussion>QCTools was used to scan each surface for potential fliers. The Detect fliers utility was initially run allowing the software to estimate heights, and it was also run where the Force flier heights value was set manually. This value varied depending on the resolution of the surface being scanned, which on occasion, yielded several false positives. Each finding from the utility was examined and checked for quality assurance. 

The Detect holidays, Grid QA, Scan features, and SBDARE checks were also used for the appropriate surface and feature files.</ns2:discussion><ns2:title>Hydroffice (QCTools version 1.5.2)</ns2:title></ns2:issue></ns1:additionalDataProcessing><ns1:drSoftware><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:featureObjectCatalog>NOAA Extended Attribute Files V5_4</ns1:featureObjectCatalog><ns1:imagerySoftware deviation="false"><ns1:name xsi:nil="true"></ns1:name><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:comments/><ns1:bathySoftware deviation="true"><ns1:name>HIPS/SIPS</ns1:name><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:version>9.1.8</ns1:version></ns1:bathySoftware><ns1:bathySoftware deviation="true"><ns1:name>HIPS/SIPS</ns1:name><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:version>9.1.9</ns1:version></ns1:bathySoftware></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_1m_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">106.85</ns2:max><ns2:min units="meters">-1.21</ns2:min></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_1m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">20</ns2:max><ns2:min units="meters">0</ns2:min></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_2m_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">106.82</ns2:max><ns2:min units="meters">-1.18</ns2:min></ns2:depthRange><ns2:resolution units="meters">2</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_2m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">40</ns2:max><ns2:min units="meters">18</ns2:min></ns2:depthRange><ns2:resolution units="meters">2</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_4m_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">106.31</ns2:max><ns2:min units="meters">-1.19</ns2:min></ns2:depthRange><ns2:resolution units="meters">4</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_4m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">80</ns2:max><ns2:min units="meters">36</ns2:min></ns2:depthRange><ns2:resolution units="meters">4</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_8m_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">106.31</ns2:max><ns2:min units="meters">-1.03</ns2:min></ns2:depthRange><ns2:resolution units="meters">8</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:surfaceName>H12885_MB_8m_MLLW_Final</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">106.31</ns2:max><ns2:min units="meters">72</ns2:min></ns2:depthRange><ns2:resolution units="meters">8</ns2:resolution></ns1:surface><ns1:surface><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H12885_LI_5m_MLLW</ns2:surfaceName><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>BASE Uncertainty</ns2:surfaceType><ns2:depthRange><ns2:max units="meters">10.47</ns2:max><ns2:min units="meters">-3.01</ns2:min></ns2:depthRange><ns2:resolution units="meters">5</ns2:resolution></ns1:surface><ns1:discussion>The surfaces have been reviewed for noisy data or 'fliers' that were incorporated into the gridded solution, causing the surface to be shoaler or deeper than the true seafloor. Spurious soundings that caused the gridded surface to be shoaler or deeper than the reliably measured seabed by greater than the maximum allowable TVU at that depth, have been rejected, and the surface recomputed. 

The NOAA CUBE parameters mandated in HSSD were used for the creation of all CUBE BASE surfaces in Survey H12885. 

Refer to the OPR-A366-KR-16 DAPR for a detailed description of the processing flow. </ns1:discussion><ns1:comments/></ns1:surfaces></ns1:dataProcessing><ns1:echoSoundingCorrections><ns1:calibrations><ns2:comments/><ns2:results deviation="true"><ns2:discussion>The R/V Westerly performed an additional patch test after needing to replace the leased IMU. The change out of the IMU with a Fugro-owned unit occurred on 10 August 2016. The patch test to calibrate the new IMU was performed on 13 August 2016. </ns2:discussion><ns2:calibration><ns2:date>2016-08-13</ns2:date><ns2:reason>IMU Swapout</ns2:reason><ns2:type>Multibeam Patch Test</ns2:type></ns2:calibration></ns2:results></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:corrections><ns2:comments/><ns2:results deviation="true"><ns2:discussion>One MB line (2P1B39-1550), acquired on Julian Day 2016-235 on sheet H12885, does not have delayed heave applied. The range of the POS file was not sufficient to cover the entire line.</ns2:discussion></ns2:results></ns1:corrections></ns1:echoSoundingCorrections><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:discussion>Towed SideScan Sonar (SSS) operations were not required by this contract, but the backscatter and beam imagery snippet data from all multibeam systems were logged and stored in the s7k files. All beam imagery snippet data was logged in the 7028 record of the s7k file for the project.

To yield the best results when processing the backscatter from the dual head 7125 systems, we recommend using the CARIS SIPS Backscatter routine. Currently, CARIS only uses the Beam Average, but in an upcoming release in v10 CARIS will apply the Time Series backscatter data. 

LiDAR reflectance was not part of the project instructions, but was processed and will be included in the final deliverables.</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:discussion>The R/V Westerly was equipped with dual head Reson 7125 sonars, which were operated in the full rate dual head (FRDH) mode in the Reson topside.

The Allied Prosilica GX3300 down-look camera and VQ-820-G (RIEGL) LiDAR sensor were not part of the project instructions or a requirement, but were installed to aid with feature verification and detection. By-products of these extra systems include the othro-mosaic, SHOALS-1000T reflectance, and RIEGL topo data and will be included as part of the final data deliverable. Patrick Keown (COR) approved these to be included in the multimedia folder. </ns1:discussion><ns1:majorSystem><ns2:model>POS M/V Version 5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>POS M/V Version 6</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SV&amp;P</ns2:model><ns2:manufacturer>Applied Micro-Systems</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>7125</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SVP70</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SHOALS-1000T</ns2:model><ns2:manufacturer>Optech</ns2:manufacturer><ns2:type>Lidar System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>Prosilica GX3300</ns2:model><ns2:manufacturer>Allied</ns2:manufacturer><ns2:type>Down-Look Camera</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>820G</ns2:model><ns2:manufacturer>RIEGL</ns2:manufacturer><ns2:type>Topo-Lidar System</ns2:type></ns1:majorSystem><ns1:comments/></ns1:equipment><ns1:vessels><ns1:discussion>R/V Westerly (1231991) and the Beechcraft King Air A90 (N87Q) systems acquired all sounding data for H12885. 

Fugro Pelagos, Inc. (Fugro) mobilized a catamaran-style jet drive survey boat (Westerly), which was equipped with an over the stern pole that housed an underwater IMU and dual head Reson 7125 multibeam sonars (dual meaning two independent systems). The Reson systems and IMU were installed on a special mount, where each Reson 7125 was rotated approximately 15 degrees and the IMU was centered above the 7125s. The vessel was utilized to survey in water depths greater than eight meters. In addition to the vessel, a small aircraft was fitted with a SHOALS-1000T Airborne LiDAR Bathymetry (ALB) system to map data inshore of the 8-meter contour. It should be noted that an Allied Prosilica GX3300 down-look camera and VQ-820-G (RIEGL) LiDAR sensor were also installed. These extra systems were not part of the project instructions or a requirement, but were installed to aid with feature verification and detection. </ns1:discussion><ns1:vessel><ns2:LOA units="feet">44</ns2:LOA><ns2:hullID>1231991</ns2:hullID><ns2:draft units="feet">2</ns2:draft></ns1:vessel><ns1:vessel><ns2:LOA units="meters">10.8</ns2:LOA><ns2:hullID>N87Q</ns2:hullID><ns2:draft units="meters">0</ns2:draft></ns1:vessel><ns1:comments/><ns1:images><ns2:caption>R/V Westerly (1231991)</ns2:caption><ns2:link>Support Files\RV Westerly (1231991).PNG</ns2:link></ns1:images><ns1:images><ns2:caption>Beechcraft King Air A90 (N87Q)</ns2:caption><ns2:link>Support Files\N87Q.PNG</ns2:link></ns1:images></ns1:vessels><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:soundSpeedMethods><ns1:discussion>R/V Westerly was equipped with two AML 1000 dbar Sound Velocity &amp; Pressure (AML SV&amp;P) Smart Sensors. The AML SV&amp;P directly measures sound velocity through a time of flight calculation, and measures pressure with a temperature compensated semiconductor strain gauge at a 10Hz sample rate. The instrument has a 0.015m/s resolution with a ±0.05m/s accuracy for sound velocity measurements and a 0.01 dbar resolution and a ±0.5m dbar accuracy for pressure.  

Sound Speed quality control checks were conducted as per the HSSD 2016, Section 5.2.3.3 and can be found in Separate II.</ns1:discussion><ns1:images><ns2:caption>AML SVP</ns2:caption><ns2:link>Support Files\AML SVP.png</ns2:link></ns1:images><ns1:comments/><ns1:castFrequency>Sound velocity casts were normally performed every two to three hours on the R/V Westerly.  For each cast, the probes were held at the surface for one to two minutes to achieve temperature equilibrium.  The probes were then lowered and raised at a rate of 1 m/s.  Between casts, the sound velocity sensors were stored inside the lab or in fresh water to minimize salt-water corrosion and to hold them at ambient water temperature. 

Refer to the DAPR for additional information.</ns1:castFrequency></ns1:soundSpeedMethods><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:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><ns2:images><ns2:caption>H12885 SVP Cast</ns2:caption><ns2:link>Support Files\H12885_SVP_Cast.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 SSP Refraction</ns2:caption><ns2:link>Support Files\H12885_SSP_Refraction.png</ns2:link></ns2:images><ns2:discussion>A general downward and/or upward cupping is noticeable in the across-track sounding profiles for certain areas. Sound speed refraction errors were seen in the outer beams on the majority of survey lines conducted and were on the order of 0.10 to 0.20 meters. These errors are a result of the strong tidal mixing in the area, which not only carries sediment, but also causes a change in water surface temperature and salinity. 

The sound speed profiles conducted throughout the project had an increased inconsistency throughout the water column, much more evident at the surface or near the face of the sonars. In order to mitigate these sound speed errors, the frequency of sound speed casts was increased and the line spacing reduced. Data were examined (and filtered) in CARIS HIPS Subset Editor routine to ensure the data met IHO Order 1a specifications.</ns2:discussion><ns2:title>Sound Speed Refraction (SSR)</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Fishing Gear</ns2:caption><ns2:link>Support Files\Fishing Gear.JPG</ns2:link></ns2:images><ns2:discussion>The survey was awarded and conducted during the peak of lobster season, resulting in an extremely high presence of fishing gear (and fishing vessels) in the survey area. This resulted in having to maneuver in and around the surface buoys and fishing vessels causing not only numerous in-fills and re-runs, but increased time spent on manually rejecting erroneous data (fishing gear in the water column) in CARIS HIPS. 

Because of the density of fishing gear in the area, vessel speed was at times reduced to near idle. Entanglements between the survey vessel’s deployed sonar equipment and fishing gear happened quite often, resulting in a loss of survey time. The risk of entanglement also increased before and after the high tide peaks due to submerged buoys in some areas. </ns2:discussion><ns2:title>Fishing Gear</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:discussion>There was a high presence of marine life in various locations within the survey area. This resulted in not only numerous in-fills and re-runs, but increased time spent on manually rejecting the erroneous data in CARIS HIPS and SIPS.</ns2:discussion><ns2:title>Marine Life</ns2:title></ns2:issue><ns2:issue><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Additional tide busts of up to 0.55 meters were found during office processing in the vicinity of Graffam Island. All are within the 2016 HSSD allowable error budget for tide.</ns2:comment></ns2:branchComment></ns2:comments><ns2:images><ns2:caption>H12885 Tidal Bust Overview</ns2:caption><ns2:link>Support Files\Tidal_Bust_TCARI_Model_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Tidal Bust (Julian Day 2016-249 Shown in Dark Green)</ns2:caption><ns2:link>Support Files\Tidal_Bust_TCARI_Model (JD 2016-249 Dark Green).png</ns2:link></ns2:images><ns2:discussion>Small tide busts, on the order of 0.15m to 0.20m were noticed between some mainscheme lines. Mainscheme lines that were conducted on Julian Day 2016-249 are 0.15 to 0.20 meters deeper than the adjacent data. This can be attributed to the overall uncertainly in the gauge data and TCARI Model.

All data fell within IHO Order 1a accuracy specifications. Note: GPS Heights were applied to the data set and a GPS Tide Computed (referenced to the WGS84 ellipsoid), but this was for troubleshooting purposes only, mostly to verify tide bust. Final tide corrections for this survey were from the TCARI Model.</ns2:discussion><ns2:title>Tidal Bust</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Water Clarity</ns2:caption><ns2:link>Support Files\Water Clarity Image.png</ns2:link></ns2:images><ns2:discussion>In addition to being an issue in equipment effectiveness, water clarity was a factor affecting soundings. Refer to section B.2.5 for the explanation on water clarity. </ns2:discussion><ns2:title>Water Clarity</ns2:title></ns2:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:uncertainty><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>A finalized LiDAR surface was created during office processing since one was not submitted.  The final uncertainty value for this grid was computed from the &quot;Greater of the two&quot; per the HSSD section 5.3.1.2 which states &quot;The uncertainty value for the grid shall be the greater of the standard deviation and the a priori computed uncertainty estimate.&quot; It was found that 75% of nodes passed IHO Order 1 uncertainty standards which differs from the reported 100% since the reported value was derived from the &quot;Uncertainty-weighted&quot; parent surface.</ns2:comment><ns2:images><ns2:caption>Finalized LiDAR surface results</ns2:caption><ns2:link>file:///M:/OPRA366KR16/Surveys/H12885/Compilation/Report/Support%20Files/H12885_LI_5m_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images></ns2:branchComment></ns2:comments><ns2:images><ns2:caption>H12885 Uncertainty</ns2:caption><ns2:link>Support Files\H12885_Uncertainty.tif</ns2:link></ns2:images><ns2:images><ns2:caption>Hydroffice Surface Report H12885 (Priority 1) 1m Final </ns2:caption><ns2:link>Support Files\H12885_MB_1m_MLLW_Final.QAv2.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Hydroffice Surface Report H12885 (Priority 1) 2m Final </ns2:caption><ns2:link>Support Files\H12885_MB_2m_MLLW_Final.QAv2.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Hydroffice Surface Report H12885 (Priority 1) 4m Final</ns2:caption><ns2:link>Support Files\H12885_MB_4m_MLLW_Final.QAv2.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Hydroffice Surface Report H12885 (Priority 1) 8m Final</ns2:caption><ns2:link>Support Files\H12885_MB_8m_MLLW_Final.QAv2.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>LTE tool results example</ns2:caption><ns2:link>Support Files\LTE Tool Results Example.png</ns2:link></ns2:images><ns2:images><ns2:caption>Total Bottom Uncertainty for SHOALS data sample</ns2:caption><ns2:link>Support Files\Total Bottom Uncertainty for SHOALS Data Sample.png</ns2:link></ns2:images><ns2:images><ns2:caption>TPU Survey Area</ns2:caption><ns2:link>Support Files\TPU Survey Area.jpg</ns2:link></ns2:images><ns2:discussion>The majority of the data fell within IHO Order 1a accuracy specifications. Nodes that exceeded the allowable specifications were located in areas where the outer beams of the coverage boundaries were the single contributor to the surface, with a small portion of the nodes exceeding specifications attributable to rapid topographical changes such as rock outcrops, etc. 

TPU was derived in CARIS from a combination of real-time and fixed values for equipment, vessel characteristics, sound speed, and tide and tide zoning. The percentage of nodes within IHO Order 1a, were computed by CARIS using the Surface QC Report utility and are as follows:

Surface                            Depth Range (m)      % of nodes within IHO Order1a
H12885_MB_1m_MLLW              0-20                                      99.99%
H12885_MB_2m_MLLW             18-40                                     99.99%
H12885_MB_4m_MLLW             36-80                                     99.99%
H12885_MB_8m_MLLW            72-160                                    100%
H12885_LI_5m_MLLW         -3.01-10.47                                  100%

The uncertainty is generally lowest near the sonar nadir beams (in the sectors where the dual heads overlap) and increases toward the outside of each swath. This is expected and primarily a result of the sonar’s device model used within CARIS HIPS for TPU calculations. In general, TPU varies proportionally to water depth. Outer beams also have higher uncertainty values as a function of the bottom-detection algorithms within the sonar.

In addition to using the surface QC report in CARIS to derive the TPU for H12885, HydroOffice QCTools were used to compute the total propagated vertical uncertainty (TVU). Both methods yielded similar results.

Regarding LiDAR, in order to accurately determine TVU for all depth data collected as part of the project, a ‘TPU’ line was designed and flown on eight separate occasions. One area of low gradient seabed was identified across the TPU line. Once all of the depth data had been processed, cleaned, and reduced to datum by a VDatum model, Fugro’s LiDAR Total Error (LTE) tool (an extension in ArcGIS) was used to determine SHOALS uncertainty. LTE is a tool implemented in ArcGIS that uses spatial analysis of LiDAR point elevations to determine statistical variance of a significant data sample. The LTE tool application shows the common parameters for data sampling, as well as the water depth ranges being analyzed (or elevation on the ellipsoid). The inputs were the Hydrographic Output Files (HOF) files generated in the SHOALS-GCS processing software. The results of the analysis were tabulated and plotted to derive a depth-dependent model of Total Bottom Uncertainty (TBU). Refer to the Appendix II for the full report.</ns2:discussion><ns2:values><ns2:tideUncertainty><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>TCARI</ns2:tideMethod><ns2:measured units="meters">0</ns2:measured></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:surface units="meters/second">0.25</ns2:surface><ns2:hullID>1231991</ns2:hullID><ns2:measuredCTD units="meters/second">2.58</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values></ns1:uncertainty><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:crosslines><ns2:comments/><ns2:images><ns2:caption>H12885 Crossline Overview</ns2:caption><ns2:link>Support Files\01_H12885_MB_Crossline_Overview.tif</ns2:link></ns2:images><ns2:images><ns2:caption>2PB09-TIE02 Subset Overview</ns2:caption><ns2:link>Support Files\2P1B09-TIE02_Subset_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>2PB09-TIE02 Subset</ns2:caption><ns2:link>Support Files\2P1B09-TIE02_Subset.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 LiDAR Crossline Overview</ns2:caption><ns2:link>Support Files\01_H12885_LiDAR_Crossline_Overview.tif</ns2:link></ns2:images><ns2:images><ns2:caption>Flight Line 20160713 1713 01191 QC</ns2:caption><ns2:link>Support Files\02_04DS16000_004_160713_1713_A Histogram.png</ns2:link></ns2:images><ns2:images><ns2:caption>Flight Line 20160713 1713 01191</ns2:caption><ns2:link>Support Files\03_20160713_1713_01191_DIFF.bmp</ns2:link></ns2:images><ns2:discussion>Multibeam crosslines were planned and well distributed throughout the survey to ensure adequate quality control. Total crossline length surveyed was 45.5 nautical miles or 5.2 percent of the total mainscheme line length. Depending on depth, each crossline was compared to the entire mainscheme line plan through a 1m, 2m, or 4m CUBE surface using the CARIS HIPS QC report routine. 

The majority of the QC Reports fall well within the required accuracy specifications. However, crossline 2P1B09-TIE02 run by R/V Westerly in the northeastern half of H12885 contains several beams in the QC report that fall below the 95% confidence level. This is due to a very steep slope and to sound speed refraction, as illustrated in the graphic labelled “2P1B09-TIE02_Subset”. Despite the issues raised by the steep slope and the sound speed refraction, good conformity is still seen between the mainscheme lines and the crossline. Mainscheme lines are shown in purple, and the crossline (2P1B09-TIE02) is shown in light green. All data are well within the IHO Order 1a allowable error. 

LiDAR crosslines were planned and well distributed throughout the survey to ensure adequate quality control. A total of 17 specific crosslines were planned and flown perpendicular to the mainscheme survey lines. 

A difference analysis between the crosslines and the main survey lines was performed using the Crosscheck program within Fledermaus. A surface grid was created from the production lines at a bin size of approximately 3 meters. The crossline points were then compared to the surface, and point-to-surface statistics generated. The crossline comparison documents illustrate that elevated standard deviation of the differences occurs over rocky and high gradient seabed. In relatively featureless areas of seabed, the differences present a much lower variability.

Quality Control Results are located in Separate II Digital Data.</ns2:discussion></ns1:crosslines><ns1:junctions><ns2:comments/><ns2:images><ns2:caption>H12885 Junctions Overview</ns2:caption><ns2:link>Support Files\H12885 Junctions Overview.png</ns2:link></ns2:images><ns2:discussion>Comparisons between H12885 were made with contemporary survey H10820, H12256, H12478 and the current surveys H12884 and H12887.  The results are as follows:
</ns2:discussion><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Junction between Survey H12885 and H10820</ns2:caption><ns2:link>Support Files\Junction between Survey H12885 and H10820.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H10820 Diff Surface</ns2:caption><ns2:link>Support Files\H12885_Minus_H10820_1m_2m_4m_Diff_Surface.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H10820 Diff 1m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H10820_Diff_1m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H10820 Diff 2m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H10820_Diff_2m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H10820 Diff 4m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H10820_Diff_4m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:discussion>The conformity between H12885 and the junction with survey H10820 was inspected during processing using the CARIS HIPS Subset Editor routine and finalized as BASE Surfaces. A Difference Surface was generated using the CARIS HIPS Difference Surface function; comparing the depths from the H12885 survey (1, 2, and 4-meter resolution) CUBE surfaces against the H10820 survey. Using the Compute Statistics function in CARIS, the difference surface yielded the following results: a standard deviation of 0.5 meters, and a mean difference of 0.2 meters for the one-meter surface, along with a standard deviation of 0.5 meters, and a mean difference of 0.1 meters for the two-meter surface, and a standard deviation of 0.6 meters, and a mean difference of 0.2 meters for the four-meter surface. The surveys are in agreement along their common borders and well within the total allowable IHO Order 1a vertical uncertainty. The majority of the difference between the two surveys can be attributed to the course resolution of H10820 data that was provided for the survey junction.  Sound-speed refraction with tide error also accounts for a small portion of that difference.</ns2:discussion><ns2:survey><ns2:scale>10000</ns2:scale><ns2:relativeLocation>SE</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship Rude</ns2:fieldUnit><ns2:year>1998</ns2:year><ns2:registryNumber>H10820</ns2:registryNumber></ns2:survey></ns2:junction><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Junction between Survey H12885 and H12256</ns2:caption><ns2:link>Support Files\Junction between Survey H12885 and H12256.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12256 Diff_Surface</ns2:caption><ns2:link>Support Files\H12885_Minus_H12256_1m_2m_4m_8m_Diff_Surface.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12256 Diff 1m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12256_Diff_1m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12256 Diff 2m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12256_Diff_2m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12256 Diff 4m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12256_Diff_4m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12256 Diff 8m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12256_Diff_8m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:discussion>The conformity between H12885 and the junction with survey H12256 was inspected during processing using the CARIS HIPS Subset Editor routine and finalized as BASE Surfaces. A Difference Surface was generated using the CARIS HIPS Difference Surface function; comparing the depths from the H12885 survey (1, 2, 4, and 8-meter resolution) CUBE surfaces against the H12256 survey. Using the Compute Statistics function in CARIS, the difference surface yielded the following results: a standard deviation of 0.4 meters, and a mean difference of 0.4 meters for the one-meter surface, along with a standard deviation of 0.4 meters, and a mean difference of 0.3 meters for the two-meter surface, and a standard deviation of 0.7 meters, and a mean difference of 0.0 meters for the four-meter surface, and a standard deviation of 0.6 meters, and a mean difference of 0.0 meters for the eight-meter surface. The surveys are in agreement along their common borders and well within the total allowable IHO Order 1a vertical uncertainty. The majority of the difference between the two surveys can be attributed to motion artifacts in the H12256 data along with sound speed refraction and tide error accounting for a small portion of that difference.</ns2:discussion><ns2:survey><ns2:scale>10000</ns2:scale><ns2:relativeLocation>E</ns2:relativeLocation><ns2:fieldUnit>Williamson &amp; Associates, Inc.</ns2:fieldUnit><ns2:year>2010</ns2:year><ns2:registryNumber>H12256</ns2:registryNumber></ns2:survey></ns2:junction><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Junction between Survey H12885 and H12478</ns2:caption><ns2:link>Support Files\Junction between Survey H12885 and H12478.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12478 Diff Surface</ns2:caption><ns2:link>Support Files\H12885_Minus_H12478_2m_4m_Diff_Surface.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12478 Diff 2m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12478_Diff_2m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12478 Diff 4m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12478_Diff_4m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:discussion>The conformity between H12885 and the junction with survey H12478 was inspected during processing using the CARIS HIPS Subset Editor routine and finalized as BASE Surfaces. A Difference Surface was generated using the CARIS HIPS Difference Surface function; comparing the depths from the H12885 survey (2 and 4-meter resolution) CUBE surfaces against the H12478 survey. Using the Compute Statistics function in CARIS, the difference surface yielded the following results: a standard deviation of 0.2 meters, and a mean difference of 0.4 meters for the two-meter surface, along with a standard deviation of 0.1 meters, and a mean difference of 0.3 meters for the four-meter surface. The surveys are in agreement along their common borders and well within the total allowable IHO Order 1a vertical uncertainty. The majority of the difference between the two surveys can be attributed to motion artifacts in the H12478 data along with sound speed refraction and tide error accounting for a small portion of that difference.</ns2:discussion><ns2:survey><ns2:scale>20000</ns2:scale><ns2:relativeLocation>SE</ns2:relativeLocation><ns2:fieldUnit>Williamson &amp; Associates, Inc.</ns2:fieldUnit><ns2:year>2012</ns2:year><ns2:registryNumber>H12478</ns2:registryNumber></ns2:survey></ns2:junction><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Junction between Survey H12885 and H12884</ns2:caption><ns2:link>Support Files\Junction between Survey H12885 and H12884.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12884 Diff Surface</ns2:caption><ns2:link>Support Files\H12885_Minus_H12884_1m_2m_4m_8m_Diff_Surface.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12884 Diff 1m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12884_Diff_1m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12884 Diff 2m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12884_Diff_2m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12884 Diff 4m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12884_Diff_4m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12884 Diff 8m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12884_Diff_8m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:discussion>The conformity between H12885 and the junction with survey H12884 was inspected during processing using the CARIS HIPS Subset Editor routine and finalized as BASE Surfaces. A Difference Surface was generated using the CARIS HIPS Difference Surface function; comparing the depths from the H12885 survey (1, 2, 4, and 8-meter resolution) CUBE surfaces against the H12884 survey. Using the Compute Statistics function in CARIS, the difference surface yielded the following results: a standard deviation of 0.2 meters, and a mean difference of 0.0 meters for the one-meter surface, a standard deviation of 0.2 meters, and a mean difference of 0.0 meters for the two-meter surface, a standard deviation of 0.5 meters, and a mean difference of 0.2 meters for the four-meter surface, and a standard deviation of 0.9 meters, and a mean difference of 0.1 meters for the eight-meter surface. The surveys are in agreement along their common borders and well within the total allowable IHO Order 1a vertical uncertainty. The majority of the difference between the two surveys can be attributed to sound speed refraction with tide error also accounting for a small portion of that difference. The increased standard deviation between the higher resolution grids can also be attributed to the grid, or node placement in the CUBE surface during creation.  When CARIS creates the nodes for the H12885 8-meter surface, these will differ from the position of the nodes for H12884 8-meter surface.  This small horizontal shift in the grid nodes can result in a depth difference, especially in areas with an irregular seafloor.</ns2:discussion><ns2:survey><ns2:scale>10000</ns2:scale><ns2:relativeLocation>N</ns2:relativeLocation><ns2:fieldUnit>Fugro</ns2:fieldUnit><ns2:year>2016</ns2:year><ns2:registryNumber>H12884</ns2:registryNumber></ns2:survey></ns2:junction><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Junction between Survey H12885 and H12887</ns2:caption><ns2:link>Support Files\Junction between Survey H12885 and H12887.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12887 Diff Surface</ns2:caption><ns2:link>Support Files\H12885_Minus_H12887_2m_4m_8m_Diff_Surface.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12887 Diff 2m Diff_Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12887_Diff_2m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12887 Diff 4m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12887_Diff_4m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:images><ns2:caption>H12885 Minus H12887 Diff 8m Diff Histogram</ns2:caption><ns2:link>Support Files\H12885_Minus_H12887_Diff_8m_Diff_Histogram.tif</ns2:link></ns2:images><ns2:discussion>The conformity between H12885 and the junction with survey H12887 was inspected during processing using the CARIS HIPS Subset Editor routine and finalized as BASE Surfaces. A Difference Surface was generated using the CARIS HIPS Difference Surface function; comparing the depths from the H12885 survey (2, 4, and 8-meter resolution) CUBE surfaces against the H12887 survey. Using the Compute Statistics function in CARIS, the difference surface yielded the following results: a standard deviation of 0.4 meters, and a mean difference of -0.3 meters for the two-meter surface, a standard deviation of 0.5 meters, and a mean difference of -0.2 meters for the four-meter surface, and a standard deviation of 0.6 meters, and a mean difference of -0.3 meters for the eight-meter surface. The surveys are in agreement along their common borders and well within the total allowable IHO Order 1a vertical uncertainty. The majority of the difference between the two surveys can be attributed to sound speed refraction with tide error also accounting for a small portion of that difference. The increased standard deviation between the higher resolution grids can also be attributed to the grid, or node placement in the CUBE surface during creation.  When CARIS creates the nodes for the H12885 8-meter surface, these will differ from the position of the nodes for H12887 8-meter surface.  This small horizontal shift in the grid nodes can result in a depth difference, especially in areas with an irregular seafloor.   </ns2:discussion><ns2:survey><ns2:scale>10000</ns2:scale><ns2:relativeLocation>NE</ns2:relativeLocation><ns2:fieldUnit>Fugro</ns2:fieldUnit><ns2:year>2016</ns2:year><ns2:registryNumber>H12887</ns2:registryNumber></ns2:survey></ns2:junction></ns1:junctions><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:comments/><ns2:images><ns2:caption>H12885 Final Density</ns2:caption><ns2:link>Support Files\01_H12885_Final_Density.tif</ns2:link></ns2:images><ns2:discussion>The NOS HSSD, March 2016, require 95% of all nodes to be populated with at least five soundings. Survey H12885 met these project specifications.

Surface                                      Depth Range (m)       % of nodes with five soundings  
H12885_MB_1m_MLLW_Final              0-20                                   99.52%
H12885_MB_2m_MLLW_Final            18-40                                   99.99%
H12885_MB_4m_MLLW_Final            36-80                                   99.93%
H12885_MB_8m_MLLW_Final            72-160                                 99.24%
H12885_LI_5m_MLLW_Final          -3.01-10.47                              75.66%

Detection requirements were met by minimizing vessel speed when necessary, using sonar range scales appropriate to the water depth to maximize ping rates, and maximizing swath overlap. These variables were adjusted in real-time by the online acquisition crew based on the WinFrog QC and coverage displays. The processing crew provided feedback after preliminary processing and coverage creation in CARIS HIPS. Infill lines were run as necessary.

The LiDAR program was proposed and planned for 100% of the area to be flown with a five by five (or better) spot spacing. In other words, a reconnaissance coverage survey would be used from the inshore limit (4 meters) to the 8-meter water depth. This explains the percentage of nodes that fall below the five sounding per bin threshold. It should be noted that per the project instructions, the final LiDAR surface was binned at five meters.         </ns2:discussion><ns2:title>Data Density</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:discussion>Positioning system confidence checks for the R/V Westerly were conducted daily using the POS/MV controller software. The controller software had numerous real-time displays that were monitored throughout the survey to ensure the positional accuracies specified in the NOS HSSD were achieved. These include, but are not limited to the following: GPS Status, Position Accuracy, and Receiver Status, which includes Horizontal Dilution of Position (HDOP) and Precise Dilution of Position (PDOP), and Satellite Status. During periods of high HDOP and/or a low number of available satellites, survey operations were suspended. 

Sonar system confidence checks were performed weekly by comparing post processed depth information collected by multiple vessels surveying over a common area. In addition, bar checks were performed to maintain a high confidence level. Sound Velocity Probe confidence checks were conducted weekly by producing comparable sound velocity data between all vessels. This check was carried out by having all sound velocity profiling equipment perform a cast in close proximity to each other in a near simultaneous time period.</ns2:discussion><ns2:title>MB Quality Control Checks</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:discussion>Before each flight, a POS Hold is conducted to ensure Full Nav has been initialized. Once the Position and Orientation System for Airborne Vehicles (POS/AV) system powers up and the “Full Nav” indicator has been reached, the POS initialization hold is started for a minimum of 6 minutes in a static position. After holding the static position, the aircraft can taxi to the takeoff position. Full Nav status indicates that Global Navigation Satellite System (GNSS) position and velocities have been resolved and will aid to initialize the inertial navigation frame, which is the process of aligning the navigation frame with respect to the vertical (levelling) and orientation to North (heading).</ns2:discussion><ns2:title>LiDAR POS Hold Position Checks</ns2:title></ns2:issue></ns1:additionalQualityControl><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Water Clarity</ns2:caption><ns2:link>Support Files\Water Clarity 1.png</ns2:link></ns2:images><ns2:discussion>The greatest contributor to depth performance, seabed coverage, and data quality with a LiDAR system is water clarity. To address this concern, Fugro conducted water clarity assessments across the project area, from the planning phase through to the final flight, using several different techniques. Refer to the DAPR for more details.

On 13 June 2016, Fugro staff undertook an aerial reconnaissance mission in the vicinity of Penobscot Bay. Conditions of the water clarity were documented in photos and overall, found to be relatively poor. Water was seen to be clear in the very shallow depths (likely, under four meters) and murky in deeper depths. 

In general, water clarity in the Penobscot Bay survey area was less than ideal for ALB acquisition. Clear water was more common in shallow areas, but water in the four to eight meter range of interest was typically murky. 

Conditions were similar in the survey area around Vinalhaven Island and North Haven Island as well, with shallow depths being clearer than the depth range of interest (four to eight meters). The bathymetry in the area tends toward a steep descent into depths outside the range of ALB. 

The water clarity had a negative impact on coverage within the four to eight meter depth range, a range of particular interest to this survey. A test flight was conducted during high tide in order to eliminate the low tide timing as the issue with water clarity, due to tidal flushing. Water conditions on this test flight were consistent with those seen on the flights timed around low tide so it was concluded that the tide level was not the cause of the poor water clarity.</ns2:discussion><ns2:title>Water Clarity</ns2:title></ns2:issue></ns2:results></ns1:equipmentEffectiveness></ns1:qualityControl></ns1:dataAcquisitionAndProcessing></ns1:descriptiveReport>