Saved in:
| Main Authors: | , , , , |
|---|---|
| Format: | Dataset Open Access |
| Language: | en |
| Published: |
PANGAEA
2024
|
| Subjects: | |
| Online Access: | https://doi.org/10.1594/PANGAEA.974280 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1867168231926530048 |
|---|---|
| author | Kopte, Robert Merten, Veronique Schulz, Marco Hoving, Henk-Jan T Schütte, Florian |
| author_facet | Kopte, Robert Merten, Veronique Schulz, Marco Hoving, Henk-Jan T Schütte, Florian |
| collection | Datos científicos de ciencias marinas y ambientales |
| contents | Current velocities of the upper water column along the cruise track of R/V Meteor cruise M202 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.0492° +/- 0.5431°) and scale factor (1.0041 +/- 0.0107) 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'. |
| format | Dataset Open Access |
| id | pangaea_https___doi_org_10_1594_PANGAEA_974280 |
| institution | PANGAEA |
| language | en |
| publishDate | 2024 |
| publisher | PANGAEA |
| record_format | pangaea |
| spellingShingle | Shipboard ADCP current measurements (38 kHz) during RV METEOR cruise M202 Kopte, Robert Merten, Veronique Schulz, Marco Hoving, Henk-Jan T Schütte, Florian Backscatter, relative; Current velocity, east-west; Current velocity, north-south; DAM_Underway; DAM Underway Research Data; DataHub; DataHub Earth and Environment of the Helmholtz Association; DATE/TIME; DEPTH, water; Echo intensity; Echo intensity, cleaned; ISAAC; LATITUDE; LONGITUDE; M202; M202_0_Underway-5; Meteor (1986); Percent good pings; Pings, averaged to a double ensemble value; Quality flag, current velocity; Seadatanet flag: Data quality control procedures according to SeaDataNet (2010); Vessel mounted Acoustic Doppler Current Profiler [38 kHz]; VMADCP-38 Current velocities of the upper water column along the cruise track of R/V Meteor cruise M202 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.0492° +/- 0.5431°) and scale factor (1.0041 +/- 0.0107) 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'. |
| title | Shipboard ADCP current measurements (38 kHz) during RV METEOR cruise M202 |
| topic | Backscatter, relative; Current velocity, east-west; Current velocity, north-south; DAM_Underway; DAM Underway Research Data; DataHub; DataHub Earth and Environment of the Helmholtz Association; DATE/TIME; DEPTH, water; Echo intensity; Echo intensity, cleaned; ISAAC; LATITUDE; LONGITUDE; M202; M202_0_Underway-5; Meteor (1986); Percent good pings; Pings, averaged to a double ensemble value; Quality flag, current velocity; Seadatanet flag: Data quality control procedures according to SeaDataNet (2010); Vessel mounted Acoustic Doppler Current Profiler [38 kHz]; VMADCP-38 |
| url | https://doi.org/10.1594/PANGAEA.974280 |