Nearshore Single-Beam 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 Single-Beam Bathymetry Data: Madeira Beach, Florida, February 2017
Abstract:
In February 2017, the United States Geological Survey Saint Petersburg Coastal and Marine Science Center (USGS SPCMSC) conducted multibeam and single-beam bathymetric surveys of the nearshore waters off Madeira Beach, Florida. These data were collected as part of a regional study designed to better understand coastal processes on barrier islands and sandy beaches. Results from this study will be incorporated with observations from other regional studies in order to validate operational water level and coastal change hazards models being expanded nationwide (National Assessment of Storm-Induced Coastal Change Hazards). The regional study area is Madeira Beach located on one of eleven barrier islands in Pinellas County in west-central Florida along the Gulf of Mexico. These barrier islands support highly developed and densely populated coastal communities, comprised of local residents, year-round tourist population, and undeveloped natural habitats within local and state parks. A measure of the nearshore bathymetry is useful for better understanding the interaction of the hydrodynamics and morphodynamics offshore and in the surf zone that ultimately control the beach response. This USGS data release provides processed multibeam bathymetry (MBES) and processed single-beam bathymetry (SBES) data collected under the USGS field activity number (FAN) 2017-305-FA. This FAN has four subfans each representing one research vessel (R/V): 17TST01 (R/V Sallenger), 17TST02 (R/V Jabba Jaw, a 22-foot shallow draft Twin Vee [TVEE]), 17TST03 (R/V Shark, a 12-foot Yamaha personal watercraft [SHRK]) and 17TST04 (R/V Chum, a 12-foot Yamaha personal watercraft [CHUM]). The point data (x,y,z) are provided in two datums: 1) the International Reference Frame of 2008 (ITRF08) and ellipsoid height; and 2) the North American Datum 1983 in the CORS96 realization (NAD83 (CORS96)) for the horizontal and the North American Vertical Datum 1988 (NAVD88) with respect to GEOID12B for the vertical. Additional files include a single-beam trackline shapefile (.shp) and a 20-meter (m) cell size single-beam digital elevation model (DEM, .tif). For further information regarding data collection and/or processing please see the metadata associated with this data release.
Supplemental_Information:
For the single-beam bathymetry data, the differential positioning was obtained through post-processing the base station data to the rovers. The dataset was transformed from the initial WGS84 (G1762) UTM 17N datum to NAD83 UTM 17N NAVD88, using the GEOID12B model (National Oceanic Atmospheric Administration [NOAA] and the National Geodetic Survey [NGS] VDatum software version 3.6 - http://vdatum.noaa.gov/).
  1. How might this data set be cited?
    DeWitt, Nancy T., 20240307, Nearshore Single-Beam 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, Andy, 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, U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center, St. Petersburg, Florida.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -82.827188
    East_Bounding_Coordinate: -82.776611
    North_Bounding_Coordinate: 27.808530
    South_Bounding_Coordinate: 27.761500
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 14-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 and 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 Point data set. It contains the following vector data types (SDTS terminology):
      • Point (1,166,747)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 17N
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -81.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      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_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257223563.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum 1988
      Altitude_Resolution: 0.01
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt
    Comma-delimited ASCII text file (.txt) containing the processed single-beam bathymetry data points from USGS FAN 2017-305-FA (subFANs 17TST02, 17TST03, and 17TST04). Data are in the native acquisition and processing datum WGS84 (G1762) equivalent to ITRF08. Text file attributes include easting and northing (WGS84 G1762 UTM 17N), ellipsoid height (WGS84 G1762 UTM 17N), latitude (WGS84 G1762), longitude (WGS84 G1762), year, day of year (DOY), UTC time, GPS week, GPS second of the week, and trackline name. (Source: U.S. Geological Survey)
    WGS84_UTM17N_X
    x-axis coordinate, easting, WGS84 (G1762) UTM 17N (Source: U.S. Geological Survey)
    Range of values
    Minimum:320011.275
    Maximum:324921.079
    Units:meters
    WGS84_UTM17N_Y
    y-axis coordinate, northing, WGS84 (G1762) UTM 17N (Source: U.S. Geological Survey)
    Range of values
    Minimum:3072119.463
    Maximum:3077259.719
    Units:meters
    WGS84_ELLIPSOID_Z
    z-value, ellipsoid height (elevation) (Source: U.S. Geological Survey)
    Range of values
    Minimum:-38.648
    Maximum:-26.133
    Units:meters
    WGS84_UTM17N_LAT
    x-axis coordinate, latitude, WGS84 (G1762) UTM 17N (Source: U.S. Geological Survey)
    Range of values
    Minimum:27.761902
    Maximum:27.808064
    Units:Decimal Degrees
    WGS84_UTM17N_LONG
    y-axis coordinate, longitude, WGS84 (G1762) UTM 17N (Source: U.S. Geological Survey)
    Range of values
    Minimum:-82.827003
    Maximum:-82.777056
    Units:Decimal Degrees
    YEAR
    Calendar year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2017
    Maximum:2017
    DOY
    Day of year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:45
    Maximum:48
    UTC_TIME
    GPS second of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:14:35:45.806
    Maximum:21:23:34.630
    Units:HH:MM:SS.sss
    HYPACK_LINE
    Identifier assigned to each HYPACK line during acquisition (Source: HYPACK/U.S. Geological Survey) Example: TVEE_002_1741_1000, where the first 5 characters are the platform/vessel followed by an underscore (TVEE_, SHRK_ or CHUM_) and the next 8 characters are the start time in UTC (002_1741). If the line has segments, there will be 5 more characters corresponding to the segment number (_0001, _0002, et cetera).
    GPS_SECOND
    The GPS second of the GPS week that the data was collected (Source: GrafNav)
    Range of values
    Minimum:229022
    Maximum:498339
    Units:seconds
    GPS_WEEK
    The GPS week that the data was collected (Source: GrafNav)
    Range of values
    Minimum:1936
    Maximum:1936
    Madeira_Beach_2017_SBES_NAD83_NAVD88_UTM17N_GEOID12B_xyz.txt
    Comma-delimited ASCII text file (.txt) containing of the processed single-beam bathymetry data points from FAN 2017-305-FA (subFANs 17TST02, 17TST03, and 17TST04). Data were re-projected from its native datum to NAD83 NAVD88 UTM Zone 17 North coordinate system with respect to the GEOID 12B datum. Text file attributes include easting (NAD83 UTM 17N), northing (NAD83 UTM 17N), orthometric height (NAVD88 GEOID 12B), latitude (NAD83 UTM 17N), longitude (NAD83 UTM 17N), year, day of year (DOY), UTC time, GPS week, GPS second of the week, and trackline name. (Source: VDatum)
    NAD83_UTM17N_X
    x-axis coordinate, easting, NAD83 UTM 17N (Source: VDatum)
    Range of values
    Minimum:320011.869
    Maximum:324921.671
    Units:meters
    NAD83_UTM17N_Y
    y-axis coordinate, northing, NAD83 UTM 17N (Source: VDatum)
    Range of values
    Minimum:3072118.834
    Maximum:3077259.089
    Units:meters
    NAVD88_G12B
    z-value, orthometric height (elevation) in NAVD88 GEOID 12B (Source: VDatum)
    Range of values
    Minimum:-12.771
    Maximum:-0.26
    Units:meters
    NAD83_UTM17N_LAT
    x-axis coordinate, latitude, NAD83 UTM 17N (Source: VDatum)
    Range of values
    Minimum:27.761896
    Maximum:27.808059
    Units:Decimal Degrees
    NAD83_UTM17N_LONG
    y-axis coordinate, longitude, NAD83 UTM 17N (Source: VDatum)
    Range of values
    Minimum:-82.826997
    Maximum:-82.77705
    Units:Decimal Degrees
    YEAR
    Calendar year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2017
    Maximum:2017
    DOY
    Day of year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:45
    Maximum:48
    UTC_TIME
    UTC time of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:14:35:45.806
    Maximum:21:23:34.630
    Units:HH:MM:SS.sss
    HYPACK_LINE
    Identifier assigned to each HYPACK line during acquisition (Source: HYPACK/U.S. Geological Survey) Example: TVEE_002_1741_1000, where the first 5 characters are the platform/vessel followed by an underscore (TVEE_, SHRK_ or CHUM_) and the next 8 characters are the start time in UTC (002_1741). If the line has segments, there will be 5 more characters corresponding to the segment number (_0001, _0002, et cetera).
    GPS_SECOND
    The GPS second of the GPS week that the data was collected (Source: GrafNav)
    Range of values
    Minimum:229022
    Maximum:498339
    Units:seconds
    GPS_WEEK
    The GPS week that the data was collected (Source: GrafNav)
    Range of values
    Minimum:1936
    Maximum:1936
    Madeira_Beach_2017_SBES_tracklines.shp
    Polyline shapefile of the single-beam bathymetry tracklines containing FID, Shape, HYPACKLine name, and line length (in meters). (Source: Esri)
    FID
    Automatically generated feature attribute by Esri. (Source: Esri)
    Range of values
    Minimum:0
    Maximum:195
    Shape
    Automatically generated feature attribute by Esri. (Source: Esri) Polyline ZM
    HYPACKLine
    Identifier assigned to each HYPACK line during acquisition. (Source: HYPACK/U.S. Geological Survey) Example: TVEE_002_1741_1000, where the first 5 characters are the platform/vessel followed by an underscore (TVEE_, SHRK_ or CHUM_) and the next 8 characters are the start time in UTC (002_1741). If the line has segments, there will be 5 more characters corresponding to the segment number (_0001, _0002, et cetera).
    Length_M
    Length of the trackline polyline, in meters. (Source: Esri)
    Range of values
    Minimum:22.51
    Maximum:5286.13
    MadeiraBeach_2017_SBES_20m_DEM.tif
    This is a 20-m cell size gridded DEM GeoTIFF (.tif) created from the x,y,z point dataset in this data release (Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt). The ellipsoid elevation ranges from -26.47 m to -37.57 m and is projected in WGS84 UTM 17N. The file format is 32-bit floating point GeoTIFF with 246 columns, 258 rows. (Source: Esri)

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Nancy T. DeWitt
  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?
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

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

Why was the data set created?

The purpose of this data release is to archive the bathymetric data and associated files collected off Madeira Beach, FL from February 14-17, 2017, during FAN 2017-305-FA. Additional survey and data details are available in the Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-305-FA. The dataset Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt provides single-beam bathymetry data points (x,y,z) referenced to World Geodetic System 1984 (WGS84) Universal Transverse Mercator (UTM) Zone 17 North (N) for the horizontal (x,y) and WGS84 ellipsoid height for the vertical (z). The dataset Madeira_Beach_2017_SBES_NAD83_NAVD88_UTM17N_GEOID12B_xyz.txt provides single-beam bathymetry data points (x,y,z) referenced to North American Datum of 1983 (NAD83) UTM Zone 17N for the horizontal (x,y,z) and North American Vertical Datum of 1988 (NAVD88) orthometric height using GEOID12B model for the vertical (z).

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 7)
    Global Navigation Satellite System (GNSS) Acquisition: GNSS data was recorded at a primary base station and aboard each roving vessel. The primary base station was FDOT FPRN base station FLIS located approximately 15 kilometers (km) north of the survey area. The base station was operational for the entire survey and the Receiver Independent Exchange Format (RINEX) datafiles (FLIS045M00.17O, FLIS045M00.17N, and FLIS045M00.17G) were downloaded from the FPRN website post survey. FLIS was the name at the time of the single-beam survey in 2017. But at the time of this publication, the location has been renamed FLIB in the FDOT system. The roving vessels were each outfitted with a Spectra Geospatial SP90M GNSS receivers and GNSS antennae recording data at 10 hertz (10 epochs/second). The GNSS files were converted from proprietary G-file format into the non-proprietary RINEX raw data file format using RINEX Converter version 3.00. The base and rover RINEX files were post processed together in a subsequent step to obtain differentially corrected navigation data, which is described later in the metadata. Example RINEX filename TVEE0450.17O where the convention TVEE is the four-letter rover name, 045 is the day of year, 0 is the session number, 17 is the year and O is the observation file (or N for navigation file, M for meteorlogical file, G for Global Navigation Satellite Navigation System (GLONASS) navigation message file. Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources produced in this process:
    • *.17O, *.17N, *.17M
    Date: 2017 (process 2 of 7)
    Single-Beam Bathymetry Acquisition: TVEE collected 87.12 line-km (62 lines), SHRK collected 145.46 line-km (60 lines) and the CHUM collected 61.83 line-km (80 lines). Boat motion was recorded at 50-millisecond (ms) using a SBG Ellipse A motion sensor. HYPACK A Xylem Brand (version 16.1.9.0), a marine surveying, positioning, and navigation software package, managed the planned-transect information and provided real-time navigation, steering, correction, data quality, and instrumentation status to the boat operator. Depth soundings were recorded at 50-ms intervals using an Odom echotrac CV100 echosounder with a 4-degree, 200-kilohertz (kHz) transducer. Data from the GNSS receiver, motion sensor, and echosounder were recorded in real-time aboard all vessels independently and merged into a single raw data file (.RAW) in HYPACK, with each device string referenced by a device identification code and time stamped to Coordinated Universal Time (UTC). Sound velocity profile (SVP) measurements were collected using SonTek Castaway Conductivity, Temperature, and Depth (CTD) instruments. The instruments were periodically cast overboard to record changes in water column speed of sound (SOS). A total of 17 successful sound velocity casts were collected and ranged in depth from 0.15 to 6.48 m (average 2.14 m), and in sound velocity from 1518.18 to 1525.69 meters per second (m/s) (average 1520.94 m/s). Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Date: 2017 (process 3 of 7)
    Differentially Corrected Navigation Processing: The FDOT FPRN datasheet for FLIS were retrieved from the database and the base station coordinates were converted from NAD83 (2011) EPOCH 2010.0 into WGS84 (G1762) equivalent to ITRF2008 using the HTDP online transformation utility version 3.2.5 (https://www.ngs.noaa.gov/TOOLS/Htdp/Htdp.shtml). The WGS84 (G1762) epoch realization was introduced in 2013. The survey acquisition dates succeed this date; therefore, it was the appropriate datum realization for post-processing the navigation data which was acquired in the WGS84 (G1762) datum. The resultant base position used for post-processing was 27°5247.88931 North (WGS84-G1762), 82°5033.69685 West (WGS84-G1762), and -17.543 m ellipsoid height (WGS84-G1762). The kinematic trajectories (rover to base) were processed using NovAtel's Waypoint GrafNav software version 8.60.5025. The rover RINEX files and the base RINEX files were imported into Grafnav, converted into proprietary files, and the kinematic (rover) GNSS data session from the survey vessel was post-processed to the concurrent base GNSS data session. Analyzing the data plots, trajectory maps, processing logs, satellite health plots, and other viewing utilities that GrafNav produces, provided measures to attain trajectory solutions (between the rover and the base) free of erroneous data that resulted in fixed positions. Some analytic examples include 1) excluding satellites flagged by the program as having bad/poor health or cycle slips, 2) Excluding poor satellite time segments that have a negative influence toward a fixed solution, and 3) adjusting the satellite elevation mask angle to improve the position solutions. This process was repeated for every GNSS data session(Hansen and others, 2017). The final differentially corrected, precise DGPS positions were computed at and exported in American Standard Code for Information Interchange (ASCII) text format in WGS84 (G1762) UTM 17N geodetic datum. Filename example 17TST02_045_2017_FLIS_TVEE_A.txt where the convention 17TST02 is the subFAN, 045 is day of year, 2017 is the year, FLIS is the base station used, TVEE is the rover, and A is the GPS session from A to Z. Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources used in this process:
    • *.17O, *.17N, *.17G, *.17M
    Data sources produced in this process:
    • 17TST02_045_2017_FLIS_TVEE_A.txt
    Date: 2017 (process 4 of 7)
    Bathymetry Processing: All data were processed using CARIS HIPS and SIPS (Hydrographic Information Processing System and Sonar Information Processing System) version 10.2. First, a vessel file *.vhf, unique to the platform, was created that contains the surveyed offsets measurements between the sensors. A CARIS project was created using the *.vhf file, and then the HYPACK *.RAW and the SVP profiles *.SVP were loaded. Next, the differentially corrected navigation files were imported using the generic data parser tool. Then, the differently corrected navigation files overwrote every non-differential position in the HYPACK *.RAW file based upon time. The bathymetric data components (position, motion, depth, and SOS) were then georeferenced and geometrically corrected in CARIS to produce processed x,y,z positional data. Once georeferenced, the data were reviewed and edited for outliers, including further review in the Subset Editor utility for crossing status, and questionable areas or data points were removed. The geometrically corrected point data were then exported as an x,y,z ASCII text file referenced to WGS84 (G1762) UTM 17N (Hansen and others, 2017). Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources used in this process:
    • *.VHF
    • *.RAW
    • *.SVP
    • 17TST02_045_2017_FLIS_TVEE_A.txt
    Data sources produced in this process:
    • 17TST02_SBB_ITRF08_Level_003_xxx.txt
    • 17TST03_SBB_ITRF08_Level_003_xxx.txt
    • 17TST04_SBB_ITRF08_Level_003_xxx.txt
    Date: 2017 (process 5 of 7)
    Quality Control, Quality Assurance (QA/QC) and Uncertainty Analysis: The single-beam data exported from CARIS HIPS and SIPS (x,y,z ASCII text files) were transformed in Esri ArcMap version 10.4.1 to a point shapefile (.shp) utilizing the "Create Feature Class From XY Table" geoprocessing tool. The projection was set to WGS84 UTM 17N. The generated shapefile was visually scanned for any obvious outliers or problems. Next, a polyline shapefile (representing tracklines) was produced from the point shapefile using XTools Pro (version 16.1) "Make Polylines from Points" geoprocessing tool for each survey platform (subFANs 17TST02, 17TST03 and 17TST04). Utilizing both the x,y,z (point) and trackline (polyline) shapefiles, a Python script was used to evaluate elevation differences at the intersection of crossing tracklines by calculating the elevation difference between points at each intersection using an inverse distance weighting equation with a search radius of 5 m (Hansen and others, 2017). The maximum crossing error for TVEE (17TST02), when crossing a trackline it previously surveyed, was 18 cm. The maximum crossing error for SHRK (17TST03), when crossing a trackline it previously surveyed, was 22 cm. The maximum crossing error for CHUM (17TST04), when crossing a trackline it previously surveyed, was 43 cm. Any crossings greater than 30 cm were reviewed a final time for errors and either removed or adjusted, based on the situation when compared with the other vessels. The shapefiles were merged into one large file and sent through the python crossing program a last time. The final crossing file had 1847 crossings ranging from 0.00 to 34 cm in which 80.7% were 10 cm or less; 13.5% were between 10-15 cm; 6.1% were between 15-30 cm, and 0.22% were greater than 30cm. These files were then exported from Esri ArcMap as x,y,z ASCII text (.txt) files using the XTools Pro "Table to Text" function. The resultant ASCII text file can be downloaded from this data release in Madeira_Beach_2017_SBES_xyz.zip, and the trackline shapefile Madeira_Beach_2017_SBES_tracklines.zip. Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources used in this process:
    • 17TST02_SBB_ITRF08_Level_003_xxx.txt
    • 17TST03_SBB_ITRF08_Level_003_xxx.txt
    • 17TST04_SBB_ITRF08_Level_003_xxx.txt
    Data sources produced in this process:
    • Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt
    • Madeira_Beach_2017_SBES_tracklines.shp
    Date: 2023 (process 6 of 7)
    Datum Transformation: NOAA/NGS's VDatum v.3.6 was used to transform the single-beam data points' horizontal and vertical datums (x,y,z). The transformation was from WGS84 (G1762) into NAD83 (horizontal) UTM 17N and NAVD88 (vertical) using GEOID12B. VDatum reports a nationwide standard deviation of 2.0 centimeters (cm) for ellipsoid - NAD83 transformations, and a nationwide standard deviation of 5.0 cm for NAD83 to NAVD88 transformations in the coastal regions of the continental U.S. For more information about the positional accuracy for these datum transformations, visit the Estimation of Vertical Uncertainties VDatum webpage, https://vdatum.noaa.gov/docs/est_uncertainties.html. The resultant data points ASCII data file can be downloaded from this data release in Madeira_Beach_2017_SBES_xyz.zip. Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources used in this process:
    • Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt
    Data sources produced in this process:
    • Madeira_Beach_2017_SBES_NAD83_NAVD88_UTM17N_GEOID12B_xyz.txt
    Date: 2023 (process 7 of 7)
    DEM Creation: Using Esri ArcGIS version 10.4.1, a polygon shapefile of the single-beam data extent was created (MadeiraBeach_2017_SBB_polygon.shp). Next using ArcGIS "polygon to raster" conversion tool a raster mask of the shapefile was created (mb2017ply20m). Next using the single-beam x,y,z data a 20 x 20-m cell resolution DEM was generated using the natural neighbor algorithm. The algorithm computation results produce minimum and maximum values (-26.469 to -37.569) different then the ascii text xyz values (-23.133 to -38.648) from which it was created. The DEM was then clipped to the raster mask using ArcGIS Spatial Analyst "extract by raster mask" tool and then exported as a GeoTIFF file for this data release. Person who carried out this activity:
    Nancy T. DeWitt
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    ndewitt@usgs.gov
    Data sources used in this process:
    • Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt
    Data sources produced in this process:
    • MadeiraBeach_2017_SBES_20m_DEM.tif
  3. What similar or related data should the user be aware of?
    Hansen, Mark E., Dewitt, Nancy T., and Reynolds, Billy J., 20170810, Archive of bathymetry data collected in South Florida from 1995 to 2015: U.S. Geological Survey Data Series 1031, U.S. Geological Survey, Reston, VA.

    Online Links:


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 is derived from a single field survey using identical equipment set-ups, and staff; therefore, the dataset is internally consistent. Methods were employed to maintain data collection consistency aboard the platforms. 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 then digitally entered into their respective programs. Offsets between the single-beam transducers, motion reference units, and the antenna reference point (ARP) were measured using a geodimeter and accounted for during acquisition and (or) in post-processing. Differential Global Positioning System (DGPS) coordinates were obtained using the following post-processing software packages: NovAtel's Waypoint Product Group GrafNav, version 8.60.5025).
  2. How accurate are the geographic locations?
    The Florida Department of Transportation's (FDOT) Florida Permanent Reference Network (FPRN) datasheet for the FPRN location named FLIS was retrieved from their database. FLIS was the location name at the time of the single-beam survey in 2017. But at the time of this publication, the location has been renamed FLIB in the FDOT system. The base station coordinates were converted from NAD83 (2011) EPOCH 2010.0 into WGS84 (G1762) equivalent to ITRF2008 using the HTDP online transformation utility version 3.2.5 (https://www.ngs.noaa.gov/TOOLS/Htdp/Htdp.shtml). The WGS84 (G1762) epoch realization was introduced in 2013. The survey acquisition dates succeed this date; therefore, it was the appropriate datum realization for post-processing the navigation data which was acquired in the WGS84 (G1762) datum. The resultant base position used for post-processing was 27°5247.88931 North, 82°5033.69685 West (WGS84-G1762), and -17.543 m ellipsoid height (WGS84-G1762). The kinematic trajectories (rover to base) were processed using NovAtel's Waypoint GrafNav software version 8.60.5025.
  3. How accurate are the heights or depths?
    The ellipsoid height value -17.543 m (WGS84-G1762) was used in NovAtel's Waypoint GrafNav software. Please refer to the Horizontal_Positional_Accuracy_Report segment for vertical position transformation into ellipsoid height.
  4. Where are the gaps in the data? What is missing?
    This data release contains single-beam bathymetry data points in the horizontal position and vertical elevation (x,y,z) from February 2017 collected off Madeira Beach, Florida. Users are advised to read the complete metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    These data were collected during a single field activity with consistent instrument calibrations.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints None. These data are held in the public domain.
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. These data should not be used for navigational purposes.
  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? Madeira_Beach_2017_SBES_WGS84_UTM17N_xyz.txt, Madeira_Beach_2017_SBES_WGS84_tracklines.shp, Madeira_Beach_2017_SBES_NAD83_NAVD88_UTM17N_GEOID12B_xyz.txt, Madeira_Beach_2017_SBES_20m_DEM.tif
  3. What legal disclaimers am I supposed to read?
    This digital publication was prepared by an agency of the United States Government. Although these data were processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, nor shall the act of distribution imply any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 01-May-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_SBES_xyz_metadata.faq.html>
Generated by mp version 2.9.51 on Wed May 1 12:26:26 2024