Trusted Nodes and DCDB

Overview of Trusted Nodes and DCDB

This section provides an overview of the Data Collection and Dissemination Bureau (DCDB) and its initiative regarding trusted nodes in data submission for bathymetric data. Lee Shoemaker serves as the Data Manager at DCDB, succeeding Georgie Zelenak, who left in 2024. The session outlines the critical roles, responsibilities, onboarding process, resource availability, and data submission expectations for trusted nodes.

Introduction to DCDB

DCDB was established in 1990 to host a global collection of open bathymetric data. It operates in conjunction with the United States National Oceanic and Atmospheric Administration (NOAA) on behalf of International Hydrographic Organization (IHO) member states. It serves as a centralized repository for submissions from various sectors, promoting standardization in the collection and dissemination of bathymetric data.

Data Flow Process

A simplified outline of the data flow process is highlighted:

  • Prior to Submission:

    • DCDB collaborates with trusted nodes to assure compliance with submission standards established under standard B12.

    • Emphasizes the importance of metadata being in a standard format.

    • Uses a standard HTTP post request, allowing data to be sent securely from trusted nodes to DCDB.

    • Data is typically integrated into DCDB’s services and public access portals within 24 hours.

Concept of Trusted Nodes

The concept of trusted nodes emerged from the need for an effective data collection strategy that could manage contributions from numerous vessels without direct interaction:

  • Definition: Trusted nodes refer to data providers that include academic institutions, non-profit organizations, commercial enterprises, and regional centers.

  • **Functionality: **

    • Act as intermediaries for data collection and submission.

    • Perform tasks such as installing data loggers, offloading data, community engagement, and outreach initiatives.

    • Critical for ensuring data integrity and quality prior to reaching DCDB.

Responsibilities of Trusted Nodes

Responsibilities of trusted nodes encompass various functions crucial for effective data management:

  • Ensure data is submitted in acceptable formats per B12 standards.

  • Provide test files and sign agreements necessary for data submission.

  • Receive secure tokens from DCDB to facilitate submission.

  • Serve as contact points for addressing data-related issues and maintaining data quality.

  • Engage in proactive communications with DCDB whenever submission failures or data integrity issues occur.

Resources for Trusted Nodes

DCDB offers various resources available through their contributors page:

  • Updated hyperlinks to aid trusted nodes in data submission processes.

  • Access to sample data files and schema links to facilitate understanding of data format expectations.

  • Dashboard link provided for monitoring and tracking submissions, though may face outages.

Expectations from Trusted Nodes

Expectations of trusted nodes include:

  • Keeping abreast of resources and changes related to B12 protocols, particularly backward compatibility.

  • Having technical skills necessary for data submission, which may include manual and automated processes.

Types of Data Submissions Allowed

The trusted nodes can submit various types of data:

  • Acceptable formats include GeoJSON and CSV files, with a preference for raw data submissions over processed data.

  • Frequency of data submissions varies, with many organizations opting for daily reconciliations of their data submissions.

List of Current Trusted Nodes

The current list of trusted nodes includes:

  1. Navico

  2. C-MAP

  3. GEC Aquamap

  4. SignalK (recent addition with automated submission)

  5. FarSounder

  6. Orange Force Marine

  7. McGregor

  8. Carnival Cruise Corporation

  9. PGS (Marine data from offshore vessels)

  10. Alcatel Submarine Networks

  11. James Cook University (Australia)

  12. University of South Florida (USF)

  13. Sidco

  14. Seakeepers

  15. CVED 2030 Project (for one-off submissions)

Onboarding Process for Trusted Nodes

The onboarding process for becoming a trusted node includes the following steps:

  • Interested parties are encouraged to read the information provided on the DCDB website

  • Initial meetings to discuss potential candidacy for becoming a trusted node.

  • A request for a test data submission to assess compatibility with DCDB expectations.

  • Review of the submission agreement comprising seven sections over five pages, centering on data usage rights and expectations (notably Section 6, which relates to the CC0 public domain licenses).

Monitoring Data Quality

Once testing and onboarding are complete:

  • Trusted nodes begin utilizing the test endpoint for submissions, which allows them to refine their processes without impacting live data.

  • Upon successful transitions, data from trusted nodes appears on DCDB map services the following day, with live updates monitored continually.

Closing Remarks

Lee Shoemaker concludes by emphasizing the importance of trusted nodes to the Collaborative Technical Staff Project (CSP). Active engagement and collaboration during the meetings are encouraged for shared understanding of processes across all participating entities. Lee also opens the floor for further questions and facilitates networking among participants to enhance collaborative efforts.