cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.1594/pangaea.974300
title: Shipboard ADCP current measurements (38 kHz) during RV SONNE cruise SO307

description: Current velocities of the upper water column along the cruise track of R/V Sonne cruise SO307 were collected by a vessel-mounted 38 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 6.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 32.00 m, a blanking distance of 16.00 m, and a total of 50 bins, covering the depth range between 54.0 m and 1622.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-0.0783° +/- 0.6694°) and scale factor (1.0030 +/- 0.0104) of the measured velocities. The velocity data were averaged in time using an average interval of 180 s. Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'.
DOI: 10.57760/sciencedb.33417
title: Artificial Intelligence Invention Patent Data in the Yangtze River Delta Region from 2015 to 2019
title: 2015-2019年长三角地区人工智能发明专利数据

description: The data source of this article is Incopat Technology Innovation Information Retrieval Platform, and the retrieval time is November 10, 2020. For the topic of patent search, due to the wide scope of the artificial intelligence field and the numerous technical aspects involved, after referencing and synthesizing relevant materials [44] and referring to the relevant standards on artificial intelligence in the revised information technology of ISO, after several pre searches, the Chinese keyword search formula was finally determined as "artificial intelligence" or "pattern recognition" or "natural language processing" or "speech recognition" or "image recognition" or "video recognition" or "iris recognition" or "intelligent processor" or "intelligent robot" or "expert system" or "intelligent search" or "intelligent driving" or "machine learning" or "deep learning" or "neural network" or "computer vision"“ Cognitive Computing ". Set the patent application period from January 1, 2015 to December 31, 2019, with application addresses including" Shanghai "," Jiangsu "," Zhejiang ", and" Anhui ". Remove patents that contain these names but are not from the Yangtze River Delta provinces and cities, and then filter out search reports, translations, and short-term patents. 
description: The data source of this article is Incopat Technology Innovation Information Retrieval Platform, and the retrieval time is November 10, 2020. For the topic of patent search, due to the wide scope of the artificial intelligence field and the numerous technical aspects involved, after referencing and synthesizing relevant materials [44] and referring to the relevant standards on artificial intelligence in the revised information technology of ISO, after several pre searches, the Chinese keyword search formula was finally determined as "artificial intelligence" or "pattern recognition" or "natural language processing" or "speech recognition" or "image recognition" or "video recognition" or "iris recognition" or "intelligent processor" or "intelligent robot" or "expert system" or "intelligent search" or "intelligent driving" or "machine learning" or "deep learning" or "neural network" or "computer vision"“ Cognitive Computing ". Set the patent application period from January 1, 2015 to December 31, 2019, with application addresses including" Shanghai "," Jiangsu "," Zhejiang ", and" Anhui ". Remove patents that contain these names but are not from the Yangtze River Delta provinces and cities, and then filter out search reports, translations, and short-term patents.
DOI: 10.1594/pangaea.974246
title: Shipboard ADCP current measurements (75 kHz) during RV MARIA S. MERIAN cruise MSM127

description: This report describes the processing of current velocities of the upper water column along the cruise track of R/V Maria S. Merian cruise MSM127 collected by a vessel-mounted 75 kHz RDI Ocean Surveyor ADCP. The expedition took place during 18.03.2024- 20.04.2024 from Las Palmas to Las Palmas (Gran Canaria) in the Northern Atlantic. Data were recorded mostly in the EEZs of Mauritania. The main objective of the MSM127 (Bremen Cluster expedition MAURIBO) research expedition was aimed at obtaining long sedimentary records by using the Bremen sea floor drill rig MeBo70. Data acquisition of the ADCP current velocities is supported by the DAM Underway Project and published according to the FAIR principles. The ADCP transducer was located at 6.0 m below the water line. The instrument was operated in broadband mode (WM1) with a bin size of 8.00 m, a blanking distance of 8.00 m, and a total of 100 bins, covering the depth range between 22.0 m and 814.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-47.3549° +/- 0.5297°) and scale factor (1.0080 +/- 0.0090) of the measured velocities. The velocity data were averaged in time using an average interval of 120 s. Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'.
DOI: 10.1594/pangaea.974251
title: Shipboard ADCP current measurements (38 kHz) during RV METEOR cruise M203

description: Current velocities of the upper water column along the cruise track of R/V Meteor cruise M203 were collected by a vessel-mounted 38 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 5.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 32.00 m, a blanking distance of 16.00 m, and a total of 55 bins, covering the depth range between 53.0 m and 1781.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (0.0691° +/- 0.5613°) and scale factor (1.0054 +/- 0.0088) of the measured velocities. The velocity data were averaged in time using an average interval of 60 s. Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'.
DOI: 10.1594/pangaea.974242
title: Shipboard ADCP current measurements (75 kHz) during RV SONNE cruise SO304

description: Current velocities of the upper water column along the cruise track of R/V Sonne cruise SO304 were collected by a vessel-mounted 75 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 6.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 8.00 m, a blanking distance of 8.00 m, and a total of 100 bins, covering the depth range between 22.0 m and 814.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-0.0343° +/- 0.7392°) and scale factor (1.0001 +/- 0.0164) of the measured velocities. The velocity data were averaged in time using an average interval of 300 s. Depth cells with ensemble-averaged percent-good values below 50% are marked as 'bad data'.
DOI: 10.1594/pangaea.974252
title: Shipboard ADCP current measurements (75 kHz) during RV METEOR cruise M203

description: Current velocities of the upper water column along the cruise track of R/V Meteor cruise M203 were collected by a vessel-mounted 75 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 5.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 8.00 m, a blanking distance of 4.00 m, and a total of 100 bins, covering the depth range between 17.0 m and 809.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-46.4281° +/- 0.5612°) and scale factor (1.0069 +/- 0.0086) of the measured velocities. The velocity data were averaged in time using an average interval of 60 s. Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'.
DOI: 10.15468/dl.24npv8
title: Occurrence Download

description: A dataset containing 77 species occurrences available in GBIF matching the query:
{
 "and" : [
 "Country is China",
 "HasCoordinate is true",
 "HasGeospatialIssue is false",
 "TaxonKey is Moschus berezovskii"
 ]
}

 The dataset includes 77 records from 6 constituent datasets; see https://api.gbif.org/v1/occurrence/download/0048453-251120083545085/datasets/export for details.
 
Data from some individual datasets included in this download may be licensed under less restrictive terms.
DOI: 10.1594/pangaea.974226
title: Shipboard ADCP current measurements (75 kHz) during RV METEOR cruise M192/2

description: Current velocities of the upper water column along the cruise track of R/V Meteor cruise M192/2 were collected by a vessel-mounted 75 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 5.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 8.00 m, a blanking distance of 4.00 m, and a total of 100 bins, covering the depth range between 17.0 m and 809.0 m. Heading, pitch and roll data from the ship's motion reference unit and the navigation data from the Global Positioning systems were used by the data acquisition software VmDAS internally to convert ADCP velocities into earth coordinates. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. The ship's velocity was calculated from position fixes obtained by the Global Positioning System (GPS). Accuracy of the ADCP velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data post-processing included water track calibration of the misalignment angle (0.1526° +/- 0.5397°) and scale factor (1.0061 +/- 0.0094) of the Ocean Surveyor signal. The velocity data were averaged in time using an average interval of 60 s. Velocity quality flagging is based on different threshold criteria: Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'. Depth cells with velocities above 1.5 m/s are flagged as 'bad data'. Depth cells with a root-mean-square deviation between the measured ensemble-average velocity and a cell-wise running-mean velocity above 0.3 m/s are flagged as 'probably bad data'.
DOI: 10.1594/pangaea.974292
title: Shipboard ADCP current measurements (75 kHz) during RV MARIA S. MERIAN cruise MSM56

description: Current velocities of the upper water column along the cruise track of R/V Maria S. Merian cruise MSM56 were collected by a vessel-mounted 75 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 6.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 8.00 m, a blanking distance of 8.00 m, and a total of 100 bins, covering the depth range between 22.0 m and 814.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Single-ping data were screened for bottom signals and, where appropriate, a bottom mask was manually processed. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-48.3423° +/- 0.6544°) and scale factor (0.9983 +/- 0.0113) of the measured velocities. The velocity data were averaged in time using an average interval of 180 s. Depth cells with ensemble-averaged percent-good values below 50% are marked as 'bad data'. Furthermore, the time series of cell 1 to 4 are flagged as 'potentially correctable bad data' because of velocities biases most likely caused by transducer ringing.
DOI: 10.1594/pangaea.974282
title: Shipboard ADCP current measurements (38 kHz) during RV SONNE cruise SO305

description: Current velocities of the upper water column along the cruise track of R/V Sonne cruise SO305 were collected by a vessel-mounted 38 kHz RDI Ocean Surveyor ADCP. The ADCP transducer was located at 6.0 m below the water line. The instrument was operated in narrowband mode (WM10) with a bin size of 32.00 m, a blanking distance of 16.00 m, and a total of 55 bins, covering the depth range between 54.0 m and 1782.0 m. Attitude data from the ship's motion reference unit were used by the data acquisition software VmDAS internally to convert ADCP beam velocities to geographic coordinates. The Python toolbox OSADCP (version 2.0.0) was used for data post-processing. Acoustic Interferences were identified based on outliers in the ADCP echo intensity data. Echo intensity data were cleaned accordingly and affected velocity cells were flagged to be removed prior ensemble-averaging. The ship's velocity was calculated from position fixes obtained by the Global Navigation Satellite System (GNSS), taking into account lever arms of ADCP transducer and GNSS antenna. Accuracy of the derived water velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data processing included water track calibration of the misalignment angle (-0.3026° +/- 0.5541°) and scale factor (1.0053 +/- 0.0095) of the measured velocities. The velocity data were averaged in time using an average interval of 60 s. Depth cells with ensemble-averaged percent-good values below 25% are marked as 'bad data'.
DOI: 10.1594/pangaea.953082
title: Continuous thermosalinograph oceanography along RV SONNE cruise track SO287

description: Underway temperature and salinity data was collected along the cruise track with two autonomous measurement systems, called self-cleaning monitoring boxes (SMBs). Usually, the SMBs are changed after 12 hours. While temperature is taken at the water inlet in about 4 m depth, salinity is estimated within the SMB from conductivity and interior temperature. Salinity and temperature were calibrated with CTD values from 7m depth. For details to all processing steps see Data Processing Report.
DOI: 10.1594/pangaea.935587
title: Multibeam bathymetry raw data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM02/3

description: Multibeam bathymetry raw data using the ship's own Kongsberg (Simrad) EM 1002 multibeam echosounder was almost continuously recorded during RV MARIA S. MERIAN cruise MSM02/3. Data were recorded on 17 days between 2006-07-31 and 2006-08-17. Data cover various areas of shoreline and fjord system of Svalbard. The approximate average depth of the entire dataset is around 200m.The data are archived at the Federal Maritime and Hydrographic Agency of Germany (Bundesamt für Seeschifffahrt und Hydrographie, BSH) and provided to PANGAEA database for data curation and publication. No ancillary sound velocity profiles (SVP) from the cruise are archived at the BSH, thus added to this dataset. However, data analysis of the raw data reveled that SVP has been changed on several occasions during the cruise.This publication is conducted within the efforts of the German Marine Research Alliance in the core area "Data management and Digitalization" (Deutsche Allianz Meeresforschung, DAM).Data are unprocessed and therefore may contain incorrect depth measurements (artifacts) 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).
description: These data should not be used for navigational purposes.Data publishing was realized by Daniel Damaske, MARUM - Center for Marine Environmental Sciences (University Bremen).
DOI: 10.1594/pangaea.938470
title: Continuous thermosalinograph oceanography along RV Sonne cruise SO276

description: Underway temperature and salinity data was collected along the cruise track with two autonomous measurement systems, called self-cleaning monitoring boxes (SMBs). Usually, the SMBs are changed after 12 hours. However, on this cruise only SMB_B was working properly. While temperature is taken at the water inlet in about 3 m depth, salinity is estimated within the SMB from conductivity and interior temperature. No calibration was performed, neither for temperature nor for salinity. For details to all processing steps see Data Processing Report.
DOI: 10.1594/pangaea.938252
title: ADCP current measurements (75 kHz) during Meteor cruise M170

description: Upper-ocean velocities along the cruise track of Meteor cruise M170 were continuously collected by a vessel-mounted Teledyne RD Instruments 75 kHz Ocean Surveyor ADCP. The transducer was located at 5.0 m below the water line. The instrument was operated in narrowband mode with 8 m bins and a blanking distance of 4.0 m, while 100 bins were recorded using a pulse of 1.43 s. The ship's velocity was calculated from position fixes obtained by the Global Positioning System (GPS). Heading, pitch and roll data from the ship's gyro platforms and the navigation data were used by the data acquisition software VmDas internally to convert ADCP velocities into earth coordinates. Accuracy of the ADCP velocities mainly depends on the quality of the position fixes and the ship's heading data. Further errors stem from a misalignment of the transducer with the ship's centerline. Data post-processing included water track calibration of the misalignment angle ( -0.18° +/- 0.5601°) and scale factor (0.9992 +/- 0.0098) of the Ocean Surveyor signal. The average interval was set to 60 s.
description: Velocity quality flagging is based on following threshold criteria: abs(UC) or abs(VC) &gt; 2.0 m/s, rms(UC_z) or rms(VC_z) &gt; 0.3.
DOI: 10.1594/pangaea.938474
title: Continuous thermosalinograph oceanography along RV Meteor cruise M169

description: Underway temperature and salinity data was collected along the cruise track with two autonomous thermosalinograph (TSG) systems, each consisting of a SBE21 TSG together with a SBE38 Thermometer. Both systems worked independent from each other throughout the cruise. While temperature is taken at the water inlet in about 2.5 m depth, salinity is estimated within the interior TSG from conductivity and interior temperature. No correction against independent data was performed for temperature and salinity. Finally, TSG1 was chosen for publication. For details to all processing steps see Data Processing Report.
DOI: 10.1594/pangaea.938269
title: Continuous thermosalinograph oceanography along RV Maria S. Merian cruise MSM99/2

description: Underway temperature and salinity data was collected along the cruise track with two autonomous measurement systems. Usually, the systems are changed after 6 hours. While temperature is taken at the water inlet in about 6.5 m depth, salinity is estimated within the interior measurement container from conductivity and interior temperature. Salinity was calibrated independently for both measurement containers (MCs). No correction was done for temperature. For details to all processing steps see Data Processing Report.
description: Salinity Offset MC1 = 0.000542 Salinity Offset MC2 = -0.003731