<?xml version="1.0" encoding="utf-8"?>
<smd:surveyMetadata xmlns:hsd="http://svn.pydro.noaa.gov/2025/01/AllGlobalTypes" xmlns:smd="http://svn.pydro.noaa.gov/2025/01/SurveyMetadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2025/01/SurveyMetadata http://svn.pydro.noaa.gov/2025/01/SurveyMetadata.xsd">
    <smd:metadata>
        <smd:project>
            <smd:uniqueId>OPR-N338-NRTSE-23</smd:uniqueId>
            <smd:name>Columbia River, WA and OR</smd:name>
            <smd:state>Oregon</smd:state>
            <smd:state>Washington</smd:state>
        </smd:project>
        <smd:survey>
            <smd:uniqueId>H13847</smd:uniqueId>
            <smd:name>Bonneville to Drano Lake</smd:name>
        </smd:survey>
        <smd:date>
            <smd:utc>-0700</smd:utc>
            <smd:start>2023-09-07</smd:start>
            <smd:end>2023-09-16</smd:end>
        </smd:date>
        <smd:poc>
            <smd:responsibleParty>DOC/NOAA/NOS/OCS -- Office of Coast Survey</smd:responsibleParty>
            <smd:contactInfo>HSD.Chief@noaa.gov</smd:contactInfo>
            <smd:fieldUnit>NOAA NRT-Seattle</smd:fieldUnit>
        </smd:poc>
        <smd:dataLicense>
            <hsd:classification>CC0-1.0 (NOAA Field Units)</hsd:classification>
            <hsd:spdx>
                <hsd:licenseIdentifier>CC0-1.0</hsd:licenseIdentifier>
                <hsd:licenseDeed>https://creativecommons.org/publicdomain/zero/1.0/</hsd:licenseDeed>
                <hsd:legalCode>https://creativecommons.org/publicdomain/zero/1.0/legalcode</hsd:legalCode>
            </hsd:spdx>
            <hsd:description>These data were produced by NOAA and are in the public domain within the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0).</hsd:description>
        </smd:dataLicense>
        <smd:graphics>
            <smd:overview>file:///M:/OPR-N338-NRTSE-23/Surveys/H13847/01_HDR/Reports/QC/PI_survey%20area.png</smd:overview>
            <smd:surveyArea>file:///M:/OPR-N338-NRTSE-23/Surveys/H13847/01_HDR/Reports/QC/Survey%20Surface.png</smd:surveyArea>
        </smd:graphics>
        <smd:grid>
            <smd:gridName>H13847_MB_VR_CRD_1of1</smd:gridName>
            <smd:coordinateReferenceSystem>
                <smd:projection>Projected UTM 10</smd:projection>
                <smd:horizontal>
                    <smd:datum>North American Datum 1983 (2011)</smd:datum>
                    <smd:unit>arc degree</smd:unit>
                </smd:horizontal>
                <smd:vertical>
                    <smd:datum>Columbia River Datum</smd:datum>
                    <smd:unit>meters</smd:unit>
                </smd:vertical>
            </smd:coordinateReferenceSystem>
            <smd:soundingTechnique>found by multi beam</smd:soundingTechnique>
            <smd:detection>
                <smd:significantFeature>Yes</smd:significantFeature>
                <smd:leastDepth>Yes</smd:leastDepth>
                <smd:size>
                    <smd:fixed>1.0m (Critical)</smd:fixed>
                    <smd:variable>N/A</smd:variable>
                </smd:size>
            </smd:detection>
            <smd:coverageAssessment>
                <smd:fullSeafloor>Yes</smd:fullSeafloor>
                <smd:bathymetric>Yes</smd:bathymetric>
                <smd:interpolated>No</smd:interpolated>
            </smd:coverageAssessment>
            <smd:uncertainty>
                <smd:horizontal>
                    <smd:fixed>2m (Critical)</smd:fixed>
                    <smd:variable>N/A</smd:variable>
                </smd:horizontal>
                <smd:vertical>
                    <smd:fixed>0.25m (Critical)</smd:fixed>
                    <smd:variable>0.75% (Exceptional/Critical)</smd:variable>
                </smd:vertical>
            </smd:uncertainty>
        </smd:grid>
    </smd:metadata>
    <smd:equipmentList>
        <smd:platform>
            <smd:vessel>
                <smd:hull>
                    <smd:idNumber>S3006</smd:idNumber>
                    <smd:name>NRT Seattle</smd:name>
                </smd:hull>
                <smd:positioningSystem>
                    <smd:equipment>
                        <smd:type>Positioning and Attitude System</smd:type>
                        <smd:manufacturer>Applanix</smd:manufacturer>
                        <smd:systemName>POS MV 320 v5</smd:systemName>
                        <smd:modelNumber>POS MV V5</smd:modelNumber>
                        <smd:serialNumber>14128</smd:serialNumber>
                        <smd:calibrationDate>2023-04-13</smd:calibrationDate>
                    </smd:equipment>
                </smd:positioningSystem>
                <smd:depthHeightSensor>
                    <smd:equipment>
                        <smd:type>Multibeam</smd:type>
                        <smd:manufacturer>Kongsberg Maritime</smd:manufacturer>
                        <smd:systemName>EM 2040C</smd:systemName>
                        <smd:modelNumber>EM2040C Processing Unit 2U</smd:modelNumber>
                        <smd:serialNumber>CZC3440R5X</smd:serialNumber>
                        <smd:frequency>NA</smd:frequency>
                        <smd:calibrationDate>2018-05-02</smd:calibrationDate>
                        <smd:accuracyCheckDate>2023-03-28</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:depthHeightSensor>
                <smd:soundSpeedSensor>
                    <smd:equipment>
                        <smd:type>Conductivity, Temperature, and Depth Sensor</smd:type>
                        <smd:manufacturer>SonTek</smd:manufacturer>
                        <smd:systemName>CastAway-CTD</smd:systemName>
                        <smd:modelNumber>SonTek</smd:modelNumber>
                        <smd:serialNumber>CC1433007</smd:serialNumber>
                        <smd:calibrationDate>2023-04-27</smd:calibrationDate>
                        <smd:accuracyCheckDate>2023-04-27</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:soundSpeedSensor>
            </smd:vessel>
        </smd:platform>
        <smd:controlPoint />
    </smd:equipmentList>
    <smd:qualityControlProcedures>
        <smd:methods>
            <smd:crossline performed="false">
                <smd:discussion>
                    <smd:text>Crossline was not performed for this survey</smd:text>
                </smd:discussion>
            </smd:crossline>
            <smd:junctionOverlap performed="true">
                <smd:discussion>
                    <smd:text>Survey H13847 junctions with H13669. The Pydro 24 tool Compare Grids tool was utilized to assess the overlap of these junctions. The results of these junctions are shown in the final data package. The results between H13847 and H13669 indicate that 85.76% of grid-node comparisons are within Allowable Error Fraction Exceptional standards for depth. The resulting mean of this comparison was 0.07m, with a standard deviation of 0.61m which is within allowable total vertical uncertainty (TVU) for the area.</smd:text>
                    <smd:images>
                        <smd:caption>H13847 and H13669 Junction</smd:caption>
                        <smd:link>file:///M:/OPR-N338-NRTSE-23/Surveys/H13847/Metadata/QC/H13847_MB_VR_CRD_Final-H13669_MB_VR_CRD_Final_depth_delta_2024.png</smd:link>
                    </smd:images>
                </smd:discussion>
            </smd:junctionOverlap>
            <smd:statisticalAnalysis performed="true">
                <smd:discussion>
                    <smd:text>NRT-SE's primary bathymetric data review and quality control tool is the CARIS CUBE surfaces. The CUBE algorithm generates a surface consisting of multiple hypotheses that represent the possible depths at any given position. The CUBE surface is a grid of estimation nodes where depth values are computed based on the horizontal and vertical uncertainty of each contributing sounding. Any individual sounding’s uncertainty, or Total Propagated Uncertainty (TPU), is derived from the assumed uncertainty in the echosounder measurement itself, as well as the contributing correctors from sound speed, water levels, position, and attitude. TPU values for tide and sound velocity must be entered for each vessel during TPU computation, unless using TCARI, where uncertainty is added directly to survey lines by Pydro.

NRT-SE is currently using the following uncertainty values: GPS tide uncertainty is unique to the separation model in use. Measured sound speed uncertainty was set to a recommended value of 2 m/s as recommended by the FPM when 1 cast is taken every 4 hours. Surface sound speed value is dependent on the manufacturer specifications of the unit utilized to measure surface SV values for refraction corrections to flat-faced transducers. The AML Oceanographic Micro-X probe with an SV-Xchange sensor has a published accuracy of 0.025 m/s, however, a value of 0.2 m/s is used for surface sound speed uncertainty.

All other error estimates are read from the Hydrographic Vessel File (HVF). The HVF contains all offsets and system biases for the survey vessel and its systems, as well as error estimates for latency, sensor offset measurements, attitude and navigation measurements, and draft measurements. In addition, the HVF specifies which type of sonar system the vessel is using.

In addition to the usual a priori estimates of uncertainty, some real-time and post-processed uncertainty sources were also incorporated into the depth estimates. Real-time uncertainties from the Kongsberg EM2040C were recorded and applied in post-processing. Applanix TrueHeave files are recorded, which include an estimate of the heave uncertainty, and are applied during post processing. Uncertainties associated with vessel roll, pitch, gyro, and navigation are applied in CARIS HIPS and SIPS via a SBET and RMS files generated in POSPac.

The Grid QA tool within QC Tools was used to analyze data density and uncertainty of gridded data. The finalized VR surface was analyzed using the Pydro QC Tools Grid QA feature to determine compliance with specifications. Density requirements for H13847 were achieved with at least 99.5+% of surface nodes containing five or more soundings as required by HSSD Section 6.9.

The surface was analyzed using the HydrOffice QC Tools Grid QA feature to determine compliance with specifications. Overall, 99.5+% of nodes within the surface meet NOAA Allowable Uncertainty specifications for H13847.
</smd:text>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing percent of nodes in compliance with HSSD standards for H13847 VR surface</smd:caption>
                        <smd:link>file:///M:/OPR-N338-NRTSE-23/Surveys/H13847/Metadata/QC/H13847_MB_VR_CRD_Final.QAv7.density.png</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing TVU compliance of H13847 VR surface</smd:caption>
                        <smd:link>file:///M:/OPR-N338-NRTSE-23/Surveys/H13847/Metadata/QC/H13847_MB_VR_CRD_Final.QAv7.tvu_qc.gn1.png</smd:link>
                    </smd:images>
                </smd:discussion>
            </smd:statisticalAnalysis>
            <smd:directedEditing performed="true">
                <smd:discussion>
                    <smd:text>The CUBE surface child layers: uncertainty, standard deviation, and node standard deviation were primarily used to help focus directed editing to soundings that were negatively affecting the BASE surface. Another method to check the quality of sounding data prior to submission is the Pydro QC Tools “Flier Finder.” This software scans the CUBE surface for potential anomalous grid data. Lowering the flier height value will increase the sensitivity of the flier finder, resulting in more nodes being flagged. Fliers are then exported as .000 S-57 files that can be imported into CARIS HIPS and SIPS to aid in further cleaning. If desired, the user can set a new tolerance (“Flier height”) and rerun Flier finder.

On occasion, the resolution of the CUBE surface may not be sufficient to capture the high point of a feature. In less than 20 m of water, any feature where the most probable accurate sounding is shoaler than the CUBE surface by greater than one half the allowable error OCS Quality Metrics for Uncertainty is considered inadequately captured by the CUBE surface. In greater than 20m of water, this allowable error is expanded to the full OCS Quality Metric error allowance at that depth. Although missed shoal points may occur on irregular shoals or rock pinnacles, man-made features such as piles and wrecks are of particular concern. These features have very slender high points that extend far above the surrounding seafloor as well as the CUBE surface. To ensure that these features are properly represented, the shoalest point is flagged “designated” in CARIS. During the “finalization” process, the CUBE surface is forced to honor all soundings which have been flagged “designated.” In the case of a survey where the high points of many features (i.e. a boulder field) are not being captured by the CUBE surface, the hydrographer may decide to produce higher resolution CUBE surfaces to ensure that these features are being honored.</smd:text>
                </smd:discussion>
            </smd:directedEditing>
            <smd:holidayIdentification performed="true">
                <smd:discussion>
                    <smd:text>Most holidays are identified and addressed while in the field. During data acquisition, the display of the real-time swath coverage is based upon the matrix file, a polygon with user-defined geographic bounds and resolution set up prior to data collection. The resolution of the matrix is selected to match depth range of the polygon currently being worked on. The launch coxswain uses this matrix display to adjust the line as it is driven so that the swath currently being collected overlaps the grid of previously collected data. In this way, insufficient overlap can be seen and addressed immediately. Due to equipment failure, some holidays were unable to be addressed while in the field and and are shown within the data.

The Pydro QC Tools "Holiday Finder" is used to detect holidays in post-processing. This tool scans the grid, and any empty nodes surrounded by populated nodes are identified and was run in conjunction with a visual inspection of all surfaces by the hydrographer. The user can specify whether to search for holidays according NOAA HSSD. In the event of finding any holidays in post-processing, small polygons are made in HIPS to direct data acquisition to fill them in.

Holiday Finder identified 48 holidays for H13847_MB_VR_CRD_Final.</smd:text>
                </smd:discussion>
            </smd:holidayIdentification>
            <smd:surveyAdequacy performed="true">
                <smd:discussion>
                    <smd:text>These data are adequate to supersede charted data in their common areas.</smd:text>
                </smd:discussion>
            </smd:surveyAdequacy>
            <smd:imageryCoverage performed="false">
                <smd:discussion>
                    <smd:text>Imagery coverage assessment was not performed for this survey</smd:text>
                </smd:discussion>
            </smd:imageryCoverage>
            <smd:dataInterpolation performed="false">
                <smd:discussion>
                    <smd:text>Data interpolation was not performed for this survey</smd:text>
                </smd:discussion>
            </smd:dataInterpolation>
            <smd:backscatter performed="true">
                <smd:calibration>N/A</smd:calibration>
                <smd:dynamicRange>
                    <smd:discussion>
                        <smd:text>MBES frequency and settings remained unchanged throughout the survey area. Swath width was manually decreased in shallow water to mitigate edge fliers.</smd:text>
                    </smd:discussion>
                </smd:dynamicRange>
                <smd:acquisitionConfiguration>
                    <smd:discussion>
                        <smd:text>N/A</smd:text>
                    </smd:discussion>
                </smd:acquisitionConfiguration>
                <smd:environmentalVariable>
                    <smd:discussion>
                        <smd:text>N/A</smd:text>
                    </smd:discussion>
                </smd:environmentalVariable>
                <smd:acquisitionOutput>
                    <smd:discussion>
                        <smd:text>Kongsberg EM2040C stores the raw backscatter data in the .all file. Raw MBES backscatter was logged as part of the .all file of the Kongsberg EM2040 systems. Backscatter was processed in QPS Fledermaus GeoCoder Toolbox (FMGT) software, and the exported geotiffs are included in the final processed data package. </smd:text>
                    </smd:discussion>
                </smd:acquisitionOutput>
            </smd:backscatter>
        </smd:methods>
    </smd:qualityControlProcedures>
    <smd:controlPointEstablishment />
    <smd:reportOfSurvey>
        <smd:HSSD>
            <smd:version>2025-0-00</smd:version>
        </smd:HSSD>
        <smd:uncertaintySource>
            <smd:discussion>
                <smd:text>Total Propagated Uncertainty (TPU) values for H13847 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties. The uncertainty for the VDatum model was provided to the field units. In addition to the usual a prior estimates of uncertainty, some real time and post processed uncertainty sources were also incorporated into the depth estimates of the survey. Real-time uncertainties from the Kongsberg MBES sonars were incorporated and applied during post processing. Uncertainties associated with vessel roll, pitch, gyro, navigation, and heave were applied during post-processing. All of the aforementioned uncertainties were applied in CARIS.

As stated, H13847 is an ellipsoidally referenced survey (ERS) and the tidal component was accomplished with a separation model. There are two places in CARIS where the user directly defines uncertainty values for use in CARIS to calculate TPU values, in the HVF and the direct input of SV and GPS model values during the TPU computation. TPU values for all motion, navigation position and timing values are taken directly from Appendix IV (Uncertainty values for use in CARIS with vessels equipped WITH an attitude sensor) of the FPM. All timing values were set to 0.001 seconds as outlined for setups with Ethernet connections and precise timing. All offset values were chosen to be 0.02 meters based on the accuracy provided by professional surveys. All MRU alignment values are derived from the patch test. The gyro value is taken directly from the standard deviation of the yaw .</smd:text>
            </smd:discussion>
        </smd:uncertaintySource>
        <smd:errorSource />
        <smd:unusualConditions>
            <smd:discussion>
                <smd:text>Data gaps exist within the survey as the team did not return to the field post equipment failures. The area is highly changeable with sand waves throughout the area increased the probability of offsets for returning at a later date. Sea grass is present throughout the survey grounds and has been filtered out of the data, however some sea grass may remain. The removal of sea grass has left areas of tracklines where no bathymetric coverage exists and has been indicated in the feature file. 
</smd:text>
            </smd:discussion>
        </smd:unusualConditions>
        <smd:junctionAnalysis />
        <smd:additionalInformation>
            <smd:discussion>
                <smd:text>In certain areas the coastline should be reviewed based on data collected. Issues with .bag file checks may be flagged due to designated soundings within the data and is a known issue. One assigned rock feature was unable to have least depth known collected due to covering/ uncovering nature, making it a hazard to proceed with data collection in the area. 
</smd:text>
            </smd:discussion>
        </smd:additionalInformation>
        <smd:PIAlteration>
            <smd:discussion>
                <smd:text>The Navigation Response Branch Chief received authorization from the Pacific Hydrographic Branch to submit H13847 in accordance with the HSSD 2024 on April 18, 2024. The Project Instructions stated that object detection acquisition was required for assigned priority areas as safe operations permitted and complete coverage elsewhere in H13847. H13847 was processed to Critical specifications for priority areas and General 1 specifications for elsewhere.</smd:text>
            </smd:discussion>
        </smd:PIAlteration>
        <smd:supplementals>
            <smd:document>
                <smd:subject>Final Survey Outline</smd:subject>
                <smd:submissionDate>2024-08-14</smd:submissionDate>
            </smd:document>
            <smd:document>
                <smd:subject>NCEI Sound Speed Data</smd:subject>
                <smd:submissionDate>2024-08-13</smd:submissionDate>
            </smd:document>
        </smd:supplementals>
    </smd:reportOfSurvey>
    <smd:personnel>
        <smd:approvalStatement>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 and approved all data and metadata. The survey meets or exceeds requirements as set forth in the Project Instructions and NOS Hydrographic Surveys Specifications and Deliverables. The survey is complete and no additional work is required with the exception of any deficiencies noted in the Report of Survey.
</smd:approvalStatement>
        <smd:approver>
            <smd:name>LTJG Ashley Howell</smd:name>
            <smd:title>Chief of Party</smd:title>
        </smd:approver>
    </smd:personnel>
</smd:surveyMetadata>