-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
68 changed files
with
348,262 additions
and
0 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| <html><head><title>/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.err.html errors</title> | ||
| <meta charset="UTF-8"/> | ||
| <style> pre { white-space: pre-wrap; } | ||
| thead th { font-weight: bold; background-color: aqua; } | ||
| .severity0 { font-weight: bold; background-color: lightpink } | ||
| .severity1 { font-weight: bold; } | ||
| .severity2 { } | ||
| .severity3 { font-style: italic; color: grey; } | ||
| </style> | ||
| </head><body><h1>/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.err.html errors</h1> | ||
| <ul><li><p><b><a href="#Style">Style</a></b>: Severity 2: <b>11</b> errors</p></li> | ||
|
|
||
| <li><p><b><a href="#Metanorma_XML_Syntax">Metanorma XML Syntax</a></b>: Severity 2: <b>2</b> errors</p></li> | ||
| </ul> | ||
| <h2 id="Style">Style</h2> | ||
| <table border="1"> | ||
| <thead><th width="5%">Line</th><th width="20%">ID</th> | ||
| <th width="30%">Message</th><th width="40%">Context</th><th width="5%">Severity</th></thead> | ||
| <tbody> | ||
| <tr class="severity2"> | ||
| <td>000126</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#data-contribution'>data-contribution</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="data-contribution" obligation="normative"> | ||
| <title>Data Contribution</title> | ||
| <p id="_582e58a9-d828-a8b4-851b-bc3f0f6fb4e5">This chapter details the process for contributing crowdsourced bathymetry (CSB) data to the IHO Data Centre for Digital Bathymetry (DCDB), via Trusted Nodes, and specifies required data formats. CSB data collectors and Trusted Nodes are strongly encouraged to provide their data to the DCDB to help fill gaps in global bathymetric coverage. These data will in turn be made freely and publicly available through the DCDB CSB web portal.</p> | ||
|
|
||
| <p id="_3d9a59b3-6c97-5c2a-f215-f0b43da53816">Hydrographic and bathymetric data collected by the National Antarctic Programmes’ ships and others linked with their activity in the Antarctic, should be forwarded by the National Antarctic Programmes, or by other means, to the national hydrographic services using the IHO Collection and Rendering of Hydrographic Data Form available via the IHO website<fn reference="1"> <p id="_b2c14125-99e4-74d5-b2bb-00edc485e875"> <link target="https://www.iho.int/mtg_docs/rhc/HCA/HCA_Misc/HCA_HPWG/HCA_Hydrography_Priorities_WG.htm"/> </p></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000145</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_the_trusted_node_model'>_the_trusted_node_model</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_the_trusted_node_model" obligation="normative"> | ||
| <title>The Trusted Node Model</title> | ||
| <p id="_b809e45b-3c5f-b666-b7d3-b35c0716962b">The DCDB currently accepts crowdsourced bathymetry (CSB) contributions through a network of <xref target="term-trusted-nodes">Trusted Nodes</xref>, which are organizations or individuals that serve as data liaisons between mariners (data collectors) and the DCDB (<xref target="figure-01"/>). Trusted Nodes may assist the mariner by supplying data logging equipment, providing technical support to vessels, downloading data from data loggers, and providing the information to the DCDB. The DCDB works with each Trusted Node to standardize metadata and data formats and define data delivery requirements. This model normalises data contributions and minimizes the requirements and effort for mariners.</p> | ||
|
|
||
| <p id="_2b344e90-9818-185e-e80a-45a99b6d71b8">At present, individual data contributors are encouraged to join an existing Trusted Node. In the future, the DCDB may expand its capability to support individual contributors or other models of contribution.</p></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000173</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_overview_of_csb_data_flow'>_overview_of_csb_data_flow</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_overview_of_csb_data_flow" obligation="normative"> | ||
| <title>Overview of CSB Data Flow</title> | ||
| <p id="_4ef4e69d-3dc5-fbff-3ce3-9c07c5a085f0">CSB data, identified as belonging to the high seas (according to UNCLOS as “the area”), will be ingested into the DCDB database without restrictions on its further reuse. <xref target="figure-02"/> is designed to show future filter processes, including a geographical location checking process and any subsequent masking actions, which will be applied to any incoming CSB data, collected within waters of national jurisdiction, before ingestion into the DCDB database. The flow diagram is of generic nature. The filtered flow of CSB data will be based on the information received by the IHO Secretariat from individual coastal states on request. Further details of which coastal states support CSB activities within their waters of national jurisdiction, along with any caveats they have articulated, will available from the IHO website. CSB data, collected within waters of national jurisdiction of coastal states who did not notify their respective CSB support towards the IHO Secretariat, will not be ingested. This data will be stored and only made available at such time as authorization is received by the IHO from the respective coastal state.</p> | ||
|
|
||
| <figure id="figure-02"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000205</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_systems_and_sensors'>_systems_and_sensors</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_systems_and_sensors" obligation="normative"> | ||
| <title>Systems and Sensors</title> | ||
| <p id="_7c1cf66f-32bb-ba5b-66e9-dc98f44a6ba6">Many vessels already possess the minimum equipment needed to collect CSB, and only need to install a data logger, or enable logging software, to begin collecting CSB. The following sections provide basic information about sensors, as well as best practices and recommendations for collecting CSB. For more in-depth information about systems and sensors, please refer to the IHO publication <link target="https://iho.int/iho_pubs/CB/C13_Index.htm">C-13, Manual on Hydrography</link> (Chapters 2 and 3).</p> | ||
|
|
||
| <clause id="_echo_sounders" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000209</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_echo_sounders'>_echo_sounders</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_echo_sounders" obligation="normative"> | ||
| <title>Echo-sounders</title> | ||
| <p id="_9750e8d4-2ac2-635f-ba03-7051c628191b">Echo-sounders, or depth sounders, determine the water depth by transmitting sound pulses from a transducer, and recording the time it takes for the sensor to receive the return echo from the seafloor. Transducers are usually mounted on the hull of a vessel, but can be mounted on other platforms, as well. There are two main types of echo-sounders: single beam and multibeam. Either of these echo-sounders can be used to collect crowdsourced bathymetry, however the guidance developed in this document will focus on single beam CSB, as the Trusted Node/DCDB model is currently equipped to receive and process those data. Vessels using multibeam for safety of navigation purposes and wishing to contribute their single profiles should submit their data to the appropriate coastal state national Hydrographic Office under cover of a Hydrographic Note.</p> | ||
|
|
||
| <clause id="_single_beam_echo_sounders" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000235</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_hardware_and_software'>_hardware_and_software</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_hardware_and_software" obligation="normative"> | ||
| <title>Hardware and Software</title> | ||
| <p id="_295676a8-f46e-fef5-55d5-d9198705178b">In addition to depth, positioning, and motion sensors, there are several hardware and software variables that mariners should consider, when collecting CSB data.</p> | ||
|
|
||
| <clause id="_data_loggers" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000245</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_understanding_nmea_0183'>_understanding_nmea_0183</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_understanding_nmea_0183" obligation="normative"> | ||
| <title>Understanding NMEA 0183</title> | ||
| <p id="_4c166a28-3e58-261f-5876-d0f921744e85">It is helpful for mariners to understand the raw data that is being output by their sensors. Many marine sensors, such as GNSS positioning systems or echo-sounder transducers, transmit data in accordance with standards developed by the <link target="https://www.nmea.org/">National Marine Electronics Association (NMEA)</link>. The NMEA 0183 standard data format, or ‘sentences,’ are both human- and machine-readable, and provide information about the sensor measurement and status. All NMEA sentences begin with a $, and each field is comma-delimited. There are many different types of NMEA sentences. The following sections describe a few that may be useful for CSB data collection.</p> | ||
|
|
||
| <clause id="_gnss_nmea_sentences" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000292</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_vessel_and_sensor_measurements'>_vessel_and_sensor_measurements</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_vessel_and_sensor_measurements" obligation="normative"> | ||
| <title>Vessel and Sensor Measurements</title> | ||
| <p id="_51672bc0-d0b5-f8d6-4510-9031b350bf9c">The horizontal and vertical measurements between the GNSS and the echo-sounder, and between the waterline and the transducer, are key components of the quality and accuracy of the data. Some systems are programmed to incorporate these offsets when the sensors are installed. If they do not, mariners should record these measurements as best as possible, and include them in their metadata. The following sections provide information about these measurements, and best practices for collecting and recording them.</p> | ||
|
|
||
| <clause id="_sensor_offsets" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000325</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_the_importance_of_metadata'>_the_importance_of_metadata</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_the_importance_of_metadata" obligation="normative"> | ||
| <title>The Importance of Metadata</title> | ||
| <p id="_748406d8-b739-4cde-f091-37f2a8768d28">Metadata provides information to data users that helps them determine the quality of the data, and therefore use the data for more applications than would be possible with depth and position information alone. If the metadata are also consistent, it is easier to incorporate the data into a database, and for users to manipulate the data for their own purposes.</p> | ||
|
|
||
| <clause id="_tidal_information" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000342</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_metadata_and_data_formats'>_metadata_and_data_formats</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_metadata_and_data_formats" obligation="normative"> | ||
| <title>Metadata and Data Formats</title> | ||
| <p id="_c162bf90-83f5-d104-d2e2-f7fc92eed1fe">This section provides guidance to data collectors and Trusted Nodes about the standard metadata that is required for submitting data to the DCDB. In addition, it provides information about additional metadata that would enhance the value of the data for end users. Mariners should collect and forward this information whenever possible.</p> | ||
|
|
||
| <clause id="_required_data" obligation="normative"></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td>000637</td><th><code><a href='/__w/mn-samples-iho/mn-samples-iho/_site/documents/b12/document.html#_uncertainty_for_trusted_nodes_and_data_users'>_uncertainty_for_trusted_nodes_and_data_users</a></code></th> | ||
| <td>Hanging paragraph in clause</td><td><pre><clause id="_uncertainty_for_trusted_nodes_and_data_users" obligation="normative"> | ||
| <title>Uncertainty for Trusted Nodes and Data Users</title> | ||
| <p id="_a1b7873f-4e8a-c6f2-6bbc-feb66ae8b5d7">There are additional uncertainty components that Trusted Nodes and data users should understand when dealing with crowdsourced bathymetry. These uncertainty concerns are mostly about validation and processing of the data, and therefore can only truly be assessed at the Trusted Node, or from the DCDB as a whole. It is expected that data collectors are unlikely to be able to assess these types of uncertainty, although they may find the information of interest.</p> | ||
|
|
||
| <clause id="_effects_of_sensor_integration_on_data_capture" obligation="normative"></pre></td><td>2</td></tr> | ||
| </tbody></table> | ||
| <h2 id="Metanorma_XML_Syntax">Metanorma XML Syntax</h2> | ||
| <table border="1"> | ||
| <thead><th width="5%">Line</th><th width="20%">ID</th> | ||
| <th width="30%">Message</th><th width="40%">Context</th><th width="5%">Severity</th></thead> | ||
| <tbody> | ||
| <tr class="severity2"> | ||
| <td></td><th><code>XML Line 000807:98</code></th> | ||
| <td>value of attribute "obligation" is invalid; must be equal to "informative" or "normative"</td><td><pre></pre></td><td>2</td></tr> | ||
| <tr class="severity2"> | ||
| <td></td><th><code>XML Line 001009:16</code></th> | ||
| <td>element "iho-standard" incomplete; missing required element "bibliography"</td><td><pre></pre></td><td>2</td></tr> | ||
| </tbody></table> | ||
| </body></html> |
Oops, something went wrong.