PANGAEA Wiki - User contributions [en]

Best practice manuals and templates

2026-04-27T13:25:50Z

Ddamaske: /* Guidelines and templates for specific research domains */

<h1 style="background-color:#3ba39b; font-size: 30px; font-weight:bold; color:white; padding:0.3em 1em; margin:1em 0; text-align:center"> Best practice manuals and templates </h1>
__TOC__
==About this page==
On this page we present a collection of best practice manuals & submission templates for data submissions to PANGAEA. We provide a general field observation template and a series of guides for specific research areas in order to best capture and preserve the particular contextual information of these research areas for reuse, and to best assist our authors in compiling this helpful and necessary information. The guides also include the corresponding adapted templates to help our authors submit their data. For further information about data submission, please refer to our [[Authors Guides]].

The templates support the comprehensive compilation of required meta-information related to sampling, methodology, and measured parameters/variables in a well-defined, structured manner. They help to be compliant with our guidelines and requirements, standardize metadata and data in submissions and thus also assist PANGAEA in the process of reviewing and ingesting data submissions, which in turn considerably contributes to a reduction in overall submission processing time.

== General field observation studies from earth and environmental sciences ==
We recommend the following template for authors wishing to submit data for studies that do not fall within the more specific research areas listed below.
[[Media:Envir sample template.xlsx|'''Generic spreadsheet template''' for field observation data]] ('''xlsx-file''' including detailed instructions)

[[Media:Envir sample template tsv.zip|'''Generic text-file template''' for field observation data]] ('''zipped tab separated text files'''. Please see instruction file 0_README.md first!)

==Guidelines and templates for specific research domains==

[[Biology|'''Biological data''']] [[Chemical data|'''Chemical data''']] [[Vertical sediment profile|'''Geological data''']]

'''Geophysical data'''

* Multibeam echosounder data (incl. SVP, MBES water column data) & Side-scan sonar data & bathymetry model data ([[Bathymetry]])

* Sediment echosounder data (e.g. Atlas Parasound P70 echosounder data) ([[Sediment_echosounder]])
* Seismic data ([[Seismic]])

[[Meteorological data|'''Meteorological data''']]

[[Eddy-Covariance-Measurement Systems|'''Eddy-Covariance-Measurement Systems''']]

'''Oceanography data'''

* [[ADCP Underway Data]]
* [[Bio-optical Sensors Underway Data]]
* [[CTD|CTD Data]]
* [[CTD Underway Data]]
* [[Ferrybox Underway Data]]
* [[TSG Underway Data]]

== Binary objects ==

This category of data publications includes georeferenced binary object, e.g. NetCDF-files, seismic data files (e.g. segy), photos/images or videos.
* [[Binary_objects|Binary objects]]

Seismic

2026-04-27T13:25:10Z

Ddamaske:

== Introduction ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / [https://creativecommons.org/licenses/by-sa/4.0 CC BY-SA]" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]] The German marine seismic community seeks to establish a standardized approach for archiving seismic data, covering both raw and processed field data. The primary objective is to comply with the '''FAIR''' principles [https://doi.org/10.1038%2FSDATA.2016.18 Wilkinson et al. 2016] while ensuring compliance with the EU INSPIRE directive. This initiative aims to systematically archive newly acquired 2D raw seismic reflection data from German research vessels and, to the greatest extent possible, preserve existing ''legacy'' data. By implementing this standardization, the archived data will achieve interoperability with various global repositories and portals, such as [https://www.marine-geo.org/index.php MGDS], [https://sdls.ogs.it/cache/index.jsp SDLS], [https://snap.ogs.it/cache/index.jsp SNAP], [https://www.geo-seas.eu/ GeoSeas] (see also [https://doi.org/10.4430/bgta0163 Diviacco et al., 2015]), and [https://www.seadatanet.org/ SeaDataNet] (see also [https://doi.org/10.4430/bgta0051 Diviacco et al., 2012]).

== ''Standardized content of datasets'' ==
=== Standardized ''language'' ===
To ensure that data adheres to the '''FAIR''' principles [https://doi.org/10.1038%2FSDATA.2016.18 Wilkinson et al. 2016], it is essential to use a common vocabulat for data description. To enhance data interoperability, PANGAEA utilizes terms of the [https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/ NERC catalogue] for describing seismic data whenever feasible (see also [https://vocab.seadatanet.org/search SeaDataNet vocabularies] ).

=== Standardized ''Authors'' ===

The Authorship of (national/German) datasets is currently under review with respect to the [http://doi.org/10.1002/9783527679188.oth1 Guidelines for Safeguarding Good Research Practice] of the (German Research Foundation).

On German research vessels, when archiving raw data in PANGAEA, it is common practice to list the chief scientist, the lead scientist on board, and the individual who submits the data as authors. Occasionally, other contributors, such as co-applicants of the research expedition, may also be included, though this is typically an exception.

For processed data, authorship is generally granted to those who have played a significant role in the data processing.

=== Standardized ''Title'' ===
To enhance the reusability and interoperability of datasets, it is important that metadata for similar datasets—such as 2D multichannel reflection seismic data collected from comparable research missions, vessels, or platforms—adhere to a standardized template and vocabulary.

This uniformity ensures that datasets are consistent and easily comparable. A key aspect of this standardization is the dataset title. PANGAEA has adopted a **construction kit** template for titles of different seismic data, originally developed by the [https://www.allianz-meeresforschung.de/en German Marine Research Alliance] (DAM) for bathymetry data under the Project [https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitalisation/underway-research-data Underway Research Data].

This template incorporates essential elements such as data type, device, platform type, platform name, cruise identifier, and area. To uphold FAIR standards, PANGAEA encourages data submitters to utilize this template, extending its application beyond German research data to foster global uniformity.

The ''construction kit'' is shown below:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! select: !! of !! select platform type: !! platform name or project (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name or other offcial naming !! optional: IHO Sea Area (1953),
|-
| 2D multichannel seismic reflection || raw data || (entire dataset) || " || RV || || || || https://www.gebco.net/data_and_products/undersea_feature_names/
https://www.marineregions.org
| https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
| 2D multichannel seismic reflection || raw data || (working area dataset) || " || RV || || || ||
|
|-
| Continous seismic|| ||(Ocean Bottom Seismometer working area dataset)
| "|| || || || ||
|
|-
|Seismic
|
|(Ocean Bottom Hydrophone working area dataset)
|"
|
|
|
|
|
|
|-
|Seismic
|
|(Onshore Seismometer working area dataset)
|"
|
|
|
|
|
|
|-
|Seismic
| -
|(Onshore Seismometer working area dataset)
|"
|
|project PISAGUA
|
|
|
|
|-
|
|
|(dataset compilation)
*only for processed data
|"
|
|
|
|
|
|
|}
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! !! !! !! !! !! !! !! !! !!
|-
| 2D multichannel seismic reflection || raw data || (entire dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| 2D multichannel seismic reflection || raw data || (working area dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| 2D multichannel seismic reflection || processed data || (dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || || ,South Pacific Ocean
|-
|Continous seismic
|raw data
|(Ocean Bottom Seismometer working area dataset)
|of
|RV
|POSEIDON
|during cruise
|POS515
|Poseidon mud volcano chain, Calabrian Arc
|Mediterranean Sea
|-
|Seismic
|
|(Onshore Seismometer working area dataset)
|of
|
|project PISAGUA
|
|
|Atacama Desert near Taltal
|Chile
|-
|Seismic
|processed data
|(Ocean Bottom Hydrophone working area dataset)
|of
|RV
|Sonne
|during cruise
|SO297
|Taltal Ridge
|Chile
|}
Currently, we only distinguish between "raw" and "processed" data. However, in future times, we will distinguish between those three data types:

* RAW data (not touched at all; metadata should include full geometrical setup information) – e.g., a SEG-D file
* Primary data (e.g., including geometrical information in the file itself) – usually a SEG-Y file
* Data product (processed data) – SEG-Y file

This approach, including naming convention, will be introduced and implemented in the standardization process of the various seismic data types.

=== Standardized ''Abstract'' ===
To enhance the FAIR principles, PANGAEA requires a concise abstract for each dataset. For more details on writing abstracts, please visit [[Abstract|PANGAEA Abstract]] guidelines.

Please note that cruise summary reports or other references should not be cited exclusively in the abstract, as references are also included in the dataset’s metaheader. However, if processed data are submitted to PANGAEA and you wish to credit and cite the original raw data, you may include a statement such as:

''"Raw data for this study were published open access (Authors, YYYY)."''

If you would like a reference (e.g., paper) to be linked, please inform the data editor. Be sure to provide the '''full citation''' in the reference list (e.g., Urlaub, Morelia; Husrin, Semeidi; Kühn, Michel; Papenberg, Cord; Berndt, Janine: Technical Report for Raw 2D MCS Reflection Data, R/V Sonne Cruise 299, Leg 2, Singapore (Singapore) – Port Louis (Mauritius), 15/08/23 – 02/09/23. GEOMAR Helmholtz Centre for Ocean Research Kiel, 8 pp, https://doi.org/10.3289/TR_2D-MCS_so299_2).

=== Standardized usage of ''Reference'' ===
When processed datasets derived from the same raw dataset are submitted to PANGAEA, they are interrelated through a '''Reference''' linkage. PANGAEA reviews archived datasets to identify relationships, establishing '''Related to''' or '''Source''' relation when appropriate. These relationships are displayed accordingly. For further details, please refer to the ([[Reference|PANGAEA Reference]] guidelines.

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from [[Metaheader|PANGAEA ''GEOCODE'']].

=== Standardized usage of ''Parameter (Metadata)'' ===

The selection of appropriate [[Parameter|PANGAEA parameter]] for seismic datasets depends on whether '''raw''' or '''processed data''' are being submitted. This applies to both '''seismic reflection''' and '''refraction data'''. The chosen parameters will be included in the metadata and added to the data files accordingly.

The following standards of metadata (parameters) have been published or are currently under development:

* '''Metadata description 2D multichannel seismic reflection raw data'''
** Berndt, J., Papenberg, C., Damaske, D., Schnabel, M., Berndt, C., Crutchley, G., Huebscher, C., Keil, H., Krastel, S., Kühn, M., Lohrberg, A., Riedel, M., Selke, N., & Weigelt, E. (2025). Metadata description of 2D multichannel seismic reflection raw data (1.0.0). Zenodo. https://doi.org/10.5281/zenodo.14754825
* '''Metadata description 3D multichannel seismic reflection raw data'''
** in preparation
* '''Metadata description ocean bottom seismometer raw data'''
** in preparation

== Your Dataset Submission to PANGAEA ==
Recent submissions have highlighted the need for Standard Operating Procedures (SOPs) to streamline the submission process and minimize time-consuming discussions.

These SOPs have been developed to make data submission easier for researchers. They provide recommended wording to help meet the expectations and requirements of PANGAEA curators. While the SOPs are suggestions rather than strict rules, they were created in collaboration with the scientific community, including contributors ranging from PhD students to professors.

The following SOPs provide guidance on how to publish the corresponding datasets. Developed in collaboration with scientists, these SOPs reflect the recommended format and standardized vocabulary required for the submission of processed data.

* Berndt, J., Damaske, D., Rehage, M., & Riedel, M. (2026). Standard Operating Procedure (SOP): Archiving Legacy Ocean-Bottom Seismometer (OBS) and Ocean-Bottom Hydrophone (OBH) Raw Data at PANGAEA. Zenodo. https://doi.org/10.5281/zenodo.19482745
* Berndt, J., Damaske, D., Rehage, M., & Riedel, M. (2026). Standard Operating Procedure (SOP): Archiving Legacy Ocean-Bottom Seismometer (OBS) and Ocean-Bottom Hydrophone (OBH) Processed Data at PANGAEA. Zenodo. https://doi.org/10.5281/zenodo.19482964
* Berndt, J., Damaske, D., Rehage, M., & Warwel, A. (2026). Standard Operating Procedure (SOP): Archiving Legacy Seismic (Onshore Seismometer) Processed Data at PANGAEA. Zenodo. https://doi.org/10.5281/zenodo.19482202

==== Seismic Raw Data ====
The marine seismic community, in collaboration with data management experts and PANGAEA editors (curators), is actively working to define metadata standards for various types of seismic raw data (from active source).

SOPs for each metadata standard will be published once the corresponding workflows are fully established. As data acquisition methods can vary, multiple SOPs may exist for a single standard to reflect different recording procedures.

'''Current Status:'''

Data publication through the Underway Research Data project coordinated by the [https://www.allianz-meeresforschung.de/en German Marine Research Alliance] (DAM) is currently managed by data stewards as part of the development and implementation of these standards and workflows. In the future, however, it is planned to provide additional tools (external) —such as SOPs including Jupyter Notebooks—to enable researchers to independently create the data matrix (data table) for the dataset required for submission to PANGAEA.

The standardization of legacy seismic raw data will be addressed with further details at a later stage. However, as a general guideline, please ensure the following when submitting legacy data:

* Please include the observer log and navigation files in the correct format.
* Please provide links to the cruise report and any relevant publications associated with the dataset.

Following these guidelines will help facilitate the data curation and submission process.

== References ==

Berndt, Janine, Hübscher, Christian, Keil, Hanno, Lehmann, Andreas, & Berndt, Christian. (2023). German Marine Seismic Data Access. Zenodo. https://doi.org/10.5281/zenodo.7875451

Seismic

2026-04-07T13:40:35Z

Ddamaske: Created page with "50px "

[[Image:Under_construction.jpg| thumb | left |50px ]]

Principal investigator

2025-08-06T14:37:16Z

Ddamaske:

A '''Principal Investigator (PI)''' in the context of PANGAEA is the person responsible for the acquisition and scientific quality of a [[dataset]] or [[data series]]. This is typically the researcher who generated or curated the data and is scientifically accountable for it. The PI serves as the main scientific contact and can be seen as the equivalent of a corresponding author for a specific part of the dataset.

In a published data table, each data series (i.e., table column) can have a maximum of one PI assigned. This ensures clear responsibility, scientific traceability, and proper attribution for each parameter.

== Contact information ==
For enabling users of the data to contact the responsible person for clarification, collaboration, or further information, each PI must be identified with valid contact details, including:
* an e‑mail address
* ideally an ORCID iD to enable persistent and unique researcher identification

If the PI’s name is not yet linked to their ORCID iD in PANGAEA, this can be corrected by:
* associating the relevant PANGAEA user account with the ORCID iD (only the user account owner can do it)
* if the link is not established automatically after that, submitting a request via the [https://www.pangaea.de/contact/ contact form] to have it added manually

== Relation to authorship ==
The PI is typically also one of the authors of the dataset and is responsible for the scientific validity of the data series. While the PI ensures the scientific quality, data submission may be performed by another contributor (e.g., a co-author, data manager, or data steward).

== Clarification ==
It is important to distinguish a PANGAEA PI from a project PI. In this context, the PI designation is not related to funding responsibilities or project management. It refers exclusively to scientific responsibility for individual data series within the dataset.

"This article reflects the current practice concerning this topic, i.e. as of fall 2025. It is very likely that this was handled differently at some point in PANGAEA's long history. We ask for your understanding that there is no entitlement to publish your data in accordance with past practices in this regard. "

PANGAEA Bathymetry Web Map Services

2025-01-29T13:40:01Z

Ddamaske:

{{construction}}
Page content may change in future (current status: 13.11.2024)

= PANGAEA Bathymetry Web Map and Feature Service =

This new '''PANGAEA Bathymetry Web Map and Feature Service''' https://www.ogc.org/standards/wms/introduction (first release 2021) contains bathymetry data archived at PANGAEA (including only data with a CC-BY 3.0 or CC-BY 4.0 license). This service is developed as part of the '''German Marine Research Alliance''' in the core area '''"Data management and Digitalization"''' ('''Deutsche Allianz Meeresforschung, DAM''' https://www.allianz-meeresforschung.de/en/).
Note that not all bathymetry data currently archived in PANGAEA are visualized through this service. However, the number of datasets will be continuously increased in the future. As of now, only raw & processed data from multibeam echosounder measurements are incorporated in this service (further developments are in progress).
'''Please acknowledge that each layer of this service contains further usage requirements (e.g. citation rules) provided in the abstract (see [[PANGAEA_Bathymetry_Web_Map_Services#Layer_Abtracts|below]])'''. Data visualized in this service shall not be used for navigational purposes. 
For feedback & questions please contact PANGAEA. https://www.pangaea.de/contact/ 
This web map service is accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wms''' This web feature service is still considered a beta version and accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wfs'''

Each incorporated PANGAEA dataset in this service contains a vast amount of dataset-specific individual metadata. If you consider incorporating this service (data layers) into any front-end application (e.g., a web-based data portal), please also make the incorporated metadata of each layer available and visible to the user. 
Please note that a Geographic Information System (GIS) (e.g. QGIS https://qgis.org/ ) is required to access this service. However, data of this service can also be explored using the '''Viewer''' https://marine-data.de/?site=viewers of the '''Data Portal German Marine Research''' https://marine-data.de/. (see also below)

Further information about development and usage requirements are documented in Damaske et al. (2024). Generally cite the service also with:

* Damaske, D., Selke, N., & Balamurugan, A. (2024). PANGAEA Bathymetry Web Map & Feature Service – Standard Operating Procedures visualizing bathymetry data archived in PANGAEA - Data Publisher for Earth & Environmental Data. Zenodo. https://doi.org/10.5281/zenodo.8296986

== Data Contribution ==

To facilitate incorporating PANGAEA data to this service, please note the detailed information about '''bathymetry data submissions to PANGAEA''' [https://wiki.pangaea.de/wiki/Bathymetry '''here'''].

== Layer Overview ==
Currently only data layers originating from multibeam echosounder data are available in the service (see list below). For detailed information check the abstract of each corresponding data layer.

'''Raw data:'''
*PANGAEA Water Column Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Footprints
*PANGAEA Multibeam Raw Data Footprints Simplified
*PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional)
'''Processed data:'''
*PANGAEA Multibeam Processed Data Footprints
*PANGAEA Multibeam Processed Data Footprints Simplified
*PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional)

== Layer Abstracts ==
directly embedded into the service:
https://maps.awi.de/services/common/pangaea_bathymetry/wms?service=WMS&request=GetCapabilities
<nowiki>*</nowiki>Abstract update 21.08.2024 (note, that currently more layers are available. Update on this will follow soon)
{| class="wikitable" style="font-size: 86%;"
! Layer name (technical name) !! Layer title !! Abstract (embedded in service)
|-
| mbes_raw_acquisition_tracklines_wcd_4326 || PANGAEA Water Column Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_acquisition_tracklines_4326 || PANGAEA Multibeam Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_4326 || PANGAEA Multibeam Raw Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_simplified_4326 || PANGAEA Multibeam Raw Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_bathymetry_8000_haxby_multidirectional_4326 || PPANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_4326 || PANGAEA Multibeam Processed Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_simplified_4326 || PANGAEA Multibeam Processed Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_8000_haxby_multidirectional_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|}

 Available metadata

A list of currently available metadata:
*Please see here: https://doi.org/10.5281/zenodo.8296986

== Known incorporated web based data portals ==
This service is incorporated in the following data portals::
*[https://marine-data.de/?site=viewer Viewer of the Data Portal German Marine Research]
*[https://www.ncei.noaa.gov/maps/iho_dcdb/ IHO Data Centre for Digital Bathymetry (DCDB)]
....more information will be provided......

Bathymetry

2024-11-26T10:10:35Z

Ddamaske:

== Page content (please note) ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]]

Please note, '''bathymetry data curation SOPs''' in PANGAEA with respect to '''FAIR data principles''' (https://doi.org/10.1038/sdata.2016.18) are revised within the scope of of the German Marine Research Alliance (DAM) Underway Research Data project (https://www.allianz-meeresforschung.de/). This page and the information provided here is addressed to PANGAEA users and data submitter's. [https://wiki.pangaea.de/wiki/Metaheader '''PANGAEA's Metaheader'''] explicitly for bathymetry datasets and other data curation requirements are explained on this page. In addition, data management at PANGAEA and requirements for bathymetry data submission to PANGAEA are documented. 
This page is mainly made for bathymetry data from multibeam echosounder data (MBES), however can also be used for data from Satellite derived bathymetry (SDB) or ''Light Detection and Ranging (LIDAR)'' data. 
'''Please note, that this page may still be revised in the future. '''
 

== DAM Underway Research Data project background ==

The '''German Marine Research Alliance (DAM)''' is a combined effort to exploit the full potential of German research vessels as mobile measuring platforms and currently involves 24 institutions and research facilities in Germany. The Underway Research Data project is part of DAM core area ''data management and digitalization'' (https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation/).

[[Image:DAM_Logo_small.png| thumb | right |250px| https://www.allianz-meeresforschung.de/en/]]

Please note for the German research vessels RV POLARSTERN, RV METEOR, RV MARIA S. MERIAN & RV SONNE there is no need to upload the data if data are (usually) less than 2 years old. We’ll then take the data form the DSHIP ''Mass Data Management System (MDM)'' and prepare your dataset. Please mentioned in you submission in the comment; please take data from DSHIP ''Mass Data Management System (MDM)'' 
 
 
 
 

== PANGAEA Bathymetry Web Map & Feature services ==

'''All submitted bathymetry data''' (raw data & processed data) are being semi-automatically processed at PANGAEA. '''Tracklines and coverage polygones (footprint)''' of all submitted bathymetry data are extracted from the data and '''added to the Viewer of the Marine Data Portal''' https://marine-data.org/ (direct link to the viewer https://marine-data.de/?site=viewer),
if data have a '''CC BY 4.0''' (or CC-ZERO) data license. If '''data are not under a moratorium period''', also a '''raster image''' is being calculated and '''added'''. Here, the (meta-)data can be explored (and are linked to the DOI). These vector & raster data are also available through OGC Web Map services. https://maps.awi.de/services/common/pangaea_bathymetry/wms and Web Feature Service [https://maps.awi.de/services/common/pangaea_bathymetry/wms https://maps.awi.de/services/common/pangaea_bathymetry/wfs] (please note, this is not a webpage, you need e.g. a GIS to use this service). 
Further information can be found [https://wiki.pangaea.de/wiki/PANGAEA_Bathymetry_Web_Map_Services '''here'''].

== ''Standardized content of datasets'' ==
To make data '''findable''' (F) and due to PANGAEAs archiving '''SOP'''s, bathymetry datasets from multibeam echosounders will be separated into two datasets (when stored in separate files), if the water column data is simultaneously being recorded during data acquisition (e.g. .wcd files from Kongsbergs MBES Systems) . This is necessary due to data curation processes, consequently reducing the download volume if it is intended to download only bathymetry data from PANGAEA. The water column data are usually much larger than regular bathymetry files. However, both datasets will be connected / linked to each other, making it easy to find the corresponding dataset.

=== Standardized ''language'' ===
To make data FAIR, “to speak” a common language is required. PANGAEA specifically uses for bathymetry data the Natural Environment Research Council's Data (NERC) Catalogue for describing data.
https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/
https://vocab.seadatanet.org/search

== Standardized ''Metaheader'' ==

=== Standardized ''Authors'' ===

The Authorship of national (German research) datasets are revised with respect to the ''Guidelines for Safeguarding Good Research Practice'' of the ''German Research Foundation'' http://doi.org/10.1002/9783527679188.oth1 . Although it is not generally agreed on, usually the authorship is given to anyone who was significantly involved in data acquisition on board or post-processing on land:

For raw data of German research vessels which are published at PANGAEA, it is very common to include the responsible scientific team on board, including all scientist (including student assistants) who were involved in monitoring, detailed survey planning or performing the survey. This can be considered as a genuine, identifiable contribution to the content of the research data, therefore fulfilling the requirements for authorship's according the ''Guidelines for Safeguarding Good Research Practice''. When no other main responsible scientist for the e.g. multibeam device was on board (also responsible to allows the data publication at PANGAEA in the first place), usually the first authorship is provided to the chief scientist (the chief scientist is usually the one person who has to allow the data publication). Credit may be given to the personal in the comment metadata field, who was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list. This is for instance the case for "historical" multibeam data which are submitted to PANGAEA.

For processed data of German research vessels which are published at PANGAEA, the authorship is generally only given to the person, who was working (processing) the data. Avoid to include person, which were only involved in the raw data acquisition (the scientific credit is usually provided in the corresponding raw dataset).

Since this common practice mostly apply to PANGAEA dataset of German Research vessels, PANGAEA recommend to follow this common practice if you are submitting datasets other than German Research vessels related data.

=== Standardized ''Title'' ===
To ensure the '''reusability''' (R) and '''interoperability''' (I) of datasets, metadata of similar datasets such as bathymetry data gathered from similar research missions, research vessels or research platforms should follow a common template and a common vocabulary (Generally speaking; they should look alike!). This also includes the title. Therefore, the title of bathymetry data which are entrusted to PANGAEA shall follow a certain template ''“construction kit”''. This ''“construction kit”'' was developed within the DAM efforts (Project Underway Research Data). It includes the feedback of several German scientists from different institutions, PANGAEA bathymetry data submitters & data management personal. Key elements of each dataset title are incorporated, such as data type, device, platform type, platform, cruise (& area). To guarantee and fulfil FAIR standards, PANGAEA is encouraging data submitters to follow this template (also covering none German research data). To follow these standards is mandatory for all PANGAEA datasets. 
 
Example: 
''Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM55'' 
''Multibeam bathymetry raw data (Kongsberg EM 122 working area dataset) of RV METEOR during cruise M127, Fictional Bank canyon, North Atlantic Ocean'' 
 
The ''“construction kit”'' - incorporating all feedback - is shown below.:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! (device according to L22 vocabulary "Alt label" (NERC*) !! select: !! of !! select platform type: !! platform name (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| Multibeam bathymetry || raw data || || entire dataset) || " || RV || || " || || ||
|-
| Sidescan sonar || processed data || || transit dataset) || " || AUV || || " || || ||
|-
| Water column || || || working area dataset) || " || ROV || || " || || ||
|-
| || || || working area dataset, Generic sensor format) || " || ROV || || " || || ||
|-
| || || || dataset compilation)* || " || || || " || || ||
|-
| || || || *only for processed data || " || || || " || || ||
|}
Further information about the entries can be found here:
{| class="wikitable" style="font-size: 86%;"
! (device according to L22 vocabulary "Alt label" (seadatanet) !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| *http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=L22 || https://www.gebco.net/data_and_products/undersea_feature_names/ || https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
||| https://www.marineregions.org ||
|}
'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! Multibeam bathymetry !! raw data !! (Kongsberg EM 122 !! working area dataset) !! of !! RV !! SONNE !! during cruise !! SO250 !! Loyd Dill Seamount, !! South Pacific Ocean
|-
| Multibeam bathymetry || raw data || (Atlas Hydrosweep DS 3 echo sounder || transit dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| Multibeam bathymetry || raw data || (R2Sonic SONIC 2024 || entire dataset) || of || AUV || ABYSS || during cruise || MSM50 || ||
|-
| Multibeam bathymetry || processed data || (Kongsberg EM 122 || entire dataset) || of || RV || METEOR || during cruise || M74 || ||
|-
| Multibeam bathymetry || processed data || (EM 120 echosounder || dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| Water column || raw data || (Kongsberg EM710 || entire dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || || ,South Pacific Ocean
|}

=== Standardized ''Abstract'' ===
Intending to make data more ''FAIR,'' PANGAEA requires a compact ''Abstract'' for each dataset. For more information regarding abstracts, see https://wiki.pangaea.de/wiki/Abstract. 
Please note that cruise summary reports or other reference must not be cited exclusively in the abstract because references are also included in the metaheader (references) of the dataset. However, to provide credit and cite e.g. raw data if processed data are submitted to PANGAEA, you might add to the abstract: "Raw data for this study were published by (Authors, YYYY)." (followed by the full citation of the dataset in the list of references). If reference shall be linked, please inform the data editor. 
If you would like to provide other contact information related to this dataset (e.g. Email address), please inform the data editor. 
Please specify in the abstract whether sound velocity profiles are part of the raw dataset publication or not. Comparatively for processed data publications, please describe your processing steps (further, see below and examples).

For processed data please describe whether:
*depth measurements manually cleaned from errors during processing?
*sound velocity profile correction applied during processing?
*navigation correction applied during processing?
*tide correction applied during processing?
*horizontal datum, EPSG code from raster data in this publication are?
For raw data please describe whether:
*sound velocity profile correction applied during acquisition?
*are ancillary sound velocity profiles part of this data publication?
*which device recorded the data, which ship, which cruise?
*why have the data being recorded?

==== Raw data (example) ====

Multibeam bathymetry raw data using the ship's own Kongsberg EM 122 multibeam echosounder was not continuously recorded during RV MARIA S. MERIAN cruise MSM97/2. Data were recorded on 3 days between 2020-12-16 and 2020-12-19 in the Norwegian Sea and data acquisition was almost continuously monitored during the survey. Previous to the survey, gaps in already existing database were identified using the General Bathymetric Chart of the Oceans (GEBCO 2020) Type Identifier (TID) grid. These gaps were used as a base to determine the course of the ship during the cruise. During data acquisition, sound velocity measurements using sound velocity profiles (SVP) derived from CTD casts was applied on the data for data calibration. Ancillary SVP raw data (.asvp files) and SVP from CTD-cast (.txt) are part of this dataset publication.
Data are unprocessed and therefore contain incorrect depth measurements without further processing. Data can be processed e.g. with the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021). 
''(FEEL FREE TO ADD MORE INFORMATION)''

==== Processed data (example) ====
Swath sonar bathymetry data used for that dataset was recorded during RV SURVEY during cruise S143 using Kongsberg EM 122 multibeam echosounder. The cruise took place between 2016-12-12 and 2011-12-23 in the North Atlanic Ocean. Data were recorded on 8 days between 2011-12-15 and 2011-12-23. The approximate average depth of the entire dataset is around 1500m. 
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic. After processing, these data were directly imported into the MBES Acquisition software Kongsberg SIS Seafloor Information System. Raw data were converted to MB-System format. Data were manually edited for false measurements. No further artificial sound velocity profiles were used during further processing. The data were corrected for tidal changes using data provided by the OSU Tidal Prediction Software
OTPS that is retrievable through MB-System. The vertical datum of the data is now matched to ''mean sea level (MSL)''. A raster was calculated and stored in GeoTIFF format with a 25m resolution (negative values). In addition, the full resolution of avilable ASCII data and used for grid calculation are also archived in this dataset. 
''(FEEL FREE TO ADD MORE INFORMATION)''

=== Standardized usage of ''Reference'' ===
Typically, processed datasets, which are all based of the same raw dataset (also archived in PANGAEA), are submitted to PANGAEA. These datasets will be linked to each other as a ''Reference''
Currently, all bathymetry datasets already archived in PANGAEA are reviewed and checked for relations. If a relationship is found, a linkage between both datasets is being created and is shown as ''Related to''. More information can be found here https://wiki.pangaea.de/wiki/Reference

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from ''Events'' or PANGAEA ''GEOCODE'' (see below): https://wiki.pangaea.de/wiki/Metaheader. Please note, that ''Minimum Elevation'' und ''Maximum Elevation'' does not represent min / max depth values measured from MBES data contained in this dataset. It is rather in this case the reference height on earth from the instrument used for the measurements. 
Note: Currently, the ''Coverage'' will be visible on PANGAEA website with points having an ''GoogleMaps'' image in the background (right upper corner). It does not show the actual coverage of the surveyed area. The visible points are, instead, representing the ''Events'' (see below).

=== Standardized usage of ''Events'' ===
Bathymetry datasets contain so called PANGAEA ''Events'' (https://wiki.pangaea.de/wiki/Event). The Event links to the scientific ''Campaign'', Method/Device and ''Basis'' (platform) containing further additional information. Please note that, if you browse with your mouse cursor on ''Campaign'', Method/Device or ''Basis'', a field will pop up (do not click). In some datasets, it is possible to click on these fields and a link with detailed information will be provided.
 Further information for Bathymetry related events is given below. 

==== ''Underway event'' ====
(update of this section is in progress) 

For bathymetry data from multbeam echosounders, a so called ''"Underway"'' ''Event'' is created on board of the research vessel. The ''"Underway"'' ''Event'' is named ''CruiseID_0_Underway-number(undefined, )'' e.g. ''M127_0_Underway-1''. The event shows the starting and end point (coordinates & datetime) of the first and last data record of the MBES device acquired during the cruise. Also, the ''Methods/device'' used to record the data is included for Event description. Please note, that PANGAEA specific vocabulary is used here. Providing further detailed information using standard common vocabulary such as the NERC catalogue (https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/) is currently being prepared (more information is provided as soon as possible.....). 
If available, an additional link to the Sensor description hosted on https://registry.awi.de is provided. 

If the dataset is compilation of many datasets (only possible for processed data), several ''"Underway"'' ''Events'' will be used. 
Note, that the prefix of the ''Event'' name contains the official cruise ID (cruise label, e.g. https://www.pangaea.de/expeditions/bybasis/Meteor%20%281986%29), not the campaign name. The suffix number does not follow any specific rule, as this number is usually chronologically created on board, which is why the numbering can differ from cruise to cruise. 

==== ''SVP casts and event(s)'' ====

If ''SVP casts'' (sound velocity profile measurements using an external device, e.g. using an ''AML Oceanographic Plus X sound velocity probe'') or CTD casts (sound velocity derived from CTD measurements) were performed during the cruise, the acquired data files (and used for import to the acquisition software, e.g. the ''Kongsberg Seafloor Information'', SIS) will be stored in the same raw dataset. The corresponding event of the ''Event list'' of the cruise (e.g. https://www.pangaea.de/expeditions/events/M160) will be linked to these files. This ''Event'' will contain similar information as described above, e.g. ''coordinates'', ''methods/devices'', ''etc.''. If SVP's are used for data post-processing (sound velocity correction), these data files can also be submitted to PANGAEA. If possible, these SVP can be linked to the corresponding ''Event''. In general, please always try to describe your submitted SVPs as good as possible for scientific re-use (state the origin of data, whether data are extrapolated e.g. to 12000m, etc.).
You can use the following '''[http://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/Template_PANGAEA_SUBMISSION_bathymetry_processed_V4.xlsx template]''' to support your submission.

=== Standardized usage of ''Parameter and data formats'' ===

Which [https://wiki.pangaea.de/wiki/Parameter PANGAEA parameter] for bathymetry datasets will be used & added to the data files, depend on whether raw or processed data are being submitted.

==== Raw data curation ====

Standard parameters for bathymetry raw data also include PANGAEA’s so called [https://wiki.pangaea.de/wiki/Geocode Geocodes]. These are standard important parameters, which are mandatory to keep the data georeferenced. '''These metadata for each file will be automatically created while data curation process''' Metadata are extracted using the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2023) when data format is supported by MB-System. 

{| class="wikitable"
|-
! Name!! Short Name !! Unit !! Comment
|-
| [https://wiki.pangaea.de/wiki/Event Event label] || Event || ||
|-
| [https://wiki.pangaea.de/wiki/Binary_object Binary Object] || Binary|| || *this will in PANGAEA download URL
|-
| [https://en.wikipedia.org/wiki/Media_type Binary Object (Media Type)] || Binary (Type) |||| *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || Bytes || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || || *automated entry during data curation process
|-
| [https://epic.awi.de/id/eprint/29970/ Kongsberg datagram raw file name] || Datagram rfn || || *only for data from EM Series
|-
| File content || Content || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording duration] || Data record duration || min||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording distance]|| Data record distance || m ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Ship speed]|| Ship sp|| knots ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Number of pings]|| Pings|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, date/time]|| File start date/time || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, latitude] || File start latitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, longitude] || File start longitude|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, heading] || Start heading || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, depth] || Start depth || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, date/time] || File stop date/time|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, latitude] || File stop latitude ||||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, longitude] || File stop longitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, heading]|| Stop heading|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, depth]|| Stop depth|| ||
|-
| DATE/TIME || Date/Time || || *Geocode – copy of 'Start of data file recording, date/time'
|-
| LATITUDE|| Latitude || || *Geocode – copy of 'Start of data file recording, latitude'
|-
| LONGITUDE || Longitude|| || *Geocode – copy of 'Start of data file recording, longitude'
|-
| ELEVATION || Elevation || || *Geocode – copy of 'File start depth, change of sign'
|-
| Comment || Comment || ||
|}
 
Please note, if you do have ancillary data, such as ''operational logs'' created on board or detailed ''processing reports'', please add those files to the submission.

==== Processed data curation ====
Standard important parameters extracted from raster data (and ASCII data), which are mandatory to keep the data georeferenced, will be attached automatically. Please note that ASCII however are not recommended for further reuse. 
Feel free to upload bathymetry data, backscatter and/or a sidescan data, in raster (and/or ACSII) format (+ .xyz point cloud data, see below). In general, for raster data GeoTiff files (*.tif) and the grid data format (*.grd) is always preferred, since these data are usually easy to reuse, having less projection issues using standard GIS software. Please indicated whether depth values of the grid cells (also for ASCII data) contain positive or negative values (e.g. elevation / this can be indicated in the file content description). In generel you can submit any projection of the raster image, however if you do so please always add an additional GeoTiff at best with the projection [https://epsg.io/4326 '''WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326''']. Also here, try in include the projection in the raster file. Please make sure, if you provide a “bathymetry” raster data, that they contain depth information rather than just an georeferenced image with RGB values (and image is not considered as data). To submit raster images with RGB values is also fine, however they do not represent an resuable data format. In that case, always provide an raster file with true depth information (same coverage). Most dataset in PANGAEA have negative values for depth (= elevation), so we recommend to convert your data accordingly. 
If you want to '''upload xyz files (point cloud data)''' to PANGAEA, you are welcome to do so. However, please also '''upload an auxiliary gridded raster image for each individual xyz (point cloud data) data file'''. In general raster data are more user-friendly (e.g. by using GIS systems), therefore raster images are of high value for scientist. '''Raster images are considered as a (FAIR) interoperable data format, highly supporting the [https://www.go-fair.org/fair-principles/r1-3-metadata-meet-domain-relevant-community-standards/ resuablity] of data by scientists, especially from other scientific domains'''. Raster image and point cloud data (xyz) will be published using the same doi.
 
Parameters for raster data are listed below (these parameter do not apply for GSF or MB-System data files. GSF or MB-System data files will get the same parameters as for raw data, see above ):

{| class="wikitable"
|-
! Name!! Short Name !! Value/unit !! Comment
|-
| Event label || Event || - || *automated entry during data curation process
|-
| Binary Object || Binary|| || *this will in PANGAEA download URL
|-
| Binary Object (Media Type) || Binary (Type) || - || *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || - || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || - || *automated entry during data curation process
|-
| [https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/cell-size-of-raster-data.htm Raster cell size] || Raster cell size || || * raster cell size, e.g. 100m *only for raster data *if possible in meters
|-
| File content || Content || || * data description, e.g. bathymetry / negative values in meters for depth measurements (= elevation) / GeoTIFF raster image, Float32, DEFLATE compression / *feel free to add a comment specifically referring this data file
|-
| [http://vocab.nerc.ac.uk/collection/V12/current/L11/ Vertical datum]|| Vertical datum|| || * e.g. mean sea level
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum]|| Horizontal datum|| || * e.g. WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum, projection stored in file]|| Horizontal datum in file || || * e.g. EPSG:4326 (some files may not have the raster projection stored in itself)
|-
| Longitude, westbound|| Longitude west|| ||
|-
| Longitude, eastbound|| Longitude east|| ||
|-
| Latitude, southbound|| Latitude south || ||
|-
| Latitude, northbound ||Latitude north|| ||
|-
| Soundings || Soundings || || *only for xyz data / *not for backscatter data / *currently under development (not always included)
|-
| Area ||Area || km² || *currently under development (not always included)
|-
| Elevation, Minimum ||Elev min|| m a.s.l. || *not for backscatter data
|-
| Elevation, Maximum ||Elev max|| m a.s.l. || *not for backscatter data
|}

=== Standardized usage of ''Comment'' ===
Bathymetry raw and processed data, which are acquired on scientific vessels, might contain erroneous depth values and/or data artifacts. These data shall never be used for navigational purposes involving safety at sea. For safety reasons, it is widely common to state this explicitly: The comment ''These data should not be used for navigational purposes'' will be '''automatically included as a comment''' on each bathymetry dataset in PANGAEA. Please also check the PANGAEA data policy for more information: https://wiki.pangaea.de/wiki/Data_policy (page currently under construction). Bathymetry data for official nautical chart production must explicitly fulfill the requirements of the International Hydrographic Organisation (IHO) https://iho.int/.
In addition the comment may give credit to personal who was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list.
=== ''Licence'' ===
PANGAEA and DAM are encouraging data submitters to submit bathymetry data under [(https://creativecommons.org/licenses/by-nc/4.0/) '''CC-BY 4.0'''] License terms, which allows sharing (copying and redistributing the material in any medium or format) and adapting (remixing, transforming, and building upon the material) the data. In this way, PANGAEA / DAM can also make the data coverage (footprint) and the trackline visible with a direct link to PANGAEA at https://marine-data.de/ . Note, within the DAM efforts, coverage (footprint) and trackline off all submitted bathymetry data will be made available to the community via OGC Web Map Services (WMS) and OGC Web Feature Services (WFS) . Avoid licence CC-0 & CC-BY-SA, if possible.

Which CC license choose for data? Check also [https://wiki.pangaea.de/wiki/License here]

=== (Standardized usage of ''Data model extensions)'' (for raw and processed data curation) ===

The usage of so-called ''data model extensions'' which are further ''attributes'' is currently developed. This is a new feature for PANGAEA in order to include more standardized metadata. This new feature shall insure further '''findabilty''' (F) and '''interoperability'''(I) of the datasets (more information is provided as soon as possible.....).

== Example datasets ==

=== Raw data ===

Damaske, Daniel; Becker, Marius (2021): Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV MARIA S. MERIAN during cruise MSM97/2. PANGAEA, https://doi.pangaea.de/10.1594/PANGAEA.927786

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+raw+data+(%22

=== Processed data ===
Simkins, Lauren M; Greenwood, Sarah L; Munevar Garcia, Santiago; Eareckson, Elizabeth; Anderson, John B; Prothro, Lindsay O (2021): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset) of RVIB NATHANIEL B. PALMER during cruise NBP150-02. PANGAEA, https://doi.org/10.1594/PANGAEA.937597, In: Simkins, LM et al. (2021): Pennell Trough, Ross Sea bathymetry and glacial landforms. PANGAEA, https://doi.org/10.1594/PANGAEA.937602

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data+(%22

Generic sensor format (GSF) data:

Dufek, Tanja; Schniotalla, Cara; Kinne, Stefan; Sternberg, Harald (2023): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset, Generic sensor format) of RV SONNE during cruise SO268/3, North Pacific Ocean. PANGAEA, https://doi.org/10.1594/PANGAEA.957204

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data%22+AND+citation%3Atitle%3A%22Generic+Sensor+format%22

== How to submit bathymetry data to PANGAEA and what to do? ==

Please submit bathymetry data here https://www.pangaea.de/submit/. During submission, you may have to provide information for the data curation process (e.g. cruise, device, etc). For your submission, please edit/modify the title & abstract as stated above ("title construction kit").

'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]

For raw data:

Usually for raw data, an upload area will be created for you where you can drop your files (on request). Feel free to drop your data as zip- or individual files. Please also include sound velocity profiles (only SVP raw data, e.g. MSM88_2-1_0.asvp) for raw data submission if available. Your files should not exceed a volume of 10GB, however several files can be uploaded simultaneously. Please avoid renaming of raw data files, even if they are imperfect.
If raw data from '''RV Sonne''', '''RV Maria S. Merian''', '''RV Polarstern''' or '''RV Meteor''' are being submitted, '''please make a comment in your submission before you upload any multibeam echosounder raw data files (e.g. .all format)'''. Please leave a comment: '''''please take data from DSHIP Mass Data Management System (MDM)'''''.

For processed data:

Just drop your files after you get your upload link (see requirements above). If additional SVP's have been used for data processing, you can also upload these files too. 

===PANGAEA Data Submission Form Example===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]please note that the table below show's the simplified data submission workflow. The data submission form can be accessed here https://www.pangaea.de/submit/<nowiki/>Further information can also be found here [[Data submission]] .
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Title
|Adapted, generalized [[#Standardized_Title]]
|Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV SONNE during cruise SO250
|-
|Author(s)
|[[#Standardized_Authors]]
|[chief scientist], [responsible scientist(s)]
|-
|Keywords
|
|''(default)''
|-
| Abstract/Describe your Data
|[[#Standardized_Abstract]]; if the processed or raw data were already archived, the links may be placed here
|The survey data contain MBES measurements of the Fictional Bank canyon. No bathymetric measurements of Fictional Bank canyon were found in international databases prior to the cruise.
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic SVP Plus X. After processing, these data were directly imported into the MBES acquisition software Kongsberg SIS Seafloor Information System.
|-
| License
|[[#Licence]] 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 the 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).
|[https://creativecommons.org/licenses/by/4.0/ 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
|Files containing metadata information for the data
|
|}

Bathymetry

2024-11-26T10:08:27Z

Ddamaske:

== Page content (please note) ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]]

Please note, '''bathymetry data curation SOPs''' in PANGAEA with respect to '''FAIR data principles''' (https://doi.org/10.1038/sdata.2016.18) are revised within the scope of of the German Marine Research Alliance (DAM) Underway Research Data project (https://www.allianz-meeresforschung.de/). This page and the information provided here is addressed to PANGAEA users and data submitter's. [https://wiki.pangaea.de/wiki/Metaheader '''PANGAEA's Metaheader'''] explicitly for bathymetry datasets and other data curation requirements are explained on this page. In addition, data management at PANGAEA and requirements for bathymetry data submission to PANGAEA are documented. 
This page is mainly made for bathymetry data from multibeam echosounder data (MBES), however can also be used for data from Satellite derived bathymetry (SDB) or ''Light Detection and Ranging (LIDAR)'' data. 
'''Please note, that this page may still be revised in the future. '''
 

== DAM Underway Research Data project background ==

The '''German Marine Research Alliance (DAM)''' is a combined effort to exploit the full potential of German research vessels as mobile measuring platforms and currently involves 24 institutions and research facilities in Germany. The Underway Research Data project is part of DAM core area ''data management and digitalization'' (https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation/).

[[Image:DAM_Logo_small.png| thumb | right |250px| https://www.allianz-meeresforschung.de/en/]]

Please note for the German research vessels RV POLARSTERN, RV METEOR, RV MARIA S. MERIAN & RV SONNE there is no need to upload the data if data are (usually) less than 2 years old. We’ll then take the data form the DSHIP ''Mass Data Management System (MDM)'' and prepare your dataset. Please mentioned in you submission in the comment; please take data from DSHIP ''Mass Data Management System (MDM)'' 
 
 
 
 

== PANGAEA Bathymetry Web Map & Feature services ==

'''All submitted bathymetry data''' (raw data & processed data) are being semi-automatically processed at PANGAEA. '''Tracklines and coverage polygones (footprint)''' of all submitted bathymetry data are extracted from the data and '''added to the Viewer of the Marine Data Portal''' https://marine-data.org/ (direct link to the viewer https://marine-data.de/?site=viewer),
if data have a '''CC BY 4.0''' (or CC-ZERO) data license. If '''data are not under a moratorium period''', also a '''raster image''' is being calculated and '''added'''. Here, the (meta-)data can be explored (and are linked to the DOI). These vector & raster data are also available through OGC Web Map services. https://maps.awi.de/services/common/pangaea_bathymetry/wms and Web Feature Service [https://maps.awi.de/services/common/pangaea_bathymetry/wms https://maps.awi.de/services/common/pangaea_bathymetry/wfs] (please note, this is not a webpage, you need e.g. a GIS to use this service). 
Further information can be found [https://wiki.pangaea.de/wiki/PANGAEA_Bathymetry_Web_Map_Services '''here'''].

== ''Standardized content of datasets'' ==
To make data '''findable''' (F) and due to PANGAEAs archiving '''SOP'''s, bathymetry datasets from multibeam echosounders will be separated into two datasets (when stored in separate files), if the water column data is simultaneously being recorded during data acquisition (e.g. .wcd files from Kongsbergs MBES Systems) . This is necessary due to data curation processes, consequently reducing the download volume if it is intended to download only bathymetry data from PANGAEA. The water column data are usually much larger than regular bathymetry files. However, both datasets will be connected / linked to each other, making it easy to find the corresponding dataset.

=== Standardized ''language'' ===
To make data FAIR, “to speak” a common language is required. PANGAEA specifically uses for bathymetry data the Natural Environment Research Council's Data (NERC) Catalogue for describing data.
https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/
https://vocab.seadatanet.org/search

== Standardized ''Metaheader'' ==

=== Standardized ''Authors'' ===

The Authorship of national (German research) datasets are revised with respect to the ''Guidelines for Safeguarding Good Research Practice'' of the ''German Research Foundation'' http://doi.org/10.1002/9783527679188.oth1 . Although it is not generally agreed on, usually the authorship is given to anyone who was significantly involved in data acquisition on board or post-processing on land:

For raw data of German research vessels which are published at PANGAEA, it is very common to include the responsible scientific team on board, including all scientist (including student assistants) who were involved in monitoring, detailed survey planning or performing the survey. This can be considered as a genuine, identifiable contribution to the content of the research data, therefore fulfilling the requirements for authorship's according the ''Guidelines for Safeguarding Good Research Practice''. When no other main responsible scientist for the e.g. multibeam device was on board (also responsible to allows the data publication at PANGAEA in the first place), usually the first authorship is provided to the chief scientist (the chief scientist is usually the one person who has to allow the data publication). Credit may be given to the personal in the comment metadata field, who was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list

For processed data of German research vessels which are published at PANGAEA, the authorship is generally only given to the person, who was working (processing) the data. Avoid to include person, which were only involved in the raw data acquisition (the scientific credit is usually provided in the corresponding raw dataset).

Since this common practice mostly apply to PANGAEA dataset of German Research vessels, PANGAEA recommend to follow this common practice if you are submitting datasets other than German Research vessels related data.

=== Standardized ''Title'' ===
To ensure the '''reusability''' (R) and '''interoperability''' (I) of datasets, metadata of similar datasets such as bathymetry data gathered from similar research missions, research vessels or research platforms should follow a common template and a common vocabulary (Generally speaking; they should look alike!). This also includes the title. Therefore, the title of bathymetry data which are entrusted to PANGAEA shall follow a certain template ''“construction kit”''. This ''“construction kit”'' was developed within the DAM efforts (Project Underway Research Data). It includes the feedback of several German scientists from different institutions, PANGAEA bathymetry data submitters & data management personal. Key elements of each dataset title are incorporated, such as data type, device, platform type, platform, cruise (& area). To guarantee and fulfil FAIR standards, PANGAEA is encouraging data submitters to follow this template (also covering none German research data). To follow these standards is mandatory for all PANGAEA datasets. 
 
Example: 
''Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM55'' 
''Multibeam bathymetry raw data (Kongsberg EM 122 working area dataset) of RV METEOR during cruise M127, Fictional Bank canyon, North Atlantic Ocean'' 
 
The ''“construction kit”'' - incorporating all feedback - is shown below.:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! (device according to L22 vocabulary "Alt label" (NERC*) !! select: !! of !! select platform type: !! platform name (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| Multibeam bathymetry || raw data || || entire dataset) || " || RV || || " || || ||
|-
| Sidescan sonar || processed data || || transit dataset) || " || AUV || || " || || ||
|-
| Water column || || || working area dataset) || " || ROV || || " || || ||
|-
| || || || working area dataset, Generic sensor format) || " || ROV || || " || || ||
|-
| || || || dataset compilation)* || " || || || " || || ||
|-
| || || || *only for processed data || " || || || " || || ||
|}
Further information about the entries can be found here:
{| class="wikitable" style="font-size: 86%;"
! (device according to L22 vocabulary "Alt label" (seadatanet) !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| *http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=L22 || https://www.gebco.net/data_and_products/undersea_feature_names/ || https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
||| https://www.marineregions.org ||
|}
'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! Multibeam bathymetry !! raw data !! (Kongsberg EM 122 !! working area dataset) !! of !! RV !! SONNE !! during cruise !! SO250 !! Loyd Dill Seamount, !! South Pacific Ocean
|-
| Multibeam bathymetry || raw data || (Atlas Hydrosweep DS 3 echo sounder || transit dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| Multibeam bathymetry || raw data || (R2Sonic SONIC 2024 || entire dataset) || of || AUV || ABYSS || during cruise || MSM50 || ||
|-
| Multibeam bathymetry || processed data || (Kongsberg EM 122 || entire dataset) || of || RV || METEOR || during cruise || M74 || ||
|-
| Multibeam bathymetry || processed data || (EM 120 echosounder || dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| Water column || raw data || (Kongsberg EM710 || entire dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || || ,South Pacific Ocean
|}

=== Standardized ''Abstract'' ===
Intending to make data more ''FAIR,'' PANGAEA requires a compact ''Abstract'' for each dataset. For more information regarding abstracts, see https://wiki.pangaea.de/wiki/Abstract. 
Please note that cruise summary reports or other reference must not be cited exclusively in the abstract because references are also included in the metaheader (references) of the dataset. However, to provide credit and cite e.g. raw data if processed data are submitted to PANGAEA, you might add to the abstract: "Raw data for this study were published by (Authors, YYYY)." (followed by the full citation of the dataset in the list of references). If reference shall be linked, please inform the data editor. 
If you would like to provide other contact information related to this dataset (e.g. Email address), please inform the data editor. 
Please specify in the abstract whether sound velocity profiles are part of the raw dataset publication or not. Comparatively for processed data publications, please describe your processing steps (further, see below and examples).

For processed data please describe whether:
*depth measurements manually cleaned from errors during processing?
*sound velocity profile correction applied during processing?
*navigation correction applied during processing?
*tide correction applied during processing?
*horizontal datum, EPSG code from raster data in this publication are?
For raw data please describe whether:
*sound velocity profile correction applied during acquisition?
*are ancillary sound velocity profiles part of this data publication?
*which device recorded the data, which ship, which cruise?
*why have the data being recorded?

==== Raw data (example) ====

Multibeam bathymetry raw data using the ship's own Kongsberg EM 122 multibeam echosounder was not continuously recorded during RV MARIA S. MERIAN cruise MSM97/2. Data were recorded on 3 days between 2020-12-16 and 2020-12-19 in the Norwegian Sea and data acquisition was almost continuously monitored during the survey. Previous to the survey, gaps in already existing database were identified using the General Bathymetric Chart of the Oceans (GEBCO 2020) Type Identifier (TID) grid. These gaps were used as a base to determine the course of the ship during the cruise. During data acquisition, sound velocity measurements using sound velocity profiles (SVP) derived from CTD casts was applied on the data for data calibration. Ancillary SVP raw data (.asvp files) and SVP from CTD-cast (.txt) are part of this dataset publication.
Data are unprocessed and therefore contain incorrect depth measurements without further processing. Data can be processed e.g. with the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021). 
''(FEEL FREE TO ADD MORE INFORMATION)''

==== Processed data (example) ====
Swath sonar bathymetry data used for that dataset was recorded during RV SURVEY during cruise S143 using Kongsberg EM 122 multibeam echosounder. The cruise took place between 2016-12-12 and 2011-12-23 in the North Atlanic Ocean. Data were recorded on 8 days between 2011-12-15 and 2011-12-23. The approximate average depth of the entire dataset is around 1500m. 
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic. After processing, these data were directly imported into the MBES Acquisition software Kongsberg SIS Seafloor Information System. Raw data were converted to MB-System format. Data were manually edited for false measurements. No further artificial sound velocity profiles were used during further processing. The data were corrected for tidal changes using data provided by the OSU Tidal Prediction Software
OTPS that is retrievable through MB-System. The vertical datum of the data is now matched to ''mean sea level (MSL)''. A raster was calculated and stored in GeoTIFF format with a 25m resolution (negative values). In addition, the full resolution of avilable ASCII data and used for grid calculation are also archived in this dataset. 
''(FEEL FREE TO ADD MORE INFORMATION)''

=== Standardized usage of ''Reference'' ===
Typically, processed datasets, which are all based of the same raw dataset (also archived in PANGAEA), are submitted to PANGAEA. These datasets will be linked to each other as a ''Reference''
Currently, all bathymetry datasets already archived in PANGAEA are reviewed and checked for relations. If a relationship is found, a linkage between both datasets is being created and is shown as ''Related to''. More information can be found here https://wiki.pangaea.de/wiki/Reference

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from ''Events'' or PANGAEA ''GEOCODE'' (see below): https://wiki.pangaea.de/wiki/Metaheader. Please note, that ''Minimum Elevation'' und ''Maximum Elevation'' does not represent min / max depth values measured from MBES data contained in this dataset. It is rather in this case the reference height on earth from the instrument used for the measurements. 
Note: Currently, the ''Coverage'' will be visible on PANGAEA website with points having an ''GoogleMaps'' image in the background (right upper corner). It does not show the actual coverage of the surveyed area. The visible points are, instead, representing the ''Events'' (see below).

=== Standardized usage of ''Events'' ===
Bathymetry datasets contain so called PANGAEA ''Events'' (https://wiki.pangaea.de/wiki/Event). The Event links to the scientific ''Campaign'', Method/Device and ''Basis'' (platform) containing further additional information. Please note that, if you browse with your mouse cursor on ''Campaign'', Method/Device or ''Basis'', a field will pop up (do not click). In some datasets, it is possible to click on these fields and a link with detailed information will be provided.
 Further information for Bathymetry related events is given below. 

==== ''Underway event'' ====
(update of this section is in progress) 

For bathymetry data from multbeam echosounders, a so called ''"Underway"'' ''Event'' is created on board of the research vessel. The ''"Underway"'' ''Event'' is named ''CruiseID_0_Underway-number(undefined, )'' e.g. ''M127_0_Underway-1''. The event shows the starting and end point (coordinates & datetime) of the first and last data record of the MBES device acquired during the cruise. Also, the ''Methods/device'' used to record the data is included for Event description. Please note, that PANGAEA specific vocabulary is used here. Providing further detailed information using standard common vocabulary such as the NERC catalogue (https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/) is currently being prepared (more information is provided as soon as possible.....). 
If available, an additional link to the Sensor description hosted on https://registry.awi.de is provided. 

If the dataset is compilation of many datasets (only possible for processed data), several ''"Underway"'' ''Events'' will be used. 
Note, that the prefix of the ''Event'' name contains the official cruise ID (cruise label, e.g. https://www.pangaea.de/expeditions/bybasis/Meteor%20%281986%29), not the campaign name. The suffix number does not follow any specific rule, as this number is usually chronologically created on board, which is why the numbering can differ from cruise to cruise. 

==== ''SVP casts and event(s)'' ====

If ''SVP casts'' (sound velocity profile measurements using an external device, e.g. using an ''AML Oceanographic Plus X sound velocity probe'') or CTD casts (sound velocity derived from CTD measurements) were performed during the cruise, the acquired data files (and used for import to the acquisition software, e.g. the ''Kongsberg Seafloor Information'', SIS) will be stored in the same raw dataset. The corresponding event of the ''Event list'' of the cruise (e.g. https://www.pangaea.de/expeditions/events/M160) will be linked to these files. This ''Event'' will contain similar information as described above, e.g. ''coordinates'', ''methods/devices'', ''etc.''. If SVP's are used for data post-processing (sound velocity correction), these data files can also be submitted to PANGAEA. If possible, these SVP can be linked to the corresponding ''Event''. In general, please always try to describe your submitted SVPs as good as possible for scientific re-use (state the origin of data, whether data are extrapolated e.g. to 12000m, etc.).
You can use the following '''[http://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/Template_PANGAEA_SUBMISSION_bathymetry_processed_V4.xlsx template]''' to support your submission.

=== Standardized usage of ''Parameter and data formats'' ===

Which [https://wiki.pangaea.de/wiki/Parameter PANGAEA parameter] for bathymetry datasets will be used & added to the data files, depend on whether raw or processed data are being submitted.

==== Raw data curation ====

Standard parameters for bathymetry raw data also include PANGAEA’s so called [https://wiki.pangaea.de/wiki/Geocode Geocodes]. These are standard important parameters, which are mandatory to keep the data georeferenced. '''These metadata for each file will be automatically created while data curation process''' Metadata are extracted using the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2023) when data format is supported by MB-System. 

{| class="wikitable"
|-
! Name!! Short Name !! Unit !! Comment
|-
| [https://wiki.pangaea.de/wiki/Event Event label] || Event || ||
|-
| [https://wiki.pangaea.de/wiki/Binary_object Binary Object] || Binary|| || *this will in PANGAEA download URL
|-
| [https://en.wikipedia.org/wiki/Media_type Binary Object (Media Type)] || Binary (Type) |||| *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || Bytes || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || || *automated entry during data curation process
|-
| [https://epic.awi.de/id/eprint/29970/ Kongsberg datagram raw file name] || Datagram rfn || || *only for data from EM Series
|-
| File content || Content || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording duration] || Data record duration || min||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording distance]|| Data record distance || m ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Ship speed]|| Ship sp|| knots ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Number of pings]|| Pings|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, date/time]|| File start date/time || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, latitude] || File start latitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, longitude] || File start longitude|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, heading] || Start heading || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, depth] || Start depth || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, date/time] || File stop date/time|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, latitude] || File stop latitude ||||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, longitude] || File stop longitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, heading]|| Stop heading|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, depth]|| Stop depth|| ||
|-
| DATE/TIME || Date/Time || || *Geocode – copy of 'Start of data file recording, date/time'
|-
| LATITUDE|| Latitude || || *Geocode – copy of 'Start of data file recording, latitude'
|-
| LONGITUDE || Longitude|| || *Geocode – copy of 'Start of data file recording, longitude'
|-
| ELEVATION || Elevation || || *Geocode – copy of 'File start depth, change of sign'
|-
| Comment || Comment || ||
|}
 
Please note, if you do have ancillary data, such as ''operational logs'' created on board or detailed ''processing reports'', please add those files to the submission.

==== Processed data curation ====
Standard important parameters extracted from raster data (and ASCII data), which are mandatory to keep the data georeferenced, will be attached automatically. Please note that ASCII however are not recommended for further reuse. 
Feel free to upload bathymetry data, backscatter and/or a sidescan data, in raster (and/or ACSII) format (+ .xyz point cloud data, see below). In general, for raster data GeoTiff files (*.tif) and the grid data format (*.grd) is always preferred, since these data are usually easy to reuse, having less projection issues using standard GIS software. Please indicated whether depth values of the grid cells (also for ASCII data) contain positive or negative values (e.g. elevation / this can be indicated in the file content description). In generel you can submit any projection of the raster image, however if you do so please always add an additional GeoTiff at best with the projection [https://epsg.io/4326 '''WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326''']. Also here, try in include the projection in the raster file. Please make sure, if you provide a “bathymetry” raster data, that they contain depth information rather than just an georeferenced image with RGB values (and image is not considered as data). To submit raster images with RGB values is also fine, however they do not represent an resuable data format. In that case, always provide an raster file with true depth information (same coverage). Most dataset in PANGAEA have negative values for depth (= elevation), so we recommend to convert your data accordingly. 
If you want to '''upload xyz files (point cloud data)''' to PANGAEA, you are welcome to do so. However, please also '''upload an auxiliary gridded raster image for each individual xyz (point cloud data) data file'''. In general raster data are more user-friendly (e.g. by using GIS systems), therefore raster images are of high value for scientist. '''Raster images are considered as a (FAIR) interoperable data format, highly supporting the [https://www.go-fair.org/fair-principles/r1-3-metadata-meet-domain-relevant-community-standards/ resuablity] of data by scientists, especially from other scientific domains'''. Raster image and point cloud data (xyz) will be published using the same doi.
 
Parameters for raster data are listed below (these parameter do not apply for GSF or MB-System data files. GSF or MB-System data files will get the same parameters as for raw data, see above ):

{| class="wikitable"
|-
! Name!! Short Name !! Value/unit !! Comment
|-
| Event label || Event || - || *automated entry during data curation process
|-
| Binary Object || Binary|| || *this will in PANGAEA download URL
|-
| Binary Object (Media Type) || Binary (Type) || - || *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || - || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || - || *automated entry during data curation process
|-
| [https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/cell-size-of-raster-data.htm Raster cell size] || Raster cell size || || * raster cell size, e.g. 100m *only for raster data *if possible in meters
|-
| File content || Content || || * data description, e.g. bathymetry / negative values in meters for depth measurements (= elevation) / GeoTIFF raster image, Float32, DEFLATE compression / *feel free to add a comment specifically referring this data file
|-
| [http://vocab.nerc.ac.uk/collection/V12/current/L11/ Vertical datum]|| Vertical datum|| || * e.g. mean sea level
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum]|| Horizontal datum|| || * e.g. WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum, projection stored in file]|| Horizontal datum in file || || * e.g. EPSG:4326 (some files may not have the raster projection stored in itself)
|-
| Longitude, westbound|| Longitude west|| ||
|-
| Longitude, eastbound|| Longitude east|| ||
|-
| Latitude, southbound|| Latitude south || ||
|-
| Latitude, northbound ||Latitude north|| ||
|-
| Soundings || Soundings || || *only for xyz data / *not for backscatter data / *currently under development (not always included)
|-
| Area ||Area || km² || *currently under development (not always included)
|-
| Elevation, Minimum ||Elev min|| m a.s.l. || *not for backscatter data
|-
| Elevation, Maximum ||Elev max|| m a.s.l. || *not for backscatter data
|}

=== Standardized usage of ''Comment'' ===
Bathymetry raw and processed data, which are acquired on scientific vessels, might contain erroneous depth values and/or data artifacts. These data shall never be used for navigational purposes involving safety at sea. For safety reasons, it is widely common to state this explicitly: The comment ''These data should not be used for navigational purposes'' will be '''automatically included as a comment''' on each bathymetry dataset in PANGAEA. Please also check the PANGAEA data policy for more information: https://wiki.pangaea.de/wiki/Data_policy (page currently under construction). Bathymetry data for official nautical chart production must explicitly fulfill the requirements of the International Hydrographic Organisation (IHO) https://iho.int/.
In addition the comment may give credit to personal who was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list.
=== ''Licence'' ===
PANGAEA and DAM are encouraging data submitters to submit bathymetry data under [(https://creativecommons.org/licenses/by-nc/4.0/) '''CC-BY 4.0'''] License terms, which allows sharing (copying and redistributing the material in any medium or format) and adapting (remixing, transforming, and building upon the material) the data. In this way, PANGAEA / DAM can also make the data coverage (footprint) and the trackline visible with a direct link to PANGAEA at https://marine-data.de/ . Note, within the DAM efforts, coverage (footprint) and trackline off all submitted bathymetry data will be made available to the community via OGC Web Map Services (WMS) and OGC Web Feature Services (WFS) . Avoid licence CC-0 & CC-BY-SA, if possible.

Which CC license choose for data? Check also [https://wiki.pangaea.de/wiki/License here]

=== (Standardized usage of ''Data model extensions)'' (for raw and processed data curation) ===

The usage of so-called ''data model extensions'' which are further ''attributes'' is currently developed. This is a new feature for PANGAEA in order to include more standardized metadata. This new feature shall insure further '''findabilty''' (F) and '''interoperability'''(I) of the datasets (more information is provided as soon as possible.....).

== Example datasets ==

=== Raw data ===

Damaske, Daniel; Becker, Marius (2021): Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV MARIA S. MERIAN during cruise MSM97/2. PANGAEA, https://doi.pangaea.de/10.1594/PANGAEA.927786

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+raw+data+(%22

=== Processed data ===
Simkins, Lauren M; Greenwood, Sarah L; Munevar Garcia, Santiago; Eareckson, Elizabeth; Anderson, John B; Prothro, Lindsay O (2021): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset) of RVIB NATHANIEL B. PALMER during cruise NBP150-02. PANGAEA, https://doi.org/10.1594/PANGAEA.937597, In: Simkins, LM et al. (2021): Pennell Trough, Ross Sea bathymetry and glacial landforms. PANGAEA, https://doi.org/10.1594/PANGAEA.937602

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data+(%22

Generic sensor format (GSF) data:

Dufek, Tanja; Schniotalla, Cara; Kinne, Stefan; Sternberg, Harald (2023): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset, Generic sensor format) of RV SONNE during cruise SO268/3, North Pacific Ocean. PANGAEA, https://doi.org/10.1594/PANGAEA.957204

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data%22+AND+citation%3Atitle%3A%22Generic+Sensor+format%22

== How to submit bathymetry data to PANGAEA and what to do? ==

Please submit bathymetry data here https://www.pangaea.de/submit/. During submission, you may have to provide information for the data curation process (e.g. cruise, device, etc). For your submission, please edit/modify the title & abstract as stated above ("title construction kit").

'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]

For raw data:

Usually for raw data, an upload area will be created for you where you can drop your files (on request). Feel free to drop your data as zip- or individual files. Please also include sound velocity profiles (only SVP raw data, e.g. MSM88_2-1_0.asvp) for raw data submission if available. Your files should not exceed a volume of 10GB, however several files can be uploaded simultaneously. Please avoid renaming of raw data files, even if they are imperfect.
If raw data from '''RV Sonne''', '''RV Maria S. Merian''', '''RV Polarstern''' or '''RV Meteor''' are being submitted, '''please make a comment in your submission before you upload any multibeam echosounder raw data files (e.g. .all format)'''. Please leave a comment: '''''please take data from DSHIP Mass Data Management System (MDM)'''''.

For processed data:

Just drop your files after you get your upload link (see requirements above). If additional SVP's have been used for data processing, you can also upload these files too. 

===PANGAEA Data Submission Form Example===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]please note that the table below show's the simplified data submission workflow. The data submission form can be accessed here https://www.pangaea.de/submit/<nowiki/>Further information can also be found here [[Data submission]] .
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Title
|Adapted, generalized [[#Standardized_Title]]
|Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV SONNE during cruise SO250
|-
|Author(s)
|[[#Standardized_Authors]]
|[chief scientist], [responsible scientist(s)]
|-
|Keywords
|
|''(default)''
|-
| Abstract/Describe your Data
|[[#Standardized_Abstract]]; if the processed or raw data were already archived, the links may be placed here
|The survey data contain MBES measurements of the Fictional Bank canyon. No bathymetric measurements of Fictional Bank canyon were found in international databases prior to the cruise.
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic SVP Plus X. After processing, these data were directly imported into the MBES acquisition software Kongsberg SIS Seafloor Information System.
|-
| License
|[[#Licence]] 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 the 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).
|[https://creativecommons.org/licenses/by/4.0/ 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
|Files containing metadata information for the data
|
|}

PANGAEA Bathymetry Web Map Services

2024-11-13T15:02:24Z

Ddamaske:

{{construction}}
Page content may change in future (current status: 13.11.2024)

= PANGAEA Bathymetry Web Map and Feature Service =

This new '''PANGAEA Bathymetry Web Map and Feature Service''' https://www.ogc.org/standards/wms/introduction (first release 2021) contains bathymetry data archived at PANGAEA (including only data with a CC-BY 3.0 or CC-BY 4.0 license). This service is developed as part of the '''German Marine Research Alliance''' in the core area '''"Data management and Digitalization"''' ('''Deutsche Allianz Meeresforschung, DAM''' https://www.allianz-meeresforschung.de/en/).
Note that not all bathymetry data currently archived in PANGAEA are visualized through this service. However, the number of datasets will be continuously increased in the future. As of now, only raw & processed data from multibeam echosounder measurements are incorporated in this service (further developments are in progress).
'''Please acknowledge that each layer of this service contains further usage requirements (e.g. citation rules) provided in the abstract (see [[PANGAEA_Bathymetry_Web_Map_Services#Layer_Abtracts|below]])'''. Data visualized in this service shall not be used for navigational purposes. 
For feedback & questions please contact PANGAEA. https://www.pangaea.de/contact/ 
This web map service is accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wms''' This web feature service is still considered a beta version and accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wfs'''

Each incorporated PANGAEA dataset in this service contains a vast amount of dataset-specific individual metadata. If you consider incorporating this service (data layers) into any front-end application (e.g., a web-based data portal), please also make the incorporated metadata of each layer available and visible to the user. 
Please note that a Geographic Information System (GIS) (e.g. QGIS https://qgis.org/ ) is required to access this service. However, data of this service can also be explored using the '''Viewer''' https://marine-data.de/?site=viewer of the '''Data Portal German Marine Research''' https://marine-data.de/. (see also below)

Further information about development and usage requirements are documented in Damaske et al. (2024). Generally cite the service also with:

* Damaske, D., Selke, N., & Balamurugan, A. (2024). PANGAEA Bathymetry Web Map & Feature Service – Standard Operating Procedures visualizing bathymetry data archived in PANGAEA - Data Publisher for Earth & Environmental Data. Zenodo. https://doi.org/10.5281/zenodo.8296986

== Data Contribution ==

To facilitate incorporating PANGAEA data to this service, please note the detailed information about '''bathymetry data submissions to PANGAEA''' [https://wiki.pangaea.de/wiki/Bathymetry '''here'''].

== Layer Overview ==
Currently only data layers originating from multibeam echosounder data are available in the service (see list below). For detailed information check the abstract of each corresponding data layer.

'''Raw data:'''
*PANGAEA Water Column Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Footprints
*PANGAEA Multibeam Raw Data Footprints Simplified
*PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional)
'''Processed data:'''
*PANGAEA Multibeam Processed Data Footprints
*PANGAEA Multibeam Processed Data Footprints Simplified
*PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional)

== Layer Abstracts ==
directly embedded into the service:
https://maps.awi.de/services/common/pangaea_bathymetry/wms?service=WMS&request=GetCapabilities
<nowiki>*</nowiki>Abstract update 21.08.2024 (note, that currently more layers are available. Update on this will follow soon)
{| class="wikitable" style="font-size: 86%;"
! Layer name (technical name) !! Layer title !! Abstract (embedded in service)
|-
| mbes_raw_acquisition_tracklines_wcd_4326 || PANGAEA Water Column Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_acquisition_tracklines_4326 || PANGAEA Multibeam Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_4326 || PANGAEA Multibeam Raw Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_simplified_4326 || PANGAEA Multibeam Raw Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_bathymetry_8000_haxby_multidirectional_4326 || PPANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_4326 || PANGAEA Multibeam Processed Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_simplified_4326 || PANGAEA Multibeam Processed Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_8000_haxby_multidirectional_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|}

 Available metadata

A list of currently available metadata:
*Please see here: https://doi.org/10.5281/zenodo.8296986

== Known incorporated web based data portals ==
This service is incorporated in the following data portals::
*[https://marine-data.de/?site=viewer Viewer of the Data Portal German Marine Research]
*[https://www.ncei.noaa.gov/maps/iho_dcdb/ IHO Data Centre for Digital Bathymetry (DCDB)]
....more information will be provided......

Sediment echosounder

2024-10-17T07:40:23Z

Ddamaske: /* How to submit sediment echosounder data to PANGAEA and what to do? */

Bathymetry

2024-10-17T07:40:22Z

Ddamaske: /* How to submit bathymetry data to PANGAEA and what to do? */

== Page content (please note) ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]]

Please note, '''bathymetry data curation SOPs''' in PANGAEA with respect to '''FAIR data principles''' (https://doi.org/10.1038/sdata.2016.18) are currently revised within the scope of of the German Marine Research Alliance (DAM) Underway Research Data project (https://www.allianz-meeresforschung.de/). This page and the information provided here is adressed to PANGAEA users and data submitters. [https://wiki.pangaea.de/wiki/Metaheader '''PANGAEA's Metaheader'''] explicitly for bathymetry datasets and other data curation requirements are explained on this page. In addition, data management at PANGAEA and requirements for bathymetry data submission to PANGAEA are documented. 
This page is mainly made for bathymetry data from multibeam echosounder data (MBES), however can also be used for data from Satellite derived bathymetry (SDB) or ''Light Detection and Ranging (LIDAR)'' data. 
'''Please note, that this page may still be revised in the future. '''
 

== DAM Underway Research Data project background ==

The '''German Marine Research Alliance (DAM)''' is a combined effort to exploit the full potential of German research vessels as mobile measuring platforms and currently involves 24 institutions and research facilities in Germany. The Underway Research Data project is part of DAM core area ''data management and digitalization'' (https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation/).

[[Image:DAM_Logo_small.png| thumb | right |250px| https://www.allianz-meeresforschung.de/en/]]

Please note for the German research vessels RV POLARSTERN, RV METEOR, RV MARIA S. MERIAN & RV SONNE there is no need to upload the data if data are (usually) less than 2 years old. We’ll then take the data form the DSHIP ''Mass Data Management System (MDM)'' and prepare your dataset. Please mentioned in you submission in the comment; please take data from DSHIP ''Mass Data Management System (MDM)'' 
 
 
 
 

== PANGAEA Bathymetry Web Map & Feature services ==

'''All submitted bathymetry data''' (raw data & processed data) are being semi-automatically processed at PANGAEA. '''Tracklines and coverage polygones (footprint)''' of all submitted bathymetry data are extracted from the data and '''added to the Viewer of the Marine Data Portal''' https://marine-data.org/ (direct link to the viewer https://marine-data.de/?site=viewer),
if data have a '''CC BY 4.0''' (or CC-ZERO) data license. If '''data are not under a moratorium period''', also a '''raster image''' is being calculated and '''added'''. Here, the (meta-)data can be explored (and are linked to the DOI). These vector & raster data are also available through OGC Web Map services. https://maps.awi.de/services/common/pangaea_bathymetry/wms and Web Feature Service [https://maps.awi.de/services/common/pangaea_bathymetry/wms https://maps.awi.de/services/common/pangaea_bathymetry/wfs] (please note, this is not a webpage, you need e.g. a GIS to use this service). 
Further information can be found [https://wiki.pangaea.de/wiki/PANGAEA_Bathymetry_Web_Map_Services '''here'''].

== ''Standardized content of datasets'' ==
To make data '''findable''' (F) and due to PANGAEAs archiving '''SOP'''s, bathymetry datasets from multibeam echosounders will be separated into two datasets, if the water column data (e.g. wcd files from Kongsbergs MBES Systems) is simultaneously being recorded during data acquisition. 
This is necessary due to data curation processes, consequently reducing the download volume if it is intended to download only bathymetry data (containing only the seafloor reflector information) from PANGAEA. The water column data are usually much larger than regular bathymetry files (e.g. .all). However, both datasets will be connected / linked to each other, making it easy to find the corresponding dataset).

=== Standardized ''language'' ===
To make data FAIR, “to speak” a common language is required. PANGAEA specifically uses for bathymetry data the Natural Environment Research Council's Data (NERC) Catalogue for describing data.
https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/
https://vocab.seadatanet.org/search

== Standardized ''Metaheader'' ==

=== Standardized ''Authors'' ===

The Authorship of (national/German) datasets is currently revised with respect to the ''Guidelines for Safeguarding Good Research Practice'' of the ''German Research Foundation'' http://doi.org/10.1002/9783527679188.oth1 . 
Although it is not generally agreed on, usually the authorship is given to anyone who was significantly involved in data acquisition on board or post-processing on land. 
For German research vessels raw data (archived in PANGAEA), it is very common to include the responsible scientific team on board, including all scientist (including student assistants) who were involved in monitoring, detailed survey planning or performing the survey (only raw data). This can also be considered as a genuine, identifiable contribution to the content of the research data, therefore fulfilling the requirements for authorship's according the ''Guidelines for Safeguarding Good Research Practice''.

=== Standardized ''Title'' ===
To ensure the '''reusability''' (R) and '''interoperability''' (I) of datasets, metadata of similar datasets such as bathymetry data gathered from similar research missions, research vessels or research platforms should follow a common template and a common vocabulary (Generally speaking; they should look alike!). This also includes the title. Therefore, the title of bathymetry data which are entrusted to PANGAEA shall follow a certain template ''“construction kit”''. This ''“construction kit”'' was developed within the DAM efforts (Project Underway Research Data). It includes the feedback of several German scientists from different institutions, PANGAEA bathymetry data submitters & data management personal. Key elements of each dataset title are incorporated, such as data type, device, platform type, platform, cruise (& area). To guarantee and fulfil FAIR standards, PANGAEA is encouraging data submitters to follow this template (also covering none German research data). To follow these standards is mandatory for all PANGAEA datasets. 
 
Example: 
''Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM55'' 
''Multibeam bathymetry raw data (Kongsberg EM 122 working area dataset) of RV METEOR during cruise M127, Fictional Bank canyon, North Atlantic Ocean'' 
 
The ''“construction kit”'' - incorporating all feedback - is shown below.:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! (device according to L22 vocabulary "Alt label" (NERC*) !! select: !! of !! select platform type: !! platform name (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| Multibeam bathymetry || raw data || || entire dataset) || " || RV || || " || || ||
|-
| Sidescan sonar || processed data || || transit dataset) || " || AUV || || " || || ||
|-
| Water column || || || working area dataset) || " || ROV || || " || || ||
|-
| || || || working area dataset, Generic sensor format) || " || ROV || || " || || ||
|-
| || || || dataset compilation)* || " || || || " || || ||
|-
| || || || *only for processed data || " || || || " || || ||
|}
Further information about the entries can be found here:
{| class="wikitable" style="font-size: 86%;"
! (device according to L22 vocabulary "Alt label" (seadatanet) !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| *http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=L22 || https://www.gebco.net/data_and_products/undersea_feature_names/ || https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
||| https://www.marineregions.org ||
|}
'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! Multibeam bathymetry !! raw data !! (Kongsberg EM 122 !! working area dataset) !! of !! RV !! SONNE !! during cruise !! SO250 !! Loyd Dill Seamount, !! South Pacific Ocean
|-
| Multibeam bathymetry || raw data || (Atlas Hydrosweep DS 3 echo sounder || transit dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| Multibeam bathymetry || raw data || (R2Sonic SONIC 2024 || entire dataset) || of || AUV || ABYSS || during cruise || MSM50 || ||
|-
| Multibeam bathymetry || processed data || (Kongsberg EM 122 || entire dataset) || of || RV || METEOR || during cruise || M74 || ||
|-
| Multibeam bathymetry || processed data || (EM 120 echosounder || dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| Water column || raw data || (Kongsberg EM710 || entire dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || || ,South Pacific Ocean
|}

=== Standardized ''Abstract'' ===
Intending to make data more ''FAIR,'' PANGAEA requires a compact ''Abstract'' for each dataset. For more information regarding abstracts, see https://wiki.pangaea.de/wiki/Abstract. 
Please note that cruise summary reports or other reference must not be cited exclusively in the abstract because references are also included in the metaheader (references) of the dataset. However, to provide credit and cite e.g. raw data if processed data are submitted to PANGAEA, you might add to the abstract: "Raw data for this study were published by (Authors, YYYY)." (followed by the full citation of the dataset in the list of references). If reference shall be linked, please inform the data editor. 
If you would like to provide other contact information related to this dataset (e.g. Email address), please inform the data editor. 
Please specify in the abstract whether sound velocity profiles are part of the raw dataset publication or not. Comparatively for processed data publications, please describe your processing steps (further, see below and examples).

For processed data please describe whether:
*depth measurements manually cleaned from errors during processing?
*sound velocity profile correction applied during processing?
*navigation correction applied during processing?
*tide correction applied during processing?
*horizontal datum, EPSG code from raster data in this publication are?
For raw data please describe whether:
*sound velocity profile correction applied during acquisition?
*are ancillary sound velocity profiles part of this data publication?
*which device recorded the data, which ship, which cruise?
*why have the data being recorded?

==== Raw data (example) ====

Multibeam bathymetry raw data using the ship's own Kongsberg EM 122 multibeam echosounder was not continuously recorded during RV MARIA S. MERIAN cruise MSM97/2. Data were recorded on 3 days between 2020-12-16 and 2020-12-19 in the Norwegian Sea and data acquisition was almost continuously monitored during the survey. Previous to the survey, gaps in already existing database were identified using the General Bathymetric Chart of the Oceans (GEBCO 2020) Type Identifier (TID) grid. These gaps were used as a base to determine the course of the ship during the cruise. During data acquisition, sound velocity measurements using sound velocity profiles (SVP) derived from CTD casts was applied on the data for data calibration. Ancillary SVP raw data (.asvp files) and SVP from CTD-cast (.txt) are part of this dataset publication.
Data are unprocessed and therefore contain incorrect depth measurements without further processing. Data can be processed e.g. with the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021). 
''(FEEL FREE TO ADD MORE INFORMATION)''

==== Processed data (example) ====
Swath sonar bathymetry data used for that dataset was recorded during RV SURVEY during cruise S143 using Kongsberg EM 122 multibeam echosounder. The cruise took place between 2016-12-12 and 2011-12-23 in the North Atlanic Ocean. Data were recorded on 8 days between 2011-12-15 and 2011-12-23. The approximate average depth of the entire dataset is around 1500m. 
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic. After processing, these data were directly imported into the MBES Acquisition software Kongsberg SIS Seafloor Information System. Raw data were converted to MB-System format. Data were manually edited for false measurements. No further artificial sound velocity profiles were used during further processing. The data were corrected for tidal changes using data provided by the OSU Tidal Prediction Software
OTPS that is retrievable through MB-System. The vertical datum of the data is now matched to ''mean sea level (MSL)''. A raster was calculated and stored in GeoTIFF format with a 25m resolution (negative values). In addition, the full resolution of avilable ASCII data and used for grid calculation are also archived in this dataset. 
''(FEEL FREE TO ADD MORE INFORMATION)''

=== Standardized usage of ''Reference'' ===
Typically, processed datasets, which are all based of the same raw dataset (also archived in PANGAEA), are submitted to PANGAEA. These datasets will be linked to each other as a ''Reference''
Currently, all bathymetry datasets already archived in PANGAEA are reviewed and checked for relations. If a relationship is found, a linkage between both datasets is being created and is shown as ''Related to''. More information can be found here https://wiki.pangaea.de/wiki/Reference

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from ''Events'' or PANGAEA ''GEOCODE'' (see below): https://wiki.pangaea.de/wiki/Metaheader. Please note, that ''Minimum Elevation'' und ''Maximum Elevation'' does not represent min / max depth values measured from MBES data contained in this dataset. It is rather in this case the reference height on earth from the instrument used for the measurements. 
Note: Currently, the ''Coverage'' will be visible on PANGAEA website with points having an ''GoogleMaps'' image in the background (right upper corner). It does not show the actual coverage of the surveyed area. The visible points are, instead, representing the ''Events'' (see below).

=== Standardized usage of ''Events'' ===
Bathymetry datasets contain so called PANGAEA ''Events'' (https://wiki.pangaea.de/wiki/Event). The Event links to the scientific ''Campaign'', Method/Device and ''Basis'' (platform) containing further additional information. Please note that, if you browse with your mouse cursor on ''Campaign'', Method/Device or ''Basis'', a field will pop up (do not click). In some datasets, it is possible to click on these fields and a link with detailed information will be provided.
 Further information for Bathymetry related events is given below. 

==== ''Underway event'' ====
(update of this section is in progress) 

For bathymetry data from multbeam echosounders, a so called ''"Underway"'' ''Event'' is created on board of the research vessel. The ''"Underway"'' ''Event'' is named ''CruiseID_0_Underway-number(undefined, )'' e.g. ''M127_0_Underway-1''. The event shows the starting and end point (coordinates & datetime) of the first and last data record of the MBES device acquired during the cruise. Also, the ''Methods/device'' used to record the data is included for Event description. Please note, that PANGAEA specific vocabulary is used here. Providing further detailed information using standard common vocabulary such as the NERC catalogue (https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/) is currently being prepared (more information is provided as soon as possible.....). 
If available, an additional link to the Sensor description hosted on https://registry.awi.de is provided. 

If the dataset is compilation of many datasets (only possible for processed data), several ''"Underway"'' ''Events'' will be used. 
Note, that the prefix of the ''Event'' name contains the official cruise ID (cruise label, e.g. https://www.pangaea.de/expeditions/bybasis/Meteor%20%281986%29), not the campaign name. The suffix number does not follow any specific rule, as this number is usually chronologically created on board, which is why the numbering can differ from cruise to cruise. 

==== ''SVP casts and event(s)'' ====

If ''SVP casts'' (sound velocity profile measurements using an external device, e.g. using an ''AML Oceanographic Plus X sound velocity probe'') or CTD casts (sound velocity derived from CTD measurements) were performed during the cruise, the acquired data files (and used for import to the acquisition software, e.g. the ''Kongsberg Seafloor Information'', SIS) will be stored in the same raw dataset. The corresponding event of the ''Event list'' of the cruise (e.g. https://www.pangaea.de/expeditions/events/M160) will be linked to these files. This ''Event'' will contain similar information as described above, e.g. ''coordinates'', ''methods/devices'', ''etc.''. If SVP's are used for data post-processing (sound velocity correction), these data files can also be submitted to PANGAEA. If possible, these SVP can be linked to the corresponding ''Event''. In general, please always try to describe your submitted SVPs as good as possible for scientific re-use (state the origin of data, whether data are extrapolated e.g. to 12000m, etc.).
You can use the following '''[http://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/Template_PANGAEA_SUBMISSION_bathymetry_processed_V4.xlsx template]''' to support your submission.

=== Standardized usage of ''Parameter and data formats'' ===

Which [https://wiki.pangaea.de/wiki/Parameter PANGAEA parameter] for bathymetry datasets will be used & added to the data files, depend on whether raw or processed data are being submitted.

==== Raw data curation ====

Standard parameters for bathymetry raw data also include PANGAEA’s so called [https://wiki.pangaea.de/wiki/Geocode Geocodes]. These are standard important parameters, which are mandatory to keep the data georeferenced. '''These metadata for each file will be automatically created while data curation process''' Metadata are extracted using the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021) when data format is supported by MB-System . 

{| class="wikitable"
|-
! Name!! Short Name !! Unit !! Comment
|-
| [https://wiki.pangaea.de/wiki/Event Event label] || Event || ||
|-
| [https://wiki.pangaea.de/wiki/Binary_object Binary Object] || Binary|| || *this will in PANGAEA download URL
|-
| [https://en.wikipedia.org/wiki/Media_type Binary Object (Media Type)] || Binary (Type) |||| *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || Bytes || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || || *automated entry during data curation process
|-
| [https://epic.awi.de/id/eprint/29970/ Kongsberg datagram raw file name] || Datagram rfn || || *only for data from EM Series
|-
| File content || Content || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording duration] || Data record duration || min||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording distance]|| Data record distance || m ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Ship speed]|| Ship sp|| knots ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Number of pings]|| Pings|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, date/time]|| File start date/time || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, latitude] || File start latitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, longitude] || File start longitude|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, heading] || Start heading || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, depth] || Start depth || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, date/time] || File stop date/time|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, latitude] || File stop latitude ||||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, longitude] || File stop longitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, heading]|| Stop heading|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, depth]|| Stop depth|| ||
|-
| DATE/TIME || Date/Time || || *Geocode – copy of 'Start of data file recording, date/time'
|-
| LATITUDE|| Latitude || || *Geocode – copy of 'Start of data file recording, latitude'
|-
| LONGITUDE || Longitude|| || *Geocode – copy of 'Start of data file recording, longitude'
|-
| ELEVATION || Elevation || || *Geocode – copy of 'File start depth, change of sign'
|-
| Comment || Comment || ||
|}
 
Please note, if you do have ancillary data, such as ''operational logs'' created on board or detailed ''processing reports'', please add those files to the submission.

==== Processed data curation ====
Standard important parameters extracted from raster data (and ASCII data), which are mandatory to keep the data georeferenced, will be attached automatically. Please note that ASCII however are not recommended for further reuse. 
Feel free to upload bathymetry data, backscatter and/or a sidescan data, in raster (and/or ACSII) format (+ .xyz point cloud data, see below). In general, for raster data GeoTiff files (*.tif) and the grid data format (*.grd) is always preferred, since these data are usually easy to reuse, having less projection issues using standard GIS software. Please indicated whether depth values of the grid cells (also for ASCII data) contain positive or negative values (e.g. elevation / this can be indicated in the file content description). In generel you can submit any projection of the raster image, however if you do so please always add an additional GeoTiff at best with the projection [https://epsg.io/4326 '''WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326''']. Also here, try in include the projection in the raster file. Please make sure, if you provide a “bathymetry” raster data, that they contain depth information rather than just an georeferenced image with RGB values (and image is not considered as data). To submit raster images with RGB values is also fine, however they do not represent an resuable data format. In that case, always provide an raster file with true depth information (same coverage). Most dataset in PANGAEA have negative values for depth (= elevation), so we recommend to convert your data accordingly. 
If you want to '''upload xyz files (point cloud data)''' to PANGAEA, you are welcome to do so. However, please also '''upload an auxiliary gridded raster image for each individual xyz (point cloud data) data file'''. In general raster data are more user-friendly (e.g. by using GIS systems), therefore raster images are of high value for scientist. '''Raster images are considered as a (FAIR) interoperable data format, highly supporting the [https://www.go-fair.org/fair-principles/r1-3-metadata-meet-domain-relevant-community-standards/ resuablity] of data by scientists, especially from other scientific domains'''. Raster image and point cloud data (xyz) will be published using the same doi.
 
Parameters for raster data are listed below (these parameter do not apply for GSF or MB-System data files. GSF or MB-System data files will get the same parameters as for raw data, see above ):

{| class="wikitable"
|-
! Name!! Short Name !! Value/unit !! Comment
|-
| Event label || Event || - || *automated entry during data curation process
|-
| Binary Object || Binary|| || *this will in PANGAEA download URL
|-
| Binary Object (Media Type) || Binary (Type) || - || *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || - || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || - || *automated entry during data curation process
|-
| [https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/cell-size-of-raster-data.htm Raster cell size] || Raster cell size || || * raster cell size, e.g. 100m *only for raster data *if possible in meters
|-
| File content || Content || || * data description, e.g. bathymetry / negative values in meters for depth measurements (= elevation) / GeoTIFF raster image, Float32, DEFLATE compression / *feel free to add a comment specifically referring this data file
|-
| [http://vocab.nerc.ac.uk/collection/V12/current/L11/ Vertical datum]|| Vertical datum|| || * e.g. mean sea level
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum]|| Horizontal datum|| || * e.g. WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum, projection stored in file]|| Horizontal datum in file || || * e.g. EPSG:4326 (some files may not have the raster projection stored in itself)
|-
| Longitude, westbound|| Longitude west|| ||
|-
| Longitude, eastbound|| Longitude east|| ||
|-
| Latitude, southbound|| Latitude south || ||
|-
| Latitude, northbound ||Latitude north|| ||
|-
| Soundings || Soundings || || *only for xyz data / *not for backscatter data / *currently under development (not always included)
|-
| Area ||Area || km² || *currently under development (not always included)
|-
| Elevation, Minimum ||Elev min|| m a.s.l. || *not for backscatter data
|-
| Elevation, Maximum ||Elev max|| m a.s.l. || *not for backscatter data
|}

=== Standardized usage of ''Comment'' ===
Bathymetry raw and processed data, which are acquired on scientific vessels, might contain erroneous depth values and/or data artifacts. These data shall never be used for navigational purposes involving safety at sea. For safety reasons, it is widely common to state this explicitly: The comment ''These data should not be used for navigational purposes'' will be '''automatically included as a comment''' on each bathymetry dataset in PANGAEA. Please also check the PANGAEA data policy for more information: https://wiki.pangaea.de/wiki/Data_policy (page currently under construction). Bathymetry data for official nautical chart production must explicitly fulfill the requirements of the International Hydrographic Organisation (IHO) https://iho.int/.
In addition the comment may give credit to personal how was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list.
=== ''Licence'' ===
PANGAEA and DAM are encouraging data submitters to submit bathymetry data under [(https://creativecommons.org/licenses/by-nc/4.0/) '''CC-BY 4.0'''] License terms, which allows sharing (copying and redistributing the material in any medium or format) and adapting (remixing, transforming, and building upon the material) the data. In this way, PANGAEA / DAM can also make the data coverage (footprint) and the trackline visible with a direct link to PANGAEA at https://marine-data.de/ . Note, within the DAM efforts, coverage (footprint) and trackline off all submitted bathymetry data will be made available to the community via OGC Web Map Services (WMS) and OGC Web Feature Services (WFS) . Avoid licence CC-0 & CC-BY-SA, if possible.

Which CC license choose for data? Check also [https://wiki.pangaea.de/wiki/License here]

=== (Standardized usage of ''Data model extensions)'' (for raw and processed data curation) ===

The usage of so-called ''data model extensions'' which are further ''attributes'' is currently developed. This is a new feature for PANGAEA in order to include more standardized metadata. This new feature shall insure further '''findabilty''' (F) and '''interoperability'''(I) of the datasets (more information is provided as soon as possible.....).

== Example datasets ==

=== Raw data ===

Damaske, Daniel; Becker, Marius (2021): Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV MARIA S. MERIAN during cruise MSM97/2. PANGAEA, https://doi.pangaea.de/10.1594/PANGAEA.927786

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+raw+data+(%22

=== Processed data ===
Simkins, Lauren M; Greenwood, Sarah L; Munevar Garcia, Santiago; Eareckson, Elizabeth; Anderson, John B; Prothro, Lindsay O (2021): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset) of RVIB NATHANIEL B. PALMER during cruise NBP150-02. PANGAEA, https://doi.org/10.1594/PANGAEA.937597, In: Simkins, LM et al. (2021): Pennell Trough, Ross Sea bathymetry and glacial landforms. PANGAEA, https://doi.org/10.1594/PANGAEA.937602

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data+(%22

Generic sensor format (GSF) data:

Dufek, Tanja; Schniotalla, Cara; Kinne, Stefan; Sternberg, Harald (2023): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset, Generic sensor format) of RV SONNE during cruise SO268/3, North Pacific Ocean. PANGAEA, https://doi.org/10.1594/PANGAEA.957204

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data%22+AND+citation%3Atitle%3A%22Generic+Sensor+format%22

== How to submit bathymetry data to PANGAEA and what to do? ==

Please submit bathymetry data here https://www.pangaea.de/submit/. During submission, you may have to provide information for the data curation process (e.g. cruise, device, etc). For your submission, please edit/modify the title & abstract as stated above ("title construction kit").

'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]

For raw data:

Usually for raw data, an upload area will be created for you where you can drop your files (on request). Feel free to drop your data as zip- or individual files. Please also include sound velocity profiles (only SVP raw data, e.g. MSM88_2-1_0.asvp) for raw data submission if available. Your files should not exceed a volume of 10GB, however several files can be uploaded simultaneously. Please avoid renaming of raw data files, even if they are imperfect.
If raw data from '''RV Sonne''', '''RV Maria S. Merian''', '''RV Polarstern''' or '''RV Meteor''' are being submitted, '''please make a comment in your submission before you upload any multibeam echosounder raw data files (e.g. .all format)'''. Please leave a comment: '''''please take data from DSHIP Mass Data Management System (MDM)'''''.

For processed data:

Just drop your files after you get your upload link (see requirements above). If additional SVP's have been used for data processing, you can also upload these files too. 

===PANGAEA Data Submission Form Example===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]please note that the table below show's the simplified data submission workflow. The data submission form can be accessed here https://www.pangaea.de/submit/<nowiki/>Further information can also be found here [[Data submission]] .
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Title
|Adapted, generalized [[#Standardized_Title]]
|Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV SONNE during cruise SO250
|-
|Author(s)
|[[#Standardized_Authors]]
|[chief scientist], [responsible scientist(s)]
|-
|Keywords
|
|''(default)''
|-
| Abstract/Describe your Data
|[[#Standardized_Abstract]]; if the processed or raw data were already archived, the links may be placed here
|The survey data contain MBES measurements of the Fictional Bank canyon. No bathymetric measurements of Fictional Bank canyon were found in international databases prior to the cruise.
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic SVP Plus X. After processing, these data were directly imported into the MBES acquisition software Kongsberg SIS Seafloor Information System.
|-
| License
|[[#Licence]] 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 the 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).
|[https://creativecommons.org/licenses/by/4.0/ 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
|Files containing metadata information for the data
|
|}

Bathymetry

2024-10-17T07:17:26Z

Ddamaske: /* DAM Underway Research Data project background */

== Page content (please note) ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]]

Please note, '''bathymetry data curation SOPs''' in PANGAEA with respect to '''FAIR data principles''' (https://doi.org/10.1038/sdata.2016.18) are currently revised within the scope of of the German Marine Research Alliance (DAM) Underway Research Data project (https://www.allianz-meeresforschung.de/). This page and the information provided here is adressed to PANGAEA users and data submitters. [https://wiki.pangaea.de/wiki/Metaheader '''PANGAEA's Metaheader'''] explicitly for bathymetry datasets and other data curation requirements are explained on this page. In addition, data management at PANGAEA and requirements for bathymetry data submission to PANGAEA are documented. 
This page is mainly made for bathymetry data from multibeam echosounder data (MBES), however can also be used for data from Satellite derived bathymetry (SDB) or ''Light Detection and Ranging (LIDAR)'' data. 
'''Please note, that this page may still be revised in the future. '''
 

== DAM Underway Research Data project background ==

The '''German Marine Research Alliance (DAM)''' is a combined effort to exploit the full potential of German research vessels as mobile measuring platforms and currently involves 24 institutions and research facilities in Germany. The Underway Research Data project is part of DAM core area ''data management and digitalization'' (https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation/).

[[Image:DAM_Logo_small.png| thumb | right |250px| https://www.allianz-meeresforschung.de/en/]]

Please note for the German research vessels RV POLARSTERN, RV METEOR, RV MARIA S. MERIAN & RV SONNE there is no need to upload the data if data are (usually) less than 2 years old. We’ll then take the data form the DSHIP ''Mass Data Management System (MDM)'' and prepare your dataset. Please mentioned in you submission in the comment; please take data from DSHIP ''Mass Data Management System (MDM)'' 
 
 
 
 

== PANGAEA Bathymetry Web Map & Feature services ==

'''All submitted bathymetry data''' (raw data & processed data) are being semi-automatically processed at PANGAEA. '''Tracklines and coverage polygones (footprint)''' of all submitted bathymetry data are extracted from the data and '''added to the Viewer of the Marine Data Portal''' https://marine-data.org/ (direct link to the viewer https://marine-data.de/?site=viewer),
if data have a '''CC BY 4.0''' (or CC-ZERO) data license. If '''data are not under a moratorium period''', also a '''raster image''' is being calculated and '''added'''. Here, the (meta-)data can be explored (and are linked to the DOI). These vector & raster data are also available through OGC Web Map services. https://maps.awi.de/services/common/pangaea_bathymetry/wms and Web Feature Service [https://maps.awi.de/services/common/pangaea_bathymetry/wms https://maps.awi.de/services/common/pangaea_bathymetry/wfs] (please note, this is not a webpage, you need e.g. a GIS to use this service). 
Further information can be found [https://wiki.pangaea.de/wiki/PANGAEA_Bathymetry_Web_Map_Services '''here'''].

== ''Standardized content of datasets'' ==
To make data '''findable''' (F) and due to PANGAEAs archiving '''SOP'''s, bathymetry datasets from multibeam echosounders will be separated into two datasets, if the water column data (e.g. wcd files from Kongsbergs MBES Systems) is simultaneously being recorded during data acquisition. 
This is necessary due to data curation processes, consequently reducing the download volume if it is intended to download only bathymetry data (containing only the seafloor reflector information) from PANGAEA. The water column data are usually much larger than regular bathymetry files (e.g. .all). However, both datasets will be connected / linked to each other, making it easy to find the corresponding dataset).

=== Standardized ''language'' ===
To make data FAIR, “to speak” a common language is required. PANGAEA specifically uses for bathymetry data the Natural Environment Research Council's Data (NERC) Catalogue for describing data.
https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/
https://vocab.seadatanet.org/search

== Standardized ''Metaheader'' ==

=== Standardized ''Authors'' ===

The Authorship of (national/German) datasets is currently revised with respect to the ''Guidelines for Safeguarding Good Research Practice'' of the ''German Research Foundation'' http://doi.org/10.1002/9783527679188.oth1 . 
Although it is not generally agreed on, usually the authorship is given to anyone who was significantly involved in data acquisition on board or post-processing on land. 
For German research vessels raw data (archived in PANGAEA), it is very common to include the responsible scientific team on board, including all scientist (including student assistants) who were involved in monitoring, detailed survey planning or performing the survey (only raw data). This can also be considered as a genuine, identifiable contribution to the content of the research data, therefore fulfilling the requirements for authorship's according the ''Guidelines for Safeguarding Good Research Practice''.

=== Standardized ''Title'' ===
To ensure the '''reusability''' (R) and '''interoperability''' (I) of datasets, metadata of similar datasets such as bathymetry data gathered from similar research missions, research vessels or research platforms should follow a common template and a common vocabulary (Generally speaking; they should look alike!). This also includes the title. Therefore, the title of bathymetry data which are entrusted to PANGAEA shall follow a certain template ''“construction kit”''. This ''“construction kit”'' was developed within the DAM efforts (Project Underway Research Data). It includes the feedback of several German scientists from different institutions, PANGAEA bathymetry data submitters & data management personal. Key elements of each dataset title are incorporated, such as data type, device, platform type, platform, cruise (& area). To guarantee and fulfil FAIR standards, PANGAEA is encouraging data submitters to follow this template (also covering none German research data). To follow these standards is mandatory for all PANGAEA datasets. 
 
Example: 
''Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM55'' 
''Multibeam bathymetry raw data (Kongsberg EM 122 working area dataset) of RV METEOR during cruise M127, Fictional Bank canyon, North Atlantic Ocean'' 
 
The ''“construction kit”'' - incorporating all feedback - is shown below.:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! (device according to L22 vocabulary "Alt label" (NERC*) !! select: !! of !! select platform type: !! platform name (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| Multibeam bathymetry || raw data || || entire dataset) || " || RV || || " || || ||
|-
| Sidescan sonar || processed data || || transit dataset) || " || AUV || || " || || ||
|-
| Water column || || || working area dataset) || " || ROV || || " || || ||
|-
| || || || working area dataset, Generic sensor format) || " || ROV || || " || || ||
|-
| || || || dataset compilation)* || " || || || " || || ||
|-
| || || || *only for processed data || " || || || " || || ||
|}
Further information about the entries can be found here:
{| class="wikitable" style="font-size: 86%;"
! (device according to L22 vocabulary "Alt label" (seadatanet) !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| *http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=L22 || https://www.gebco.net/data_and_products/undersea_feature_names/ || https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
||| https://www.marineregions.org ||
|}
'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! Multibeam bathymetry !! raw data !! (Kongsberg EM 122 !! working area dataset) !! of !! RV !! SONNE !! during cruise !! SO250 !! Loyd Dill Seamount, !! South Pacific Ocean
|-
| Multibeam bathymetry || raw data || (Atlas Hydrosweep DS 3 echo sounder || transit dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| Multibeam bathymetry || raw data || (R2Sonic SONIC 2024 || entire dataset) || of || AUV || ABYSS || during cruise || MSM50 || ||
|-
| Multibeam bathymetry || processed data || (Kongsberg EM 122 || entire dataset) || of || RV || METEOR || during cruise || M74 || ||
|-
| Multibeam bathymetry || processed data || (EM 120 echosounder || dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| Water column || raw data || (Kongsberg EM710 || entire dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || || ,South Pacific Ocean
|}

=== Standardized ''Abstract'' ===
Intending to make data more ''FAIR,'' PANGAEA requires a compact ''Abstract'' for each dataset. For more information regarding abstracts, see https://wiki.pangaea.de/wiki/Abstract. 
Please note that cruise summary reports or other reference must not be cited exclusively in the abstract because references are also included in the metaheader (references) of the dataset. However, to provide credit and cite e.g. raw data if processed data are submitted to PANGAEA, you might add to the abstract: "Raw data for this study were published by (Authors, YYYY)." (followed by the full citation of the dataset in the list of references). If reference shall be linked, please inform the data editor. 
If you would like to provide other contact information related to this dataset (e.g. Email address), please inform the data editor. 
Please specify in the abstract whether sound velocity profiles are part of the raw dataset publication or not. Comparatively for processed data publications, please describe your processing steps (further, see below and examples).

For processed data please describe whether:
*depth measurements manually cleaned from errors during processing?
*sound velocity profile correction applied during processing?
*navigation correction applied during processing?
*tide correction applied during processing?
*horizontal datum, EPSG code from raster data in this publication are?
For raw data please describe whether:
*sound velocity profile correction applied during acquisition?
*are ancillary sound velocity profiles part of this data publication?
*which device recorded the data, which ship, which cruise?
*why have the data being recorded?

==== Raw data (example) ====

Multibeam bathymetry raw data using the ship's own Kongsberg EM 122 multibeam echosounder was not continuously recorded during RV MARIA S. MERIAN cruise MSM97/2. Data were recorded on 3 days between 2020-12-16 and 2020-12-19 in the Norwegian Sea and data acquisition was almost continuously monitored during the survey. Previous to the survey, gaps in already existing database were identified using the General Bathymetric Chart of the Oceans (GEBCO 2020) Type Identifier (TID) grid. These gaps were used as a base to determine the course of the ship during the cruise. During data acquisition, sound velocity measurements using sound velocity profiles (SVP) derived from CTD casts was applied on the data for data calibration. Ancillary SVP raw data (.asvp files) and SVP from CTD-cast (.txt) are part of this dataset publication.
Data are unprocessed and therefore contain incorrect depth measurements without further processing. Data can be processed e.g. with the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021). 
''(FEEL FREE TO ADD MORE INFORMATION)''

==== Processed data (example) ====
Swath sonar bathymetry data used for that dataset was recorded during RV SURVEY during cruise S143 using Kongsberg EM 122 multibeam echosounder. The cruise took place between 2016-12-12 and 2011-12-23 in the North Atlanic Ocean. Data were recorded on 8 days between 2011-12-15 and 2011-12-23. The approximate average depth of the entire dataset is around 1500m. 
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic. After processing, these data were directly imported into the MBES Acquisition software Kongsberg SIS Seafloor Information System. Raw data were converted to MB-System format. Data were manually edited for false measurements. No further artificial sound velocity profiles were used during further processing. The data were corrected for tidal changes using data provided by the OSU Tidal Prediction Software
OTPS that is retrievable through MB-System. The vertical datum of the data is now matched to ''mean sea level (MSL)''. A raster was calculated and stored in GeoTIFF format with a 25m resolution (negative values). In addition, the full resolution of avilable ASCII data and used for grid calculation are also archived in this dataset. 
''(FEEL FREE TO ADD MORE INFORMATION)''

=== Standardized usage of ''Reference'' ===
Typically, processed datasets, which are all based of the same raw dataset (also archived in PANGAEA), are submitted to PANGAEA. These datasets will be linked to each other as a ''Reference''
Currently, all bathymetry datasets already archived in PANGAEA are reviewed and checked for relations. If a relationship is found, a linkage between both datasets is being created and is shown as ''Related to''. More information can be found here https://wiki.pangaea.de/wiki/Reference

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from ''Events'' or PANGAEA ''GEOCODE'' (see below): https://wiki.pangaea.de/wiki/Metaheader. Please note, that ''Minimum Elevation'' und ''Maximum Elevation'' does not represent min / max depth values measured from MBES data contained in this dataset. It is rather in this case the reference height on earth from the instrument used for the measurements. 
Note: Currently, the ''Coverage'' will be visible on PANGAEA website with points having an ''GoogleMaps'' image in the background (right upper corner). It does not show the actual coverage of the surveyed area. The visible points are, instead, representing the ''Events'' (see below).

=== Standardized usage of ''Events'' ===
Bathymetry datasets contain so called PANGAEA ''Events'' (https://wiki.pangaea.de/wiki/Event). The Event links to the scientific ''Campaign'', Method/Device and ''Basis'' (platform) containing further additional information. Please note that, if you browse with your mouse cursor on ''Campaign'', Method/Device or ''Basis'', a field will pop up (do not click). In some datasets, it is possible to click on these fields and a link with detailed information will be provided.
 Further information for Bathymetry related events is given below. 

==== ''Underway event'' ====
(update of this section is in progress) 

For bathymetry data from multbeam echosounders, a so called ''"Underway"'' ''Event'' is created on board of the research vessel. The ''"Underway"'' ''Event'' is named ''CruiseID_0_Underway-number(undefined, )'' e.g. ''M127_0_Underway-1''. The event shows the starting and end point (coordinates & datetime) of the first and last data record of the MBES device acquired during the cruise. Also, the ''Methods/device'' used to record the data is included for Event description. Please note, that PANGAEA specific vocabulary is used here. Providing further detailed information using standard common vocabulary such as the NERC catalogue (https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/) is currently being prepared (more information is provided as soon as possible.....). 
If available, an additional link to the Sensor description hosted on https://registry.awi.de is provided. 

If the dataset is compilation of many datasets (only possible for processed data), several ''"Underway"'' ''Events'' will be used. 
Note, that the prefix of the ''Event'' name contains the official cruise ID (cruise label, e.g. https://www.pangaea.de/expeditions/bybasis/Meteor%20%281986%29), not the campaign name. The suffix number does not follow any specific rule, as this number is usually chronologically created on board, which is why the numbering can differ from cruise to cruise. 

==== ''SVP casts and event(s)'' ====

If ''SVP casts'' (sound velocity profile measurements using an external device, e.g. using an ''AML Oceanographic Plus X sound velocity probe'') or CTD casts (sound velocity derived from CTD measurements) were performed during the cruise, the acquired data files (and used for import to the acquisition software, e.g. the ''Kongsberg Seafloor Information'', SIS) will be stored in the same raw dataset. The corresponding event of the ''Event list'' of the cruise (e.g. https://www.pangaea.de/expeditions/events/M160) will be linked to these files. This ''Event'' will contain similar information as described above, e.g. ''coordinates'', ''methods/devices'', ''etc.''. If SVP's are used for data post-processing (sound velocity correction), these data files can also be submitted to PANGAEA. If possible, these SVP can be linked to the corresponding ''Event''. In general, please always try to describe your submitted SVPs as good as possible for scientific re-use (state the origin of data, whether data are extrapolated e.g. to 12000m, etc.).
You can use the following '''[http://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/Template_PANGAEA_SUBMISSION_bathymetry_processed_V4.xlsx template]''' to support your submission.

=== Standardized usage of ''Parameter and data formats'' ===

Which [https://wiki.pangaea.de/wiki/Parameter PANGAEA parameter] for bathymetry datasets will be used & added to the data files, depend on whether raw or processed data are being submitted.

==== Raw data curation ====

Standard parameters for bathymetry raw data also include PANGAEA’s so called [https://wiki.pangaea.de/wiki/Geocode Geocodes]. These are standard important parameters, which are mandatory to keep the data georeferenced. '''These metadata for each file will be automatically created while data curation process''' Metadata are extracted using the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021) when data format is supported by MB-System . 

{| class="wikitable"
|-
! Name!! Short Name !! Unit !! Comment
|-
| [https://wiki.pangaea.de/wiki/Event Event label] || Event || ||
|-
| [https://wiki.pangaea.de/wiki/Binary_object Binary Object] || Binary|| || *this will in PANGAEA download URL
|-
| [https://en.wikipedia.org/wiki/Media_type Binary Object (Media Type)] || Binary (Type) |||| *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || Bytes || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || || *automated entry during data curation process
|-
| [https://epic.awi.de/id/eprint/29970/ Kongsberg datagram raw file name] || Datagram rfn || || *only for data from EM Series
|-
| File content || Content || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording duration] || Data record duration || min||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording distance]|| Data record distance || m ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Ship speed]|| Ship sp|| knots ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Number of pings]|| Pings|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, date/time]|| File start date/time || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, latitude] || File start latitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, longitude] || File start longitude|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, heading] || Start heading || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, depth] || Start depth || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, date/time] || File stop date/time|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, latitude] || File stop latitude ||||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, longitude] || File stop longitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, heading]|| Stop heading|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, depth]|| Stop depth|| ||
|-
| DATE/TIME || Date/Time || || *Geocode – copy of 'Start of data file recording, date/time'
|-
| LATITUDE|| Latitude || || *Geocode – copy of 'Start of data file recording, latitude'
|-
| LONGITUDE || Longitude|| || *Geocode – copy of 'Start of data file recording, longitude'
|-
| ELEVATION || Elevation || || *Geocode – copy of 'File start depth, change of sign'
|-
| Comment || Comment || ||
|}
 
Please note, if you do have ancillary data, such as ''operational logs'' created on board or detailed ''processing reports'', please add those files to the submission.

==== Processed data curation ====
Standard important parameters extracted from raster data (and ASCII data), which are mandatory to keep the data georeferenced, will be attached automatically. Please note that ASCII however are not recommended for further reuse. 
Feel free to upload bathymetry data, backscatter and/or a sidescan data, in raster (and/or ACSII) format (+ .xyz point cloud data, see below). In general, for raster data GeoTiff files (*.tif) and the grid data format (*.grd) is always preferred, since these data are usually easy to reuse, having less projection issues using standard GIS software. Please indicated whether depth values of the grid cells (also for ASCII data) contain positive or negative values (e.g. elevation / this can be indicated in the file content description). In generel you can submit any projection of the raster image, however if you do so please always add an additional GeoTiff at best with the projection [https://epsg.io/4326 '''WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326''']. Also here, try in include the projection in the raster file. Please make sure, if you provide a “bathymetry” raster data, that they contain depth information rather than just an georeferenced image with RGB values (and image is not considered as data). To submit raster images with RGB values is also fine, however they do not represent an resuable data format. In that case, always provide an raster file with true depth information (same coverage). Most dataset in PANGAEA have negative values for depth (= elevation), so we recommend to convert your data accordingly. 
If you want to '''upload xyz files (point cloud data)''' to PANGAEA, you are welcome to do so. However, please also '''upload an auxiliary gridded raster image for each individual xyz (point cloud data) data file'''. In general raster data are more user-friendly (e.g. by using GIS systems), therefore raster images are of high value for scientist. '''Raster images are considered as a (FAIR) interoperable data format, highly supporting the [https://www.go-fair.org/fair-principles/r1-3-metadata-meet-domain-relevant-community-standards/ resuablity] of data by scientists, especially from other scientific domains'''. Raster image and point cloud data (xyz) will be published using the same doi.
 
Parameters for raster data are listed below (these parameter do not apply for GSF or MB-System data files. GSF or MB-System data files will get the same parameters as for raw data, see above ):

{| class="wikitable"
|-
! Name!! Short Name !! Value/unit !! Comment
|-
| Event label || Event || - || *automated entry during data curation process
|-
| Binary Object || Binary|| || *this will in PANGAEA download URL
|-
| Binary Object (Media Type) || Binary (Type) || - || *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || - || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || - || *automated entry during data curation process
|-
| [https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/cell-size-of-raster-data.htm Raster cell size] || Raster cell size || || * raster cell size, e.g. 100m *only for raster data *if possible in meters
|-
| File content || Content || || * data description, e.g. bathymetry / negative values in meters for depth measurements (= elevation) / GeoTIFF raster image, Float32, DEFLATE compression / *feel free to add a comment specifically referring this data file
|-
| [http://vocab.nerc.ac.uk/collection/V12/current/L11/ Vertical datum]|| Vertical datum|| || * e.g. mean sea level
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum]|| Horizontal datum|| || * e.g. WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum, projection stored in file]|| Horizontal datum in file || || * e.g. EPSG:4326 (some files may not have the raster projection stored in itself)
|-
| Longitude, westbound|| Longitude west|| ||
|-
| Longitude, eastbound|| Longitude east|| ||
|-
| Latitude, southbound|| Latitude south || ||
|-
| Latitude, northbound ||Latitude north|| ||
|-
| Soundings || Soundings || || *only for xyz data / *not for backscatter data / *currently under development (not always included)
|-
| Area ||Area || km² || *currently under development (not always included)
|-
| Elevation, Minimum ||Elev min|| m a.s.l. || *not for backscatter data
|-
| Elevation, Maximum ||Elev max|| m a.s.l. || *not for backscatter data
|}

=== Standardized usage of ''Comment'' ===
Bathymetry raw and processed data, which are acquired on scientific vessels, might contain erroneous depth values and/or data artifacts. These data shall never be used for navigational purposes involving safety at sea. For safety reasons, it is widely common to state this explicitly: The comment ''These data should not be used for navigational purposes'' will be '''automatically included as a comment''' on each bathymetry dataset in PANGAEA. Please also check the PANGAEA data policy for more information: https://wiki.pangaea.de/wiki/Data_policy (page currently under construction). Bathymetry data for official nautical chart production must explicitly fulfill the requirements of the International Hydrographic Organisation (IHO) https://iho.int/.
In addition the comment may give credit to personal how was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list.
=== ''Licence'' ===
PANGAEA and DAM are encouraging data submitters to submit bathymetry data under [(https://creativecommons.org/licenses/by-nc/4.0/) '''CC-BY 4.0'''] License terms, which allows sharing (copying and redistributing the material in any medium or format) and adapting (remixing, transforming, and building upon the material) the data. In this way, PANGAEA / DAM can also make the data coverage (footprint) and the trackline visible with a direct link to PANGAEA at https://marine-data.de/ . Note, within the DAM efforts, coverage (footprint) and trackline off all submitted bathymetry data will be made available to the community via OGC Web Map Services (WMS) and OGC Web Feature Services (WFS) . Avoid licence CC-0 & CC-BY-SA, if possible.

Which CC license choose for data? Check also [https://wiki.pangaea.de/wiki/License here]

=== (Standardized usage of ''Data model extensions)'' (for raw and processed data curation) ===

The usage of so-called ''data model extensions'' which are further ''attributes'' is currently developed. This is a new feature for PANGAEA in order to include more standardized metadata. This new feature shall insure further '''findabilty''' (F) and '''interoperability'''(I) of the datasets (more information is provided as soon as possible.....).

== Example datasets ==

=== Raw data ===

Damaske, Daniel; Becker, Marius (2021): Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV MARIA S. MERIAN during cruise MSM97/2. PANGAEA, https://doi.pangaea.de/10.1594/PANGAEA.927786

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+raw+data+(%22

=== Processed data ===
Simkins, Lauren M; Greenwood, Sarah L; Munevar Garcia, Santiago; Eareckson, Elizabeth; Anderson, John B; Prothro, Lindsay O (2021): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset) of RVIB NATHANIEL B. PALMER during cruise NBP150-02. PANGAEA, https://doi.org/10.1594/PANGAEA.937597, In: Simkins, LM et al. (2021): Pennell Trough, Ross Sea bathymetry and glacial landforms. PANGAEA, https://doi.org/10.1594/PANGAEA.937602

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data+(%22

Generic sensor format (GSF) data:

Dufek, Tanja; Schniotalla, Cara; Kinne, Stefan; Sternberg, Harald (2023): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset, Generic sensor format) of RV SONNE during cruise SO268/3, North Pacific Ocean. PANGAEA, https://doi.org/10.1594/PANGAEA.957204

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data%22+AND+citation%3Atitle%3A%22Generic+Sensor+format%22

== How to submit bathymetry data to PANGAEA and what to do? ==

Please submit bathymetry data here https://www.pangaea.de/submit/. During submission, you may have to provide information for the data curation process (e.g. cruise, device, etc). For your submission, please edit/modify the title & abstract as stated above ("title construction kit").

'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]

For raw data:

Usually for raw data, an upload area will be created for you where you can drop your files (on request). Feel free to drop your data as zip- or individual files. Please also include sound velocity profiles (only SVP raw data, e.g. MSM88_2-1_0.asvp) for raw data submission if available. Your files should not exceed a volume of 10GB, however several files can be uploaded simultaneously. Please avoid renaming of raw data files, even if they are imperfect.
If raw data from '''RV Sonne''', '''RV Maria S. Merian''', '''RV Polarstern''' or '''RV Meteor''' are being submitted, '''please make a comment in your submission before you upload any multibeam echosounder raw data files (e.g. .all format)'''. Please leave a comment: '''''Please take data from the MDM'''''.

For processed data:

Just drop your files after you get your upload link (see requirements above). If additional SVP's have been used for data processing, you can also upload these files too. 

===PANGAEA Data Submission Form Example===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]please note that the table below show's the simplified data submission workflow. The data submission form can be accessed here https://www.pangaea.de/submit/<nowiki/>Further information can also be found here [[Data submission]] .
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Title
|Adapted, generalized [[#Standardized_Title]]
|Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV SONNE during cruise SO250
|-
|Author(s)
|[[#Standardized_Authors]]
|[chief scientist], [responsible scientist(s)]
|-
|Keywords
|
|''(default)''
|-
| Abstract/Describe your Data
|[[#Standardized_Abstract]]; if the processed or raw data were already archived, the links may be placed here
|The survey data contain MBES measurements of the Fictional Bank canyon. No bathymetric measurements of Fictional Bank canyon were found in international databases prior to the cruise.
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic SVP Plus X. After processing, these data were directly imported into the MBES acquisition software Kongsberg SIS Seafloor Information System.
|-
| License
|[[#Licence]] 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 the 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).
|[https://creativecommons.org/licenses/by/4.0/ 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
|Files containing metadata information for the data
|
|}

Sediment echosounder

2024-10-17T07:17:22Z

Ddamaske: /* DAM Underway Research Data project background */

PANGAEA Bathymetry Web Map Services

2024-09-06T05:08:18Z

Ddamaske:

{{construction}}
Page content may change in future (current status: 03.01.2023)

= PANGAEA Bathymetry Web Map and Feature Service =

This new '''PANGAEA Bathymetry Web Map and Feature Service''' https://www.ogc.org/standards/wms/introduction (first release 2021) contains bathymetry data archived at PANGAEA (including only data with a CC-BY 3.0 or CC-BY 4.0 license). This service is developed as part of the '''German Marine Research Alliance''' in the core area '''"Data management and Digitalization"''' ('''Deutsche Allianz Meeresforschung, DAM''' https://www.allianz-meeresforschung.de/en/).
Note that not all bathymetry data currently archived in PANGAEA are visualized through this service. However, the number of datasets will be continuously increased in the future. As of now, only raw & processed data from multibeam echosounder measurements are incorporated in this service (further developments are in progress).
'''Please acknowledge that each layer of this service contains further usage requirements (e.g. citation rules) provided in the abstract (see [[PANGAEA_Bathymetry_Web_Map_Services#Layer_Abtracts|below]])'''. Data visualized in this service shall not be used for navigational purposes. 
For feedback & questions please contact PANGAEA. https://www.pangaea.de/contact/ 
This web map service is accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wms''' This web feature service is still considered a beta version and accessible via: 
'''https://maps.awi.de/services/common/pangaea_bathymetry/wfs'''

Each incorporated PANGAEA dataset in this service contains a vast amount of dataset-specific individual metadata. If you consider incorporating this service (data layers) into any front-end application (e.g., a web-based data portal), please also make the incorporated metadata of each layer available and visible to the user. 
Please note that a Geographic Information System (GIS) (e.g. QGIS https://qgis.org/ ) is required to access this service. However, data of this service can also be explored using the '''Viewer''' https://marine-data.de/?site=viewer of the '''Data Portal German Marine Research''' https://marine-data.de/. (see also below)

Further information about development and usage requirements are documented in Damaske et al. (2024). Generally cite the service also with:

* Damaske, D., Selke, N., & Balamurugan, A. (2024). PANGAEA Bathymetry Web Map & Feature Service – Standard Operating Procedures visualizing bathymetry data archived in PANGAEA - Data Publisher for Earth & Environmental Data. Zenodo. https://doi.org/10.5281/zenodo.8296986

== Data Contribution ==

To facilitate incorporating PANGAEA data to this service, please note the detailed information about '''bathymetry data submissions to PANGAEA''' [https://wiki.pangaea.de/wiki/Bathymetry '''here'''].

== Layer Overview ==
Currently only data layers originating from multibeam echosounder data are available in the service (see list below). For detailed information check the abstract of each corresponding data layer.

'''Raw data:'''
*PANGAEA Water Column Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Acquisition Tracklines
*PANGAEA Multibeam Raw Data Footprints
*PANGAEA Multibeam Raw Data Footprints Simplified
*PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional)
'''Processed data:'''
*PANGAEA Multibeam Processed Data Footprints
*PANGAEA Multibeam Processed Data Footprints Simplified
*PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°)
*PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional)

== Layer Abstracts ==
directly embedded into the service:
https://maps.awi.de/services/common/pangaea_bathymetry/wms?service=WMS&request=GetCapabilities
<nowiki>*</nowiki>Abstract update 21.08.2024
{| class="wikitable" style="font-size: 86%;"
! Layer name (technical name) !! Layer title !! Abstract (embedded in service)
|-
| mbes_raw_acquisition_tracklines_wcd_4326 || PANGAEA Water Column Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_acquisition_tracklines_4326 || PANGAEA Multibeam Raw Data Acquisition Tracklines || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_4326 || PANGAEA Multibeam Raw Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_footprints_simplified_4326 || PANGAEA Multibeam Raw Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_raw_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Raw Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_bathymetry_8000_haxby_multidirectional_4326 || PPANGAEA Multibeam Raw Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_raw_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Raw Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_4326 || PANGAEA Multibeam Processed Data Footprints || Please see here:
https://doi.org/10.5281/zenodo.8296986

|-
|-
| mbes_processed_footprints_simplified_4326 || PANGAEA Multibeam Processed Data Footprints Simplified || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_5000_haxby_315deg_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-5000m haxby, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_bathymetry_8000_haxby_multidirectional_4326 || PANGAEA Multibeam Processed Data Bathymetry (0-8000m haxby, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_315deg_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, azimuth 315°/altitude 45°) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|-
|-
| mbes_processed_hillshade_greyscale_multidirectional_4326 || PANGAEA Multibeam Processed Data Hillshade (greyscale, multidirectional) || Please see here:
https://doi.org/10.5281/zenodo.8296986
|}

 Available metadata

A list of currently available metadata:
*Please see here: https://doi.org/10.5281/zenodo.8296986

== Known incorporated web based data portals ==
This service is incorporated in the following data portals::
*[https://marine-data.de/?site=viewer Viewer of the Data Portal German Marine Research]
*[https://www.ncei.noaa.gov/maps/iho_dcdb/ IHO Data Centre for Digital Bathymetry (DCDB)]
....more information will be provided......

CTD

2024-08-28T13:25:26Z

Ddamaske:

This page provides information on the requirements for submitting, archiving and publishing '''Conductivity, Temperature, Depth sonde (CTD) data''' to ensure fulfilling the '''[https://www.nature.com/articles/sdata201618 FAIR data principles]'''.

PANGAEA differentiates between raw data and processed data publications. The differences are explained below. Please note the extra paragraph on *.cnv files.

If you are preparing CTD data in the context of the [https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation DAM Underway Research Data project], find specific project related details on this page: [[CTD Underway Data|CTD Underway data]].

==Standardized meta information==
The following information needs to be included in any '''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 [https://wiki.pangaea.de/wiki/Ticket_System in this wiki].
[[File:workflow_underway.png|frame|Workflow: Processing of a Data Submission]]
===List of authors===
Usually, the list of authors should contain the '''scientist responsible for the sampling device''', the '''chief scientist''' and the PI, the contact person responsible for the data.
===Dataset title===
The title should ideally reflect what has been measured, observed, or calculated, when, where, and how. If applicable, the title of the data publication should be generalized and is defined by the specific '''[ship]''', '''[cruise]''' and '''[device]'''.
===[https://wiki.pangaea.de/wiki/Abstract Abstract]===
In general, a '''generalized abstract''' is mandatory 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 [https://wiki.pangaea.de/wiki/Ticket_System this page].
===[https://wiki.pangaea.de/wiki/Reference References]===
Several references may be of importance for the dataset.

==== Cruise report ====
If a '''cruise report''' is available it is sometimes already archived at the [https://www.tib.eu/en/ Technische Informationsbibliothek] and might be linked to the dataset (see [https://doi.org/10.2312/cr_msm88 this example]).

====Data processing report ====
If a '''data processing report''' exists, it 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 [https://epic.awi.de/id/eprint/56595/ this example]).

Currently, the data processing reports are being archived at PANGAEA; A long-term solution will include the assignment of a doi for each data processing report.
====Linking between processed and raw data====
If possible, the raw data should be linked to the processed dataset and vice versa. This link may lead to an external source, but it may also be an PANGAEA-internal link (see this [https://doi.pangaea.de/10.1594/PANGAEA.956146 example] ).
===Additional data files===
These may, for example, include additional *.cnv files in zip format, protocol files in pdf format, salinity measurements as .txt files, etc. They will be stored on one of PANGAEA's servers and can be accessed via a link to the data publication (see this [https://doi.pangaea.de/10.1594/PANGAEA.953836 example]).
===Further information===
====Cruise label====
The '''[cruise] label''' usually includes [ship]number/leg (e.g.: MSM88/1). Please provide further information on the cruise (synonyms: ''campaign, expedition, leg'') as described in https://wiki.pangaea.de/wiki/Campaign. You may also check the [https://wiki.pangaea.de/wiki/Campaign#CAMPAIGN_list_of_ships_in_PANGAEA overview table of campaigns] and the existing labels.
====Event label(s)====
The '''[https://wiki.pangaea.de/wiki/Event event label(s)]''' should be part of each data submission. Event labels equal the station labels and provide meta-information for the data. An Event Label consists of the cruise label and the station ending: [ship]number/leg_station (e.g.: [https://www.pangaea.de/expeditions/events/HE605 HE605_1-1]).
====Device/Sensor====
'''Information on the device''' used for measuring should also be provided, so it can be linked to the measured parameters (see this [https://doi.pangaea.de/10.1594/PANGAEA.950213 example]).

==Processed Data==
Processed data are prepared for submission following the guidelines of a general [[Data submission#READ FIRST|data submission]], which includes

* date and time information in ISO format (e.g. 1954-04-07T13:34:11) in coordinated universal time (UTC)
* 3 dimensional [[geocode]]: latitude/longitude in decimal degree (WGS84) and water depth of CTD
* an [[event]] for each CTD cast
* full [[Parameter|parameter names]] (no abbreviations) including units
* standardized meta information (see above).

=== Examples of a processed CTD data publication===
Physical oceanography during RV HEINCKE cruise HE609: https://doi.pangaea.de/10.1594/PANGAEA.961721.

Physical Oceanography measured with CTD on Triaxus topAWI (towed ocean profiler of the AWI) during MERIAN cruise MSM93: https://doi.pangaea.de/10.1594/PANGAEA.940010.

=== File name===
If CTD profiles are provided as individual data files, please name them after their events (see the '''Event label(s)''' paragraph above).
===File formats===
Possible file formats include .txt, .tab, .csv, .xlsx . The preferred file format is tab-delimited text file. 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. Preferably, the submitted data contains blanks. Alternatives such as "NaN", "NA" are acceptable in the data table.
=== Parameters and meta data information in the data table (example)===
This table gives an overview on the '''parameter names and specifications''' as they 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''' will be included in the data publication by the data editor as specified in the submitted meta-information.
{| class="wikitable"
!|Parameter Name
!|Format
!|Unit
!|Value
!'''Principal Investigator'''
!|Method/Device
!|Comment
|-
|Event label
|
|
|HE609_1-10
|
|
|
|-
|DATE/TIME
|yyyy-MM-ddTHH:mm:ss
|
|2022-10-05T10:23:55
|
|
|
|-
|LATITUDE
|decimal
|
|53.7504
|
|
|
|-
|LONGITUDE
|decimal
|
|8.0703
|
|
|
|-
|Depth, water
|
|m
|18.2
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; calculated using SBE Data Processing Version 7.22.5
|
|-
|Pressure, water
|
|dbar
|18.4
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus
|
|-
|Temperature, water
|
|°C
|14.5508
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus
|ITS-90; in situ
|-
|Conductivity
|
|mS/cm
|39.2215
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; measured with Conductivity sensor, Sea-Bird, SBE 4
|
|-
|Salinity
|
|
|32.0127
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; calculated using SBE Data Processing Version 7.22.5
|PSU
|-
|Temperature, water, potential
|
| °C
|14.5482
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; calculated using SBE Data Processing Version 7.22.5 and SEAWATER Routines
|ITS-90
|-
|Density, sigma-theta (0)
|
|kg/m3
|23.7659
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; calculated using SBE Data Processing Version 7.22.5 and SEAWATER Routines
|
|-
|Oxygen
|
|µmol/l
|236.233
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; Calculation according to Morgan (1994; SEAWATER Routines)
|
|-
| Oxygen saturation
|
|%
|90.48
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; calculated using SBE Data Processing Version 7.22.5 and SEAWATER Routines
|
|-
|Attenuation, optical beam transmission
|
|%
|20.02
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; measured with Transmissometer, WET Labs, C-Star
|
|-
|Chlorophyll a
|
|µg/l
|2.81
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus; measured with Fluorometer, WET Labs, ECO-AFL
|
|-
|Number of observations
|
| #
|4
|Tippenhauer, Sandra
|CTD, Sea-Bird, SBE 911plus
|
|}Note: If Quality Flags are used, the flagging code needs to be explained and will be archived in the parameter comment.

=== Templates for processed CTD data submissions ===
These templates may help for preparation of your data file:
* [https://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/CTD_template.txt '''template in tab delimited text format (preferred)''']; Additional meta information as name of the principal investigator and name of method and device are given as comments during the submission process.

* [https://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/CTD_template.xlsx '''template in excel format''']; Additional meta information as name of the principal investigator and name of method and device are either given as comments during the submission process or via an additional sheet in the excel file.

'''A few information on density in water:'''

Density = 1027.1234 kg/m³

Sigma = Density - 1000 = 27.1234 kg/m³

Density depends on pressure, temperature and salt content: Density = f(P,T,S)

As a rule, one considers the density (or sigma) and sets P = 0 and denotes this as sigma-theta.

If the potential temperature (theta) is used instead of the in-situ temperature T, then the result is the potential density or sigma-theta.

'''Density in situ''' ('' Note: "Density, mass density [kg/m³]" in 4D'') - should always have values around 1000 (e.g. 1027)

'''Density, potential''' [kg/m³] should also always have values around 1000 (e.g. 1027)

'''Density sigma-theta''' [kg/m³] should always have lower tens values, e.g. around 27

'''Density, sigma, in situ''' [kg/m³] should also have lower tens values, e.g. around 27

Further information on parameters: https://wiki.pangaea.de/wiki/Parameter.

== Raw Data ==
CTDs produce several raw files in various formats. The output of raw data varies depending on the preferences set by the CTD user.

A minimum set of the following files for each cast are needed for a raw data publication:

* bottle information file *.bl
* sensor configuration including calibration information file *.xmlcon
* header file containing meta data on CTD system, position and time *.hdr
* CTD raw data in hexadecimal format file *.hex

Optional additional files:

* bottle data *.btl
* summary file in text format *.cnv
* protocol sheet/file *.pdf

=== Example of a CTD raw data publication===
Raw data of physical oceanography during RV POLARSTERN cruises PS130/1 and PS130/2. https://doi.pangaea.de/10.1594/PANGAEA.957843.

=== File name ===
Please name each individual data file after its event (see the '''Event label(s)''' paragraph above).

== The special case of *cnv files ==
Some CTDs provide *cnv files consisting of a meta data summary plus raw data translated to text format which might include flagging. This data type is neither considered raw data nor processed data. Please see a detailed description on raw and processed data in the paragraphs above.

If you like to archive *.cnv files along with either raw or processed data submissions, you can do so as additional optional files. These will be either listed together with other [[CTD#Raw Data|raw data files]] or linked as a zipped [[CTD#Additional data files|additional file]].

Sediment echosounder

2024-08-28T13:01:01Z

Ddamaske:

Bathymetry

2024-08-28T13:00:25Z

Ddamaske:

== Page content (please note) ==

[[Image:FAIR data principles.jpg| thumb | right | 250px | Image by SangyaPundir / CC BY-SA (https://creativecommons.org/licenses/by-sa/4.0)" "https://commons.wikimedia.org/wiki/File:FAIR_data_principles.jpg"]]

Please note, '''bathymetry data curation SOPs''' in PANGAEA with respect to '''FAIR data principles''' (https://doi.org/10.1038/sdata.2016.18) are currently revised within the scope of of the German Marine Research Alliance (DAM) Underway Research Data project (https://www.allianz-meeresforschung.de/). This page and the information provided here is adressed to PANGAEA users and data submitters. [https://wiki.pangaea.de/wiki/Metaheader '''PANGAEA's Metaheader'''] explicitly for bathymetry datasets and other data curation requirements are explained on this page. In addition, data management at PANGAEA and requirements for bathymetry data submission to PANGAEA are documented. 
This page is mainly made for bathymetry data from multibeam echosounder data (MBES), however can also be used for data from Satellite derived bathymetry (SDB) or ''Light Detection and Ranging (LIDAR)'' data. 
'''Please note, that this page may still be revised in the future. '''
 

== DAM Underway Research Data project background ==

The '''German Marine Research Alliance (DAM)''' is a combined effort to exploit the full potential of German research vessels as mobile measuring platforms and currently involves 24 institutions and research facilities in Germany. The Underway Research Data project is part of DAM core area ''data management and digitalization'' (https://www.allianz-meeresforschung.de/en/activities/data-management-and-digitisation/).

[[Image:DAM_Logo_small.png| thumb | right |250px| https://www.allianz-meeresforschung.de/en/]]

 
 
 
 
 

== PANGAEA Bathymetry Web Map & Feature services ==

'''All submitted bathymetry data''' (raw data & processed data) are being semi-automatically processed at PANGAEA. '''Tracklines and coverage polygones (footprint)''' of all submitted bathymetry data are extracted from the data and '''added to the Viewer of the Marine Data Portal''' https://marine-data.org/ (direct link to the viewer https://marine-data.de/?site=viewer),
if data have a '''CC BY 4.0''' (or CC-ZERO) data license. If '''data are not under a moratorium period''', also a '''raster image''' is being calculated and '''added'''. Here, the (meta-)data can be explored (and are linked to the DOI). These vector & raster data are also available through OGC Web Map services. https://maps.awi.de/services/common/pangaea_bathymetry/wms and Web Feature Service [https://maps.awi.de/services/common/pangaea_bathymetry/wms https://maps.awi.de/services/common/pangaea_bathymetry/wfs] (please note, this is not a webpage, you need e.g. a GIS to use this service). 
Further information can be found [https://wiki.pangaea.de/wiki/PANGAEA_Bathymetry_Web_Map_Services '''here'''].

== ''Standardized content of datasets'' ==
To make data '''findable''' (F) and due to PANGAEAs archiving '''SOP'''s, bathymetry datasets from multibeam echosounders will be separated into two datasets, if the water column data (e.g. wcd files from Kongsbergs MBES Systems) is simultaneously being recorded during data acquisition. 
This is necessary due to data curation processes, consequently reducing the download volume if it is intended to download only bathymetry data (containing only the seafloor reflector information) from PANGAEA. The water column data are usually much larger than regular bathymetry files (e.g. .all). However, both datasets will be connected / linked to each other, making it easy to find the corresponding dataset).

=== Standardized ''language'' ===
To make data FAIR, “to speak” a common language is required. PANGAEA specifically uses for bathymetry data the Natural Environment Research Council's Data (NERC) Catalogue for describing data.
https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/
https://vocab.seadatanet.org/search

== Standardized ''Metaheader'' ==

=== Standardized ''Authors'' ===

The Authorship of (national/German) datasets is currently revised with respect to the ''Guidelines for Safeguarding Good Research Practice'' of the ''German Research Foundation'' http://doi.org/10.1002/9783527679188.oth1 . 
Although it is not generally agreed on, usually the authorship is given to anyone who was significantly involved in data acquisition on board or post-processing on land. 
For German research vessels raw data (archived in PANGAEA), it is very common to include the responsible scientific team on board, including all scientist (including student assistants) who were involved in monitoring, detailed survey planning or performing the survey (only raw data). This can also be considered as a genuine, identifiable contribution to the content of the research data, therefore fulfilling the requirements for authorship's according the ''Guidelines for Safeguarding Good Research Practice''.

=== Standardized ''Title'' ===
To ensure the '''reusability''' (R) and '''interoperability''' (I) of datasets, metadata of similar datasets such as bathymetry data gathered from similar research missions, research vessels or research platforms should follow a common template and a common vocabulary (Generally speaking; they should look alike!). This also includes the title. Therefore, the title of bathymetry data which are entrusted to PANGAEA shall follow a certain template ''“construction kit”''. This ''“construction kit”'' was developed within the DAM efforts (Project Underway Research Data). It includes the feedback of several German scientists from different institutions, PANGAEA bathymetry data submitters & data management personal. Key elements of each dataset title are incorporated, such as data type, device, platform type, platform, cruise (& area). To guarantee and fulfil FAIR standards, PANGAEA is encouraging data submitters to follow this template (also covering none German research data). To follow these standards is mandatory for all PANGAEA datasets. 
 
Example: 
''Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM55'' 
''Multibeam bathymetry raw data (Kongsberg EM 122 working area dataset) of RV METEOR during cruise M127, Fictional Bank canyon, North Atlantic Ocean'' 
 
The ''“construction kit”'' - incorporating all feedback - is shown below.:

'''Construction kit:'''
{| class="wikitable" style="font-size: 86%;"
! select data type: !! select data level: !! (device according to L22 vocabulary "Alt label" (NERC*) !! select: !! of !! select platform type: !! platform name (capital letters): !! during cruise !! Cruise ID !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| Multibeam bathymetry || raw data || || entire dataset) || " || RV || || " || || ||
|-
| Sidescan sonar || processed data || || transit dataset) || " || AUV || || " || || ||
|-
| Water column || || || working area dataset) || " || ROV || || " || || ||
|-
| || || || working area dataset, Generic sensor format) || " || ROV || || " || || ||
|-
| || || || dataset compilation)* || " || || || " || || ||
|-
| || || || *only for processed data || " || || || " || || ||
|}
Further information about the entries can be found here:
{| class="wikitable" style="font-size: 86%;"
! (device according to L22 vocabulary "Alt label" (seadatanet) !! optional: IHO-IOC GEBCO undersea feature name) !! optional: IHO Sea Area (1953),
|-
| *http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=L22 || https://www.gebco.net/data_and_products/undersea_feature_names/ || https://epic.awi.de/id/eprint/29772/1/IHO1953a.pdf
|-
||| https://www.marineregions.org ||
|}
'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]
----
'''Examples:'''

{| class="wikitable" style="font-size: 86%;"
! Multibeam bathymetry !! raw data !! (Kongsberg EM 122 !! working area dataset) !! of !! RV !! SONNE !! during cruise !! SO250 !! Loyd Dill Seamount, !! South Pacific Ocean
|-
| Multibeam bathymetry || raw data || (Atlas Hydrosweep DS 3 echo sounder || transit dataset) || of || RV || SONNE || during cruise || SO250 || ||
|-
| Multibeam bathymetry || raw data || (R2Sonic SONIC 2024 || entire dataset) || of || AUV || ABYSS || during cruise || MSM50 || ||
|-
| Multibeam bathymetry || processed data || (Kongsberg EM 122 || entire dataset) || of || RV || METEOR || during cruise || M74 || ||
|-
| Multibeam bathymetry || processed data || (EM 120 echosounder || dataset compilation) || of || RV || METEOR & RV MARIA S. MERIAN || during cruise || M74 & MSM66 || ,Sardino-Balearic Abyssal Plain || ,Mediterranean Sea
|-
| Water column || raw data || (Kongsberg EM710 || entire dataset) || of || RV || MARIA S. MERIAN || during cruise || MSM66 || || ,South Pacific Ocean
|}

=== Standardized ''Abstract'' ===
Intending to make data more ''FAIR,'' PANGAEA requires a compact ''Abstract'' for each dataset. For more information regarding abstracts, see https://wiki.pangaea.de/wiki/Abstract. 
Please note that cruise summary reports or other reference must not be cited exclusively in the abstract because references are also included in the metaheader (references) of the dataset. However, to provide credit and cite e.g. raw data if processed data are submitted to PANGAEA, you might add to the abstract: "Raw data for this study were published by (Authors, YYYY)." (followed by the full citation of the dataset in the list of references). If reference shall be linked, please inform the data editor. 
If you would like to provide other contact information related to this dataset (e.g. Email address), please inform the data editor. 
Please specify in the abstract whether sound velocity profiles are part of the raw dataset publication or not. Comparatively for processed data publications, please describe your processing steps (further, see below and examples).

For processed data please describe whether:
*depth measurements manually cleaned from errors during processing?
*sound velocity profile correction applied during processing?
*navigation correction applied during processing?
*tide correction applied during processing?
*horizontal datum, EPSG code from raster data in this publication are?
For raw data please describe whether:
*sound velocity profile correction applied during acquisition?
*are ancillary sound velocity profiles part of this data publication?
*which device recorded the data, which ship, which cruise?
*why have the data being recorded?

==== Raw data (example) ====

Multibeam bathymetry raw data using the ship's own Kongsberg EM 122 multibeam echosounder was not continuously recorded during RV MARIA S. MERIAN cruise MSM97/2. Data were recorded on 3 days between 2020-12-16 and 2020-12-19 in the Norwegian Sea and data acquisition was almost continuously monitored during the survey. Previous to the survey, gaps in already existing database were identified using the General Bathymetric Chart of the Oceans (GEBCO 2020) Type Identifier (TID) grid. These gaps were used as a base to determine the course of the ship during the cruise. During data acquisition, sound velocity measurements using sound velocity profiles (SVP) derived from CTD casts was applied on the data for data calibration. Ancillary SVP raw data (.asvp files) and SVP from CTD-cast (.txt) are part of this dataset publication.
Data are unprocessed and therefore contain incorrect depth measurements without further processing. Data can be processed e.g. with the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021). 
''(FEEL FREE TO ADD MORE INFORMATION)''

==== Processed data (example) ====
Swath sonar bathymetry data used for that dataset was recorded during RV SURVEY during cruise S143 using Kongsberg EM 122 multibeam echosounder. The cruise took place between 2016-12-12 and 2011-12-23 in the North Atlanic Ocean. Data were recorded on 8 days between 2011-12-15 and 2011-12-23. The approximate average depth of the entire dataset is around 1500m. 
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic. After processing, these data were directly imported into the MBES Acquisition software Kongsberg SIS Seafloor Information System. Raw data were converted to MB-System format. Data were manually edited for false measurements. No further artificial sound velocity profiles were used during further processing. The data were corrected for tidal changes using data provided by the OSU Tidal Prediction Software
OTPS that is retrievable through MB-System. The vertical datum of the data is now matched to ''mean sea level (MSL)''. A raster was calculated and stored in GeoTIFF format with a 25m resolution (negative values). In addition, the full resolution of avilable ASCII data and used for grid calculation are also archived in this dataset. 
''(FEEL FREE TO ADD MORE INFORMATION)''

=== Standardized usage of ''Reference'' ===
Typically, processed datasets, which are all based of the same raw dataset (also archived in PANGAEA), are submitted to PANGAEA. These datasets will be linked to each other as a ''Reference''
Currently, all bathymetry datasets already archived in PANGAEA are reviewed and checked for relations. If a relationship is found, a linkage between both datasets is being created and is shown as ''Related to''. More information can be found here https://wiki.pangaea.de/wiki/Reference

=== Standardized ''Coverage'' ===
Coverage is an automatic entry into PANGAEA calculated from ''Events'' or PANGAEA ''GEOCODE'' (see below): https://wiki.pangaea.de/wiki/Metaheader. Please note, that ''Minimum Elevation'' und ''Maximum Elevation'' does not represent min / max depth values measured from MBES data contained in this dataset. It is rather in this case the reference height on earth from the instrument used for the measurements. 
Note: Currently, the ''Coverage'' will be visible on PANGAEA website with points having an ''GoogleMaps'' image in the background (right upper corner). It does not show the actual coverage of the surveyed area. The visible points are, instead, representing the ''Events'' (see below).

=== Standardized usage of ''Events'' ===
Bathymetry datasets contain so called PANGAEA ''Events'' (https://wiki.pangaea.de/wiki/Event). The Event links to the scientific ''Campaign'', Method/Device and ''Basis'' (platform) containing further additional information. Please note that, if you browse with your mouse cursor on ''Campaign'', Method/Device or ''Basis'', a field will pop up (do not click). In some datasets, it is possible to click on these fields and a link with detailed information will be provided.
 Further information for Bathymetry related events is given below. 

==== ''Underway event'' ====
(update of this section is in progress) 

For bathymetry data from multbeam echosounders, a so called ''"Underway"'' ''Event'' is created on board of the research vessel. The ''"Underway"'' ''Event'' is named ''CruiseID_0_Underway-number(undefined, )'' e.g. ''M127_0_Underway-1''. The event shows the starting and end point (coordinates & datetime) of the first and last data record of the MBES device acquired during the cruise. Also, the ''Methods/device'' used to record the data is included for Event description. Please note, that PANGAEA specific vocabulary is used here. Providing further detailed information using standard common vocabulary such as the NERC catalogue (https://www.bodc.ac.uk/resources/inventories/nerc_data_catalogue/) is currently being prepared (more information is provided as soon as possible.....). 
If available, an additional link to the Sensor description hosted on https://registry.awi.de is provided. 

If the dataset is compilation of many datasets (only possible for processed data), several ''"Underway"'' ''Events'' will be used. 
Note, that the prefix of the ''Event'' name contains the official cruise ID (cruise label, e.g. https://www.pangaea.de/expeditions/bybasis/Meteor%20%281986%29), not the campaign name. The suffix number does not follow any specific rule, as this number is usually chronologically created on board, which is why the numbering can differ from cruise to cruise. 

==== ''SVP casts and event(s)'' ====

If ''SVP casts'' (sound velocity profile measurements using an external device, e.g. using an ''AML Oceanographic Plus X sound velocity probe'') or CTD casts (sound velocity derived from CTD measurements) were performed during the cruise, the acquired data files (and used for import to the acquisition software, e.g. the ''Kongsberg Seafloor Information'', SIS) will be stored in the same raw dataset. The corresponding event of the ''Event list'' of the cruise (e.g. https://www.pangaea.de/expeditions/events/M160) will be linked to these files. This ''Event'' will contain similar information as described above, e.g. ''coordinates'', ''methods/devices'', ''etc.''. If SVP's are used for data post-processing (sound velocity correction), these data files can also be submitted to PANGAEA. If possible, these SVP can be linked to the corresponding ''Event''. In general, please always try to describe your submitted SVPs as good as possible for scientific re-use (state the origin of data, whether data are extrapolated e.g. to 12000m, etc.).
You can use the following '''[http://store.pangaea.de/documentation/PANGAEA-Wiki/Templates/Template_PANGAEA_SUBMISSION_bathymetry_processed_V4.xlsx template]''' to support your submission.

=== Standardized usage of ''Parameter and data formats'' ===

Which [https://wiki.pangaea.de/wiki/Parameter PANGAEA parameter] for bathymetry datasets will be used & added to the data files, depend on whether raw or processed data are being submitted.

==== Raw data curation ====

Standard parameters for bathymetry raw data also include PANGAEA’s so called [https://wiki.pangaea.de/wiki/Geocode Geocodes]. These are standard important parameters, which are mandatory to keep the data georeferenced. '''These metadata for each file will be automatically created while data curation process''' Metadata are extracted using the open source software package MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, http://www.mbari.org/products/research-software/mb-system/, 2021) when data format is supported by MB-System . 

{| class="wikitable"
|-
! Name!! Short Name !! Unit !! Comment
|-
| [https://wiki.pangaea.de/wiki/Event Event label] || Event || ||
|-
| [https://wiki.pangaea.de/wiki/Binary_object Binary Object] || Binary|| || *this will in PANGAEA download URL
|-
| [https://en.wikipedia.org/wiki/Media_type Binary Object (Media Type)] || Binary (Type) |||| *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || Bytes || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || || *automated entry during data curation process
|-
| [https://epic.awi.de/id/eprint/29970/ Kongsberg datagram raw file name] || Datagram rfn || || *only for data from EM Series
|-
| File content || Content || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording duration] || Data record duration || min||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Data file recording distance]|| Data record distance || m ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Ship speed]|| Ship sp|| knots ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Number of pings]|| Pings|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, date/time]|| File start date/time || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, latitude] || File start latitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file recording, longitude] || File start longitude|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, heading] || Start heading || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Start of data file, depth] || Start depth || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, date/time] || File stop date/time|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, latitude] || File stop latitude ||||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file recording, longitude] || File stop longitude || ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, heading]|| Stop heading|| ||
|-
| [http://www3.mbari.org/products/mbsystem/html/mbinfo.html Stop of data file, depth]|| Stop depth|| ||
|-
| DATE/TIME || Date/Time || || *Geocode – copy of 'Start of data file recording, date/time'
|-
| LATITUDE|| Latitude || || *Geocode – copy of 'Start of data file recording, latitude'
|-
| LONGITUDE || Longitude|| || *Geocode – copy of 'Start of data file recording, longitude'
|-
| ELEVATION || Elevation || || *Geocode – copy of 'File start depth, change of sign'
|-
| Comment || Comment || ||
|}
 
Please note, if you do have ancillary data, such as ''operational logs'' created on board or detailed ''processing reports'', please add those files to the submission.

==== Processed data curation ====
Standard important parameters extracted from raster data (and ASCII data), which are mandatory to keep the data georeferenced, will be attached automatically. Please note that ASCII however are not recommended for further reuse. 
Feel free to upload bathymetry data, backscatter and/or a sidescan data, in raster (and/or ACSII) format (+ .xyz point cloud data, see below). In general, for raster data GeoTiff files (*.tif) and the grid data format (*.grd) is always preferred, since these data are usually easy to reuse, having less projection issues using standard GIS software. Please indicated whether depth values of the grid cells (also for ASCII data) contain positive or negative values (e.g. elevation / this can be indicated in the file content description). In generel you can submit any projection of the raster image, however if you do so please always add an additional GeoTiff at best with the projection [https://epsg.io/4326 '''WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326''']. Also here, try in include the projection in the raster file. Please make sure, if you provide a “bathymetry” raster data, that they contain depth information rather than just an georeferenced image with RGB values (and image is not considered as data). To submit raster images with RGB values is also fine, however they do not represent an resuable data format. In that case, always provide an raster file with true depth information (same coverage). Most dataset in PANGAEA have negative values for depth (= elevation), so we recommend to convert your data accordingly. 
If you want to '''upload xyz files (point cloud data)''' to PANGAEA, you are welcome to do so. However, please also '''upload an auxiliary gridded raster image for each individual xyz (point cloud data) data file'''. In general raster data are more user-friendly (e.g. by using GIS systems), therefore raster images are of high value for scientist. '''Raster images are considered as a (FAIR) interoperable data format, highly supporting the [https://www.go-fair.org/fair-principles/r1-3-metadata-meet-domain-relevant-community-standards/ resuablity] of data by scientists, especially from other scientific domains'''. Raster image and point cloud data (xyz) will be published using the same doi.
 
Parameters for raster data are listed below (these parameter do not apply for GSF or MB-System data files. GSF or MB-System data files will get the same parameters as for raw data, see above ):

{| class="wikitable"
|-
! Name!! Short Name !! Value/unit !! Comment
|-
| Event label || Event || - || *automated entry during data curation process
|-
| Binary Object || Binary|| || *this will in PANGAEA download URL
|-
| Binary Object (Media Type) || Binary (Type) || - || *automated entry during data curation process
|-
| Binary Object (File Size) || Binary (Size) || - || *automated entry during data curation process
|-
| Binary Object (MD5 Hash) || Binary (MD5 Hash) || - || *automated entry during data curation process
|-
| [https://desktop.arcgis.com/en/arcmap/10.3/manage-data/raster-and-images/cell-size-of-raster-data.htm Raster cell size] || Raster cell size || || * raster cell size, e.g. 100m *only for raster data *if possible in meters
|-
| File content || Content || || * data description, e.g. bathymetry / negative values in meters for depth measurements (= elevation) / GeoTIFF raster image, Float32, DEFLATE compression / *feel free to add a comment specifically referring this data file
|-
| [http://vocab.nerc.ac.uk/collection/V12/current/L11/ Vertical datum]|| Vertical datum|| || * e.g. mean sea level
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum]|| Horizontal datum|| || * e.g. WGS 84 -- WGS84 - World Geodetic System 1984, EPSG:4326
|-
| [https://gisgeography.com/horizontal-datum/ Horizontal datum, projection stored in file]|| Horizontal datum in file || || * e.g. EPSG:4326 (some files may not have the raster projection stored in itself)
|-
| Longitude, westbound|| Longitude west|| ||
|-
| Longitude, eastbound|| Longitude east|| ||
|-
| Latitude, southbound|| Latitude south || ||
|-
| Latitude, northbound ||Latitude north|| ||
|-
| Soundings || Soundings || || *only for xyz data / *not for backscatter data / *currently under development (not always included)
|-
| Area ||Area || km² || *currently under development (not always included)
|-
| Elevation, Minimum ||Elev min|| m a.s.l. || *not for backscatter data
|-
| Elevation, Maximum ||Elev max|| m a.s.l. || *not for backscatter data
|}

=== Standardized usage of ''Comment'' ===
Bathymetry raw and processed data, which are acquired on scientific vessels, might contain erroneous depth values and/or data artifacts. These data shall never be used for navigational purposes involving safety at sea. For safety reasons, it is widely common to state this explicitly: The comment ''These data should not be used for navigational purposes'' will be '''automatically included as a comment''' on each bathymetry dataset in PANGAEA. Please also check the PANGAEA data policy for more information: https://wiki.pangaea.de/wiki/Data_policy (page currently under construction). Bathymetry data for official nautical chart production must explicitly fulfill the requirements of the International Hydrographic Organisation (IHO) https://iho.int/.
In addition the comment may give credit to personal how was involved in the data submission and not related to the data acquisition at all, therefore not part of the author list.
=== ''Licence'' ===
PANGAEA and DAM are encouraging data submitters to submit bathymetry data under [(https://creativecommons.org/licenses/by-nc/4.0/) '''CC-BY 4.0'''] License terms, which allows sharing (copying and redistributing the material in any medium or format) and adapting (remixing, transforming, and building upon the material) the data. In this way, PANGAEA / DAM can also make the data coverage (footprint) and the trackline visible with a direct link to PANGAEA at https://marine-data.de/ . Note, within the DAM efforts, coverage (footprint) and trackline off all submitted bathymetry data will be made available to the community via OGC Web Map Services (WMS) and OGC Web Feature Services (WFS) . Avoid licence CC-0 & CC-BY-SA, if possible.

Which CC license choose for data? Check also [https://wiki.pangaea.de/wiki/License here]

=== (Standardized usage of ''Data model extensions)'' (for raw and processed data curation) ===

The usage of so-called ''data model extensions'' which are further ''attributes'' is currently developed. This is a new feature for PANGAEA in order to include more standardized metadata. This new feature shall insure further '''findabilty''' (F) and '''interoperability'''(I) of the datasets (more information is provided as soon as possible.....).

== Example datasets ==

=== Raw data ===

Damaske, Daniel; Becker, Marius (2021): Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV MARIA S. MERIAN during cruise MSM97/2. PANGAEA, https://doi.pangaea.de/10.1594/PANGAEA.927786

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+raw+data+(%22

=== Processed data ===
Simkins, Lauren M; Greenwood, Sarah L; Munevar Garcia, Santiago; Eareckson, Elizabeth; Anderson, John B; Prothro, Lindsay O (2021): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset) of RVIB NATHANIEL B. PALMER during cruise NBP150-02. PANGAEA, https://doi.org/10.1594/PANGAEA.937597, In: Simkins, LM et al. (2021): Pennell Trough, Ross Sea bathymetry and glacial landforms. PANGAEA, https://doi.org/10.1594/PANGAEA.937602

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data+(%22

Generic sensor format (GSF) data:

Dufek, Tanja; Schniotalla, Cara; Kinne, Stefan; Sternberg, Harald (2023): Multibeam bathymetry processed data (Kongsberg EM 122 working area dataset, Generic sensor format) of RV SONNE during cruise SO268/3, North Pacific Ocean. PANGAEA, https://doi.org/10.1594/PANGAEA.957204

further example data you can find here: https://www.pangaea.de/?q=citation%3Atitle%3A%22Multibeam+bathymetry+processed+data%22+AND+citation%3Atitle%3A%22Generic+Sensor+format%22

== How to submit bathymetry data to PANGAEA and what to do? ==

Please submit bathymetry data here https://www.pangaea.de/submit/. During submission, you may have to provide information for the data curation process (e.g. cruise, device, etc). For your submission, please edit/modify the title & abstract as stated above ("title construction kit").

'''Please always make individual submission's''' https://www.pangaea.de/submit/ '''for each resulting dataset as defined through the "construction kit"''' [[Bathymetry#Standardized Title]]

For raw data:

Usually for raw data, an upload area will be created for you where you can drop your files (on request). Feel free to drop your data as zip- or individual files. Please also include sound velocity profiles (only SVP raw data, e.g. MSM88_2-1_0.asvp) for raw data submission if available. Your files should not exceed a volume of 10GB, however several files can be uploaded simultaneously. Please avoid renaming of raw data files, even if they are imperfect.
If raw data from '''RV Sonne''', '''RV Maria S. Merian''', '''RV Polarstern''' or '''RV Meteor''' are being submitted, '''please make a comment in your submission before you upload any multibeam echosounder raw data files (e.g. .all format)'''. Please leave a comment: '''''Please take data from the MDM'''''.

For processed data:

Just drop your files after you get your upload link (see requirements above). If additional SVP's have been used for data processing, you can also upload these files too. 

===PANGAEA Data Submission Form Example===
[[File:workflow_underway.png|frame|Workflow: Processing of an Underway Data Submission]]please note that the table below show's the simplified data submission workflow. The data submission form can be accessed here https://www.pangaea.de/submit/<nowiki/>Further information can also be found here [[Data submission]] .
{| class="wikitable"
!|'''Field Name'''
!|'''Explanation'''
!|'''Content Example'''
|-
|Title
|Adapted, generalized [[#Standardized_Title]]
|Multibeam bathymetry raw data (Kongsberg EM 122 entire dataset) of RV SONNE during cruise SO250
|-
|Author(s)
|[[#Standardized_Authors]]
|[chief scientist], [responsible scientist(s)]
|-
|Keywords
|
|''(default)''
|-
| Abstract/Describe your Data
|[[#Standardized_Abstract]]; if the processed or raw data were already archived, the links may be placed here
|The survey data contain MBES measurements of the Fictional Bank canyon. No bathymetric measurements of Fictional Bank canyon were found in international databases prior to the cruise.
To enhance MBES data accuracy, two sound velocity profile casts were conducted in the vicinity of the working area prior to the survey using sound velocity profiler AML Oceanographic SVP Plus X. After processing, these data were directly imported into the MBES acquisition software Kongsberg SIS Seafloor Information System.
|-
| License
|[[#Licence]] 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 the 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).
|[https://creativecommons.org/licenses/by/4.0/ 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
|Files containing metadata information for the data
|
|}