DCDB contact for inquiries about becoming a Trusted Node:
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](https://iho.int/en/csbwg) 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/templates "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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/templates "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](https://crowdthebay-usfmarsci.hub.arcgis.com/).". 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](https://main.d2vtqxl26xb7vf.amplifyapp.com/providers/). Another publicly available dashboard includes the [FARSOUNDER Dashboard](https://mycsb.farsounder.com/), 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/data-extraction-and-processing "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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/data-visualization "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](https://crowdthebay-usfmarsci.hub.arcgis.com/pages/8d8e20c6fd454a29a7944dc15be35368) - [Link to the video produced by the Canadian Hydrographic Service](https://www.youtube.com/watch?v=8yW3tHG_Cvc) (CHS) about what installing a logger means - Information on use cases (see the [Use Cases](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/use-cases-and-effective-communication "Use Cases and Effective Communication") section for examples) - Links to the [DCDB](https://www.ncei.noaa.gov/iho-data-centre-digital-bathymetry), [Seabed2030](https://seabed2030.org/), or [IHO](https://iho.int/en/csbwg) 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 loggerExamples of each of these can be found in the [Templates](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/templates "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](https://github.com/CCOMJHC/WIBL) and [Open VBI](https://github.com/CCOMJHC/OpenVBI) 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](https://bitbucket.org/ccomjhc/wibl/wiki/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)[https://bitbucket.org/ccomjhc/wibl/wiki/Home](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.](https://www.orangeforcemarine.com/crowdsourced-bathymetry), 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 ](https://actisense.com/products/nmea-2000-gateway-ngw-1/?srsltid=AfmBOoohW6piuekOsbtRu3BURipqMU7RAPBwZRLG8JfUQpqwwp-awVlx)or [NGX-1](https://actisense.com/products/nmea-2000-gateway-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](https://docs.google.com/spreadsheets/d/17hp9U1nOp_xTb_pHWBl48W002VBrBlpZ/edit?gid=1807714141#gid=1807714141). 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/installation-kit "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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/wibl-and-ydvr-data-processing "WIBL and YDVR data processing"). Instructions for updating the firmware and flashing the WIBLs can be found in the [WIBL Installation Guide](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/installation-guide-nemo30wibl "Installation guide: NEMO30/WIBL") section and on[ CCOM's WIBL GitHub page](https://github.com/CCOMJHC/WIBL). 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/wibl-and-ydvr-data-processing "WIBL and YDVR data processing") for instructions). Prior to the installation date, direct the participant to the[ Equipment Check](https://crowdthebay-usfmarsci.hub.arcgis.com/pages/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](https://drive.google.com/file/d/1Zmbg6OCpyknaXo4mNv05RbuuEzkRgcPt/view?usp=sharing) 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](https://www.orangeforcemarine.com/contact) 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[ ](https://drive.google.com/file/d/1PFSkoR7dxEbR8IYzMDXWIndG62kcQlK4/view?usp=drive_link)[Installation and Operating Instructions](https://www.orangeforcemarine.com/s/Mussel-Kit-Installation-Operating-Instructions-Generation-2-January-2024.pdf) 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](https://www.orangeforcemarine.com/contact) 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](https://www.orangeforcemarine.com/s/Mussel-Kit-Installation-Operating-Instructions-Generation-2-January-2024.pdf)), which can be completed manually on the printed sheets and submitted electronically[ here](https://docs.google.com/forms/d/e/1FAIpQLSdsOATPpHmrYqy0GpDm-pQeFsKnTIMXlF5pHu63Xm1Rfv4gqg/viewform). When the installation is complete, [contact Orange Force Marine](https://www.orangeforcemarine.com/contact) to confirm that the logger is online and working properly. # Installation guide: YDVR 1. 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. 2. Ensure proper termination: the two ends of the backbone must each have one terminator. Any unused T-connector ports should be capped. 3. Secure the logger in a dry, protected location away from bilge water or spray. 4. Confirm network power (10.5–16 V) is present before connecting. 5. Lock the connector collar to maintain water resistance. 6. Insert the MicroSD card into the logger until it clicks into place. 7. Connect the vessel’s NMEA 2000 power or turn the system “on." 8. Observe the **LED indicator** at the end of the logger: 1. - **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) 9. When powering down, a **short red flash** confirms safe file closure. 10. Data are stored automatically in folders named YDVR#### on the MicroSD card. 11. To retrieve data, remove the card, copy files to a computer, and process with YDVR Converter software (available for download [here](https://www.yachtd.com/downloads/YDVRCONV.zip)). # Installation guide: NEMO30/WIBL 1. Confirm that the NMEA network starts when the vessel is powered on. 2. Remove the backplate/cover of the logger. 3. Check to make sure the logger has an SD card for data storage and that it’s clicked "in".  (disengaged)  (engaged) 4. Place 1-3 desiccant packs into the logger. It’s okay for the packs to rest on the circuit board. 5. 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\] 6. Locate the NMEA network hub. If there isn’t an empty port, swap in a T-splitter if needed. 7. Determine the best placement for the logger within 1- or 0.5-meters (depending on drop cable length) of the port. 8. Before placing the Velcro to mount the logger, ensure no pinching, blocking, or other clearance issues will happen when closing the console. 9. Use 2 strips of Velcro at the mounting site and on the backplate of the logger, alternating rough and smooth sides.  10. Connect the logger to the NMEA network with the drop cable. Make sure the locking threads are tightened on both sides. 11. Plan to let the WIBL run after installation, pull the SD card, and check for proper function using the appropriate python scripts. 12. 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** 1. Start Visual Studio Basic with PlatformIO. 2. Build the library (check mark at bottom of PlatformIO). 3. Open WIBL box to access board. 4. Connect USB to serial pin. 5. 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. 6. You should now be in PROG mode to download new firmware and edit metadata – no lights will be on the board. 7. If updating firmware, select Upload and allow program to run. 8. After completing the download and/or metadata edits, touch the jumper to the other “RESET” header pin briefly again to reboot the logger. 9. Remove the jumper from the “RESET” header pins. 10. Open a new terminal window.  11. Connect the WIBL to Wi-Fi. 12. 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 13. Edit config/metadata as needed. 14. 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](https://iho.int/uploads/user/pubs/bathy/B_12_CSB-Guidance_Document-Edition_3.0.0_Final.pdf) 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/example-data-retrieval-guide "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](https://www.python.org/downloads/). Choose *Customize Installation*. Under Advanced Options check the box "Add Python to Environmental Variables." \[More detailed instructions are provided[ here](https://www.codewithharry.com/blogpost/the-term-pip-is-not-recognized-error/)\]    - **Windows PowerShell 7**: download[ here](https://www.thomasmaurer.ch/2019/07/how-to-install-and-update-powershell-7/) - **Miniconda**: download[ here](https://www.anaconda.com/download/success) - **Visual Studio Code**: download[ here](https://code.visualstudio.com/Download) - **WIBL GitHub Repository**: [Linked here](https://github.com/CCOMJHC/WIBL). 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: 1. Copy the example files to a new folder in Documents (or Desktop) - don't work within the WIBL repository. 2. Open the copied files in **Visual Studio Code** to edit. 3. 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**. 4. The configure-submission-test.json can be used to submit data to the test-API on the DCDB (does not officially submit data). 5. 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](https://iho.int/uploads/user/pubs/bathy/B_12_CSB-Guidance_Document-Edition_3.0.0_Final.pdf)
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]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 `Your CSB data are now downloaded and ready to have[ Pydro tidal corrections](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/pydro-tidal-corrections "Pydro tidal corrections") applied.
# Pydro tidal correctionsSupport 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: 1. You will need to download the **Pydro** software[ here.](https://svn.pydro.noaa.gov/Docs/html/Pydro/downloads.html) 2. Follow the [Data Extraction](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/nceidcdb-data-extraction "NCEI/DCDB data extraction") instructions to retrieve the data you want to process. 3. When you receive the email link from NCEI, download the data and save it in an appropriate location. 4. Open **Pydro**, navigate to the ‘**BETA/EXPERIMENTAL**’ section of the Applications pane, and select ‘**CSB Processing.’** **** 5. 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.  6. 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
7. 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/chapter/data-visualization "Data Visualization").
# 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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/qgis-data-visualization "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](https://cms-kb.marine.usf.edu/books/2026-crowdsourced-bathymetry-manual/page/arcgis-generating-csb-data-shapefiles "ArcGIS: Generating CSB data shapefiles") 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. 1. 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.  2. *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.  3. 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. 1. Launch QGIS and select **New** under the **Project** tab to create a new project.  2. Click the *Save* icon to name the project and save it in an appropriate location.  3. Under the **Layer** tab, click on **Add Layer** and select **Add Vector Layer** from the drop-down menu.  4. 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.  5. *Right click *on the vector layer and select **Open Attribute Table**.  6. 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.*** 7. 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.   8. A banner at the bottom left of the window should read out how many points were included in the selection.  9. *Right click* on the vector layer and under the **Export** drop-down menu, select **Save Feature As**.  10. 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](https://qgis.org/project/overview/)). 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](https://crowdthebay-usfmarsci.hub.arcgis.com/)) or similar platform for public CSB data access. ##### Tutorial 1. You will first need to [download QGIS](https://qgis.org/download/). (If needed, installation instructions are available [here](https://qgis.org/resources/installation-guide/)). 2. 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.  3. Click on the **Plugins** tab and select '**Manage and Install Plugins**.'  4. Search for and install the **QuickMapServices** plugin.  5. Under the **Web** tab, select **QuickMapServices** and click on '**Search QMS**.'  6. Search for **ESRI Satellite (ArcGIS/World\_Imagery)** and click '**Add**.'  7. Under the **View** tab, click **Panels** and turn on the '**Layers**' option.  8. In the **Layers** panel, check the box for **ESRI Satellite (ArcGIS/World\_Imagery)** to turn it on.  9. Under the **Layer** tab, click **Add Laye**r and select '**Add Vector Layer**.'  10. In the **Source** box, enter the path to the tide-corrected CSB .shp file you wish to visualize, and click '**Add**.'  11. In the **Layers** panel, right click on the layer you just added, and select '**Properties**.'  12. 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.   13. 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](https://charts.noaa.gov/InteractiveCatalog/nrnc.shtml?rnc=12402) and follow[ these instructions](https://www.sigterritoires.fr/index.php/en/displaying-s57-nautical-charts-in-qgis-3-x/) 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: