Crowdsourced Bathymetry Manual (2026) Created as an output of the Crowd Sourced Bathymetry Working Group Work Item G Work Item Contributors - Haley Davis, Kristin Erickson, Sophia Chernoch, Jennifer Cheveaux, Aileen Bohan, Colin Thomson, Pauline Weatherall, Jennifer Jencks, Nicolette Le Roux, Anders Bergstrom, Natalie Cornish, Abukar Aminu Giginya, Jaya Ramirex, Guillaume Morissette, Lee Shoemaker, Anthony Klemm Contents Glossary Authorship and acknowledgements Goals and objectives Definition and important uses of CSB Legal considerations Finding your crowd Vessel features Motivating vessels and overcoming hesitation Maintaining vessel engagement Hardware options First generation loggers Next generation and WiFi-enabled loggers Comparison of logger options Installation and setup Installation prep Installation kit Installation guide: OFM Installation guide: YDVR Installation guide: NEMO30/WIBL Collecting metadata Data retrieval and management Frequency of data transfer Offload mechanisms Data transformation and submission WIBL and YDVR data processing Submission of GEOJSON data to the DCDB Graphic user interface Data extraction and processing NCEI/DCDB data extraction Pydro tidal corrections Data visualization ArcGIS: Editing tide-corrected CSB data ArcGIS: Generating CSB data shapefiles QGIS: Editing tide-corrected CSB data QGIS: Data visualization Use cases and effective communication NOAA data scrape Tampa Bay community mapping efforts Templates Example recruitment email for stakeholder meeting Example stakeholder meeting agenda Example stakeholder meeting session prompts Example stakeholder meeting survey Example recruitment email for Crowd the Bay participants Example memorandum of understanding Example vessel offsets worksheets Example letter of agreement and metadata form Example data transfer guide Example data retrieval guide Example logger menu Example internal SOP for a CSB company/program Glossary B-12 A guidance document created by the CSBWG and IHO to provide an outline of the technical “how-to” on CSB collection, metadata format, offset collection, and data contribution so that all Trusted Nodes follow the same format uniformly. CSB Crowd Sourced Bathymetry: The practice of utilizing a crowd or collection of vessels equipped with echosounders to collect data about the depth and shape of the seafloor using volunteer data. CSBWG Crowd Sourced Bathymetry Working Group: A group of hydrographic offices, universities, nonprofits, private companies, and other organizations interested in the utility of CSB which meets under the guidance of the IHO to determine directions for global collaboration and needs within this space. DCDB Data Center for Digital Bathymetry: Data Center co-located at NOAA’s NCEI, stores bathymetry data for all IHO initiatives including CSB, and is a major source for the Seabed2030 initiative. IHO International Hydrographic Organization: The organization that creates the structure for how we engage with Seabed2030 and global CSB initiatives.  NCEI National Centers for Environmental Information: Part of NOAA, NCEI provides environmental data, products, and services and co-hosts the IHO DCDB, which is responsible for CSB data validity, safe storage, data distribution, and more. NOAA The National Oceanic and Atmospheric Administration: The United States federal agency under which the DCDB and NCEI are co-located. S-44 Publication that defines the standard applicable to hydrographic surveys and takes its place amongst the other IHO publications, designed to improve the safety of navigation, knowledge, and protection of the marine environment. Seabed2030 A global initiative and United Nations Decade Action Program, which is supported by the Nippon Foundation, the IHO, NOAA, and GEBCO with the goal of mapping the entire seafloor by the year 2030 and providing this data as an open-access open-source resource. Trusted Node A designation that any organization can apply for which allows that organization to aggregate and directly contribute CSB data to the DCDB. Authorship and Acknowledgements This document was commissioned out of the 16th annual meeting of the Crowd Sourced Bathymetry Working Group held in March 2025 in Wellington, New Zealand. These efforts are the result of a request by new and interested Crowd Sourced Bathymetry (CSB) initiatives within various member organizations for clear guidelines and examples for how to create, recruit, operate, and maintain a CSB program. This document draws on the knowledge and resources of several major Trusted Nodes and Hydrographic Offices and highlights the information found to be most pertinent by these entities through trial-and-error. All information reflected here is an amalgamation of experience, but not necessarily the only path to success.  We would like to acknowledge the work of organizations which have contributed majorly to this effort including the International Hydrographic Organization (IHO), Seabed2030, NOAA’s NCEI and DCDB, University of New Hampshire's Center for Coastal and Ocean Mapping (CCOM), University of South Florida’s Center for Ocean Mapping and Innovative Technologies (COMIT), Orange Force Marine, and the International SeaKeepers Society, as well as other partner organizations which have contributed to amassing the knowledge contained in this document. We would also like to recognize the role of Seabed2030, the Nippon Foundation, the IHO, and GEBCO for their roles in bringing together interested parties to contribute to the overall use and compilation of global crowd sourced bathymetry data.  Goals and Objectives The goal of this document is to fulfill a request put forth by the 16th annual Crowd Sourced Bathymetry Working Group, under Work Item G, to provide guidance for the successful development and operation of a CSB program. This document was created by several of the working group members, in an effort to consolidate the resources and expertise within the field, after more than 16 years of developing CSB tools and programs across the world. Within this document, you will find information on recruiting CSB participants, best practices for data collection, guidance on the use of data after collection, and an overview of current technologies that support these efforts. How to use this manual This document is designed as a guide for hydrographic organizations, non-governmental organizations, nonprofits, companies, and any other parties aiming to establish their own CSB program, or one that contributes to existing global mapping efforts. The contents of this manual are intended to provide guidance on all aspects of CSB program development and management - from stakeholder meetings and participant recruitment to logger installation and data processing tools. The final section contains a series of Templates provided by existing CSB programs to serve as a resource for new parties interested in joining this international initiative. Definition and important uses of CSB  The International Hydrographic Organization (IHO) defines Crowdsourced Bathymetry (CSB) as the collection and sharing of depth measurements from vessels using standard navigation instruments during their normal operations. CSB data provides a valuable, cost-effective method for supplementing traditional, high-precision hydrographic surveys, filling in gaps in the existing maps of the world's oceans and waterways, and fostering a global community of ocean data contributors, while utilizing vessels which are often non-scientific in nature. These can be anything from commercial fishing vessels, to dive boats, to leisure yachts. CSB programs rely on vessels equipped with common marine electronics, such as a depth transducer (echo sounder), a GPS unit, and ideally a motion reference unit (inertial navigation system), often linked through NMEA 2000 or NMEA 0183 networks. Together, these devices provide depth measurements tied to time and position, creating seafloor profiles as vessels move through the water and resulting in a map of the seafloor. As we move into an era of increasingly capable technology becoming more accessible and widespread among vessels, the door to utilizing the masses has opened. Some of the major strengths of CSB lie in its relative (and increasing) affordability as depth sounders become more capable and simultaneously more connected. This creates the potential for countries or organizations to collect seafloor data on a much larger scale than was previously possible. Additionally, it should be noted that CSB relies on vessels that are often smaller and have a shallower draft than hydrographic research vessels. As a result, CSB can target shallow and narrow water bodies that have long been inaccessible with traditional tools. While CSB isn’t a cure-all solution, its specific strengths allow it to be useful in scenarios such as localized community waterway mapping, or first-time mapping of areas where more advanced tools are financially or physically inaccessible. While CSB data has historically been overlooked by the hydrographic community at large, the use of a “crowd” helps to bring increased legitimacy to this hydrographic tool. While multibeam data is traditionally utilized within hydrography, a high enough density of single beam data tracks over an area of seafloor could eventually allow data managers to identify and remove outliers, increasing the statistical soundness of the data. This level of sounding density could easily be generated by just a few vessels routinely navigating through the same waterways. As the volume of data within a defined area increases, so too does the accuracy and utility of crowdsourced bathymetry. This approach also allows for high-frequency, low-cost sampling of navigationally significant coastal waterways when compared to traditional hydrographic surveying, as privately owned vessels can collect data on a highly regular basis, and all data are collected in locations where mariners are actively navigating. Data managers, hydrographic offices, and private companies alike can then put this data to use for various outcomes. For example, the National Oceanic and Atmospheric Administration (NOAA) in the United States of America has utilized the CSB data collected along the Gulf and Atlantic Coasts of America to identify areas in which older and potentially outdated charts are misaligned with current data. This may indicate a need for re-surveying with advanced hydrographic tools, providing safer operation for all vessels utilizing coastal waters. With enough data density, eventually this data can also be utilized to integrate into official hydrographic charts. Private companies, such as Raymarine, Olex, and Garmin use CSB to inform charts made by their company (e.g. Raymarine’s “RealBathy”), which in turn advise users on areas which may be shallower than expected. These tools help users to make more informed navigational decisions, avoiding areas that have been flagged as potentially shallow even if these readings are not verified by official hydrographic tools. Another example can be found in work from NOAA’s Anthony Klemm who scraped all CSB data from Seabed2030 within America’s Atlantic and Gulf Coasts to assess areas of disagreement between official charts and CSB data. Through this process, more than 315 million data points were collected and assessed for their agreement with nautical charts, and areas of discrepancy were identified and tagged for potential future hydrographic resurveying utilizing more advanced survey tools. In this way, CSB has helped to identify cases in which advanced tools should be utilized and has helped to prioritize areas of interest. In theory, this data can be used to support hydrographic efforts, especially in localized areas where seafloor shapes have direct impact on coastal populations. For example, this data could help to characterize tsunami impacts, results of hurricanes, and regular changes in dredged channels. A great example of CSB utility may be found in narrow waterways where isostatic rebound is causing waterways to become shallower, reducing navigability in waterways which may be vital for transport, recreation and industry. CSB data can be used by hydrographic offices and companies to inform local mapping efforts and policies, but can also contribute to global scientific efforts, like the Seabed 2030 Project. This project is a joint initiative of the Nippon Foundation and GEBCO, the latter of which operates under the auspices of the International Hydrographic Organization (IHO) and UNESCO’s Intergovernmental Oceanographic Commission (IOC). The project’s aim is to completely map the world’s seafloor with direct measurements by 2030. Any CSB data can be contributed to the Seabed 2030 Project, and the general international community, by submitting it to the IHO’s Data Center for Digital Bathymetry (DCDB) via a Trusted Node. The “Trusted Node” conducts quality assurance on the data and then makes it available to the public, via the IHO DCDB.  The role of a trusted node is primarily to act as a secure source of data to the DCDB. This requires that someone be responsible for managing data flow from vessel into the DCDB, in line with the guidelines set up in the B-12 guiding document from the IHO. To become a trusted node, contact with the DCDB/NCEI is required. A list of existing trusted nodes exists here . Each trusted node has its own target audience; for example, the International SeaKeepers Society is primarily engaged with privately owned yachts and leisure boats, whereas the University of South Florida Center for Ocean Mapping and Innovative Technologies (COMIT) primarily engages all types of vessels within the Tampa Bay region. Finding the right trusted node to fit your vessel helps to streamline this process. To enroll your own organization as a trusted node, review the guidance on the CSB tab of the IHO DCDB website , and contact the DCDB via email: bathydata@iho.int . DCDB contact for inquiries about becoming a Trusted Node: bathydata@iho.int Legal considerations This section is not intended to provide legal advice, but rather to provide examples of some common legal considerations. Please look into your own country’s policies and feel free to investigate international laws and treaties yourself to verify the information found in this section. This section was also written prior to the ratification of the High Seas Treaty, which may change the way that data is collected within international waters. This section will be updated when more detailed information about these changes becomes available. A common question regarding CSB is whether or not work of this nature requires a permit.  Many countries hold to the standard that any marine research of any kind that takes place in national water (within a country’s own Exclusive Economic Zone [EEZ]) must be permitted. Marine research is defined differently in each country but may involve the physical or digital collection of data. One of the ways CSB falls outside of this category is that the data is not collected intentionally, but rather incidentally. Similarly, data that is collected for personal use is permitted in most EEZs without requiring any additional permitting. It is our understanding at the time of publication that CSB data must be collected by happenstance en route to a destination for non-scientific purposes. In other words – if a ferry transits back and forth between stops and happens to collect bathymetric data along the way, it would be considered an incidental collection while en route to a destination for an unrelated purpose, rather than being considered intentionally collected data. It should be clarified that in certain circumstances, commercial entities encounter different sets of rules regarding the dissemination of data. Data should not be contributed from any areas of national security.  Another common consideration is how CSB data is managed. As Seabed2030 is an international project collecting data from both inside and outside of several countries’ EEZs, it is important to determine how to best handle this data. The current approach has been to send a circular letter around to the hydrographic offices of each country to make them aware of the CSB initiative. If a country is willing to release the data from their EEZ to be publicly available, they sign an agreement, and the data can be made available through IHO DCDB. If a country chooses not to respond, or responds negatively, the data is not released publicly.  Data within a masked or hidden region still exists and is retained, in case of the eventual positive response from a country. If a country newly signs the circular letter, data previously collected and submitted in their EEZ can be retroactively made available. The IHO maintains a document on their website that lists the acceptance of CSB activities and provision of resultant datasets in waters under national jurisdiction, which shows the current status of coastal states that have agreed to participate in this effort. We acknowledge that at the time of publishing this first version of this document, the High Seas Treaty has recently been ratified. It remains unclear how this may affect the legality of participating in projects such as this, or if any permitting will be required. As new information comes to light regarding this, we will continue to update this document to the best of our ability. Finding Your Crowd This section is designed to help guide a program creator through the process of finding vessels that are both equipped for and interested in participating in CSB. The pages below outline not only what to look for in vessels and operators, but also how program managers can best optimize their program to maintain engagement and enthusiasm amongst participants (see examples of stakeholder engagement under Templates). Vessel features The suitability of a vessel for CSB depends on both its onboard hardware and the engagement of its owner or operator. A wide range of equipment brands can be used, which is important because it allows nearly any vessel to participate. As mentioned briefly in previous sections, CSB requires vessels to be equipped with navigational equipment including a depth transducer and a GNSS unit.  GNSS instruments are typically paired with a chart plotter that includes an internal timekeeping system. It is essential that the vessel’s time settings are enabled and properly calibrated to ensure data are accurate. Next, a depth transducer is required. Depth transducers, regardless of brand, are generally compatible with CSB. Transducers take measurements in a standardized digital unit that can be converted to meters, feet, or other display units, so the user’s preferred display setting does not affect data collection or utility. Each of the above tools need to be connected to one another via a backbone of some sort. Typically, this is either a NMEA2000 or a NMEA0183 backbone (pictured below), across which instruments will send messages. Each logger is built to accommodate one or both backbone types, and some models (like the WIBL) have both connectors. Adaptors that convert from NMEA0183 to NMEA2000 are available, if needed.  If a vessel does not already have an NMEA2000 backbone, one may be installed at the project’s discretion. NMEA2000 installation generally takes 30–60 minutes. Loggers may also be built into a system using a digital plugin for a chart plotter or a multi-function display system. Some great examples of companies that are working to contribute data from this form of logger to the overarching Seabed2030 project include Raymarine, Rosepoint, and WASSP. To date, these companies have generally opted to become their own trusted nodes in order to handle this data; however, WASSP has established a partnership with the International SeaKeepers Society in which they contribute data through the SeaKeepers trusted node. The final piece of this puzzle is finding a willing and engaged vessel owner. The following sections will outline some of the important considerations for a vessel to become involved in CSB, and how to find and keep participants that contribute good data. Motivating vessels and overcoming hesitation Depending on a vessel’s ownership, motivations to participate in CSB may be vastly different. Based on the authors’ collective experiences, this section outlines the common motivations observed among several types of participants. While not exhaustive, these examples are intended to illustrate patterns that may help guide outreach to similar audiences. There are several common motivations that seem to apply across many crowds and spaces. For example, lower-cost solutions and solutions that offer increased ease-of-function appeal to many crowds. Vessels may be more willing to contribute if participation in CSB costs them less financially and/or if their participation requires relatively little contribution of time or knowledge. Currently, CSB is being widely promoted by the Nippon Foundation-GEBCO Seabed2030 Project and by organizations like the International SeaKeepers Society, which can both provide YDVR loggers to participants free of charge. Alternatively, companies such as Orange Force Marine offer higher-tech options where CSB data are remotely retrieved from loggers, motion-corrected, and automatically relayed to global initiatives on behalf of and with the user’s consent. The hands-off nature of these loggers makes them an attractive solution to many vessels. In addition to this, many vessels are motivated by being able to visualize their data online (i.e., a data portal map), receiving their data in a usable format after the data have been processed (i.e., tidal corrections), and by understanding the outcomes that can or have been achieved because of their participation. Meaningful case studies, both globally and locally, often act as drivers to participate. The concerns and challenges of different crowds will vary as much as their motivations will. One classic example of a crowd is the yachting community. This community is often motivated by seeing impactful use-cases, but can have a unique need for privacy. Within this community, it is common to get requests either for data anonymity or for delayed transmission to the IHO DCDB so that near-real-time vessel tracking is not occurring. Another great example of a crowd is a fishing community. Fishers may not want their fishing spots to be made public knowledge, so providing an option for anonymous data submission could help assuage concerns about revealing fishing locations to competitors. Working to accommodate the unique needs of your own crowd is an important step in overcoming hesitation within that community. Hosting a stakeholder meeting is a great way to gather information about what motivates and what causes concerns within your crowd. For examples of stakeholder meeting agendas, see the Templates section.  Maintaining vessel engagement Tools to maintain vessel engagement may include communication and contact, personalization of mission goals, and celebrating the impact of a vessel’s participation. These forms of engagement do require input and effort on behalf of the CSB program managers and range widely in time-intensiveness. Depending on an organization's available man-hours, some of the following examples may be more feasible to implement than others. For example, the Great Lakes Observing System (GLOS), in collaboration with Orange Force Marine, has created a data visualization product that uses a hexagonal grid to highlight areas with high and low data density. This system required up-front programming labor, but now runs automatedly, making it a relatively low-maintenance way of maintaining vessel engagement. This example “gamifies” CSB efforts by encouraging participants to get involved so that they can be the one to contribute data where it’s never been collected before. ‘Gamification’ could be taken a step further by providing a dashboard or application where top contributors are rewarded. It would also be necessary to note a country’s status on having signed the global circular letter when in national waters. To better serve the Florida Tampa Bay region, the Center for Ocean Mapping and Innovative Technologies (COMIT) developed a dedicated ArcGIS® Esri Hub called “ Crowd the Bay .". This site was designed to host regional CSB data in a way that directly engages local stakeholders. CSB data are pulled quarterly from the DCDB and run through NOAA’s Pydro Explorer application to generate CSB datasets that are corrected for tidal fluctuations. Once corrected, the data are imported into ArcGIS® Pro to create user-friendly shapefiles that are then shared as Esri Web Layers within the “Crowd the Bay” Hub data portal. The ArcGIS® Pro workspace also allows the data to be reformatted and shared according to participant needs (i.e., shapefiles, KMLs, xyz, etc.). Sustained stakeholder engagement depends on ensuring that contributors benefit from the use of CSB data.  In a similar vein, although through a more manual process, the International SeaKeepers Society has developed a “Million Soundings Society” to celebrate any of their vessels that have individually contributed over 1 million depth soundings to Seabed2030. This is celebrated at their annual gala where members will be “inducted” and celebrated for their contribution. Data contributions are tracked through the DCDB CSB Data Provider Dashboard . Another publicly available dashboard includes the  FARSOUNDER Dashboard , which is likely to include leaderboard functionality in the near future, and currently includes automatically generated graphics of each vessel or trusted node’s contributions to date. If a vessel is particularly interested in seeing their own data, as is common with the COMIT program stakeholders, you can provide this to vessels directly or provide them guidance on how to retrieve their data on their own. A guide on how to do this can be found in the Data Extraction and Processing section. An additional tutorial for participants to visualize their own data using a free and open-source software (QGIS) can be found in the Data Visualization section. The DCDB is also rolling out customized provider and vessel map URLs in 2026, allowing providers and any user to quickly bookmark and share links to their specific data contributions. Finally, engagement activities such as newsletters can help maintain consistent communication with stakeholders about the progress being made, updates in the program, new tools, and overall organization contributions. This will encourage vessels to stay involved and reach out with questions. Recruitment and onboarding When initiating engagement with a recruited vessel, it is important to include information about your program motivations and process. Some of these items may include (but are not limited to) the following:  Your program's website Links to equipment checks such as the one linked here Link to the video produced by the Canadian Hydrographic Service (CHS) about what installing a logger means Information on use cases (see the Use Cases section for examples) Links to the DCDB , Seabed2030 , or IHO sites to provide context on international goals and accomplishments If possible, confirming vessel interest with a video or phone call, or in-person meeting can help to ensure everybody is on the same page about what it takes to be involved in this project. Once interest is confirmed you may want to send the following: An MOU or Letter of Agreement  Metadata worksheet (one per vessel) Offsets worksheet (one per vessel) Request for address to ship logger OR a time and place to meet and install the logger Examples of each of these can be found in the Templates section Hardware Options For ease of explanation, we will divide loggers into “First Generation” and “Next Generation,” wherein the former are not Wi-Fi enabled and the latter are.  First generation loggers First Generation loggers are characterized by the need to un-install an SD card from the logger and manually plug it into a computer to be able to access and share the data files. One of the most common examples of this logger type is the Yacht Devices Voyage Recorder or YDVR loggers. These come in either the N configuration (which is built to access NMEA backbones for all brands except Raymarine), or the R configuration (which will plug into only a Raymarine proprietary backbone). This can be determined by the brand of equipment on the vessel, as well as the number of pins in the connectors (5 vs. 6). Next generation and WiFi enabled loggers Next Generation loggers are characterized as having more than just an SD card to eject and manually upload data. These loggers currently include the Wireless Inexpensive Bathymetry Logger (WIBL), the Nemo30 logger (with WIBL software), and the Orange Force Marine Mussel Kits. These loggers allow a vessel to continuously transmit data to either the parent organization, or via Orange Force Marine as a third party. Then, data can be transformed and submitted to the DCDB. Real-time data transformation and submission is a new tool under development that is currently available through Orange Force Marine. This is also something that can be accomplished independently using open-access tools that are available through the WIBL and Open VBI GitHub repositories.  Wireless Inexpensive Bathymetry Logger (WIBL) The WIBL logger was developed by Brian Calder and Brain Miles’ team at the Center for Coastal and Ocean Mapping at the University of New Hampshire. As of the release of this manual, WIBL has released hardware version 2.5.1 and firmware version 1.6.1.  This version of the logger supports NMEA-0183 (two channels) and NMEA-2000 as inputs, and can generate data on NMEA-0183 (two channels) if required for debugging. The loggers are configured in a typical setup. The JSON configuration files corresponding to the loggers can be queried for their current configuration with the DesktopUI tool in the repository. The loggers are all configured to bring up their configuration web server on boot (the SSID will be for example wibl-comitXX-config for logger XX, with password wibl-config-password), so you can attach to them directly without having to crack open the box. Instructions on how to do this are in the Wiki associated with the repository, https://bitbucket.org/ccomjhc/wibl/wiki/Home . Orange Force Marine (OFM) Mussel Kit Developed in 2021 by Derek Niles and Colin Thomson, Orange Force Marine Ltd. , offers two types of “Next Generation” data loggers as part of their CSB solution.  The first type is a standard, Wi-Fi enabled data logger and the second type is a Cellular (3G/4G/5G) enabled data logger that also has a separate GPS antenna, cellular antenna, and internal inertial motion unit (IMU). These data loggers have an internal 8 GB SD storage card and automatically connect and upload data to the cloud when in Wi-Fi or cellular range.  Outside of connectivity, the Mussel Kit will store data on the SD card until it once again resumes connectivity and can upload the backlog of collected data. The loggers send up a “heartbeat” message periodically and can be remotely configured (or reconfigured), remotely updated (firmware), and monitored by OFM for operational status. The data logger units are NMEA 2000 enabled, although they can be employed on NMEA 0183 networks by way of a NMEA 2000 to NMEA 0183 adaptor (such as the Actisense NGW-1 or NGX-1 units). After initial installation and configuration onboard a vessel, the Mussel Kit automatically collects and uploads data without requirements for vessel operator intervention or action. When a Mussel Kit is connected to cellular or Wi-Fi, collected CSB data are automatically uploaded to OFM’s AWS S3 Cloud, processed, and sent onwards to the IHO DCDB in near-real time. Comparison of logger options Depending on a CSB program’s needs at a given time, one type of logger may be preferred over another. An in-depth comparison of the logger types currently available as of 2025 can be found here . The purpose of this comparison chart is to help CSB organizations weigh the pros and cons of each logger type, including pricing, programmatic assistance, and ease of access. Installation and Setup Installation prep At least a week before an installation is scheduled, check that the installation kit and equipment/supplies on hand are sufficient. Check the Installation Kit list to ensure all items are on-hand and have been replenished as needed. Maintain an inventory spreadsheet of the materials in the install kit and update this during the check. If possible, check logger function several days prior to installation. Bring at least one back-up logger just in case. WIBL The silk-screen on the logger boards also indicates the polarity of the cables. A blob of hot-glue on the connectors after you install them is recommended. If they are installed, just make sure they don't come loose in service. Remember that if you want to connect to the logger to update the firmware, you'll need a USB to serial converter that provides 5V power and 3.3V logic: this is not universal (if you feed the logger with 5V data, you'll likely destroy it). The current converter used is an Adafruit FTDI Friend. Looking at the board from the component side, it plugs into the pin header to the right of the microcontroller, with its components facing to the right (check the silk-screen on WIBL and converter to confirm GND pin position). Check that the firmware is updated and flash it with the appropriate metadata. If the metadata is not preloaded onto the logger, it can be fixed during WIBL Data Processing . Instructions for updating the firmware and flashing the WIBLs can be found in the WIBL Installation Guide section and on CCOM's WIBL GitHub page . Bring a laptop with you, if possible. Plan to let the WIBL run after installation, pull the SD card, and check for proper function. WIBL data are not human-readable, so to check if it’s properly recording, you’ll have to run it through the appropriate python scripts (see WIBL Data Processing for instructions). Prior to the installation date, direct the participant to the Equipment Check webpage and have them confirm that their vessel is set up with a NMEA. To help plan for the installation, it may be helpful to request photos from the participant of the NMEA location within the center console. After the installation is complete, the participant will need to handle the data hand-off. Send them a Box folder link (or another preferred file-sharing platform) and make sure that they can upload files to it. Ask them to wait to delete any items until you have downloaded them or transferred ownership to yourself. Yacht Devices (YDVR) If installing a YDVR, you will need to make sure the configuration file on the microSD card has the correct parameters specified. Open a text editor (e.g., Notepad) and copy the configuration below: “CFGSAVE NMEA2000=ON FORMAT=DAT AIS=OFF DELETE=YES AUDIO=OFF COMPRESSION=OFF GAIN=2.70 DELAY=30.0 FILTER=ON THRESHOLD=2.50 PLAYER=OFF LOOP=OFF SILENT=OFF” Save the file as YDVR.TXT to the root of the MicroSD card After the installation is complete, the participant will need to handle the data hand-off. Send them a Box folder link (or another preferred file-sharing platform) and make sure that they can upload files to it. Ask them to wait to delete any items until you have downloaded them or transferred ownership to yourself. Example YDVR configuration file: # Voyage Recorder YDVR-04 (www.yachtd.com), serial number: 00000000 # Firmware version: 1.04 17/08/2018 # Settings in this file match the settings in device’s EEPROM # SAVE TO EEPROM # To save settings, rename this file to YDVR.TXT and remove # symbol # from the line below CFGSAVE # NMEA 2000 RECORDING NMEA2000=ON FORMAT=DAT AIS=OFF DELETE=YES IGNOREPGN= IGNOREADDR= IGNORE= SPEED=250K SILENT=OFF # AUDIO RECORDING AUDIO=OFF COMPRESSION=OFF GAIN=2.70 DELAY=30.0 FILTER=ON THRESHOLD=2.50 # PLAYER MODE (disables recording when ON) PLAYER=OFF LOOP=OFF # End of file OFM Mussel Kit Make sure to contact Orange Force Marine with the date/time of the installation in case their support is needed. They can also check to ensure the logger is online, connected to the cloud environment, uploading data properly, and collecting valid depth and position data. Installation day requirements: OFM Mussel Kit data logger (plus backup(s))  Installation kit  Camera Cell phone (for contact with OFM in real-time for installation assistance, or for using a hotspot) 1-2 people (2 is best for metadata offset measurements, especially if you haven't done many installations previously) During installation, take pictures and videos of logger identification numbers, logger orientation, installation locations onboard the vessel, wiring configurations, and antenna placement. Photos can be useful for social media and marketing and also provide a visual reference for offset directions and relative positions of GPS and transducers.  Installation Kit Prior to leaving for a logger installation, ensure that the installation kit contains the following: NMEA 2000 T-splitters (single or 2-way) (single) (2-way)   NMEA 2000 drop cables (1-m or 0.5-m, of the correct connector either 0183, 2000 type N or 2000 type R) Tape measure Outdoor double-sided Velcro Pens Blank MOU (if not already filled out - see Templates for examples) Offset worksheets (if not already filled out - see Templates for examples) Metadata forms (if not already filled out - see Templates for examples) Logger + backup (of the correct connector - either 0183, 2000 type N, or 2000 type R) MicroSD card with Config file already loaded (linked YDVR here, example in Templates) Optional and backup supplies: NMEA 2000 elbow connector NMEA 2000 terminator cap NMEA 2000 power isolator Thru bolts Screw drivers Pliers Zip ties Scissors Electrical tape Duct tape Epoxy Desiccant packets Cleaning solvent Cleaning wipes/rags Installation guide: OFM OFM has provided detailed Installation and Operating Instructions for their Mussel Kits.  A hard copy will also be included in the shipment with the data logger. Be sure to contact Orange Force Marine with the date/time of the installation so they can be available to provide real-time / near real-time support. During the installation you will be directed to fill out a metadata table for the vessel (see pages 7-10 of the  Installation Instructions ), which can be completed manually on the printed sheets and submitted electronically here .  When the installation is complete, contact Orange Force Marine to confirm that the logger is online and working properly. Installation guide: YDVR Locate a NMEA 2000 backbone or T-connector with an open port. If a port is available, simply plug in the logger’s Micro Male connector. If all ports are occupied, add a new T-connector to the backbone before connecting the logger. Ensure proper termination: the two ends of the backbone must each have one terminator. Any unused T-connector ports should be capped. Secure the logger in a dry, protected location away from bilge water or spray. Confirm network power (10.5–16 V) is present before connecting. Lock the connector collar to maintain water resistance. Insert the MicroSD card into the logger until it clicks into place. Connect the vessel’s NMEA 2000 power or turn the system “on." Observe the LED indicator at the end of the logger: 1 green flash (1 second) = file created, ready to record 3 green flashes (0.5 seconds apart) = receiving NMEA 2000 data (correct installation) Constant green flashing = actively recording Red flashing = indicates error (no card, wrong format, or write issue) When powering down, a  short red flash confirms safe file closure. Data are stored automatically in folders named YDVR#### on the MicroSD card. To retrieve data, remove the card, copy files to a computer, and process with YDVR Converter software (available for download here ). Installation guide: NEMO30/WIBL Confirm that the NMEA network starts when the vessel is powered on. Remove the backplate/cover of the logger.  Check to make sure the logger has an SD card for data storage and that it’s clicked "in".   (disengaged)   (engaged) Place 1-3 desiccant packs into the logger. It’s okay for the packs to rest on the circuit board.  Put the cover back on the logger. Zip-tie the two opposite corners to secure the plate. [Note: when copying data, these zip ties will have to be cut and redone each time] Locate the NMEA network hub. If there isn’t an empty port, swap in a T-splitter if needed. Determine the best placement for the logger within 1- or 0.5-meters (depending on drop cable length) of the port. Before placing the Velcro to mount the logger, ensure no pinching, blocking, or other clearance issues will happen when closing the console. Use 2 strips of Velcro at the mounting site and on the backplate of the logger, alternating rough and smooth sides. Connect the logger to the NMEA network with the drop cable. Make sure the locking threads are tightened on both sides. Plan to let the WIBL run after installation, pull the SD card, and check for proper function using the appropriate python scripts. After installation is complete, send participant a Box folder link and make sure they can upload to it. Ask them to not delete items. Preparing a WIBL for field installation Start Visual Studio Basic with PlatformIO. Build the library (check mark at bottom of PlatformIO). Open WIBL box to access board. Connect USB to serial pin. The board should indicate it’s on with a green and blue light. Attach a jumper cable on the “PROG” header pins. Attach a jumper cable to one of the “RESET” header pins. Touch the jumper cable to the other “RESET” header pin. The lights on the board should go out. Remove the jumper from one of the “RESET” header pins. Remove the jumper from the “PROG” header pins. You should now be in PROG mode to download new firmware and edit metadata – no lights will be on the board. If updating firmware, select Upload and allow program to run. After completing the download and/or metadata edits, touch the jumper to the other “RESET” header pin briefly again to reboot the logger. Remove the jumper from the “RESET” header pins. Open a new terminal window. Connect the WIBL to Wi-Fi. Run the following commands in the Serial Monitor window: While attached to the logger, use the configure command to make sure that the webserver is configured on; you should see a line that says webserver on followed by three numbers. If this is not the case, configure it 'on' with webserver on 20 5 5 . Take note of the SSID and password for the Access Point (AP) WiFi network from the configure command output. Set them with commands ssid ap name and password ap name if they are not set (they will default to 'wibl-config' and 'wibl-config-password' otherwise). Make sure that the WiFi is set to access point mode in the configure output. Use the wireless accesspoint command if this is not the case. Reboot the logger with restart . Connect your development computer to the SSID noted above, with the associated password. If you're monitoring the serial output of the logger, you should see information messages indicating that an IP address has been assigned to your computer. Typically, it's 192.168.4.2. Start the desktop GUI with python main.py in the DesktopUI directory in the distribution, or through VSCode. Note that you may need some requirements beyond those installed for the main WIBL Python package to make this run. Note that since firmware 1.4.0, the logger has a compiled-in configuration that will turn on web server by default with a well-known SSID and password; see LoggerFirmware/src/boot_config.json and the LoggerFirmware/src/json2cstring.py Edit config/metadata as needed. Make sure to Set Logger and Save Config. Collecting metadata When installing data loggers, it is important not only to focus on the data that is being collected, but also the metadata. This allows managers to receive and use the most accurate data possible. Certain logger providers, such as Orange Force Marine, include detailed metadata forms in their installation instructions. CSB program managers are encouraged to adopt their own ways of collecting and maintaining metadata records and are referred to the IHO’s B-12 Edition 3.0.0 Guidance to Crowdsourced Bathymetry document for details on required and suggested metadata fields for CSB data. Data Retrieval and Management Frequency of data transfer Depending on logger type, CSB data will be transferred at varying intervals. For first-generation loggers like the YDVR, the data transfer timing depends on a few variables. First, the amount of onboard storage (SD card size) will determine how much data can be stored at one time before the logger is full. Cards larger than 32 GB are not recommended, as they have been associated with errors, and a 32 GB card typically lasts between six months and a year under normal use. Another variable to consider is the amount of data being saved at a time. A YDVR logger is designed to record any signals coming across the NMEA backbone. On larger vessels such as yachts or cruise ships, this could include things like greywater storage capacity, fuel load, and other kinds of information that are not relevant for CSB. As a result, these loggers can fill up more quickly. If working with a YDVR logger specifically, the “Example Configuration File” in the Templates section can be used to avoid recording some of these unnecessary data streams. For more details, please refer to the Optional Test Submission page. How frequently your organization wants to maintain contact with program participants may also be a determining factor in how often data is offloaded. Requesting data is a great way to maintain contact with a vessel, and thus it may be helpful to request more regular data drops. For example, the International SeaKeepers Society tends to request data on a quarterly basis as a way of maintaining consistent contact with vessels. Next‑generation loggers, including the WIBL and OFM Mussel Kit, offer more flexibility. These devices can transfer data via Wi‑Fi or cellular networks, meaning data is being transmitted in near-real-time. The WIBL will only transmit when the Wi-Fi signal is within range of the device, but on a vessel with star-link this should be fairly continuous. With a cellular connection, this data stream should be continuous if it is within cell-tower range. Each device has onboard storage capacity for several months’ worth of data. These loggers do not require contact with the vessel beyond initial setup, which creates a more hands-off experience for both the CSB program managers and the participating vessels.  Offload mechanisms The method of retrieving data varies with the type of logger. For first‑generation loggers, or when using a WIBL in a similar mode, data must be retrieved manually by removing the SD card, copying the files, and uploading them to a secure cloud location. This allows for the data to not only be transmitted, but to also be stored somewhere secure should something happen to any individual SD card or computer on which data is being processed.  Data offload can be conducted either by the participating vessel or by the CSB program managers. This decision can be made based on the skillsets of participants, the available time for managers, and the locations of vessels in relation to the managers. For example, SeaKeepers requests all data be transmitted by the vessel due to individual vessel locations being too far from any branch or headquarters. Exceptions can be made depending on the case, and in some circumstances, mailing the SD card to the program manager may be the best option. For example, if the vessel owner/operator is uncomfortable with the process of downloading files from an SD card, compressing them, and uploading it to a cloud-based storage account, then it may be best for the trusted node or CSB program manager to conduct this step. For guidance on how to share this procedure with volunteers, see this Example data retrieval guide . When using a next-gen logger, such as the WIBL in “station” mode, volunteers can use the Wi-Fi link to download the data remotely. As of August 2025, the batch-download function is still in development. Until it is made available, data offload can only be performed on one logger at a time. When using a fully independent next-gen solution such as WIBL in “ap” mode or OFM Mussel Kit loggers, the data offload process should occur automatically. For a WIBL, you will have set up a link to a dropbox or amazon cloud storage account where the data will automatically offload any time the vessel is within range of the Wi-Fi signal to which it is connected (eg. Starlink). Orange Force Marine (OFM) Mussel Kit loggers have the same capability and additionally can utilize cellular connection to leverage a constant data stream.  OFM handles the full data collection and management pipeline for their loggers. In addition, they have agreed to provide the raw data back to CSB programs via Dropbox (other options are available). Data Transformation and Submission WIBL and YDVR data processing Getting Set Up You will need to install the following programs to run the WIBL processing scripts: Python 3.14: download here . Choose Customize Installation . Under Advanced Options check the box "Add Python to Environmental Variables." [More detailed instructions are provided here ] Windows PowerShell 7 : download here Miniconda : download here Visual Studio Code : download here WIBL GitHub Repository : Linked here . Save the repository to Desktop (or Documents) - do not leave it in Downloads. Perform the following steps the first time you run the WIBL scripts: Note:  Edit file paths as needed to match the location where your files are saved locally #Open Anaconda Prompt #Run the following code conda init powershell #Close Anaconda Prompt --------------------------------------------- #Run Windows PowerShell 7 as an administrator (see screenshot below) #Run the following code Set-ExecutionPolicy Unrestricted #Close Windows PowerShell 7, then reopen (not as admin) #Set directory to the wibl-python folder within the WIBL repository cd .\Desktop\WIBL-main\wibl-python #Install packages pip install . #Create environment conda env create -f environment.yml #Execute the environment conda activate wibl-python Metadata - Configuration - Authentication  If you did not preload metadata onto the logger before installing it, you will need to create your metadata and configuration files before you can process raw data with the WIBL scripts. Example metadata and configuration files can be found in the WIBL repository. Guidance for how to properly format each of these file types can be found in the README file located in the same folder. Metadata, configuration, and README file locations in the WIBL repository: WIBL-Main\wibl-python\examples\ship-metadata-complete.json WIBL-Main\wibl-python\examples\configure-submission.json WIBL-Main\wibl-python\examples\configure-submission-test.json WIBL-Main\wibl-python\examples\README,md To create metadata and configuration files specific to your dataset: Copy the example files to a new folder in Documents (or Desktop) - don't work within the WIBL repository. Open the copied files in  Visual Studio Code  to edit. In the configuration file, make sure to set  "local": false , or else your files will not be transmitted to the DCDB when you run  submitDCDB.ps1 . The configure-submission-test.json can be used to submit data to the test-API on the DCDB (does not officially submit data). Save the edited files with appropriate names (e.g., chance-maritime-metadata-complete.json and configure-submission-USF.json). Further information on mandatory and recommended metadata can be found in IHO's Guidance to Crowdsourced Bathymetry B-12 Edition 3.0.0 The more comprehensive the metadata, the more valuable CSB products are to end-users! The DCDB will accept submissions meeting the mandatory metadata requirements, but organizations should strive to meet the highest standards recommended whenever possible. You will need to download your organization’s Trusted Node authentication token in order to submit processed data to the DCDB.  Running the WIBL Scripts Note: There is a README file with more detailed information about the WIBL data management scripts and how to use them in the WIBL repository. README file location in the WIBL repository: WIBL-main\wibl-python\scripts\data-management\README.md Once you're ready to start processing, perform the following steps: #Run Windows PowerShell 7 as an administrator #Run the following code Set-ExecutionPolicy Unrestricted #Close Windows PowerShell 7, then reopen (not as admin) #Set directory to folder where raw files are saved (change folder path as needed) cd .\Documents\CSB\Chance-Maritime\1-DataProcessing\ #Rename raw files to .wibl Get-ChildItem * | Rename-Item -NewName { $ .Name + ".wibl" } #Set directory to WIBL data-management scripts folder cd .\Desktop\WIBL-main\wibl-python\scripts\data-management\ #Activate environment conda activate wibl-python #Process .wibl to .geojson .\processWibl.ps1 [[-wiblPath] ] [[-metadataFile] ] [[-wiblConfig] ] #Validate .geojson against csbschema .\validateWibl.ps1 [[-inPath] ] [[-extension] GeoJSON] processWibl.ps1 : -wiblPath is the path to the folder where .wibl files are saved, -metadataFile is the path to the metadata file you created, and -wiblConfig is the path to the configuration file you created. Example: .\processWibl.ps1 -wiblPath C:\Users\schernoch\Documents\CSB\Chance-Maritime\1-DataProcessing\ -metadataFile C:\Users\schernoch\Documents\CSB\Chance-Maritime\0-Metadata\chance-maritime-metadata-complete.json -wiblConfig C:\Users\schernoch\Documents\CSB\Chance-Maritime\0-Metadata\configure-submission-USF.json validateWibl.ps1 : -inPath is the folder where processed .geojson files are saved, -extension should be set to GeoJSON Example: .\validateWibl.ps1 -inPath C:\Users\schernoch\Documents\CSB\Chance-Maritime\1-DataProcessing\ -extension GeoJSON Information on the most up-to-date csbschema can be found here . Once the .geojson files have been validated against csbschema, they are ready to be submitted to the DCDB. There is also a new CSB validator tool written by Clint Campbell (available for download through this link ) that allows CSB data to be validated by time stamp (data not collected from the future) and GPS (GPS location exists) to ensure data will actually be accepted into DCDB. This tool enables a CSB manager to validate not only that the data has something in every B-12 required section like the WIBL validator (e.g., there is a number in the “depth” category), but will actually reflect the DCDB’s data validation process and signal to practitioners if the data will be flagged in the system once submitted (e.g., the depth is 1E34, which is both beyond the transducer readable range and is in a format that cannot be utilized by DCDB, resulting in the submission being rejected). Submission of GEOJSON data to the DCDB All data submitted to the DCDB need to be in .geojson (preferred) or XYZ format and contain appropriate metadata fields. These requirements are outlined in DCDB guidance documents . For  WIBL  or  YDVR  data, you will need to upload data periodically. See the WIBL and YDVR Data Processing protocol for full details. For  Mussel Kit  data, OFM handles data submission on behalf of the Trusted Node, using the Trusted Node's secure token. OFM can also provide the raw data back to Trusted Nodes via Dropbox or AWS S3 buckets (other options are also available). Once your WIBL or YDVR data have been validated, they can be submitted to the DCDB using the following PowerShell script: #Run Windows PowerShell 7 as an administrator #Run the following code Set-ExecutionPolicy Unrestricted #Close Windows PowerShell 7, then reopen (not as admin) #Set directory to WIBL data-management scripts folder cd .\Desktop\WIBL-main\wibl-python\scripts\data-management\ #Activate environment conda activate wibl-python #Submit to DCDB .\submitDCDB.ps1 [[-inPath] ] [[-authFile] ] [[-configFile] ] [[-extension] *.geojson] submitDCDB.ps1 : -inPath is the folder where validated .geojson files are saved, -authFile is the authentication token .txt file, -configFile should be the same as used for processWibl.ps1, and -extension should be set to *.geojson. Example: .\submitDCDB.ps1 -inPath C:\Users\schernoch\Documents\CSB\Chance-Maritime\2-Validated\ -authFile C:\Users\schernoch\Documents\CSB\Chance-Maritime\3-Submission\ingest-external-COMITUSF.txt -configFile C:\Users\schernoch\Documents\CSB\Chance-Maritime\0-Metadata\configure-submission-USF.json -extension *.geojson When a file is successfully submitted to the DCDB, you should receive the following output: Each time a file is submitted successfully, the program will print a submission ID. Make sure to log these submission IDs in case your files need to be tracked down by technical support staff at the DCDB for whatever reason. If you are unable to batch-submit your processed data using the WIBL PowerShell script provided above, you can use either of the following options to manually submit your .geojson files to the DCDB Option 1: Python script Copy the following script into Visual Studio Code   and replace and with the appropriate file paths. Save the file as  submit_geojson.py  and make note of what folder you save it in. import requests token_path = r"" geojson_path = r"" unique_id = "COMITUSF-e512gc2r-q565-279j-548i-e5fc6389cth2" url = "https://www.ngdc.noaa.gov/ingest-external/upload/csb/geojson" with open(token_path, "r") as f: token = f.read().strip() headers = { "x-auth-token": token } files = { "file": ("wibl-raw.61.geojson", open(geojson_path, "rb"), "application/json"), "metadataInput": (None, f'{{"uniqueID": "{unique_id}"}}') } response = requests.post(url, headers=headers, files=files) # === OUTPUT === print(f"Status Code: {response.status_code}") print(response.text) Perform the following steps to submit your .geojson file to the DCDB. #Launch Command Prompt #Call directory to the folder where submit_geojson.py is saved cd .\ #Run the following code python submit_geojson.py #Record the submissionID You should receive the following output if your file was successfully submitted to the DCDB: Each time a file is submitted successfully, the program will print a submissionID. Make sure to log these submissionIDs in case your files need to be tracked down by technical support staff at the DCDB for whatever reason.  If you have multiple .geojson files to submit, you will need to edit within submit_geojson.py each time you submit a new file. This can be done relatively quickly if you keep submit_geojson.py open within Visual Studio Code, making sure to save (ctrl+S) your changes before running the code again. Once has been edited to the new file path, you can click the up arrow in Command Prompt to reload the previous command and click enter to run it. Options 2: Batch script Perform the following steps to submit your .geojson file to the DCDB. Make sure to replace and with the appropriate file paths. #Copy and paste the following code (lines 3-17) into Visual Studio Code @echo off REM Define paths and values set "TOKEN_FILE=" set "GEOJSON_FILE=" set "UNIQUE_ID=COMITUSF-e512gc2r-q565-279j-548i-e5fc6389cth2" REM Read token set /p TOKEN=<"%TOKEN_FILE%" REM Run curl curl -i -X POST "https://www.ngdc.noaa.gov/ingest-external/upload/csb/geojson"^ -H "x-auth-token: %TOKEN%"^ -H "Content-Type: multipart/form-data"^ -F "file=@%GEOJSON_FILE%;type=application/json"^ -F "metadataInput={\"uniqueID\":\"%UNIQUE_ID%\"}" #Replace and with appropriate file paths #Launch Command Prompt #Copy and paste your edited code into Command Prompt #Run the code #Record the submissionID You should receive the following output if your file was successfully submitted to the DCDB: If you have multiple .geojson files to submit, each time you submit a new file you will need to edit in Visual Studio Code and then run the edited code in Command Prompt. Recommended: Test submission If you would like to test out running the scripts without posting data to the DCDB Data Viewer, simply add /test/ to the endpoint URL, so it instead reads: https://www.ngdc.noaa.gov/ingest-external/upload/csb/test/geojson The test endpoint should always be used first for any system or script testing. Submissions sent to the DCDB production endpoint are considered final submissions and are subject to a lengthy process to remove if submitted in error. Graphical user interface As of March 2025, a Graphical User Interface (GUI) is being developed to aid in the processing and submission of CSB data. The GUI should lower the barrier to entry for organizations interested in becoming involved with Seabed 2030, but lacking the time or expertise to learn the programming tools required to do so. As more information becomes available on this tool, this section will be developed more fully. This toolset can be found here . Data Extraction and Processing If your stakeholders would like to see their data for themselves, it may become pertinent that you download and share the data yourself. To do this, you will need to follow the steps outlined in the NCEI/DCDB data extraction section. Once raw data are obtained from the DCDB, they should be tide corrected using the CSB Processing Tool in Pydro Explorer, following the instructions in the Pydro tidal corrections section. NCEI/DCDB data extraction Perform the following steps to extract CSB data from the DCDB: Go to the IHO Data Centre for Digital Bathymetry Viewer. Click the IHO DCDB/NOAA NCEI drop down menu, uncheck the ‘ Multibeam Surveys ’ layer and select the ‘ Crowdsourced Bathymetry Files ' layer. As an alternative to steps 1 and 2, you can use this link (bookmark it) to navigate directly to the CSB data, instead of having to deselect the multibeam data Zoom in on the area you want to extract data from. You can also select ‘ Search CSB Files ’ to filter for a certain date range, Provider (Trusted Node), or Platform Name (vessel name). You can currently only search by one 'Platform Name' at a time, but the DCDB is working on enabling multi-platform searches. When you are ready to extract data, click the ' Identify ' drop-down menu and select the option you would like to use. Draw your bounding area of interest, select ‘ Extract NCEI/DCDB Data ’ and choose the ‘ Extract CSB Point Store Data .’ You will be prompted to enter an email address where the link to download files will be sent to. Do not check the box for ‘Create Grid. ' Leave the default for the rest of the options. Depending on the current volume of requests and the size of your requested area, you should receive an email with a link to download your data within a few minutes. Your CSB data are now downloaded and ready to have Pydro tidal corrections applied. Pydro tidal corrections Support Contact: Anthony Klemm, NOAA Office of Coast Survey   anthony.r.klemm@noaa.gov  Perform the following steps to process CSB data extracted from NCEI/DCDB to correct for tides and data-derived vessel transducer offset values: You will need to download the Pydro software here. Follow the Data Extraction instructions to retrieve the data you want to process. When you receive the email link from NCEI, download the data and save it in an appropriate location. Open Pydro , navigate to the ‘ BETA/EXPERIMENTAL ’ section of the Applications pane, and select ‘ CSB Processing.’ Click ' Run Program '. You’ll see a Windows terminal execute the python environment and a GUI should eventually pop up. If no GUI pops up, open the command line window to check if the following error was encountered:  ModuleNotFoundError: No module named 'pyfes'  To resolve this error, enter the following line of code: conda install -c conda-forge pyfes Click Run Program again and the GUI should pop up. In the popup window: (1) locate and select the Folder containing the file you downloaded from NCEI; navigate to the Tide Zone Beta.shp file (see file path provided below); and specify an output folder. (2) make sure this is checked to use automated BlueTopo data, (3) the checked boxes in the image below are the suggested outputs and grid resolution (5-10) for the workflow. Note: to streamline data processing, set a designated folder where Pydro outputs .gpkg files, so a single folder connection can be added to your GIS project. For use outside the United States, the CSB Processing tool has an option to use a global tide model (AVISO+ FES2022b) to resolve/correct depths to approximate Lowest Astronomical Tide (approx LAT).  Inside United States waters, it is recommended (but not required) to use the Discrete Tide Zoning model option instead. US Tide Zone .shp location:  C:\Pydro24\NOAA\site-packages\Python3\svn_repo\HSTB\CSB_processing\BETA_subordinate_tide_zones\tide_zone_polygons_new_WGS84_merge.shp Click ' Start Processing ' and allow it to run. You can watch processing progress in the command line window. The application window will close when processing is complete. Your CSB data are now tide corrected and have been output in a GeoPackage (.gpkg) that can be visualized using GIS software . Data Visualization Tidal-corrected data should be edited using GIS software and uploaded to a central location which can be shared with your stakeholders. This allows you to provide data to participants in the format that best fits their needs. KML files are typically too large to easily manage. If a participant does not have a particular format in mind, suggest providing .shp files, which can be visualized in QGIS using the instructions provided on the QGIS: Data visualization page. ArcGIS: Editing tide-corrected CSB data For Trusted Nodes that have access to ESRI software licenses, tide-corrected CSB data can be edited and visualized using ArcGIS Pro. 1. Launch ArcGIS Pro and select 'Map' under New Project . Create a name and select a location to save your project. 2. Under the Insert tab click ' Add Folder ' and select the folder where you set Pydro to output tide corrected data. 3. In the Catalog pane, click on the Folders dropdown, open the folder you just connected and locate the GeoPackage ( .gpkg ) that contains the tide corrected shapefile ( main.csb_final_points ). C lick and drag the main.csb_final_points file over the base map to add it as a map layer. 4. In the Contents pane, right click on the main.csb_final_points layer, click on the Data dropdown menu and select ' Export Features .' 5. When the Export Features box appears, enter an appropriate name for the Output Feature Class , and click ' OK '. 6. In the Contents pane, right click on the feature layer you just created and click on ' Attribute Table .' 7. The attribute table should contain the following columns: lat, lon, depth, time, and platform_name . You are now ready to generate shapefiles of CSB data to share with participants. ArcGIS: Generating CSB data shapefiles This section provides instructions on how to export shapefiles of CSB data for specific participants, or for upload to an ArcGIS Online CSB Data Portal. If your shapefile contains data from multiple participants, you will need to apply a selection query to create individual layers for each participant's data. While the CSB map layer is selected, navigate to the Selection section under the Map tab and click on ' Select By Attributes .' Set the Selection Type to New selection and set the clauses to: " Where platform_name is equal to [ participant name ]." If a participant has data from more than one vessel, add additional clauses using the ' Or ' operator until all data for that participant are included in the selection. Click ' OK ' to apply your selection.  Right click on the CSB map layer and under the Selection dropdown choose ' Make Layer From Selected Features .' Give the new layer an appropriate name to identify the participant and date range of the data. You will need to convert this new feature class layer into a shapefile that can be sent to the participant. In the Geoprocessing pane, search for the ' Feature Class to Shapefile ' tool. Add the layer you want to convert to Input Features and select an Output Folder . Click ' Run .' You now have a shapefile of tide-corrected CSB data that can be zipped and sent to an individual participant or uploaded to an ArcGIS Online portal.  QGIS: Editing tide-corrected CSB data For Trusted Nodes that prefer to use free and open-source GIS software, the following section describes how to edit tide-corrected CSB data using QGIS, and how to export shapefiles of data that can be shared with program participants. Launch QGIS and select New under the Project tab to create a new project. Click the Save icon to name the project and save it in an appropriate location. Under the  Layer tab, click on Add Layer and select Add Vector Layer from the drop-down menu. In the Source / Vector Dataset box, navigate to the .gpkg of tide-corrected data that was output by Pydro. Click Add to import the data to the project. Right click  on the vector layer and select Open Attribute Table . The table should contain the columns : lat, lon, time, depth, and platform_name. If your shapefile contains data from multiple participants, you will need to apply a selection query to create individual layers for each participant's data. Select the CSB vector layer and click on the  Select Features by Value icon. To select all data points from an individual participant, enter an appropriate term into the platform_name box, and set the filter to Contains . Click on Select Features to apply the selection. A banner at the bottom left of the window should read out how many points were included in the selection. Right click  on the vector layer and under the Export drop-down menu, select Save Feature As . Select ESRI Shapefile as the Format and add an appropriate file name and location. Make sure to check the box to Save only selected features. Click OK to save. You now have a shapefile of tide-corrected CSB data that can be zipped and sent to an individual participant. QGIS: Data visualization Motivation Some crowdsourced bathymetry participants may have a clear idea of how they intend to use the depth soundings they've collected and what data format best suits that purpose. Others may benefit from a simple tutorial on how to visualize their data using a free, open-source software ( QGIS ). This will allow the Trusted Node to return data to participants in the .shp file format and ensure that participants can easily visualize their contributions to the program. This option may be particularly valuable to newly established Trusted Nodes that have not yet constructed an ArcGIS Hub site (e.g.,  Crowd the Bay ) or similar platform for public CSB data access. Tutorial You will first need to download QGIS . (If needed, installation instructions are available here ). Launch QGIS. Click on the  Project  tab and select ' New ' to open a blank map. Make sure to save your project with an appropriate name. Click on the Plugins tab and select ' Manage and Install Plugins .' Search for and install the QuickMapServices plugin. Under the Web tab, select QuickMapServices and click on ' Search QMS .' Search for ESRI Satellite (ArcGIS/World_Imagery) and click ' Add .' Under the View tab, click Panels and turn on the ' Layers ' option. In the Layers panel, check the box for ESRI Satellite (ArcGIS/World_Imagery) to turn it on. Under the Layer tab, click Add Laye r and select ' Add Vector Layer .' In the Source box, enter the path to the tide-corrected CSB .shp file you wish to visualize, and click ' Add .' In the Layers panel, right click on the layer you just added, and select ' Properties .' In the Symbology window, set the symbol type to Graduated , Value to depth , Color ramp to YlGnBu (and inverted), and set the classification Mode , Values , and Legend to best suit the range and distribution of your dataset. Click ' Apply ' to confirm changes. Click on the Symbol icon to adjust symbol settings. Set the Size to 1 and the Stroke color to transparent . Click ' OK ' to apply changes. You should now have a well-symbolized, tide-corrected CSB data layer to work with. If you're feeling tech-savvy and interested in overlaying CSB data onto a NOAA Electronic Navigational Chart for comparison, you can locate and download the appropriate charts here and follow these instructions to display them in QGIS. Use Cases and Effective Communication NOAA data scrape In 2025, NOAA Hydrographic Systems and Technology Branch, in collaboration with University of New Hampshire Center for Coastal and Ocean Mapping, and the IHO Data Center for Digital Bathymetry, began investigating operationalization of CSB data for safety of navigation applications. Early research indicates that CSB data, when corrected for vessel sensor offsets and tidal heights, can be used to inform chart updates and danger to navigation (DTON) reports. A research project is underway to automate this processing of CSB data to provide a map service of corrected CSB data for use in various applications. Tampa Bay community mapping efforts NOAA’s hydrographic health model is a risk-based framework that evaluates the safety of navigation by combining factors such as ship traffic, records of groundings, the quality and age of existing data, and the rate of seafloor change. The model produces a “hydrographic health score,” which highlights areas where re-surveying may be most critical. In Tampa Bay, Florida, CSB data collected by the University of South Florida Center for Ocean Mapping and Innovative Technologies' (COMIT) ‘Crowd the Bay’ program revealed southward shoal movement in Bunces Pass. This shoal migration was not reflected on existing NOAA charts but was confirmed in NOAA’s BlueTopo product. Bunces Pass is a heavily transited tidal inlet that experiences frequent sediment exchange and shoaling  – creating potential hazard for vessels and underscoring the importance of updated depth information on navigational charts. By contributing timely depth data, CSB could help NOAA’s hydrographic health model capture the likelihood of incidents and identify areas that require updated surveys or ENC revisions, ultimately improving efficiency and navigational safety. Templates Example recruitment email for stakeholder meeting For inaugural stakeholder meeting: [Fill in highlighted areas with details appropriate to your organization] Hello,   I’m reaching out to you on behalf of [Your organization name / website link] . We are building a pilot crowdsourced bathymetry (CSB) program focused in and around [Your CSB region] . If you are unfamiliar with CSB, in short it is the collection of seafloor depth from vessels engaged in their routine operations using simple data logger technology.   CSB is a global citizen science initiative with the potential to generate transformative datasets with community benefits such as:    Rapid change detection of seafloor features after storm events   More frequent updates to nautical charts    Improved data for modeling coastal flooding and storm surge estimates   [Optional / if you have a website]   Our website [Attach your website link] has more information about CSB and  [Your CSB program name] . Part of building our program includes working with relevant community members while we’re on the ground floor.    On [Meeting date]  we are planning a day-long meeting at [Meeting location]   with a small group ( [Number of participants] ) of invitees from private businesses, government agencies, and nonprofit organizations to formally launch [Your CSB program name] .    We have identified your group as a potential participant or stakeholder whose input would be invaluable to the program.    More information will follow but if you or someone from your organization is interested and willing to attend, we ask that you RSVP via this form [Attach link to a Google form / preferred survey format] or respond to this email by [Date] .   If you have any questions, please don’t hesitate to contact [POC name and email address]   We appreciate your consideration.   Regards,   [Your name, Organization] Example follow-up email:   We’re looking forward to hosting you all on [Meeting date] for our first stakeholder meeting as we work to build a crowdsourced bathymetry program in [Your CSB region] .   To reiterate the details, the meeting will be at the [Meeting location] at [Meeting time] . [Optional / if providing refreshments] We will provide lunch and refreshments so please let me know if you have any dietary restrictions as we are happy to accommodate. I’ve created Outlook (attached) and   Google   events to easily add the meeting to your calendars.   You are not expected to do anything to prepare for this meeting aside from perusing our website [Attach your website link]   if time allows. It may be helpful to bring a notebook with you for notes, but no computer or other materials should be needed.   I’ll be in contact as we get closer to the meeting date with final details about how to find parking, the exact meeting location, as well as a brief agenda with an overview of the day.   For second stakeholder meeting: [Fill in highlighted areas with details appropriate to your organization] Dear [Recipient's name] , [Your organization] is working to initiate a crowdsourced bathymetry (CSB) program in [Your CSB region] .   I immediately thought of you and [Recipient's organization]   to be a part of this initiative. I’d like to invite you to a half-day stakeholder meeting on [Meeting date] to learn about and discuss our CSB program.   In short, CSB is a global citizen science initiative that uses simple data logger technology to record depth information from boat echosounders.   We have been building our own regional CSB program, called   [Your CSB program name / website link] , as part of [List funding agency / initiative, as applicable] for the last [Duration of time / age of program] . We think you/your organization could benefit from, and potentially participate in, this movement to more frequently collect bathymetry (seafloor depth) data in and around [Your CSB region ]. I am adding a couple more links that will provide some information prior to the meeting: A short video by CHS   on what installing a logger means, and our Equipment Check webpage [ Add link to your own webpage, if applicable] . The focus of this meeting will be to recap an inaugural stakeholder meeting we had in [1st meeting date] , while delving deeper into the practicalities of sustaining a CSB program in [Your CSB region] . We’ll also spend time focusing on the applications of CSB data and how [Your organization] can best serve that information to potential stakeholders, such as yourself.   Our meeting will be [Meeting time] at the [Meeting location] . More details will follow, but we ask that if you’re interested to please  RSVP via this form   [Attach link to a Google form / preferred survey format] as soon as possible or respond to this email by [Date] at the latest. If you have any questions or would like to be removed from our communications regarding CSB, please let me know.   Regards, [Your Name, Organization] Example follow-up email:   We’re looking forward to hosting you all [Meeting date] for our second stakeholder meeting as we work to build a crowdsourced bathymetry program in [Your CSB region] .   To reiterate the details, the meeting will be at the [Meeting location] at [Meeting time] . [Optional / if providing refreshments] We will provide lunch and refreshments so please let me know if you have any dietary restrictions as we are happy to accommodate. I’ve created Outlook (attached) and   Google   events to easily add the meeting to your calendars.   You are not expected to do anything to prepare for this meeting aside from perusing our website [Attach your website link]   if time allows. It may be helpful to bring a notebook with you for notes, but no computer or other materials should be needed.   I’ll be in contact as we get closer to the meeting date with final details about how to find parking, the exact meeting location, as well as a brief agenda with an overview of the day.   Example stakeholder meeting agenda For inaugural stakeholder meeting: Crowdsourced B athymetry (CSB) in Tampa Bay /Florida     Develop ing a Stakeholder-Driven Process    USF College of Marine Science, MSL Conference Room   140 7 th Ave South, St. Petersburg, FL 33713   21 September 2023, 9:00 a.m. – 3:00 p.m.   Goal:    Engage local stakeholders in the process of creating a crowdsourced bathymetry (CSB) network in Tampa Bay.   Objectives:   Raise awareness about the Center for Ocean Mapping and Innovative Technologies (COMIT) crowdsourced bathymetry Tampa Bay pilot program   Acquire input from local stakeholders about the value of crowdsourced bathymetry , participation barriers/ concerns   D irect input on stakeholder’s ideas and views on tools, outreach materials, and incentivization measures   Deliverables :   Pre-and post-meeting baseline knowledge and opinion survey about CSB in Tampa Bay   Evaluation of existing products and materials as well as ideas for future development   Compilation document of lessons learned and main takeaways     Attendees : U.S. Coast Guard, United States Geological Survey (USGS), Tampa Bay Ports, Freedom Boat Club,  Seabulk Towing, SeaKeepers Society, US Army Corps of Engineers, University of New Hampshire /Center for Coastal and Ocean Mapping , Florida Fish and Wildlife Commission, Sea Tow Tampa Bay     Agenda :   0830 – 0900 Arrival (Parking passes provided) , i nformal coffee /tea social     0900 – 09 15 Welcome   09 15 – 0930 Pre-Meeting Survey   09 30 – 10 15 Seafloor Mapping Overview   1015 – 1025 Bio Break   1025 – 1130 Stakeholder Input Session 1: Awareness and u se of b athymetry information   1130 – 1145 Lunch Break   1145 – 1215 Optional Tour (or continued lunch break)   1215 – 1315 Stakeholder Input Session 2: Acquiring CSB information   1315 – 1325 Bio Break   1325 – 1430 Stakeholder Input Session 3: Using CSB Information   1430 – 1450 Closing   1450 – 1500 Post-Meeting Survey     Meeting Location & Parking Info:   If you would like a parking pass, we will have some available, but our lot also accepts the Parkmobile app used throughout downtown St. Pete. When you arrive, try to park in a guest space and call/text Name (xxx-xxx-xxxx) to get a parking pass and avoid any parking violation tickets. You can park in any green spots (see map below; green outlines).   The meeting will be in our conference room at the Marine Science Laboratory Building (MSL) at the College of Marine Science on the University of South Florida, St. Petersburg campus, the conference room is near the main entrance (see map below).   For second stakeholder meeting: Crowdsourced B athymetry (CSB) in Tampa Bay + Beyond     Develop ing a Stakeholder-Driven Process   Spring 2024 Meeting   The Suites at Madison, 412 E Madison St 12 th Floor, Tampa FL 33602   19 February 2024 , 2:00pm – 5:00pm   Goal:    Broaden engagement with local stakeholders and possible participants for a crowdsourced bathymetry (CSB) network in Tampa Bay.   Distribute data loggers *** to interested participants (limited number available)   Objectives:   Briefly review highlights from September 2023 stakeholder meeting. Acquire input from local stakeholders and potential participants about derived data products from crowdsourced bathymetry and the practicalities of sustaining longer term participation in a CSB program.     Deliverables :   Report covering the September 2023 and February 2024 meetings     Agenda :   13 45 – 1400 Arrival (Coffee and snacks will be provided)      1400 – 14 15 Meeting Start/ Welcome   1415 – 1445 Recap of previous meeting’s highlights    1445 – 1530 Discussion Session 1: Practical implementation of CSB in Tampa Bay   15 30 – 1 540 Bio Break   1540 – 1630 Discussion Session 2: Products derived from CSB data for stakeholders   1 6 30 – 1 6 50 Closing   1 650 – 1 700 Data Logger Distribution     Meeting Location & Parking Info:   We’ll be meeting in the Training Room at the Suites at Madison. This is group space for rent so please be mindful there may be other meetings going on and follow the signs to find the correct room.    There is paid parking under the building as well as street parking throughout downtown Tampa.    ***Please try to let us know ahead of the meeting if you/your group is or might be interested in installing a logger ***   Contact Info (call/text if needed):   Name: (xxx-xxx-xxxx)    Example stakeholder input session prompts For inaugural stakeholder meeting: Crowdsourced B athymetry (CSB) in Tampa Bay/Florida    Developing a Stakeholder-Driven Process    Stakeholder Input Session #1: Awareness and use of bathymetric information   Do you currently use seafloor mapping information? If so, what are your sources of information?   Do current seafloor mapping products meet your needs?    Can you provide an example of personal and/or professional benefit that might result from participating in CSB data collection and/or using information generated from CSB activities?     Stakeholder Input Session # 2 : Acquiring CSB I nformation   What features would you want to see on a data logging system, from set-up to use?    Do you have current capabilities that would allow you to participate in CSB with minimal adjustments to your activities/operations?   What are the major internal and external barriers to CSB participation (e.g., logistics , resources to purchase loggers, instrument and data sharing knowledge and use, long-term leadership of CSB program; see pipeline reference)   Is remaining an anonymous data provider important to you/your organization?      Stakeholder Input Session # 3 : Sustaining CSB D ata C ollection   What types of incentivization could encourage participation in CSB data collection?     How should or could CSB data be used to ensure we’re not “collecting data for data’s sake” ?      What assurances would you need to confidently use CSB data ? (e.g., concern about liability for data you provide and/or accuracy of data you use)     For second stakeholder meeting: Crowdsourced  B athymetry (CSB) in Tampa Bay/Florida    Developing a Stakeholder-Driven Process    Stakeholder Input Session #1: Practical Implementation of CSB in Tampa Bay What is the best way to implement CSB? What might be some possible challenges? More importantly, solutions?    Based on what’s been discussed about participant expectations (e.g. physically installing loggers, downloading and sending data), are any of these concerning to participants? Alternatives and solutions?   What issues do you see preventing your participation? Can these barriers be overcome or are they non-starters?   What types of incentivization could encourage, and more importantly SUSTAIN participation in CSB data collection?     Stakeholder Input Session # 2 : Products Derived from CSB Data   A (near) real-time change map may be a “holy grail” product, but this will require significant R&D. What are other products of interest and/or use? What file types/formats? What does “timely” data mean to you?   For the maps that you may use currently for maritime navigation, research, management, etc., what’s missing and does it appear that CSB can fill in those gaps?   What assurances would you need to confidently use CSB data? (e.g., error/accuracy, liability)   Example stakeholder meeting survey Provide the following questions to stakeholders as a pre- and post-meeting survey Q1 Which of the following aligns most closely with the group you are representing at this meeting? Industry Private Business Academia State Government Federal Government NGO Non-Profit Other (please specify) Q2 How many vessels (or vessel owners) do you or your organization manage or interact with on a regular basis? 0 1-5 6-10 10-25 >25 Q3 Do you or your organization use bathymetry data (e.g. seafloor depth), such as navigational charts, on a regular basis? Yes No Maybe/Unsure Q4 Does your organization participate in any other crowd sourced data collection or citizen science initiatives? Yes No Maybe/Unsure Q5 Did you review any of the outreach materials about crowdsourced bathymetry prior to the meeting? Yes No Q6 Do you think seafloor depth (bathymetric) data are critical to coastal management? Yes No Maybe Q7, 8, 9 How important do you think crowdsourced bathymetry is to: Q10 Are you aware of other relevant applications of crowdsourced bathymetry not listed in the previous question? If so, please briefly list below; If not, write N/A. Q11 Rank which outreach items you would most prefer to use for learning more about crowdsourced bathymetry programs ______ A website with brief, concise information ______ Short (2-4 min) videos with concise information ______ Written documentation (e.g. standard operating procedures, program outlines) ______ Longer (5-10 min) videos with more comprehensive information ______ 1-page flyers about different topics Q12  Are there other outreach materials not listed above you would prefer? Q13 If you were a participant in a CSB program, would you be willing to share your data with the public? Yes No Maybe/Conditional Q14 If you were to participate in a CSB program, would you be willing to install a logger yourself aboard your vessel(s) which would require opening your electronics console(s)? Yes No Maybe Q15 If no, what is/are your reason(s) or concern(s)? Check all that apply. Too much of a time commitment  Don't have enough technical expertise Concerned about breaking or damaging other electronics Not my responsibility Other (please elaborate) Q16 If a certified marine technician was available to complete the installation, would you be amenable to installing a logger? Yes No Maybe Q17 If you were a participant in a crowdsourced bathymetry program, how many hours per month would you be willing to devote to the program such as copying and sending data, reading updates about the program, and attending occasional stakeholder meetings?  0 / not interested 1-2 2-5 Q18, 19, 20, 21 How important do you think the following items are for sustaining and encouraging long-term participation in crowdsourced bathymetry? Example recruitment email for Crowd the Bay participants [ Fill in highlighted texts with appropriate information] Dear [Recipient's name] , T he Center for Ocean Mapping and Innovative Technologies (COMIT) has been developing a crowdsourced bathymetry (CSB) program in Tampa Bay, and I thought you and [Recipient's organization] would be a great fit to participate in this initiative. In short, CSB is a global citizen science initiative that uses simple data logger technology to record depth information from boat echosounders.   We have been building our own regional CSB program, called   Crowd the Bay , as part of our NOAA Office of Coast Survey-funded Center for the last two years. We think you and your organization could benefit from, and potentially participate in, this movement to more frequently collect bathymetry (seafloor depth) data in and around Tampa Bay. I am adding a couple more links that will provide some information: A short video by CHS   on what installing a logger means, and our Equipment Check webpage. I would be happy to speak with you and to dive deeper into COMIT's Crowd the Bay initiative, what it means to be a part of this CSB initiative, the applications of CSB data , and how COMIT can best provide that information to potential stakeholders such as yourself.  Data can be provided to you in a variety of formats to best fit your needs. However, shapefiles tend to be the best way to visualize your data. If you are interested, we have instructions for visualizing CSB data from shapefiles with free QGIS software here . If you have any questions and would like to setup a time to talk, or you would like to be removed from our communications regarding CSB, please let me know.   Regards, Example memorandum of understanding The University of South Florida Board of Trustees’ (“ USF ”) Center for Ocean Mapping and Innovative Technologies (“ COMIT ”) is a Trusted Node in the International Hydrographic Organization’s (“ IHO ”) Data Centre for Digital Bathymetry ’s (“ DCDB ”) project entitled C rowdsourced B athymetry D ata C ollection (“ Project ”) .    In consideration for the opportunity to participate in the Project , I , the undersigned, therefore agree as follows:   I hereby consent to the participation of the one or more vessels identified below in the Project as organized by COMIT .   I hereby acknowledge the following:   my execution of this acknowledgement and release is an inducement affecting USF’s decision to a pprove my participation in the Project ;   USF is Trusted Node approved by IHO to systematically receive crowdsourced bathymetry data (“ CSB ”) collected by vessels or other platforms and deliver them to IHO’s DCDB.   USF will provide a data logger for the participant’s one or more vessel s , t he specific model will depend on the availability of USF ’s inventory and the needs of each vessel , and any data logger installed on a vessel is, and will remain, exclusively the property of USF . Participants must have NMEA networks installed on a vessel prior to a data logger being installed.   USF prefers participants install their own data loggers and will provide resources and support to make the process quick and efficient. USF will install data loggers if participant sends a written request to COMIT’s Project Leader . However, USF will not be liable for any issues with a vessel because of USF ’s installation of a data logger .   each data logger use s the vessel’s 12/24DC and NMEA network to log bathymetry data, date, time, and vessel motion as applicable.   I, or an individual designated by me, will liaise with COMIT’s points of contact, Sophia Chernoch (xxx @usf.edu ) and Kristin Erickson (xxx @usf.edu ), every one to three months (based on frequency of data collection) to enable a representative of COMIT to board the participant’s one or more vessels to download data from the data logger.   If a Wi-Fi or cellular-enabled logger is installed , the data will be uploaded when in range of the data transfer capability .   data collected , including bathymetry data, date, time, and vessel motion , will be edited of any noise and formatted for submission to the IHO’s DCDB , the public repository for CSB data . Each vessel name will be included in the data submitted to the DCDB unless the participant send’s a written request prior to the installation of the data logger to COMIT’s Project Leader stating the participant wants to be an anonymous contributor.   I shall permit COMIT to remove any data logger from a vessel within a reasonably time if ( i ) COMIT requests it be removed from a vessel; (ii) I withdraw my participation in the Project ; or (iii) the Project ends .   I shall abide by all laws, regulations, ordinances, policies, and rules applicable to my participation in the Project .   I hereby waive all claims and causes of action that I may have, now and in the future, against USF and its trustees, officers, employees, agents, and other representatives arising out of my participation in the Project .   I hereby indemnify USF and its trustees, officers, employees, agents, and other representatives against any actual or potential losses or liabilities, including reasonable litigation costs, arising out of any of my negligent acts or omissions and those of my employees, agents, and other representatives , any failure to uphold my obligations as specified in this acknowledgement and release , or any misrepresentation by me in a statement of fact made in this acknowledgement and release .    I intend this acknowledgement and release to be as broad and inclusive as is permitted by Florida law and if any portion is held enforceable, I would want the court to interpret it as follows: ( i ) modify that portion to the minimum extent necessary to make it enforceable or, if that modification is not permitted by law, to disregard that portion ; (ii) hold that the rest of this acknowledgement and release remains in effect as written ; and (iii) hol d that any such portion remains as written in any circumstances other than those in which the portion is held to be unenforceable.       I hereby state that I am either or both the owner of the one or more vessel s named below and am an authorized representative of the owner of said vessels and have authority to execute this acknowledgement and release .   I am signing this acknowledgement and release voluntarily with full knowledge of its contents and significance.     ___________________________________________ _____________________          ______ / ______ / ______   PRINT NAME OF VESSEL OWNER                                                       DATE   ___________________________________________ _____________________          ______________________ _____________________   VESSEL OWNER/ AUTHORIZED REP . SIGNATURE          DATE                 TELEPHONE                   EMAIL     ________________________________________________________________          ______________________     NAME OF VESSEL                                                                                 VESSEL HIN   Example vessel offsets worksheets Example letter of agreement and metadata form Used by the International Seakeepers Society: linked here . Example data transfer guide Example data retrieval guide Example logger menu     Example internal SOP for a CSB company/program DISCOVERY Yacht Onboarding Process for Citizen Science & Seabed 2030  Version 1. Digital Introduction  Step 1: Application Submission  - The DISCOVERY Yacht (DY) submits their application to participate.  Step 2: Initial Contact by Programming Team  - The regional Programming Team reaches out to the vessel to discuss interests. - This can be done via email or an introductory call.  Step 3: Interest in Citizen Science (CS)  - If the vessel expresses interest in Citizen Science, connect them with the Citizen Science Manager or the propriate chapter lead.  Step 4: Interest in Seabed 2030  - If the vessel is interested in contributing to Seabed 2030, consider whether the vessel is equipped with the correct tools. Depth Transducer  GNSS/GPS Chartplotter  NMEA2000 or NMEA0183 backbone CONNECTING THE PREVIOUS TWO  - Ask the vessel to complete a Seabed 2030 Letter of Agreement (this can be a formal letter or a Google Form, as appropriate) and send the Installation Guide to the vessel.  - Proceed with delivering (by mail or hand) Data Logger (YDVR-04R for Raymarine, YDVR-04N for others, or NEMO with adapter)  SD card (no more than 32GB), T-connector Drop Cable If you do not have any available, please request these from Rosemarie@SeaKeepers.org Step 5: Logger Installation and Data Offloading  - Once the logger is shipped, connect the vessel with the Data Scientist for guidance on data offloading specifics. In the introductory email between the vessel and Data Scientist, attach the Seabed2030 agreement if it was done manually (i.e., not via the Google Form). The data scientist will create a personalized google folder for the vessel and walk them through the data offload process. Version 2. In-Person Introduction  Step 1: Initial Contact by Programming Team - Connect with the DISCOVERY Vessel in person at an event. Bring to their attention potential for Scientist Led and Citizen Science opportunities.  Step 2: Application Submission  - The DISCOVERY Yacht (DY) submits their application to participate. Step 3: Interest in Seabed 2030  - If the vessel is interested in contributing to Seabed 2030, consider whether the vessel is equipped with the correct tools. Depth Transducer  GNSS/GPS Chartplotter  NMEA2000 or NMEA0183 backbone CONNECTING THE PREVIOUS TWO  - Ask the vessel to complete a Seabed 2030 Letter of Agreement (This can be a formal letter or a Google Form, as appropriate.), and send the Installation Guide to the vessel.  - Proceed with delivering (by mail or hand) Data Logger (YDVR-04R for Raymarine, YDVR-04N for others, or NEMO with adapter)  SD card (no more than 32GB), T-connector Drop Cable. If you do not have any available, please request these from Rosemarie@SeaKeepers.org Step 5: Logger Installation and Data Offloading  -Connect vessel with pertinent staff for continued regional engagement in either additional CS or SLE programs. This can be done via call or email.  Step 6: Logger Installation and Data Offloading  - Once the logger is shipped, connect the vessel with the Data Scientist for guidance on data offloading specifics. In the introductory email between the vessel and Data Scientist, attach the Seabed2030 agreement if it was done manually (i.e., not via the Google Form). The data scientist will create a personalized google folder for the vessel and walk them through the data offload process.