Coastal Single-beam Bathymetry Data Collected in September and October 2019 from Rockaway Peninsula, New York

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

Frequently anticipated questions:

What does this data set describe?

Title:
Coastal Single-beam Bathymetry Data Collected in September and October 2019 from Rockaway Peninsula, New York
Abstract:
Scientists from the U.S. Geological Survey St. Petersburg Coastal and Marine Science Center (USGS - SPCMSC) in St. Petersburg, Florida, conducted a single-beam bathymetric survey of Rockaway Peninsula, New York September 27 - October 6, 2019. During this study, bathymetry data were collected aboard two personal watercraft (PWC) outfitted with single-beam echosounders, as well as a towed seismic sled with similar instrumentation.
Supplemental_Information:
For the single-beam bathymetry data, the differential positioning was obtained through post-processing the base station data to the rover. This dataset, Rockaway_2019_SBES_xyz.zip, was transformed from the initial World Geodetic System of 1984 (WGS84) G1762 datum to the North American Datum of 1983 (NAD83) North American Vertical Datum of 1988 (NAVD88), using the GEOID12B model (National Oceanic and Atmospheric Administration (NOAA) National Geodetic Survey (NGS) Transformation software VDatum, version 4.1 - http://vdatum.noaa.gov/).
  1. How might this data set be cited?
    Stalk, Chelsea A., DeWitt, Nancy T., Wei, Emily, Farmer, Andrew S., Miselis, Jennifer L., and Fredericks, Jake J., 20201112, Coastal Single-beam Bathymetry Data Collected in September and October 2019 from Rockaway Peninsula, New York: U.S. Geological Survey Data Release doi:10.5066/P9WNJSFN, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -73.940546
    East_Bounding_Coordinate: -73.751884
    North_Bounding_Coordinate: 40.592875
    South_Bounding_Coordinate: 40.527691
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 27-Sep-2019
    Ending_Date: 06-Oct-2019
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
  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,167,719)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 18
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -75.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?
    Rockaway_2019_SBES_WGS84_xyz.txt
    Comma-delimited x,y,z file containing location, elevation, and date information pertaining to data collected aboard two PWC's and a towed seismic sled, nearshore Rockaway Peninsula, New York in 2019. (Source: U.S. Geological Survey)
    WGS84_UTM18N_X
    WGS84 UTM x-axis coordinate (Zone 18N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:589733.035
    Maximum:605615.935
    Units:meters
    WGS84_UTM18N_Y
    WGS84 UTM y-axis coordinate (Zone 18N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:4487075.268
    Maximum:4494104.278
    Units:meters
    Ellipsoid
    Z-value (elevation) in WGS84 ellipsoid heights (Source: U.S. Geological Survey)
    Range of values
    Minimum:-48.580
    Maximum:-33.339
    Units:meters
    WGS84_Lat
    WGS84 y-axis coordinate (latitude) (Source: U.S. Geological Survey)
    Range of values
    Minimum:40.529423
    Maximum:40.591137
    Units:Decimal Degrees
    WGS84_Long
    WGS84 x-axis coordinate (longitude) (Source: U.S. Geological Survey)
    Range of values
    Minimum:-73.940371
    Maximum:-73.751911
    Units:Decimal Degrees
    Year
    Calendar year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2019
    Maximum:2019
    DOY
    Day of year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:270
    Maximum:279
    Time
    UTC time of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:13:28:21.16
    Maximum:21:47:50.513
    Hypack_Line
    Line identification assigned by HYPACK during acquisition. (Source: HYPACK/U.S. Geological Survey) Vessel SubFan_planned HYPACK line number_UTC time of the start of the line. Instances where 0001 is utilized represents a second start of a line within the same minute. Nomenclature SLED was added as an additional identifier to the 19CCT07 platform (towed seismic sled) to further differentiate platform type and separate from the towing vessel.
    Rockaway_2019_SBES_NAD83_NAVD88_G12B_xyz.txt
    Comma-delimited x,y,z file containing location, elevation, and date information pertaining to data collected aboard two PWC's and a towed seismic sled, nearshore Rockaway Peninsula, New York in 2019. (Source: U.S. Geological Survey)
    NAD83_UTM18N_X
    NAD83 UTM x-axis coordinate (Zone 18N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:589733.533
    Maximum:605616.430
    Units:meters
    NAD83_UTM18N_Y
    NAD83 UTM y-axis coordinate (Zone 18N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:4487074.224
    Maximum:4494103.231
    Units:meters
    NAVD88_G12B
    Z-value (elevation) in NAVD88 GEOID12B (Source: U.S. Geological Survey)
    Range of values
    Minimum:-15.06
    Maximum:0.068
    Units:meters
    NAD83_Lat
    NAD83 y-axis coordinate (latitude) (Source: U.S. Geological Survey)
    Range of values
    Minimum:40.529414
    Maximum:40.591137
    Units:Decimal Degrees
    NAD83_Long
    NAD83 x-axis coordinate (longitude) (Source: U.S. Geological Survey)
    Range of values
    Minimum:-73.940371
    Maximum:-73.751905
    Units:Decimal Degrees
    Year
    Calendar year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:2019
    Maximum:2019
    DOY
    Day of year of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:270
    Maximum:279
    UTC_Time
    UTC time of data acquisition (Source: U.S. Geological Survey)
    Range of values
    Minimum:13:28:21.16
    Maximum:21:47:50.51
    Hypack_Line
    Line identification assigned by HYPACK during acquisition. (Source: HYPACK/U.S. Geological Survey) Vessel SubFan_planned HYPACK line number_UTC time of the start of the line. Instances where 0001 is utilized represents a second start of a line within the same minute. Nomenclature SLED was added as an additional identifier to the 19CCT07 platform (towed seismic sled) to further differentiate platform type and separate from the towing vessel.

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
    • Nancy T. DeWitt
    • Emily Wei
    • Andrew S. Farmer
    • Jennifer L. Miselis
    • Jake J. Fredericks
  2. Who also contributed to the data set?
    Funding and (or) support for this study were provided by the NFWF Beach and Monitoring Project and USGS Coastal and Marine Hazards and Resources Program, specifically the Costal Sediment Availability and Flux (CSAF) project. The authors would like to thank Jim Flocks and Arnell Forde of the USGS - St. Petersburg, Florida for their thoughtful peer reviews.
  3. To whom should users address questions about the data?
    Chelsea A. Stalk
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Electronics Technician (Marine Instrumentation)
    600 4th St. S
    St. Petersburg, FL
    USA

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

Why was the data set created?

To evaluate shoreface morphology along the Rockaway Peninsula, New York, scientists from the USGS SPCMSC conducted a bathymetric survey during Field Activity Number (FAN) 2019-333-FA. The objectives of the data collection effort were to map shoreface morphology in support of the National Fish and Wildlife (NFWF) Beach and Marsh Monitoring Project and the USGS Coastal Sediment Availability and Flux (CSAF) Project. This dataset, Rockaway_2019_SBES_xyz.zip consists of single-beam horizontal position (x,y) and vertical (z) elevation data collected along the nearshore zone of the Rockaway Peninsula. Additional survey and data details are available from the Coastal and Marine Geoscience Data System (CMGDS) at, https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-333-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: 2019 (process 1 of 7)
    GPS Acquisition: Two Global Positioning System (GPS) base stations were established near the survey area. The primary base station, RIIS, is a USGS installed P/K nail located in the dockage area of the former Riis Landing U.S. Coast Guard Station located just west of the Marine Parkway Bridge on the Rockaway Peninsula. The secondary station, FLYD, was an additional USGS installed P/K nail located on the retired airstrip of Floyd Bennett Field, located in southeast Brooklyn, New York City. The base stations were continually occupied and equipped with a Spectra Precision SP90M (RIIS) and a Spectra Precision Proflex 800 (FLYD) GPS receiver recording full-carrier-phase positioning signals (L1/L2) from satellites via Thales Choke-ring antennas, recording at a rate of 0.1 s. Person who carried out this activity:
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Attn: Chelsea Stalk
    Electronics Technician (Marine Instrumentation)
    600 4th St. S
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    cstalk@usgs.gov
    Date: 2019 (process 2 of 7)
    Single-Beam Bathymetry Acquisition: The single-beam bathymetric data were collected under USGS FAN 2019-333-FA, which encompass data from three separate survey platforms; The R/V Shark (19CCT05), a 12-ft Yamaha PWC collected 94.73 line-km (84 lines), the R/V Chum (19CCT06), an additional 12-ft Yamaha PWC collected 94.86 line-km (83 lines), and a seismic sled towed by the R/V Sallenger (sled FAN 19CCT07) collected 210.17 line-km (73 lines). A total of 399.76 line-km (240 lines) were surveyed. Boat motion was recorded at 50-millisecond (ms) intervals using an SBG motion sensor. HYPACK (version 18.1.8.0), a marine surveying, positioning, and navigation software package, managed the planned-transect information and provided real-time navigation, steering, correction, data quality parameters, and instrumentation-status information to the vessel operator. Depth soundings were recorded at 50-ms intervals using an Odom Echotrac CV100 sounder with a 4 degree, 200-kilohertz (kHz) transducer. Data from the GPS receiver, motion sensor, and fathometer were recorded in real-time aboard the platform 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 three separate SonTek Castaway conductivity, temperature, and depth (CTD) instruments deployed from each survey platform. The instruments were periodically cast overboard to observe changes in water column speed of sound (SOS). A total of 49 successful sound velocity casts were taken throughout the survey at an average depth of 3.13 m, and on average produced a sound velocity of 1514.25 meters per second (m/s). Person who carried out this activity:
    Chelsea A. Stalk
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Date: 2019 (process 3 of 7)
    Differentially Corrected Navigation Processing: The coordinate value of the GPS base station is the time weighted average (TWA) of all current survey occupations. The base station coordinates were imported into GrafNav version 8.7 and the kinematic GPS data from the survey platform were post-processed to the concurrent GPS session data at the base station. During processing, steps were taken to ensure that the trajectories between the base and the rover were clean, resulting in fixed positions. By analyzing the graphs, trajectory maps, and processing logs that GrafNav produces for each GPS session, GPS data from satellites flagged by the program as having poor health or satellite time segments that had cycle slips could be excluded, or the satellite elevation mask angle could be adjusted to improve the position solutions. The final differentially corrected, precise DGPS positions were computed at 0.1 s and exported in American Standard Code for Information Interchange (ASCII) text format. In subsequent processing steps, these data will replace the uncorrected, real-time rover positions. The GPS data were processed and exported in the WGS84 (G1762) geodetic datum. Person who carried out this activity:
    Chelsea A. Stalk
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Date: 2019 (process 4 of 7)
    Single-beam Bathymetry Processing: All data were processed using CARIS HIPS and SIPS (Hydrographic Information Processing System and Sonar Information Processing System) version 11.3.4. The raw HYPACK data files were imported into CARIS, the differentially corrected navigation files were imported using the generic data parser (GDP) tool, and any SVP profile casts were entered and edited using the SVP editor. The bathymetric data components (position, motion, depth, and SOS) for all data were then merged and geometrically corrected in CARIS to produce processed x,y,z data. Next, the data were edited for outliers and then further reviewed in the Subset Editor utility for crossing status, and questionable data points or areas. The geometrically corrected point data were then exported as an x,y,z ASCII text file referenced to WGS84 (G1762), ellipsoid height in meters. Person who carried out this activity:
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Attn: Chelsea A. Stalk
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Date: 2019 (process 5 of 7)
    Quality Control, Quality Assurance (QA/QC): All single-beam data exported from CARIS were imported into Esri ArcMap version 10.6.0, where a shapefile of the individual sounding data points (xyz) was created and plotted in 0.25-m color coded intervals. First, all data were visually scanned for any obvious outliers or problems. Next, a track line shapefile was produced using X-tools Pro "Make Polylines from Points" function. Utilizing both the x,y,z (point) and track line (polyline) shapefiles, an in-house Python script evaluated elevation differences at the intersection of crossing track lines by calculating the elevation difference between points at each intersection using an inverse distance weighting equation with a search radius of 1 m. The calculated RMS errors when a vessel crosses a track line previously surveyed is as follows: WVR1 (19CCT05) = 7.1 cm, WRV2 (19CCT06) = 8.30 cm, and the Sled (19CCT07) = 5.1 cm, respectively. Once individual platform statistics were obtained, all x,y,z data were merged into a single shapefile and a crossing analysis preformed, which yielded an 8.16 cm RMS error. Since the bias between the platform elevations was on the order of the Odom instrument accuracy (1 cm +/- 0.7 percent depth), no adjustments were made. The merged file was exported from Esri ArcMap as an x,y,z text (.txt) file and made available in the download section of this data release, along with the populated track line shapefiles. Person who carried out this activity:
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Attn: Chelsea A. Stalk
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Data sources used in this process:
    • 19CCT05_Rockaway_SBES_WGS84_UTM18N_Level_03_xyz.txt, 19CCT06_Rockaway_SBES_WGS84_UTM18N_Level_03_xyz.txt, 19CCT07_Rockaway_SLED_SBES_WGS84_UTM18N_Level_03_xyz.txt
    Data sources produced in this process:
    • Rockaway_2019_SBES_WGS84_xyz.txt Rockaway_2019_SBES_WGS84_Tracklines.shp
    Date: 2019 (process 6 of 7)
    Datum Transformation: NOAA's VDatum v.4.1 was used to transform single-beam data points (x,y,z) from their acquisition datum WGS84 (G1762) to the NAD83 (horizontal), and the NAVD88 (vertical) reference frames using the NGS geoid model of 2012B (GEOID12B). For conversion from the WGS84 ellipsoid to NAVD88, there is a total of 7.616 cm of uncertainty in the transformation (https://vdatum.noaa.gov/docs/est_uncertainties.html). Resultant data files have been made available in the downloads section of this data release. Person who carried out this activity:
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Attn: Chelsea A. Stalk
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
    Data sources used in this process:
    • Rockaway_2019_SBES_WGS84_xyz.txt
    Data sources produced in this process:
    • Rockaway_2019_SBES_NAD83_NAVD88_G12B_xyz.txt
    Date: 17-Nov-2020 (process 7 of 7)
    Added keywords section with USGS persistent identifier as theme keyword. 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
  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 is determined during data collection. This dataset is derived from a single field survey using similar equipment, set-ups, and staff; therefore, the dataset is internally consistent. Methods are 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 Ashtech antenna reference point (ARP) were measured and accounted for in post-processing. Differential Global Positioning System (DGPS) coordinates were obtained through post-processing using the software Online Positioning User Service (OPUS) maintained by the NOAA and the NGS, and Waypoint Product Group GrafNav, version 8.7.
  2. How accurate are the geographic locations?
    All static base station sessions were processed through OPUS. The OPUS solutions were entered into a spreadsheet to compute a final, time-weighted position (latitude, longitude, and ellipsoid height) for the utilized base stations. The time-weighted position for the USGS established benchmark RIIS, a P/K nail installed in the dockage area of the former Riis Landing U.S. Coast Guard Station, was calculated and used in subsequent processing steps. Accuracy pertaining to the base station horizontal coordinates is as follows: Horizontal = 0.000009 seconds (s) or approximately 0.002 meters (m). An additional base station was erected on a USGS established benchmark FLYD, a P/K nail installed on the retired air strip of Floyd Bennett Field. FLYD served as a secondary base station and was not used in final processing. The kinematic (rover) trajectories were processed using GrafNav version 8.70 software by Novatel, Inc. Transformed data have an additional reported horizontal transformation error of 7.6158 centimeters (cm).
  3. How accurate are the heights or depths?
    All static base station sessions were processed through OPUS. The OPUS solutions were entered into a spreadsheet to compute a final, time-weighted position (latitude, longitude, and ellipsoid height) for the utilized base station. The time-weighted position for the USGS established benchmark RIIS, a P/K nail installed in the dockage area of the former Riis Landing U.S. Coast Guard Station, was calculated and used in subsequent processing steps. Accuracy pertaining to the base station vertical coordinate is 0.007 m. An additional base station was erected on a USGS established benchmark FLYD, a P/K nail installed on the retired air strip of Floyd Bennett Field. FLYD served as a secondary base station and was not used in final processing. The kinematic (rover) trajectories were processed using GrafNav version 8.70 software by Novatel, Inc. Transformed data have an additional reported vertical transformation error of 7.6158 cm.
  4. Where are the gaps in the data? What is missing?
    This data release contains horizontal position and vertical elevation (x,y,z) single-beam data from September - October 2019, collected within the nearshore waters of the Rockaway Peninsula, New York. 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 datasets are from one 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
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)
    Chelsea A. Stalk
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Electronics Technician (Marine Instrumentation)
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    cstalk@usgs.gov
  2. What's the catalog number I need to order this data set? Rockaway_2019_SBES_WGS84_xyz.txt, Rockaway_2019_SBES_NAD83_NAVD88_G12B_xyz.txt, Rockaway_2019_SBES_WGS84_Tracklines.shp
  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: 17-Nov-2020
Metadata author:
Chelsea A. Stalk
U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
Electronics Technician (Maine Instrumentation)
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/Rockaway_2019_SBES_metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:52 2021