API src

Found 384 results.

Related terms

Other language confidence: 0.5623832997602402

Multibeam bathymetry raw data (Kongsberg EM2040 entire dataset) of RV ALKOR during cruise AL644

Swath sonar bathymetry data recorded during AL644 on RV ALKOR using the hull-mounted Kongsberg EM2040 multibeam echosounder. The cruise took place between 17.11.2025 - 28.11.2025 in the German Baltic Sea. The approximate depth range of the mapped areas is between 10-30m. To improve MBES data quality, sound velocity profile (SVP) casts were conducted in the vicinity of the mapped area prior to and after each survey using a CTD. The data set includes data from the 'Adlergrund' (ADG), located within the Pommeranian Bay/Rønne Bank Nature Conservation Area (NCA), from the 'Kadet Trench ('KDR') NCA and the Fehmarn Belt ('FB') NCA. The mapping has been conducted for baseline habitat studies in the area.

Multibeam bathymetry raw data (Kongsberg EM712 entire dataset) of RV HEINCKE during cruise HE659

Raw multibeam bathymetry data from the Kongsberg EM712 was acquired during the RV Heincke cruise HE659 in the German Bight in April 2025. The data was generally acquired during calm seas in water depths between 20 and 50 m. Primarily three different regions were surveyed (Borkumer Reef Ground, Sylt Outer Reef, and Helgoland). Generally the data is comprehensive and overlapping swaths creating a continuous bathymetry were archived. In some areas the data was acquired complementary to sidescan sonar surveys and individual tracks do not overlap. Data are unprocessed and therefore may contain some incorrect depth measurements (artifacts) without further processing. No tide variations are applied. Sound velocity profiles were acquired regularly. Overall, it appears that the data quality is rather good. The gridded data showed relatively few obstacles.

Multibeam bathymetry raw data (Atlas Hydrosweep DS 3 echo sounder entire dataset) of RV POLARSTERN during cruise PS142

Multibeam data were collected with RV Polarstern along the route of cruise PS142 and data acquisition was continuously monitored during the survey. Multibeam sonar system was Teledyne/Atlas Hydrosweep DS3. SVPs were retrieved from CTD data and synthetic profiles from World Ocean Atlas 18. SVPs were processed with HydrOffice SoundSpeedManager (https://www.hydroffice.org/soundspeed/main) and extended with World Ocean Atlas 18 (https://www.ncei.noaa.gov/archive/accession/NCEI-WOA18). SVP data were applied during acquisition. Multibeam data are unprocessed and may contain outliers and blunders and should not be used for grid calculations and charting projects without further editing. The raw multibeam sonar data in Teledyne Reson multibeam processing format (.s7k) were recorded with Teledyne PDS software. Raw data files can be processed using software packages like CARIS HIPS/SIPS. For updated vessel configuration files check further details.

Multibeam bathymetry processed data (Atlas Hydrosweep DS 3 echo sounder entire dataset) of RV POLARSTERN during cruise PS145/1, Atlantic Ocean

Multibeam data were collected during RV Polarstern cruise PS145/1 (2024-11-25 to 2024-12-07). Multibeam sonar system was Atlas Hydrographic Hydrosweep DS 3 multibeam echo sounder. Data are processed with Caris HIPS, including sound velocity correction with SV data from SVPs, CTDs and World Ocean Atlas 18 (https://www.ncei.noaa.gov/archive/accession/NCEI-WOA18), tidal correction with TPXO9_atlas_v5 (https://www.tpxo.net), and manual cleaning. The soundings are combined in daily files, the format is XYZ ASCII (<Lon> <Lat> <Depth in meters, positive up, relative to mean sea level>). Additional grids have been computed with depth dependent cell size to visualize the data. These grids are not meant for scientific analysis or navigation, but for overview purposes only.

Multibeam bathymetry raw data (Atlas Hydrosweep DS 3 echo sounder entire dataset) of RV POLARSTERN during cruise PS151

Multibeam data were collected with RV Polarstern along the route of cruise PS151 and data acquisition was almost continuously monitored during the survey. Multibeam sonar system was Teledyne/Atlas Hydrosweep DS3. SVPs were retrieved from CTD data and synthetic profiles from World Ocean Atlas 23. SVPs were processed with HydrOffice SoundSpeedManager (https://www.hydroffice.org/soundspeed/main) and extended with World Ocean Atlas 23 (https://www.ncei.noaa.gov/archive/accession/NCEI-WOA23). SVP data were applied during acquisition. Multibeam data are unprocessed and may contain outliers and blunders and should not be used for grid calculations and charting projects without further editing. The raw multibeam sonar data in Teledyne Reson multibeam processing format (.s7k) were recorded with Teledyne PDS software. Raw data files can be processed using software packages like CARIS HIPS/SIPS. For updated vessel configuration files check further details.

Multibeam bathymetry processed data (EM 1002 echosounder entire dataset) of RV MARIA S. MERIAN during cruise MSM52

Swath sonar bathymetry data used for that dataset was recorded during RV MARIA S. MERIAN cruise MSM52 using Kongsberg EM1002 multibeam echosounder. The cruise took place between 01.03.2016 and 28.03.2016 in the Baltic Sea. The cruise aimed gapless imagining of the major pre-alpine tectonic lineaments due to the fact that the Glückstadt Graben and the Avalonia-Baltica suture zone run across the southern Baltic [DOI: 10.2312/cr_msm52]. CI Citation: Paul Wintersteller (seafloor-imaging@marum.de) as responsible party for bathymetry raw data ingest and approval. During the MSM52 cruise, the moonpooled KONGSBERG EM1002 multibeam echosounder (MBES) was utilized to perform bathymetric mapping in shallow depths. It has a curved transducer of which 111 beams are formed for each ping while the seafloor is detected using amplitude and phase information for each beam sounding. For further information on the system, consult https://www.km.kongsberg.com/. Generally, the system was acquiring data throughout the entire cruise. Responsible person during this cruise / PI: Laura Frahm. Postprocessing and products were conducted by the Seafloor-Imaging & Mapping group of MARUM/FB5, responsible person Paul Wintersteller (seafloor-imaging@marum.de). The open source software MB-System (Caress, D. W., and D. N. Chayes, MB-System: Mapping the Seafloor, https://www.mbari.org/products/research-software/mb-system, 2017) was utilized for this purpose. A sound velocity correction profile was applied to the MSM52 data; there were no further corrections for roll, pitch and heave applied during postprocessing. A tide correction was applied, based on the Oregon State University (OSU) tidal prediction software (OTPS) that is retrievable through MB-System. CTD measurements during the cruise were sufficient to represent the changes in the sound velocity throughout the study area. Using Mbeditviz, artefacts were cleaned manually. NetCDF (GMT) grids of the edited data as well as statistics were created with mbgrid. The published bathymetric EM1002 grid of the cruise MSM52 has a resolution of 35 m. No total propagated uncertainty (TPU) has been calculated to gather vertical or horizontal accuracy. A higher resolution is, at least partly, achievable. The grid extended with _num represents a raster dataset with the statistical number of beams/depths taken into account to create the depth of the cell. The extended _sd -grid contains the standard deviation for each cell. The DTMs projections are given in Geographic coordinate system Lat/Lon; Geodetic Datum: WGS84.

Biotopkartierung (SH4) Marine Daten

Der vorliegende Geodatensatz umfasst alle bis zum angegebenen Stand kartierten bzw. abgegrenzten FFH-Lebensraumtypen (= LRT) der Meeresgewässer und Gezeitenzonen (1110, 1130. 1140, 1160, 1170) ohne die LRT 1110 und 1170 der Ostsee, für die ein separater Datensatz bereitgestellt wird. Die Abgernzungen in der Nordsee wurden durch die zuständige Nationalparkverwaltung durchgeführt bzw. mit ihr abgestimmt und spiegeln den aktuellen Kenntnisstand wieder. Die Abgrenzungen in der Ostsee wurden in Abstimmung mit der Abteilung Wasserwirtschaft, Dezernat Küstengewässer z. T. anhand von Tiefenlinien und Exposition durchgeführt. Die Abgrenzungen erfolgten i. d. R. nicht durch tatsächliche Kartierung im klassischen Sinne durch Inaugenscheinnahme, sondern durch Detektion (z.B. Sonar) und dient in erster Linie der Abgrenzung LRT zur Erfüllung europarechtlicher Berichtspflichten. Die Anspache der z.T. flächenidentischen gesetzlichen Biotope sowie die Bewertung des Erhaltungsgrades der LRT wird in diesem Datensatz nicht abgebildet. Weitergehende Erläuterung zum Begriff "Wertbiotop": Im Rahmen der BK gehören zu den Wertbiotopen grundsätzlich alle Flächen, die entweder als gesetzlich geschützte Biotope gemäß § 30 BNatSchG i. V. m. § 21 LNatSchG gelten und/oder als Lebensraumtyp (LRT) gemäß Anhang I der FFH-Richtlinie (92/43/EWG, 21.05.1992) anzusprechen sind. Hinsichtlich des gesetzlichen Biotopschutzes ist der Stand nach der Novellierung des Landesnaturschutzgesetzes (LNatSchG) in 2016 (Veröffentlichung in dem GVO Nr. 7 vom 23.06.2016, Seite 162) berücksichtigt und schließt das „arten-und strukturreiche Dauergrünland“ mit ein. Auch die Änderungen aufgrund des § 21 Absatz 7 des Landesnaturschutzgesetzes (LNatSchG), zuletzt geändert durch Verordnung vom 27. März 2019 (GVOBl. Schl.-H. S. 85), sind berücksichtigt sowie - soweit bereits erhoben bzw. in Schleswig-Holstein überhaupt v.h. - auch die seit dem 1. März 2022 gem. § 30 Absatz 1 Nummer 7 BNatSchG neu erfassten gesetzlich geschützten Biotope. Zu den Wertbiotopen gehören im vorliegenden Geodatensatz sämtliche Flächen/ Geometrien, die in den Tabellenspalten „BTSCHUTZ_1“ und/oder „BTSCHUTZ_2“ der Attributtabelle einen Eintrag einer Biotopverordnungsnummer (VO) oder die in den Tabellenspalten „LRT_TYP_1“ und/oder „LRT_TYP_2“ einen Eintrag eines Natura 2000- bzw. EU-LRT-Codes aufweisen. Nachrichtlich weist das LfU darauf hin, dass der Schutz des § 30 BNatSchG i. V. m. § 21 LNatSchG aktiviert wird, wenn und sobald eine Fläche die charakteristischen Merkmale eines gesetzlich geschützten Biotopes erfüllt. Der in § 30 Abs. 7 thematisierten Registrierung, die sich nach Landesrecht richtet und zumeist in Biotopkartierungen, Listen oder Biotopverzeichnissen ihren Niederschlag findet, kommt daher eine lediglich deklaratorische Bedeutung zu. D.h. nicht erst durch die Kartierung bzw. Erfassung und Registrierung werden Flächen zum geschützten Biotop, sondern der Charakter als gesetzlich geschütztes Biotop ergibt sich unmittelbar aus dem Gesetz. Bei Fragen und in Zweifelsfällen ist mit der fachlich zuständigen Person im LfU Rücksprache zu halten. Hinweis: Daten der maritimen LRT 1110 und 1170 in der Ostsee, befinden sich in dem separaten Geodatensatz "Maritim_Daten_Ostsee_LRT_1110_und_1170".

GTS Bulletin: SIVX81 EDZW - Surface data (details are described in the abstract)

The SIVX81 TTAAii Data Designators decode as: T1 (S): Surface data T1T2 (SI): Intermediate synoptic hour (Remarks from Volume-C: SHIP)

GTS Bulletin: ISND74 AMDW - Observational data (Binary coded) - BUFR (details are described in the abstract)

The ISND74 TTAAii Data Designators decode as: T1 (I): Observational data (Binary coded) - BUFR T1T2 (IS): Surface/sea level T1T2A1 (ISN): Synoptic observations from fixed land stations at non-standard time (i.e. 01, 02, 04, 05, ... UTC) A2 (D): 90°E - 0° northern hemisphere (Remarks from Volume-C: NATIONAL AUTOMATIC SYNOP)

GTS Bulletin: ISND03 EDZW - Observational data (Binary coded) - BUFR (details are described in the abstract)

The ISND03 TTAAii Data Designators decode as: T1 (I): Observational data (Binary coded) - BUFR T1T2 (IS): Surface/sea level T1T2A1 (ISN): Synoptic observations from fixed land stations at non-standard time (i.e. 01, 02, 04, 05, ... UTC) A2 (D): 90°E - 0° northern hemisphere (The bulletin collects reports from stations: 10609;Trier-Petrisberg;10616;Hahn;10641;Offenbach-Wetterpark;10655;Würzburg;10675;Bamberg;10688;Weiden;10708;Saarbrücken-Ensheim;10729;Mannheim;10731;Rheinstetten;10742;Öhringen;10776;Regensburg;10791;Großer Arber;10805;Lahr;10815;Freudenstadt;10836;Stötten;10870;München-Flughafen;10895;Fürstenzell;10908;Feldberg/Schwarzwald;10929;Konstanz;10948;Oberstdorf;10961;Zugspitze;10962;Hohenpeißenberg;) (Remarks from Volume-C: SYNOP)

1 2 3 4 5 … 37 38 39