Ground-Penetrating Radar Data and Differential Global Positioning System Data Collected from Long Beach Island, New Jersey, April 2015

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

Frequently anticipated questions:

What does this data set describe?

Title:
Ground-Penetrating Radar Data and Differential Global Positioning System Data Collected from Long Beach Island, New Jersey, April 2015
Abstract:
Scientists from the United States Geological Survey, St. Petersburg Coastal and Marine Science Center, U.S. Geological Survey Pacific Coastal and Marine Science Center, and students from the University of Hawaii at Manoa collected sediment cores, sediment surface grab samples, ground-penetrating radar (GPR) and Differential Global Positioning System (DGPS) data from within the Edwin B. Forsythe National Wildlife Refuge-Holgate Unit located on the southern end of Long Beach Island, New Jersey, in April 2015 (FAN 2015-611-FA). The study's objective was to identify washover deposits in the stratigraphic record to aid in understanding barrier island evolution. This report is an archive of GPR and DGPS data collected from Long Beach Island in 2015. Data products, including raw GPR and processed DGPS data, elevation corrected GPR profiles, and accompanying Federal Geographic Data Committee metadata can be downloaded from the Data Downloads page.
Supplemental_Information:
Data were collected during USGS field activity number (FAN) 2015-611-FA, additional survey details are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2015-611-FA.
  1. How might this data set be cited?
    Zaremba, Nicholas J., 20160720, Ground-Penetrating Radar Data and Differential Global Positioning System Data Collected from Long Beach Island, New Jersey, April 2015:.

    This is part of the following larger work.

    Zaremba, Nicholas J., Smith, Kathryn E., Bishop, James M., and Smith, Christopher G., 07202016, Ground-Penetrating Radar Data and Differential Global Postiioning Systems Data Collected from Long Beach Island, New Jersey, April 2015 Geospatial_Data_Presentation_Form: Publication (Other): U.S. Geological Survey Data Series 1006, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.283240
    East_Bounding_Coordinate: -74.266045
    North_Bounding_Coordinate: 39.531646
    South_Bounding_Coordinate: 39.517144
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 09-Apr-2015
    Ending_Date: 13-Apr-2015
    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 Vector data set. It contains the following vector data types (SDTS terminology):
      • String (41)
    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.001. Longitudes are given to the nearest 0.001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is 500000.0.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
  7. How does the data set describe geographic features?
    2015-611-FA_GPR_ASCII_Raw_Data.zip
    File containing each raw, unprocessed GPR profile in ASCII format. Many XYZ processing programs will not accept column header labels; therefore, they were not placed in the file. Column 1= Horizontal distance (meters), Column 2= elevation, Column 3= two-way travel time, Column 4= Amplitude. (Source: USGS)
    Horizontal distance
    This column indicates the location in meters from the start (0) to the end of the GPR profile, this column can be used to locate the position of reflections. The distance data were collected using the distance measuring wheel. (Source: Reflexw) Values start with 0 (the beginning of the profile) and end with the total distance covered by the profile, units are in meters.
    Elevation
    All values in this column are 0 as a result of elevation data being contained in the GGA string and not recorded in the ASCII file. (Source: Reflexw) Values are all zero since elevation data have not been applied.
    Two-way travel time
    This column records the two-way travel time, in nanoseconds, that it takes to reach a reflection from the source. (Source: Reflexw)
    Range of values
    Minimum:0
    Maximum:170
    Amplitude
    Amplitude of the reflection, in Megahertz (Source: Reflexw) Data represent the amplitude of the reflection, which can vary widely, and values can be either negative or positive.
    2015-611-FA-GGA_Strings.zip
    File containing the processed navigation data for the GPR profiles. Data do not contain column labels Column 1= Message ID $GPGGA, Column 2= UTC of position fix, Column 3= Latitude, Column 4= Direction of latitude: N, Column 5= Longitude, Column 6= Direction of longitude: W, Column 7= GPS Quality indicator:0: Fix not valid 1: GPS fix 2: Differential GPS fix, OmniSTAR VBS 4: Real-Time Kinematic, fixed integers 5: Real-Time Kinematic, float integers, OmniSTAR XP/HP or Location RTK, Column 8= Number of Space Vehicles (SVs) in use, range from 00 through to 24+, Column 9= Horizontal Dilution of Precision (HDOP), Column 10= Orthometric height (MSL reference), Column 11= M: unit of measure for orthometric height is meters, Column 12= Geoid Separation, Geoid 13= M: geoid separation measured in meters, Column 14= Age of differential GPS data record, Type 1 or Type 9. Null field when DGPS is not used. Column 15= Reference station ID, range 0000-4095. A null field when any reference station ID is selected, and no corrections are received. Column 16= The checksum data always begins with *. (Source: GrafNav)
    Message ID $GPGGA
    The type of file, indicates it is a GGA string. (Source: GrafNav) Attribute is a file format identification.
    UTC of position fix
    GPS time in seconds. (Source: GrafNav) Value is GPS time, increases by 1 every second.
    Latitude
    The latitude of the XYZ point, latitude is projected in UTM 18N. (Source: GrafNav) Values are degrees of latitude, spatial data.
    Direction of latitude:
    Direction of latitude is in the Northern (N) Hemisphere. (Source: GravNav) The attribute indicates that the degree of latitude is in the Northern Hemisphere.
    Longitude
    The longitude of the XYZ data point. (Source: GrafNav) Values are the degree of longitude, spatial data.
    Direction of longitude:
    Direction of longitude is in the Western (W) Hemisphere. (Source: GrafNav) The attribute indicates that the degree of longitude is in the Western Hemisphere.
    GPS Quality indicator: 0: Fix not valid 1: GPS fix 2: Differential GPS fix, OmniSTAR VBS 4: Real-Time Kinematic, fixed integers 5: Real-Time Kinematic, float integers, OmniSTAR XP/HP or Location RTK
    Defines the type and quality of the DGPS data. (Source: GrafNav)
    Range of values
    Minimum:0
    Maximum:5
    Number of SVs in use, range from 00 through to 24+
    Number of satellites utilized by the program to process the data. (Source: GrafNav)
    Range of values
    Minimum:00
    Maximum:24
    HDOP
    Horizontal Dilution of Precision (HDOP) expresses the effect of satellite positions on the precision of the reported positions. < 1 Ideal, 1-2 Excellent, 2-5 good, 5-10 moderate, 10-20 fair, >20 poor. (Source: GrafNav)
    Range of values
    Minimum:0
    Maximum:20
    Orthometric height (MSL reference)
    Height of the XYZ position in reference to NAVD88 using GEIOD12A. (Source: GrafNav) Elevation above the GEIOD12A in meters, spatial data.
    M: unit of measure for orthometric height is meters
    The orthometric height is reported in meters. (Source: GrafNav) Indicates data are reported in meters.
    Geoid separation
    Separation between GEIOD12A and the reference ellipsoid NAVD88 in meters. (Source: GrafNav) Separation between GEIOD12A and the reference ellipsoid NAVD88 in meters.
    M: geoid separation measured in meters
    Defines the separation between GEIOD12A and the reference ellipsoid NAVD88 measured in meters (m). (Source: GrafNav) Indicates data are reported in meters.
    Age of differential GPS data record, Type 1 or Type 9. Null field when DGPS is not used.
    The corrected DGPS time (Source: GrafNav)
    Range of values
    Minimum:1
    Maximum:9
    Reference station ID, range 0000-4095. A zerois used when any reference station ID is selected and no corrections are received.
    Refers to the reference station used to process the DGPS data presented in this dataset. (Source: GrafNav)
    Range of values
    Minimum:0
    Maximum:4095
    The checksum data, always begins with *
    The name of the checksum data used to detect errors. (Source: GrafNav) Numbers increase sequentially by 1.
    2015-611-FA_GPR_Profile_Images.zip
    File contains the JPEG images of the processed GPR profiles with the elevation corrections applied. For shore perpendicular profiles, west is on the left-hand side; east is on the right-hand side. For shore-parallel profiles, north is on the left-hand side and south is on the right-hand side. Data were exported from REFLEXW using a vertical velocity of 0.09 m/ns. (Source: USGS)
    2015-611-FA_GPR_KML.zip
    File contains Keyhole Markup Language (KML) files of the GPR profiles, each KML file is a single profile. (Source: USGS)
    2015-611-FA_GPR profile parameters.xlsx
    Microsoft Excel table listing the parameters assigned to each GPR profile during collection in the field. (Source: USGS)
    Line
    Lists the profile name. (Source: User defined)
    Range of values
    Minimum:195
    Maximum:235
    scans/second
    The horizontal sampling rate if the system is in continuous data collection mode. (Source: User defined) Lines 195-221 were collected at a rate of 64 scans/second, lines 222-235 were collected at 32 scans/second.
    scans/unit(m)
    Scan/unit(m) refers to the number of scans per horizontal meter. (Source: User defined) Lines 195-221 were collected at a rate of 20 scans/unit(m) lines 222-235 were collected at 28 scans/unit(m).
    samples/scan
    Sample/scan set the number of data samples in a vertical scan. (Source: User defined) Lines 195-221 were collected at a rate of 1024 samples/scan, lines 222-235 were collected at 2048 samples/scan.
    bits/sample
    The bits/sample determine the dynamic range of the data. (Source: User defined) All lines were collected at 16 bits/sample.
    dielectric constant
    This column lists the assumed dielectric constant assigned to the GPR during collection of data, this determines the vertical scale, in meters, during data collection. (Source: User defined) All lines were collected with a display assuming a dielectric constant of 15.
    range (ns)
    range (ns) is the maximum two-way travel time in nanoseconds that is viewed during data collection. (Source: User defined) Lines 195-220 were collected with a range of 150, lines 221-235 were collected with a range of 170.
    MHz
    The MHz of the antennae used to collect the data, a 400 MHz antennae was used. (Source: Defined by antennae used.) All lines were collected with a 400 MHz antennae.
    2015-611-FA_FACs_Digital.zip
    Portable Document Format (PDF) files of the field notes, a list of crew and equipment used during field activity 2015-611-FA, and an XLSX file of start and stop times for GGA strings not associated with GPR data. (Source: USGS)
    Entity_and_Attribute_Overview:
    The entity and attribute information provided here describes the tabular data associated with the dataset. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the dataset.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information was generated by the individual or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Nicholas J. Zaremba
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Southeast Region
    Attn: Nicholas J. Zaremba
    Researcher IV
    600 4th Street South
    St. Petersburg, FL

    727-502-8000 (voice)
    727-502-8000 (FAX)
    nzaremba@usgs.gov

Why was the data set created?

The data were collected as part of the Barrier Island and Estuarine Wetland Change Assessment (BIWC) (https://coastal.er.usgs.gov/sandy-wetland-assessment/). The primary goal of the BIWC project is to quantify the physical changes that storm processes have on barrier-island wetlands and marsh ecosystems.

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: 02-Jun-2015 (process 1 of 4)
    GPR processing: The GPR data were processed using Sandmeier Scientific Software's Reflexw Version 7.2.2 geophysical near surface processing and interpretation software (http://www.sandmeier-geo.de/reflexw.html). Each GPR data file was imported into Reflex and converted from Radan’s proprietary DZT (.dzt) format to a .dat file, this file was exported in ASCII format. Next, a variety of processing steps were used, primarily applying static correction, subtracting-mean (dewow), removing header gain, and applying user-defined gains. After these initial processing steps, the GPS and elevation data were integrated into the trace headers, except for files 218-221. Lastly, all profiles were inspected for data quality to ensure no navigation or trace data gaps were present before the final profile images were output in JPEG format (available for download at pubs.usgs.gov/ds/1006/downloads/2014-611-FA_GPR_Images.zip). If any issues were discovered during the QA/QC process, this information was noted for each affected line and recorded in the metadata. A velocity of 0.09 m/ns was used to calculate and display depth on the elevation-corrected profiles. Person who carried out this activity:
    Nicholas J. Zaremba
    U.S. Geological Survey
    Researcher IV
    600 4th Street South
    St.Petersburg, FL

    (727)502-8000 (voice)
    nzaremba@usgs.gov
    Date: 08-May-2015 (process 2 of 4)
    Navigation processing: During acquisition, uncorrected real-time rover positions were output as an NMEA GGA string at a 9600 baud rate to an external GPS Acumen data logger [puck] and saved as a .plt file. Data were imported into Radan 7 (GSSI proprietary GPR software) and exported as a KML file. The GGA string data were imported into GrafNav 8.5 and post-processed to the surrounding Continuously Operating Reference Station (CORS) sites. Once processing was completed, the GGA string was exported and converted to a .txt file. Person who carried out this activity:
    Nicholas J. Zaremba
    U.S. Geological Survey
    Researcher IV
    600 4th Street South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    nzaremba@usgs.gov
    Date: 27-Mar-2018 (process 3 of 4)
    Keywords section of metadata optimized by adding theme keyword thesauri and associated keywords. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Arnell S. Forde
    Geologist
    600 4th Street South
    St. Petersburg, FL

    727-502-8000 (voice)
    aforde@usgs.gov
    Date: 13-Oct-2020 (process 4 of 4)
    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?
    No formal attribute accuracy tests were conducted.
  2. How accurate are the geographic locations?
    Location information associated with each GPR line was determined by postprocessed differential correction using a continuously operating reference stations/rover setup. Briefly, the field setup consisted of one (rover) Ashtech ProFlex Global Navigation Satellite System (GNSS) receiver, collecting raw GNSS data, at 5 Hertz (Hz).
  3. How accurate are the heights or depths?
    During acquisition of various lines, the signal between the GPS rover unit and multiple satellites was interrupted or lost. This lack of communication with the satellites caused either incorrect values or unreliable GPS data to be recorded. Lines 218-221 have non-elevation corrected profile images associated with each line.
  4. Where are the gaps in the data? What is missing?
    A total of 41 GPR lines, representing a linear distance of approximately 5.9 kilometers, were acquired during field activity 2015-611-FA.
  5. How consistent are the relationships among the observations, including topology?
    No formal logical accuracy tests were conducted.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None. Please see 'Distribution Information' for details.
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 originators of the data in future products or derivative research. Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations.
  1. Who distributes the data set? (Distributor 1 of 1)
    Nicholas J. Zaremba
    U.S. Geological Survey, Southeast Region
    Researcher IV
    600 4th Street South
    St. Petersburg, FL

    (727)-502-8000 (voice)
    nzaremba@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 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?
    • Availability in digital form:
      Data format: These zip archives contain GPR profile data in ASCII format, DGPS GGA strings associated with the GPR profiles, Google Earth KML files of the GPR profiles, JPEG images of the processed GPR profiles with elevation corrections applied, lists of crew and equipment used in PDF format and GPS acquisition parameters in Excel XLSX format. in format Compressed (zip) archive Vector digital data, tabular digital data, raster data Size: 1134
      Network links: https://pubs.usgs.gov/ds/1006/downloads/
    • Cost to order the data: None. No fees are applicable for obtaining the dataset.

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2021
Metadata author:
Nicholas J. Zaremba
U.S. Geological Survey, Southeast Region
Researcher III
600 4th Street South
St.Petersburg, FL

727-502-8000 (voice)
727-502-8000 (FAX)
nzaremba@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/2015_611_FA_GPR_Metadata.faq.html>
Generated by mp version 2.9.50 on Thu Oct 14 09:26:12 2021