Multibeam Bathymetry Data Collected in December 2017, February and March 2018 at Looe Key, the Florida Keys

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Multibeam Bathymetry Data Collected in December 2017, February and March 2018 at Looe Key, the Florida Keys
Abstract:
An Ellipsoidally Referenced Survey (ERS) using two Teledyne Reson SeaBat T50-P multibeam echosounders, in dual-head configuration, was conducted by the U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) at Looe Key, the Florida Keys, during three separate survey legs: December 14-16, 2017, February 2-9, 2018 and March 9-11, 2018. This dataset, Looe_Key_2017_2018_MBB_xyz.zip, includes the processed elevation point data (x,y,z), as derived from a 1-meter (m) bathymetric grid.
Supplemental_Information:
The processed sonar data are provided as an American Standard Code for Information Interchange (ASCII) x,y,z point data file. These values are not the individual soundings, but nodes from a 1-meter (m) bathymetric grid. The Z value for the node is generated by utilizing a Combined Uncertainty and Bathymetry Estimator (CUBE) surface and has an estimated total value of uncertainty (Calder and Wells, 2007). The bathymetry data were collected and processed in the World Geodetic System of 1984 (WGS84) vertical and horizontal datums. If the data are needed in any additional datums, it is recommended that the transformation be performed using the National Oceanic and Atmospheric Administration (NOAA) VDatum version 3.9 transformation software (https://vdatum.noaa.gov/). Data were collected under Florida Keys National Marine Sanctuary permit FKNMS-2016-068.
  1. How might this data set be cited?
    Fredericks, Jake J., Reynolds, Billy J., Farmer, Andrew S., Yates, Kimberly K., and Zawada, David G., 20190722, Multibeam Bathymetry Data Collected in December 2017, February and March 2018 at Looe Key, the Florida Keys: U.S. Geological Survey Data Release doi:10.5066/P9P2V7L0, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -81.44440279
    East_Bounding_Coordinate: -81.36410970
    North_Bounding_Coordinate: 24.59726971
    South_Bounding_Coordinate: 24.53287782
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 14-Dec-2017
    Ending_Date: 11-Mar-2018
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Point (43736982)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 17
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -81.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.6096
      Ordinates (y-coordinates) are specified to the nearest 0.6096
      Planar coordinates are specified in meters
      The horizontal datum used is World Geodetic System of 1984.
      The ellipsoid used is WGS_84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: World Geodetic System of 1984
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    2017_373_LooeKey_MBES_1m_WGS84_UTM17N.xyz
    ASCII comma-delimited text (.txt) file containing the processed 1-m bathymetric grid x,y,z data in the WGS84 [G1762] realization (ellipsoid height). (Source: HYPACK)
    WGS84_UTM17N_X
    WGS84 UTM Zone 17N X-coordinate (easting) of sample point, in meters. (Source: HYPACK)
    Range of values
    Minimum:455010.000
    Maximum:463120.000
    Resolution:0.001
    WGS84_UTM17N_Y
    WGS84 UTM Zone 17N Y-coordinate (northing) of sample point, in meters. (Source: HYPACK)
    Range of values
    Minimum:2713298.000
    Maximum:2720404.000
    Resolution:0.001
    WGS84_Z
    WGS84 (ellipsoid height) of sample point, in meters. (Source: HYPACK)
    Range of values
    Minimum:-61.454
    Maximum:-24.958
    Resolution:0.001
    TPU
    TPU = Total Propagated Uncertainty (Source: CARIS)
    Range of values
    Minimum:0.032
    Maximum:0.512
    Resolution:0.001

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Jake J. Fredericks
    • Billy J. Reynolds
    • Andrew S. Farmer
    • Kimberly K. Yates
    • David G. Zawada
  2. Who also contributed to the data set?
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
  3. To whom should users address questions about the data?
    Jake J. Fredericks
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

    (727)502-8000 (voice)
    jfredericks@usgs.gov

Why was the data set created?

The purpose of the survey was to collect high density multibeam bathymetry data of Looe Key in an effort to assess sediment accumulation within the survey area. Data were collected during USGS field activity number (FAN) 2017-373-FA. Additional survey and data details are available from the USGS Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-373-FA.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 2018 (process 1 of 3)
    Acquisition: An ERS was conducted using two Teledyne Reson SeaBat T50-P multibeam echosounders, in dual-head configuration. The pair of Mills Cross [configuration] transmit and receive arrays, were placed side-by-side within a bracket that oriented them at opposing 30-degree angles (relative to horizontal). The bracket was pole-mounted on the starboard gunnel of the R/V Sallenger, a 26-ft fiberglass research vessel. The sonar arrays were oriented athwartships (primary and secondary arrays facing outward and down to port and starboard, respectively) and located approximately 1-m below the waterline when deployed. An Applanix Pos MV Wavemaster II V5 inertially aided navigation system was used for timing, positioning, and attitude. The Inertial Measurement Unit (IMU) was mounted atop the sonar bracket just aft of the pole. Two Trimble 540AP Global Navigation Satellite System antennas were affixed atop the cabin approximately amidships of the vessel, two meters apart, port-starboard. An AML Oceanographic Micro-X sound velocity sensor was used for speed of sound readings at the sonar head. A Valeport SWiFT sound velocity profiler was used for measuring sound velocity profiles. Hydrographic survey acquisition and processing software, HYPACK/HYSWEEP (version 2016a) managed data inputs from sensors and produced two files (.RAW and .HSX). Data were collected in WGS84 [G1762] Universal Transverse Mercator (UTM) Zone 17 North (17N) coordinates. Person who carried out this activity:
    Jake J. Fredericks
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

    (727)502-8000 (voice)
    jfredericks@usgs.gov
    Date: 2018 (process 2 of 3)
    Processing: Positioning and attitude data were post-processed in Applanix POSPac MMS (POSPac) software version 8.0 Service Pack 3. Raw position files were imported into POSPac and processed with the IN-Fusion PP-RTX processing mode utilizing Trimble CenterPoint RTX technology; creating smoothed best estimate of trajectory (SBET) files and dynamic error files (SMRMSG) for each day of the survey. Bathymetric data were post-processed in CARIS Hydrographic processing software HIPS/SIPS version 11.0.7. HYPACK acquisition files (.HSX) were first imported into CARIS and then post-processed navigation files (SBET and SMRMSG) were imported and applied. Additionally, GPS tide (GPS tidal corrections utilize GPS height information from real time survey observations to obtain an ellipsoid height) was computed and sound velocity profiles were applied. Roll calibration was also performed, as necessary. TPU was calculated from real time values recorded in the HSX and the SMRMSG files. Data were filtered to exclude any points with RESON Quality flags of 0, 1, and 2 (these flags are assigned to individual soundings at the time of acquisition and are a metric of pass/fail in regards to both brightness and collinearity: 0 = fail both, 1 = pass brightness only, 2 = pass collinearity only), as well as soundings that had a TPU greater than stated IHO Special Order standards (IHO, 2008). Refraction artifacts were addressed using Refraction Editor. Further editing was performed in Subset Editor. A visual and statistical inspection of the data was performed to serve as quality control. A 1-m bathymetric CUBE surface was computed and the final surface was exported as an x,y,z ASCII file using the Base Surface to ASCII function. Person who carried out this activity:
    Jake J. Fredericks
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

    (727)502-8000 (voice)
    jfredericks@usgs.gov
    Data sources produced in this process:
    • 2017_373_LooeKey_MBES_1m_WGS84_UTM17N.xyz
    Date: 13-Oct-2020 (process 3 of 3)
    Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
  3. What similar or related data should the user be aware of?
    Calder, B.R. and Wells, D.E., 20070129, CUBE User's Manual: University of New Hampshire, Center for Coastal and Ocean Mapping, Durham, NH.

    Online Links:

    Other_Citation_Details: pages 3-12
    Organization, International Hydrographic, 2008, IHO Standards for Hydrographic Surveys: International Hydrographic Bureau, 4, quai Antoine 1er B.P. 445 - MC 98011 MONACO Cedex Principauté de Monaco.

    Online Links:

    Other_Citation_Details: pages 15-16

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    This dataset was from one research cruise and was therefore internally consistent. Methods were employed to maintain data collection consistency aboard the platform. During mobilization, each piece of equipment was isolated to obtain internal and external offset measurements with respect to the survey platform. All the critical measurements were recorded manually and digitally entered into their respective programs.
  2. How accurate are the geographic locations?
    All data were collected and processed to meet or exceed International Hydrographic Organization (IHO) Special Order standards for positioning and depth (IHO, 2008). Individual Total Propagated Uncertainty (TPU) values associated with each node are available in the XYZ file.
  3. How accurate are the heights or depths?
    All data were collected and processed to meet or exceed IHO Special Order standards for positioning and depth (IHO, 2008). Individual TPU values associated with each node are available in the XYZ file.
  4. Where are the gaps in the data? What is missing?
    These are complete post-processed x,y,z bathymetric data points from multibeam data collected at Looe Key, the Florida Keys, during three separate survey legs, December 2017, February and March 2018.
  5. How consistent are the relationships among the observations, including topology?
    This file represents the post-processed bathymetric data (x,y,z) collected during multibeam bathymetry surveys.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None
Use_Constraints:
Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. The U.S. Geological Survey requests to be acknowledged as originator of these data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    Jake J. Fredericks
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    jfredericks@usgs.gov
  2. What's the catalog number I need to order this data set? 2017_373_LooeKey_MBES_1m_WGS84_UTM17N.xyz
  3. What legal disclaimers am I supposed to read?
    Although these data have been processed successfully on a computer system at the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system, or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. The USGS shall not be held liable for improper or incorrect use of the data described or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
Metadata author:
Jake J. Fredericks
U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
Geologist
600 4th Street South
St. Petersburg, FL
USA

(727) 502-8000 (voice)
jfredericks@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/Looe_Key_2017_2018_MBB_xyz_metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:51 2021