Bio-optical Sensors Underway Data
On this page you will find information on the requirements for submitting, archiving and publishing Bio-optical Sensors Underway Data, as well as examples of datasets.
Please note
Standard operating procedures (SOPs) for the curation and publication of Underway Data are currently being revised within the DAM Underway Research Data Project to ensure fulfilling the FAIR data principles with every Underway data publication. Therefore, this page will be updated accordingly.
DAM Underway Research Data Project background
Underway Data from different devices
During DAM pilot phase, workflows for data curation, archiving and publication at PANGAEA are being revised. Besides Bio-optical Sensors, 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 a Bio-optical Sensors Underway Data
Example of data set prior to DAM Underway project: https://doi.pangaea.de/10.1594/PANGAEA.912014 (Chlorophyll, tot = Chlorophyll a)
Example of data set belonging to DAM Underway project, which is under revision: https://doi.pangaea.de/10.1594/PANGAEA.942197
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 | Title of data set
The title should ideally reflect what has been measured, observed, or calculated, when, where, and how. A maximum length of 200 characters is allowed. |
Continuous turbidity and chlorophyll measurements along [ship] cruise track [cruise label] |
| Author(s) | List of authors
Usually, the list of authors of Underway Data contains the chief scientist, the scientist responsible for the sampling device, and the principal investigator (PI), who is the contact person responsible for the data. |
[responsible scientist], [chief scientist] |
| Keywords | (default) | |
| Abstract/Describe your Data | For each dataset published in PANGAEA, the abstract provides a concise and method-oriented description of the observation or measurement, namely what, when, where, why and how the data was collected. The summary should consist of meaningful running text. The format of the dataset abstract is the same as that of paper abstracts. | |
| 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) |
References
Several references may be of importance for Underway Data.
- Cruise Report
The Cruise Report is sometimes 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 (see this example).
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. Templates for Data Processing Reports are currently being revised/created within DAM.
- 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.: SO248_8-7).
Device /Sensor
Information on the device used for measuring should also be provided, so it can be linked to the measured parameters.
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, . 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. Numbers, which are not available, 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 submission 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 | Comment |
|---|---|---|---|---|---|
| DATE/TIME | yyyy-mm-ddThh:mm:ss | 2020-12-13T10:08:00 | Geocode | ||
| LATITUDE | decimal | 54.654438 | Geocode | ||
| LONGITUDE | decimal | 7.737619 | Geocode | ||
| Depth, water | m | 6.50 | Geocode | ||
| Ship speed | kn | 5.9039 | |||
| Chlorophyll a | µg/l | 0.6296 | Fluorometer, WET Labs ECO FLNTU | MC1 | |
| Quality flag, chlorophyll a | # | 1 | MC1 | ||
| Turbidity (Nephelometric turbidity unit) | NTU | 3.2490 | Fluorometer, WET Labs ECO FLNTU | MC1 | |
| Quality flag, turbidity | # | 1 | MC1 | ||
| Chlorophyll a | µg/l | 0.6296 | Fluorometer, WET Labs ECO FLNTU | MC2 | |
| Quality flag, chlorophyll a | # | 1 | MC2 | ||
| Turbidity (Nephelometric turbidity unit) | NTU | 3.2490 | Fluorometer, WET Labs ECO FLNTU | MC2 | |
| Quality flag, turbidity | # | 1 | MC2 | ||
| Chlorophyll a | µg/l | 0.6296 | Fluorometer, WET Labs ECO FLNTU | combination of MC1 and MC2 | |
| Quality flag, chlorophyll a | # | 1 | combination of MC1 and MC2 | ||
| Turbidity (Nephelometric turbidity unit) | NTU | 3.2490 | Fluorometer, WET Labs ECO FLNTU | combination of MC1 and MC2 | |
| Quality flag, turbidity | # | 1 | combination of MC1 and MC2 |
Note: If Quality Flags are used, the flagging code needs to be explained and will be archived in the parameter comment. Turbidity parameter should be aligned with Ferrybox turbidity. Depth, water equals suction height, water supply (different for different vessels), needs to be aligned with TSG depth, water.