ADCP Underway Data
On this page you will find information on the requirements for submitting, archiving and publishing Acoustic Doppler Current Profiler (ADCP) Underway Data, as well as examples of datasets.
DAM Underway Research Data Project background
Underway Data from different devices
During the DAM pilot phase, workflows for data curation, archiving and publication at PANGAEA are being revised. Besides Acoustic Doppler Current Profiler (ADCP), other types of processed Underway Data from different devices are in the scope of the project:
Furthermore, historical and recent Bathymetry data and corresponding workflows are under revision in the framework of DAM.
Example of an Underway ADCP Data Publication
Kopte, Robert; Dierking, Jan; Schulz, Marco; Schütte, Florian (2024): Shipboard ADCP current measurements (75 kHz) during RV MARIA S. MERIAN cruise MSM126 [dataset]. PANGAEA,https://doi.pangaea.de/10.1594/PANGAEA.971773
Standardized Meta-Information of Underway Data
The following information needs to be included in any Underway Data submission at PANGAEA. To start a data submission at PANGAEA, go to https://www.pangaea.de/submit/. Further information on the ticket system used for communication and documentation during the processing of the data submission can be found in this wiki.
PANGAEA Data Submission Form Example
| Field Name | Explanation | Content Example |
|---|---|---|
| Title | Adapted, generalized #Dataset Title | ADCP current measurements (75 kHz) during [ship] cruise [cruise label] |
| Author(s) | #List of Authors | [responsible scientist], [chief scientist] |
| Summary | Name of the ticket that will be automatically generated; the institution should be included here | For example “Data submission 2020-03-24T07:32:46 ([submitter/responsible scientist], Alfred Wegener Institute Helmholtz Centre for Polar and Marine Research, Bremerhaven) |
| Keywords | (default) | |
| Abstract/Describe your Data | #Abstract; if the #Data Processing Report or the #Raw Data are already archived, the links may be placed here | Upper-ocean velocities along the cruise track of Maria S. Merian cruise MSM88/1 were continuously collected by a vessel-mounted Teledyne RD Instruments 75 kHz Ocean Surveyor ADCP. The transducer was located at 6 m below the water line. The instrument was operated in narrowband mode with 8 m bins and a blanking distance of 8 m, while 100 bins were recorded using a pulse of 1.45 seconds. The ship's velocity was calculated from position fixes obtained by the Global Positioning System (GPS). Heading, pitch and roll data from the ship's gyro platforms and the navigation data were used by the data acquistion software VmDas internally to convert ADCP velocities into earth coordinates. Accuracy of the ADCP velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. The ADCP data were processed using the Python-based DAM-ADCP software, adapted from the OSSI toolbox developed by GEOMAR Helmholtz-Zentrum für Ozeanforschung Kiel. The average interval was set to 60 seconds. Data post-processing included water track calibration of the misalignment angle (-47.1499° +/- 0.777°) and the amplitude (1.0106 +/- 0.0144) of the Ocean Surveyor signal. Velocity quality flagging is based on following threshold criteria: abs(UC) or abs(VC) > 2 m/s, rms(UC_z) or rms(VC_z) > 0.3. |
| License | The license specifies how the record can be used and modified after publication, and how it must be cited by re-users. The use of license CC-BY 4.0 is strongly recommended by PANGAEA and DAM, ensuring the re-usability of the Underway Data and the credit for the author(s) | CC-BY: Creative Commons Attribution 4.0 International (default) |
| Data used/published in the following article/manuscript | If the data is/will be published in a manuscript, please enter the details here | (default) |
| Projects and/or Awards/Grants | The project in which the data has been obtained may be named here | DAM: Underway Research Data |
| Upload | #Data Processing Report; #Data Table; #Further References | msm_88_1_vmadcp_75khz_01.txt; msm_88_1_vmadcp_75khz_01.nc |
List of Authors
Usually, the list of authors of Underway Data contains the scientist responsible for the sampling device, and the chief scientist. However, a final regulation on how to proceed with the list of authors in all Underway Data sets in the same way is still pending. The same goes for the PI, the contact person responsible for the data.
Dataset Title
The title of the data publication should be generalized and is defined by the specific [ship], [cruise] and [device] (see #PANGAEA Data Submission Form Example).
Abstract
For Underway Data, a generalized Abstract per device may be created that will be adapted to each dataset regarding [ship], [cruise] and certain peculiarities. For more information on what needs to be included in a PANGAEA data publication abstract, see this page.
References
Several reference may be of importance for Underway Data.
Cruise Report
The Cruise Report is usually already archived at the Technische Informationsbibliothek and will be linked to the dataset by a data editor (see this example).
Data Processing Report
The Data Processing Report contains information on processing and quality control procedures. It enables to reproduce the processed data from raw data. The preferred format for submission is pdf.
Example: Kopte, Robert (2020): ADCP current measurements (75 kHz) during Maria S. Merian cruise MSM88/1- Data Processing Report. Institute of Geosciences, Kiel University, https://store.pangaea.de/Publications/Kopte-etal_2020/msm_88_1_vmadcp_75khz_01_proc_report.pdf
Currently, the Data Processing Reports are being archived at PANGAEA (except for reports for data obtained during Polarstern and Heincke cruises); A long-term solution will include the assignment of a doi for each Data Processing Report.
Standard operating procedure report
A Standard operating procedure (SOP) report is linked, which is published at Zenodo. The choice of SOP depends on ship and device.
| Ship | Device | DOI |
|---|---|---|
| RV MARIA S.MERIAN | 75kHz ADCP | https://doi.org/10.5281/zenodo.7525284 |
| RV MARIA S.MERIAN | 38kHz ADCP | https://doi.org/10.5281/zenodo.7525257 |
| RV METEOR | 75kHz ADCP | https://doi.org/10.5281/zenodo.7525347 |
| RV METEOR | 38kHz ADCP | https://doi.org/10.5281/zenodo.7525334 |
| RV SONNE | 75kHz ADCP | https://doi.org/10.5281/zenodo.7525393 |
| RV SONNE | 38kHz ADCP | https://doi.org/10.5281/zenodo.7525399 |
Raw Data
If possible, the raw data should be linked to the processed dataset. This link may lead to an external source, but it may also be an PANGAEA-internal link.
Further References
These may, for example, include Salinity samples as .txt files, netcdf files, etc. They will be stored on one of PANGAEA's servers and can be accessed via a link in the reference section of the data publication.
Further information
Cruise Label
The [Cruise] Label given should always include [ship]number/leg (e.g.: MSM88/1).
Event label(s)
The Event Label(s) should be part of each data submission. Event labels equal the station labels and provide meta-information for the data. The Underway Event Label is being created onboard and should always be used when referring to Underway Data (current exception: CTD Data - several events needed). The format of Event Labels format consists of the cruise label and the station ending: [ship]number/leg_station (e.g.: MSM88/1_0_Underway-3).
Device /Sensor
Information on the device used for measuring should also be provided, so it can be linked to the measured parameters.
Keywords/Project
Use "DAM:Underway Research Project" as project and technical keyword "DAMUnderwayReserach".
Data Table
File name
A generalized file name should be used per device (see #PANGAEA Data Submission Form Example)
File Formats
Possible file formats include .txt, .tab, .csv, .xlsx . The encoding is preferably UTF-8.
Layout
Please do not include any header except column names. The decimal separator should be "." and the number of decimals should always reflect the measurement precision. Not available numbers are displayed as blanks in PANGAEA. They should be included as blanks, "NaN", "NA" or event "999.999" in the data table.
Parameters of the data table
This table gives an overview of how the parameter names and specifications will appear on the web and in the download file of the data. If possible, these names should be included in the submitted data table. Also the format and unit of data should be submitted as displayed here. The methods, as specified in the submitted meta-information, will be included in the data publication by the data editor.
| Parameter Name | Format | Unit | Example | Method |
|---|---|---|---|---|
| Event label | MSM88/1_0_Underway-3 | |||
| DATE/TIME | yyyy-mm-ddThh:mm:ss | 2019-11-29T05:01:00 | ||
| LATITUDE | decimal | 14.5006 | ||
| LONGITUDE | decimal | -28.2049 | ||
| Depth, water | m | 21.5 | ||
| Current velocity, east-west | cm/s | -14.46 | Vessel mounted Acoustic Doppler Current Profiler 75 kHz
Vessel mounted Acoustic Doppler Current Profiler 38 kHz | |
| Current velocity, north-south | cm/s | -6.62 | Vessel mounted Acoustic Doppler Current Profiler 75 kHz
Vessel mounted Acoustic Doppler Current Profiler 38 kHz | |
| Quality flag, current velocity | # | 1 | Seadatanet flag: Data quality control procedures | |
| Echo intensity, relative | cts | 195.2 | Vessel mounted Acoustic Doppler Current Profiler 75 kHz
Vessel mounted Acoustic Doppler Current Profiler 38 kHz | |
| Pings, averaged to a double ensemble value | # | 5 | Vessel mounted Acoustic Doppler Current Profiler 75 kHz
Vessel mounted Acoustic Doppler Current Profiler 38 kHz |
Note: If Quality Flags are used, the Flagging code needs to be explained and will be archived in the parameter comment.
This template may help for preparation of your data file: template