Nearshore Multibeam Bathymetry Data: Madeira Beach, Florida, February 2017

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

Frequently anticipated questions:

What does this data set describe?

Title:
Nearshore Multibeam Bathymetry Data: Madeira Beach, Florida, February 2017
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) nearshore Madeira Beach, Florida February 13-17, 2017. This dataset, Madeira_Beach_2017_MBES_1m_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 American Standard Code for Information Interchange (ASCII) x,y,z point data files. These values are not the individual soundings, but nodes from a 1-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 and were subsequently transformed using the National Oceanic and Atmospheric Administration's (NOAA) VDatum version 3.9 (v.3.9) transformation software (https://vdatum.noaa.gov/) horizontally to the North American Datum of 1983 (NAD83 [2011]) and vertically to the North American Vertical Datum of 1988 (NAVD88) relative to the GEOID model of 2012 B (GEOID12B).
  1. How might this data set be cited?
    Stalk, Chelsea A., 20240307, Nearshore Multibeam Bathymetry Data: Madeira Beach, Florida, February 2017:.

    This is part of the following larger work.

    DeWitt, Nancy T., Fredericks, Joseph J., Stalk, Chelsea A., Reynolds, Billy J., Kelso, Kyle W., Thompson, Dave M., Farmer, Andrew S., and Brown, Jenna A., 20240307, Nearshore Multibeam and Single-Beam Bathymetry Data: Madeira Beach, Florida, February 2017: U.S. Geological Survey Data Release doi:10.5066/P9Y7R8NS, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -82.850515
    East_Bounding_Coordinate: -82.778870
    North_Bounding_Coordinate: 27.804828
    South_Bounding_Coordinate: 27.751861
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 13-Feb-2017
    Ending_Date: 17-Feb-2017
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: tabular digital data
  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 (21,167,707)
    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?
    17TST01_MadeiraBeach_MBES_1m_WGS84_UTM17N.xyz
    ASCII text (.txt) file containing the processed 1-m bathymetric grid x,y,z data in the WGS84 [ITRF08] 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:317706.8
    Maximum:324682.9
    Resolution:0.1
    WGS84_UTM17N_Y
    WGS84 UTM Zone 17N Y-coordinate (northing) of sample point, in meters. (Source: HYPACK)
    Range of values
    Minimum:3071085.9
    Maximum:3076852.3
    Resolution:0.1
    WGS84_Ellipsoid_Z
    WGS84 (ellipsoid height) of sample point, in meters. (Source: HYPACK)
    Range of values
    Minimum:-39.756
    Maximum:-27.945
    Resolution:0.001
    17TST01_MadeiraBeach_MBES_1m_NAD83_UTM17N_NAVD88_G12B.xyz
    ASCII text (.txt) file containing the processed 1-m bathymetric grid x,y,z data in NAD83 [2011], NAVD88, which were derived using the GEOID12B model (orthometric height). (Source: HYPACK; VDatum)
    NAD83_UTM17N_X
    NAD83 UTM Zone 17N X-coordinate (easting) of sample point, in meters. (Source: HYPACK; VDatum)
    Range of values
    Minimum:317707.394
    Maximum:324683.492
    Resolution:0.001
    NAD83_UTM17N_Y
    NAD83 UTM Zone 17N Y-coordinate (northing) of sample point, in meters. (Source: HYPACK; VDatum)
    Range of values
    Minimum:3071085.271
    Maximum:3076851.670
    Resolution:0.001
    NAVD88_G12B_Z
    NAVD88 (orthometric height) of sample point, in meters, with respect to GEOID12B. (Source: HYPACK; VDatum)
    Range of values
    Minimum:-13.878
    Maximum:-2.062
    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)
    • Chelsea A. Stalk
  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?
    Chelsea Stalk
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Electronics Technician
    600 4th Street South
    St. Petersburg, FL
    USA

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

Why was the data set created?

The purpose of the survey was to collect high-density multibeam bathymetry data nearshore Madeira Beach, FL as part of a regional study designed to better understand coastal processes on barrier islands and sandy beaches. Data were collected during USGS Field Activity Number (FAN) 2017-305-FA, sub-FAN 17TST01. 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-305-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: 2017 (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 research vessel (R/V) Sallenger, a 26-foot fiberglass 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 GA830 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 Sontek CastAway CTD 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 [ITRF08] Universal Transverse Mercator (UTM) Zone 17 North (17N) coordinates. Person who carried out this activity:
    Chelsea Stalk
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Electronics Technician
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Date: 2017 (process 2 of 3)
    Processing: Positioning and attitude data were post-processed in Applanix POSPac MMS (POSPac) software version 8.4 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.1.3. 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 and resulting CUBE surface was performed to serve as quality control (Calder and Wells, 2007). 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:
    Chelsea A. Stalk
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Electronics Technician
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Data sources produced in this process:
    • 17TST01_MadeiraBeach_MBES_1m_WGS84_UTM17N.xyz
    Date: 2023 (process 3 of 3)
    Datum Transformation: Final x,y,z data were converted using NOAA's VDatum v.3.9 software conversion tool from the WGS84 [ITRF08] realization to NAD83 [2011] NAVD88, using the GEOID12B model (orthometric height). Person who carried out this activity:
    Chelsea Stalk
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Electronics Technician
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Data sources produced in this process:
    • 17TST01_MadeiraBeach_MBES_1m_NAD83_UTM17N_NAVD88_G12B.xyz
  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, then 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. Transformed data has an additional reported vertical transformation error of 7.6158 centimeters (cm).
  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 in nearshore Madeira Beach, FL in February 2017.
  5. How consistent are the relationships among the observations, including topology?
    This file represents the post-processed bathymetric data (x,y,z) collected during a multibeam bathymetry survey.

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)
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: USGS SPCMSC Data Management
    600 4th Street South
    Saint Petersburg, FL
    United States

    727-502-8000 (voice)
    gs-g-spcmsc_data_inquiries@usgs.gov
  2. What's the catalog number I need to order this data set? 17TST01_MadeiraBeach_MBES_1m_WGS84_UTM17N.xyz, 17TST01_MadeiraBeach_MBES_1m_NAD83_UTM17N_NAVD88_G12B.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: 07-Mar-2024
Metadata author:
U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
Attn: USGS SPCMSC Data Management
600 4th Street South
Saint Petersburg, FL
United States

727-502-8000 (voice)
gs-g-spcmsc_data_inquiries@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/Madeira_Beach_2017_MBES_1m_xyz_metadata.faq.html>
Generated by mp version 2.9.51 on Thu Mar 7 12:53:07 2024