Beach Profile Data Collected From Madeira Beach, Florida (February 17, 2017)

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

Frequently anticipated questions:

What does this data set describe?

Title:
Beach Profile Data Collected From Madeira Beach, Florida (February 17, 2017)
Abstract:
This dataset, prepared by the U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC), provides beach profile data collected at Madeira Beach, Florida. Data were collected on foot by a person equipped with a Global Positioning System (GPS) antenna affixed to a backpack outfitted for surveying location and elevation data (XYZ) along pre-determined transects. The horizontal position data are given in the Universal Transverse Mercator (UTM) projected coordinate system, Zone 17 North (17N), referenced to the North American Datum of 1983 (NAD 83); the elevation data are referenced to the North American Vertical Datum of 1988 (NAVD 88), GEOID12B.
  1. How might this data set be cited?
    Brown, Jenna A., Thompson, Dave M., and Long, Joseph W., 20180314, Beach Profile Data Collected From Madeira Beach, Florida (February 17, 2017):.

    This is part of the following larger work.

    Brown, Jenna A., Birchler, Justin J., Thompson, David M., Long, Joseph W., and Seymour, Alexander C., 20180314, Beach Profile Data Collected From Madeira Beach, Florida: U.S. Geological Survey data release doi:10.5066/F7T43S94, U.S. Geological Survey, St. Petersburg, Florida.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -82.79969246
    East_Bounding_Coordinate: -82.79497017
    North_Bounding_Coordinate: 27.79867859
    South_Bounding_Coordinate: 27.79491806
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_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 (12479)
    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.9996
      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.141
      Ordinates (y-coordinates) are specified to the nearest 0.158
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum 1988
      Altitude_Resolution: 0.0001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    20170217_MadeiraBeachFL_XYZ.zip
    Processed beach profile data collected February 17, 2017 from Madeira Beach, Florida. The location and elevation data are provided in .xyz format (Source: U.S. Geological Survey)
    Easting
    UTM x-axis coordinate (NAD83, UTM Zone 17N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:322705.234
    Maximum:323164.639
    Units:Meter
    Northing
    UTM y-axis coordinate (NAD83, UTM Zone 17N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:3075783.383
    Maximum:3076193.427
    Units:Meter
    Elevation
    Orthometric elevation z-coordinate (NAVD88, GEOID12B) (Source: U.S. Geological Survey)
    Range of values
    Minimum:-1.152
    Maximum:2.607
    Units:meters

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Jenna A. Brown
    • Dave M. Thompson
    • Joseph W. Long
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Jenna A. Brown
    600 4th Street South
    Saint Petersburg, FL
    UNITED STATES

    727-502-8125 (voice)
    jennabrown@usgs.gov

Why was the data set created?

The purpose of this dataset is to provide geospatial and topographic profile data, in support of a coastal video monitoring station at Madeira Beach, Florida. To ensure that SPCMSC data management protocols were followed, this survey was assigned a USGS field activity number (FAN), 2017-353-FA. Additional survey and data details are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-353-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: 17-Feb-2017 (process 1 of 5)
    PLANNING Transects were created using the MathWorks MATLAB R2016a computing environment. Cross-shore transects were planned perpendicular to the beach by utilizing a measured 2010 lidar shoreline to find an average shoreline angle, and were cast at locations of groins (cross-shore perpendicular structures that are connected to land and extend into the ocean) and at 3 equally spaced alongshore locations between groins in the area of interest by utilizing Google Earth to determine the location of the groins. This resulted in 25 transects spaced approximately 23 meters (m) apart and spanning approximately 555 m in the alongshore direction. An additional cross-shore transect was planned in the middle of the study area in support of the USGS National Assessment of Coastal Change Hazards project. Four alongshore transects, spanning the length of the study area, were cast approximately 10 m apart in the cross-shore, spanning from the dune toe to the shoreline. Person who carried out this activity:
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Dave M. Thompson
    Physical Scientist
    600 4th Street South
    Saint Petersburg, FL

    727-502-8079 (voice)
    dthompson@usgs.gov
    Date: 17-Feb-2017 (process 2 of 5)
    AQUISITION Transect lines were surveyed, on foot, by a person equipped with a Global Positioning System (GPS) receiver and a GPS antenna affixed to a SECO© surveying backpack, and connected to a Windows laptop PC running Hypack 2016 survey acquisition software. Kinematic GPS data were recorded at 5 Hz with an Ashtech ProFlex™ 500/800 Global Navigation Satellite System (GNSS) receiver and an Ashtech® GNSS geodetic survey antenna. The time associated with the beginning and end of surveying each transect line was recorded on the laptop in HYPACK by the surveyor. Person who carried out this activity:
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Dave M. Thompson
    Physical Scientist
    600 4th Street South
    Saint Petersburg, FL

    727-502-8079 (voice)
    dthompson@usgs.gov
    Date: 04-May-2017 (process 3 of 5)
    GPS POST-PROCESSING Raw GPS kinematic data recorded on the surveying receiver were post-processed using GNSS post-processing software GrafNav (Waypoint Product Group) version 8.7 in order to achieve higher horizontal position and elevation data accuracies. The kinematic GPS data recorded by the surveying receiver were processed in NAD 83 geographic coordinates to concurrent static GPS data recorded by a local base station of known position (NAD 83). The base station used was the Florida Permanent Reference Network (FPRN) site at Indian Shores (FLIS). The final, differentially-corrected, precise GPS positions were exported in American Standard Code for Information Interchange (ASCII) text format, with projected horizontal coordinates in NAD 83, UTM Zone 17N, and vertical coordinates in NAVD 88, GEOID12B. Person who carried out this activity:
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Dave M. Thompson
    Physical Scientist
    600 4th Street South
    Saint Petersburg, FL

    727-502-8079 (voice)
    dthompson@usgs.gov
    Date: 19-Oct-2017 (process 4 of 5)
    DATA PROCESSING Beach profile horizontal position and elevation data for each individual transect were extracted from the post-processed GPS data based on the surveying times recorded with HYPACK using the MathWorks MATLAB R2016a computing environment. The data were smoothed in the cross-shore direction to reduce the noisiness of the highly-sampled elevation data, using a moving 1-meter wide Hanning filter in MATLAB. The data were quality-controlled in MATLAB to remove invalid data points by: eliminating points with poor GPS data quality, visually inspecting plots of horizontal positions and discarding points not on the cross-shore beach profile lines (e.g., points just prior to and just after a transect), and visually inspecting plots of elevation and discarding points with erroneous GPS data (e.g., spikes in the GPS data). Lastly, the elevation data were adjusted by subtracting the elevation of the GPS antenna above the ground, when attached to the surveying backpack, during the survey (1.98 m). The final beach profile data were written to individual text files (.xyz) in tabular format, with columns representing: 1) Easting (NAD83, UTM Zone 17N), 2) Northing (NAD83, UTM Zone 17N), and 3) Orthometric Elevation (NAVD 88, GEOID12B). Person who carried out this activity:
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Dave M. Thompson
    Physical Scientist
    600 4th Street South
    Saint Petersburg, FL

    727-502-8079 (voice)
    dthompson@usgs.gov
    Date: 13-Oct-2020 (process 5 of 5)
    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?

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

  1. How well have the observations been checked?
    Cross-shore profiles were quality checked for accuracy by comparing elevations where cross-shore and alongshore transects overlapped.
  2. How accurate are the geographic locations?
    The horizontal accuracy of the post-processed kinematic GPS data is +/- 1 centimeters (cm), according to the manufacturer's specifications.
  3. How accurate are the heights or depths?
    The vertical accuracy of the post-processed kinematic GPS data is +/- 2 centimeters (cm), according to the manufacturer's specifications.
  4. Where are the gaps in the data? What is missing?
    Initial survey planning included the acquisition of 30 transects (26 cross-shore, 4 alongshore). However, no alongshore transects were collected and only 25 cross-shore transects were collected during this survey; lines 1 to 4 and 60 were not collected during this survey due to time limitations. This dataset is considered complete for the information presented, as described in the abstract section. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Cross-shore profiles were quality checked for consistency by comparing elevations to previous or subsequent surveys of the same transects.

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. Please recognize the U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center as the 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, St. Petersburg, Florida
    Attn: Jenna A. Brown
    600 4th Street South
    Saint Petersburg, FL

    727-502-8125 (voice)
    jennabrown@usgs.gov
  2. What's the catalog number I need to order this data set?
  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 have been 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: 03-Jun-2022
Metadata author:
U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
Attn: Jenna A. Brown
600 4th Street South
Saint Petersburg, FL

727-502-8125 (voice)
jennabrown@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/20170217_MadeiraBeachFL_XYZ_metadata.faq.html>
Generated by mp version 2.9.51 on Mon Jun 6 12:33:25 2022