14.0 Survey Findings
14.1 Report of Survey
The Report of Survey is required to accompany survey data submission. The Report of Survey may be written in prose with sections as described below, or it may be composed via Pydro, a freely available, open-source tool published by the Office of Coast Survey that includes XML reporting.
Uncertainty Sources
Failure to provide uncertainty values will result in the Office of Coast Survey determining the appropriate uncertainty based on an evaluation of the data and metadata provided, as well as any other factors that are deemed relevant at the sole discretion of the Office of Coast Survey.
If using a topo-bathymetric airborne lidar system, a vertical uncertainty model may be provided to the Office of Coast Survey based on the Eren et al. model (2019) if it has been computed.
Error Sources
All data submitted to the Office of Coast Survey must include a description of any unresolved errors in the provided dataset that exceeds maximum allowable uncertainties as described in Point Cloud. A description of any attempts to resolve the errors may also be included.
Unusual conditions
If the Field Unit experiences any unusual conditions that will affect the assessment of the data or would assist in planning future surveys in the area, these must be noted in the Report of Survey.
Additional information
Additional information may include recommendations for additional work, observations on the weather, observations of significant changes to shoreline or shoreline construction, or any other information that the Field Unit believes would assist in planning future surveys in the area.
PI Alterations
Supplementals
Signature
14.2 Coast Pilot Report
A Coast Pilot Field Report will be provided by the Office of Coast Survey. This report may contain specific questions about items in the Coast Pilot that require field verification or clarification. In addition, this report may contain the actual paragraphs from the Coast Pilot that are affected by the survey area.
Coast Pilot is updated weekly. Updated Coast Pilot books can be downloaded from the Coast Pilot website. The hydrographer must first download the latest edition of Coast Pilot and compare it against the information contained in the Coast Pilot Field Report. In the event of a conflict between the two sources, the review must be completed using the information in the downloaded Coast Pilot.
The Field Unit must use either the latest edition of the Coast Pilot downloaded from the Coast Pilot website, or the Coast Pilot Field Report, whichever is the latest version.
-
Deletions to the existing text must be shown as strikethroughs. -
Recommended revisions, including any new information that would be beneficial to the mariner, must be shown in red text. -
Existing text that has been reviewed and verified to be correct during Field Unit operations must be changed to green text. -
Existing text that could not be verified or refuted during operations must remain in black.
Field Units must submit this file via email to ocs.ndb@noaa.gov and coast.pilot@noaa.gov with a CC to the OCS Project Manager and/or COR. List the submission and date of submission in the Supplementals section of the Report of Survey.
14.3 Dangers to Navigation
All features with depths of 20 meters or less in navigable waters may be considered potential Dangers to Navigation (DTON) and subject to reporting. Potential DTONs should be evaluated in the context of the largest scale chart of the area and with detailed knowledge of vessel traffic in the area, including usual and seasonal routes.
Reporting DTONs to NOAA
External Source Data providers may report DTONs through the Marine Chart Division's ASSIST customer service chart reporting system.
NOAA Field Unit Reporting
-
The email subject line must adhere to the following convention: -
<registry number> DTON ## -
e.g., H12345 DTON 03
-
-
The body of the email must list the following metadata in the following order: -
General Locality -
Sub-locality -
Project Number -
Registry Number -
Field Unit
-
-
The feature file: -
May contain point, line, or area features. -
Must adhere to the naming convention presented in Delivery Structure. -
Must include NOAA Field Unit DTON recommendations and be generated as described in Features. -
Must be attributed in accordance with the Feature Attribute Encoding Guide.
-
-
At least one chartlet image portraying the feature least depth sounding and position with the largest-scale ENC as the background must be compressed in a single zip file and included with the naming convention presented in Delivery Structure. -
Images of sonar data (e.g., multibeam or side scan imagery) must not be included. -
Attach the feature file and accompanying multimedia zip file to the email.
List each submission and date of submission in the Supplementals section of the Report of Survey.
NOAA Contractor Unit Reporting
Contractor DTON recommendations must be submitted as a feature file attributed in accordance with the Feature Attribute Encoding Guide. The feature reporting must adhere to the same requirements as NOAA Field Unit Reporting with the exception:
-
Submit sonar images of multibeam and side scan sonar images as supporting data. All images and chartlets must be submitted in a multimedia zip file.
Reporting DTONs to Non-NOAA Source Authorities
NOAA is not the source authority for some charted features such as controlling depths in federal channels, Aids to Navigation (ATONs), bridge heights, and pipelines. The reporting procedures for these types of dangers are described in this section.
Federal USACE Channels
The U.S. Army Corps of Engineers (USACE) is a source of controlling depths in federal channels on NOAA charts. If surveying within a USACE maintained channel, the hydrographer must conduct a comparison of survey depths with the DRVAL1 attribute found in the ENC's DRGARE feature object in all maintained channels.
Aids to Navigation (USCG)
The U.S. Coast Guard (USCG) Local Notice to Mariners and the USCG Light List are the sources of charted Aids to Navigation on NOAA charts.
Class I and Class II Aids to Navigation
If any type of aid to navigation that is listed in the USCG Light List and that the USCG considers as a Class I Aid to Navigation or a Class II Aid to Navigation is found to be uncharted, missing, or repositioned, the hydrographer must report it to the USCG using the USCG Navigation Center’s Online ATON Discrepancy Report Form.
Class III Aids to Navigation
If any private navigation aid that the USCG considers as a Class III Aid to Navigation, and not included in the USCG Light List, is found to be uncharted, missing, or repositioned, the hydrographer must report it through the Marine Chart Division’s ASSIST customer service chart reporting system.
Report the private aid to navigation using the ‘Report an Error’ tab, providing the reporting person’s email address, attributing the geographic location of the discrepancy, selecting the type of user, describing the error, selecting the product type, attributing the observation date, and attaching any images or documents. The ASSIST system will respond with an email from ocs.customersupport@noaa.gov.
Bridge Heights (USCG)
The USCG is a source of bridge heights on NOAA charts. If a bridge height is found to be inaccurate or missing from a chart during field work, the hydrographer must inform the local USCG District’s Bridge Program via email with the pertinent information.
-
The body of the email must list the following metadata in the following order: -
General Locality -
Sub-locality -
Project Number -
Registry Number -
Field Unit
-
-
A feature file of the bridge -
Must be generated as described in Features and attributed in accordance with the Feature Attribute Encoding Guide. -
Must include vertical clearance of the bridge. -
For bridges that open or lift, the opened and closed vertical clearance of the bridge must also be included.
-
14.4 Charted Feature Removal Request
Charted features that are determined not to exist and that have a significant impact on navigation should be expeditiously removed from the chart, if sufficiently disproved. In particular, this includes disproved “Position Approximate” wrecks and obstructions that are located in major shipping corridors. The Charted Feature Removal Request (commonly known as an Anti-DTON) is similar to a Danger to Navigation Report, except it is used to remove a charted feature that represents a hazard, which does not exist, rather than add a newly found hazard. This process should be used sparingly, usually by responding to a request from local pilots or other authorities that a charted feature is a hindrance to operations. If the removal of a feature is not time-critical, do not use the Charted Feature Removal Request (Anti-DTON).
14.5 Seep and Pipeline Reports
-
The location of the seep (latitude/longitude). -
The distance from the charted feature. -
The date and time of observation. -
The depth (if appropriate). -
An image.
For unburied pipelines, the information must be conveyed in an Excel spreadsheet, attached to the email. The Excel spreadsheet must have the following columns in this order:
-
Starting Latitude -
Starting Longitude -
Ending Latitude -
Ending Longitude -
Bearing -
Length (meters) -
Height Above Seafloor (meters) -
Survey Sheet -
Date of Discovery -
Comments
-
The email subject line must adhere to the following convention: -
<registry number> Non-Dangerous Pipeline Submission ## -
e.g., H12345 Non-Dangerous Pipeline Submission 03
-
-
The body of the email must list the following metadata in the following order: -
General Locality -
Sub-locality -
Project Number -
Registry Number -
Field Unit
-
-
Screen captures of side scan sonar images, multibeam images, or chartlets (if applicable) of the exposed pipeline. -
A feature file of the pipeline. -
Must be delineated as PIPSOL line objects. -
Must be generated as described in Features and attributed in accordance with the Feature Attribute Encoding Guide. -
Must also include any features connected to the pipeline that provide insight into the pipeline's type.
-
Contractors must submit non-dangerous exposed pipelines via email to the OCS Project Manager and/or COR and the appropriate Hydrographic Branch stated in the Hydrographic Survey Project Instructions (ahb.dton@noaa.gov or phb.dton@noaa.gov) with the naming convention presented in Delivery Structure.
List each submission and the date of submission in the Supplementals section of the Report of Survey.
14.6 Potentially Sensitive Data Findings
-
The preliminary feature file must only contain uncharted wrecks and uncharted anthropogenic obstructions per the requirements as described in Section 7.4 of Features. Pound stakes, pilings, and active, unused, or ruined fishing facilities must not be included in the preliminary feature file. -
Features that are already charted but found in a different position (generally speaking within the disproval search radius from its position as charted) must not be included in the preliminary feature file, with the exception of any DTONs that were submitted during survey operations and subsequently charted. - Wrecks and anthropogenic obstructions that were submitted as DTONs must be included in the preliminary feature file.
-
<registry number> Feature Report ## -
e.g., H12345 Feature Report 03
-
The body of the email must list the following metadata in the following order: -
General Locality -
Sub-locality -
Project Number -
Registry Number -
Field Unit
-
-
The preliminary feature file: -
May contain point, line, or area features. -
Must adhere to the naming convention presented in Delivery Structure. -
Must be generated as described in Features. -
Must be attributed in accordance with the Feature Attribute Encoding Guide. For timeliness, preliminary attribution that differs from the attribution in the final feature file is acceptable.
-
-
At least two images are required per feature and may include multibeam subset images or side scan contact images. -
If side scan sonar data was collected, a side scan image is required. -
Submitting only one image for a particular feature is acceptable if: -
Multiple views of a feature are included in the same image (for example, 2D and 3D point cloud views). -
The feature was found in side scan sonar data from one pass and it is located in a shoal area where it is not safe to conduct further investigation.
-
-
Images must include the approximate dimensions (length, width, and height) in meters. -
Images must be compressed in a single zip file with the naming convention presented in Delivery Structure. -
Attach the feature file and accompanying multimedia zip file to the email. -
If there were no potentially sensitive data findings identified in the survey: -
The email must be sent per the above requirements, but without an attachment and with the subject line: -
<registry number> - no potentially sensitive data findings - e.g., H12345 - no potentially sensitive data findings
-