Multibeam Bathymetry Data Collected in 2016 from Grand Bay Alabama/Mississippi: Trackline Navigation

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

Frequently anticipated questions:


What does this data set describe?

Title:
Multibeam Bathymetry Data Collected in 2016 from Grand Bay Alabama/Mississippi: Trackline Navigation
Abstract:
A reconnaissance multibeam bathymetry survey was conducted by the U.S Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) in Grand Bay Alabama/Mississippi on May 12, 2016 as an assessment of the shallow water capabilities of the Teledyne Reson SeaBat T50-P multibeam echosounder, and as an attempt to map the eroding marsh edges at locations of interest around the bay. This dataset, Grand_Bay_2016_MBB_Tracklines.zip, includes the trackline vector file derived from the acquisition software at the time of survey.
Supplemental_Information:
Trackline files were recorded at the time of the survey using HYPACK, a marine surveying, positioning, and navigation software for data acquired by U.S Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC).
  1. How might this data set be cited?
    Stalk, Chelsea A., Fredericks, Jake J., Locker, Stanley D., and Carlson, Cody S., 20180522, Multibeam Bathymetry Data Collected in 2016 from Grand Bay Alabama/Mississippi: Trackline Navigation: U.S. Geological Survey Data Release doi:10.5066/F7MC8Z9N, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -88.411460
    East_Bounding_Coordinate: -88.395986
    North_Bounding_Coordinate: 30.383845
    South_Bounding_Coordinate: 30.364199
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 12-May-2016
    Ending_Date: 12-May-2016
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • string (34)
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.0197872573. Longitudes are given to the nearest 0.0228099669. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is World Geodetic System of 1984.
      The ellipsoid used is World Geodetic System of 1984.
      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?
    Grand_Bay_2016_MBB_Tracklines.shp
    Esri shapefile containing the survey tracklines for the multibeam data collected by the U.S. Geological Survey in May 2016 in Grand Bay Alabama/Mississippi. (Source: USGS)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: Esri) Polyline ZM is the geometry type defining the features.
    Year
    Year data were collected (Source: USGS) 2016
    Data_Type
    MBB = Multibeam Bathymetry; USGS SPCMSC identifier of bathymetry data type. (Source: USGS) Character String - MBB
    HypackLine
    Line name assigned by HYPACK during acquisition. (Source: HYPACK) Line number followed by segment number and Coordinated Universal Time (UTC) time, which are all recorded at the start of a line. The naming convention used for each line was xxx_yyy_hhmm. Example of line name: 133_000_1718.RAW, where 133 is the designated line number, 000 is the segment number, which would count up by one if the line was either re-run or if there were acquisition issues, 1718 is the UTC time in hours and minutes, and RAW is the file extension.
    Length_m
    LLength, in meters, of survey trackline. This metric is calculated by ArcMap during the creation of the polyline shapefile. (Source: Esri)
    Range of values
    Minimum:15
    Maximum:599
    Resolution:1.0

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
    • Jake J. Fredericks
    • Stanley D. Locker
    • Cody S. Carlson
  2. Who also contributed to the data set?
    U.S. Geological Survey, Sea-level and Storm Impacts on Estuarine Environments and Shorelines (SSIEES) program, St. Petersburg Coastal and Marine Science Center
  3. To whom should users address questions about the data?
    Chelsea A. Stalk
    Cherokee Nation Technologies / U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

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

Why was the data set created?

The purpose of the survey was to assess the capabilities of the Reson T50 multibeam system, and attempt to image eroding marsh edges at areas of interest within Grand Bay Alabama/Mississippi (AL/MS). In order to obtain coverage of the shallow water marsh edges, a single head of the system was utilized and tilted at an angle of 30 degrees to the port side of the vessel. Data were collected during USGS field activity number (FAN) 2016-331-FA aboard the R/V Jabba Jaw, a 22 foot (ft) shallow draft center console catamaran. 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=2016-331-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: 25-Apr-2017 (process 1 of 1)
    Navigation lines were exported from HYPACK hydrographic acquisition and processing software as a .kml file, imported into ArcGIS using the "kml to layer" tool, and exported as a shapefile. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Chelsea A. Stalk
    Researcher I
    600 4th Street South
    St. Petersburg, FL
    USA

    (727)502-8114 (voice)
    cstalk@usgs.gov
    Data sources produced in this process:
    • Grand_Bay_2016_MBB_Tracklines.shp
  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?
    The accuracy of the data was determined during data collection. 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 taken manually, and digitally entered into their respective programs. The data have not been independently verified for accuracy.
  2. How accurate are the geographic locations?
    The trackline position data were recorded using HYPACK hydrographic acquisition and processing software at the time of the survey. The system was navigated using Differential GPS (DGPS), trackline acuracy is not derived from post processed data and therefore horizontal accuracy is assumed to be 2 meters.
  3. How accurate are the heights or depths?
    The survey tracklines do not include or represent vertical data.
  4. Where are the gaps in the data? What is missing?
    These are the trackline files as recorded at the time of acquisition by HYPACK, marine surveying, positioning, and navigation software during a multibeam survey in Grand Bay Alabama/Mississippi, May 2016.
  5. How consistent are the relationships among the observations, including topology?
    This file represents the trackline navigation file 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)
    Chelsea A. Stalk
    Cherokee Nation Technologies / U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8114 (voice)
    cstalk@usgs.gov
  2. What's the catalog number I need to order this data set?
  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: 21-May-2018
Metadata author:
Chelsea A. Stalk
Cherokee Nation Technologies / U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
Geologist
600 4th Street South
St. Petersburg, FL
USA

(727) 502-8000 (voice)
cstalk@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/Grand_Bay_2016_MBB_Tracklines_metadata.faq.html>
Generated by mp version 2.9.49 on Thu Jun 27 09:51:09 2019