gov.noaa.ngdc.mgg.multibeam:EX1605L2_Multibeam
eng; USA
utf8
EX1605L2
series
multibeam series-level metadata
2016-07
ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data
ISO 19115-2:2009(E)
Multibeam Collection for EX1605L2: CAPSTONE CNMI and Mariana Trench MNM (Mapping)
EX-06-05-L2
EX1605L2
2016-07
publication
EX1605L2_Multibeam
Multibeam raw (level-0) files (.raw), post-processed (level-1) Generic Sensor Format data files store post-processed multibeam data before processing into either vector or raster form (.gsf), data products (level-2) (.asc, .kmz, .sd, .tif, .xyz) generated during post-processing, as well as the spreadsheet the processors used to annotate their processing steps (.xls).
To collect, quality-control, and post-process multibeam bathymetric data during the mission into clean, edited data and data products.
completed
unknown
OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY
theme
multibeam
theme
None
CNMI
Commonwealth of the Northern Marianas Islands
Fryer Guyot
Guam
Mariana Arc
Mariana Basin
Marianas Trench
Marianas Trench Marine National Monument
MTMNM
West Mariana Ridge
place
None
otherRestrictions
otherRestrictions
Access Constraints: None. Use Constraints: The user is responsible for the results of any application of this data for other than its intended purpose. Distribution Liability: While NCEI makes every effort to ensure that its databases are error-free, errors do occur. We ask that you notify us immediately of any errors that you discover in our data. We will make every effort to correct them. With respect to documents available from this server, neither the United States Government nor any of its employees, makes any warranty, express or implied, including the warranties of merchantability and fitness for a particular purpose; nor assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed; nor represents that its use would not infringe privately owned rights.
EX1605L2: CAPSTONE CNMI and Mariana Trench MNM (Mapping) on NOAA Ship Okeanos Explorer between 20160520 and 20160611
2016-07
creation
http://www.ncddc.noaa.gov/oer-waf/ISO/Resolved/2016/EX1605L2_COLLECTION_RESOLVED.xml
EX1605L2
largerWorkCitation
collection
eng; USA
oceans
geoscientificInformation
141.36
147.31
18.34
23.4
2016-05-20
2016-06-11
distributor
http://maps.ngdc.noaa.gov/viewers/multibeam/index.html?minx=141.36&miny=18.34&maxx=147.31&maxy=23.4
http://www.ngdc.noaa.gov/nndc/struts/results?op_0=eq&v_0=EX1605L2&t=101378&s=8&d=70&d=75&d=76&d=74&d=73&d=72&d=81&d=82&d=85&d=86&d=79&no_data=suppress
http://www.ngdc.noaa.gov/nndc/struts/results?op_0=l&v_0=&op_1=l&v_1=&op_2=l&v_2=EX1605L2&t=101378&s=2&d=6
The full-resolution multibeam .all files (Level-0 data) were copied into CARIS HIPS 8.1., and then processed and cleaned. Each line was exported to a .gsf, https://www.leidos.com/maritime/gsf, (Level-1 data). The processed and cleaned files were used to create a BASE surface in CARIS HIPS 8.1, which was then exported to ASCII XYZ text file. That ASCII XYZ file was used to generate a shaded relief DTM (SD file) in QPS, Inc. Fledermaus software, which was then used to create Geotiff files, ArcView Grids, Google Earth KMZ files, and Fledermaus scene files (Level-2 data). The data are believed to be complete in accordance with the ship's multibeam data acquisition and processing logs.
These files were tested by opening in Google Earth Pro to ensure that geospatial content of the files is not corrupted and is consistent with the Level 0 data.
The bathymetry data were generated using a Kongsberg EM302 multibeam system, and recorded using Kongsberg's Seafloor Information System (SIS) software as *.all files. Collocated to the bathymetric data, bottom backscatter data were collected stored within *.all files, both as beam averaged backscatter values, and as full time series values within each beam. Realtime corrections to the data include: continuous application of surface sound speed obtained with a hull-mounted SBE 45 thermosalinograph, application of sound speed profiles obtained with Sippican Deep Blue Expendable Bathythermographs (XBTs) and / or Seabird CTD 9/11, application of roll, pitch, and heave motion corrections obtained with POS M/V V.4 motion sensor unit. Each raw multibeam file was imported into CARIS HIPS and SIPS 8.1. Each file was individually cleaned of errant depth values using CARIS's Swath Editor. The files were then added to a cumulative gridded Base Surface within CARIS, and further cleaned of errant depth values using CARIS's Subset Editor, taking advantage of available overlapping swaths. Motion corrector values from POS M/V V. 4 applied in real-time were verified in CARIS's Attitude and Navigation editors. No tidal corrections were applied. The ASCII XYZ file was then imported into QPS Fledermaus v.7 to build an *.sd file. The *.sd file retains the resolution of the source gridded ASCII XYZ data. The *.sd file format was selected for its ability to be viewed using the Fledermaus iView4D freeware distributed by QPS.
Multibeam data was processed into Fledermaus scene files used in planing remotely-operated vehicle dives. A scene file is a combination of SD files saved into a single file, which when opened opens all the SD files in one scene . Scene files with up to four layers are viewable in Fledermaus freeware, iView4D. To create these multi-layer Fledermaus scene files, a number of additional field processing steps were performed on a subset of the multibeam files. Bathymetric SD files were run through the "Compute Slope" function in Fledermaus to generate seafloor slope maps. Fledermaus Geocoder Tool v7.3 was used to create bottom backscatter mosaic SD files. The mosaics were then draped over the bathymetric SD files using the "Attach Scalar to Surface" function in Fledermaus. ROV Dive Track points were placed on the seafloor in Fledermaus using the Geo-Picking tool, and were saved as a points layer in the scene file. Selected water column files were processed using Fledermaus FMMW, and anomalies, in particular suspected seep locations, were exported so Fledermaus SD files. These data layers were opened simultaneously in Fledermaus, then saved as a scene file with up to four layers.
processor