Reference marks, ground control points, navigation, and elevation data from pole surveys at Marconi Beach, Wellfleet during field activity 2021-022-FA on January 14 and 15 & March 10 and 17, 2021

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

Frequently anticipated questions:

What does this data set describe?

Title:
Reference marks, ground control points, navigation, and elevation data from pole surveys at Marconi Beach, Wellfleet during field activity 2021-022-FA on January 14 and 15 & March 10 and 17, 2021
Abstract:
The data in this publication map the beach and nearshore environment at Marconi Beach in Wellfleet, MA and provide regional context for the 2021 CoastCam installation that looks out at the coast shared by beachgoers, shorebirds, seals, and sharks. These data were collected as part of field activity 2021-022-FA and a collaboration with the National Park Service at Cape Cod National Seashore to monitor the region that falls within the field of view of CoastCam CACO-02, which are two video cameras aimed at the beach. Starting in February and ending in March 2021, U.S Geological Survey and Woods Hole Oceanographic Institute (WHOI) scientists conducted field surveys to collect position and orientation information for the CoastCam cameras and map the field of view. Two new reference marks were established in the Marconi Beach parking area to establish ground control for future surveys. Elevation data were collected using a real time kinematic – satellite navigation system (RTK-GNSS) receiver attached to a pole and walked on the beach. Point data of the beach face were collected along transects. Grain-size analysis was performed on sediment samples collected with a spade along multiple profiles from the bluff base to the intertidal zone. Aerial images of the beach for use in Structure-from-Motion were taken with a camera (Ricoh GRII) and a post-processed kinematic (PPK) system attached to a helium powered balloon-kite (Helikite) and high-precision GPS targets (AeroPoints) were used as ground control points. Bathymetry was collected in the nearshore using a single-beam echosounder mounted on a surf capable self-righting electric autonomous survey vehicle. Agisoft Metashape (v. 1.7.2) was used to create a digital elevation model with the collected imagery and this was merged with the bathymetry in MATLAB (v. 2020) to create a continuous topobathy product.
Supplemental_Information:
For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/fan_info.php?fan=2021-022-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 2021, Reference marks, ground control points, navigation, and elevation data from pole surveys at Marconi Beach, Wellfleet during field activity 2021-022-FA on January 14 and 15 & March 10 and 17, 2021: data release DOI:10.5066/P9POZ9VH, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Over, J., Sherwood, C., Traykovski, P., and Marsjanik, E., 2021, Topographic and bathymetric data, sediment samples, structure from motion imagery, and reference mark data collected at Marconi Beach, Wellfleet in winter 2021, U.S Geological Survey Field Activity 2021-022-FA: data release DOI:10.5066/P9POZ9VH, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Over, J.R., Sherwood, C.R., Traykovski, P., and E. Marsjanik, 2021, Topographic and bathymetric data, sediment samples, structure from motion imagery, and reference mark data collected at Marconi Beach, Wellfleet in winter 2021, U.S Geological Survey Field Activity 2021-022-FA: U.S Geological Survey data release, https://doi.org/10.5066/P9POZ9VH
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -69.96438619
    East_Bounding_Coordinate: -69.96223257
    North_Bounding_Coordinate: 41.89469982
    South_Bounding_Coordinate: 41.89117591
  3. What does it look like?
    2021022FA_Marconi_Navigation_browse.JPG https://cmgds.marine.usgs.gov/data/field-activity-data/2021-022-FA/data/Navigation/2021022FA_Marconi_Navigation_browse.JPG (JPEG)
    Browse graphic of the spatial distribution of the navigation/elevation points from surveys and ground control deployments at Marconi Beach, MA
    2021022FA_Marconi_PK_Nail_RM1_ParkingLot_ViewS.jpg https://cmgds.marine.usgs.gov/data/field-activity-data/2021-022-FA/data/Navigation/2021022FA_Marconi_PK_Nail_RM1_ParkingLot_ViewS.jpg (JPEG)
    Browse graphic of the location of Reference Mark 01 established in the Marconi Beach parking lot, MA
    2021022FA_Marconi_PK_Nail_RM2_Road_ViewN.jpg https://cmgds.marine.usgs.gov/data/field-activity-data/2021-022-FA/data/Navigation/2021022FA_Marconi_PK_Nail_RM2_Road_ViewN.jpg (JPEG)
    Browse graphic of the location of Reference Mark 02 established at Marconi Beach, MA
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 14-Jan-2021
    Currentness_Reference:
    ground condition; four survey days: reference mark data was collected on January 14 and 15, transect data on March 10, and ground control point data was collected on March 17, 2021.
  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 (122)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 19
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -69.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum of 1983 (National Spatial Reference System 2011).
      The ellipsoid used is GRS_1980.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    2021022FA_Marconi_nav_transects.csv and .shp has 122 data records and 2021022FA_Marconi_nav_AeroPoints.csv has 9 data records.
    Point positions and elevations, attributes are treated as if both CSV files are combined. (Source: U.S. Geological Survey)
    INFO
    USGS Field Activity Number (Source: USGS)
    ValueDefinition
    2021-022-FAUSGS year, ID, and Field Activity
    GPS_ID
    An identifier for the Spectra Precision equipment used to collect survey data, 3 is associated with SP80 receiver 0025. (Source: USGS)
    ValueDefinition
    999Null value
    Range of values
    Minimum:3
    Maximum:3
    Point_ID
    Unique point identification number, non-consecutive. (Source: USGS)
    Range of values
    Minimum:1
    Maximum:7020
    Attributes
    Non-unique identifier for the type of feature measured in the table array. (Source: USGS)
    ValueDefinition
    RM02_OPEN, RM01_CLOSE, RM02_OPEN, RM02_CLOSE, TRAN#, AERO###, ac########RM stands for Reference Mark with CLOSE and OPEN referring to the end or beginning of the survey (see 2021022FA_Marconi_ReferenceMark01.txt and 2021022FA_Marconi_ReferenceMark02.txt for OPUS values of the reference marks); TRAN #, where TRAN represents the transect and the # is a value between 1 and 7 referencing the 2021022FA_Marconi_Transects.shp; AERO### refers to an RTK surveyed AeroPoint and # is the last three digits printed on the AeroPoint; and ac######## refer to AeroPoint Global IDs, ac followed by a string of eight numbers and letters.
    Northing
    Feature location Y-Coordinate (NAD83(2011)/UTM Zone 19N) (Source: USGS)
    Range of values
    Minimum:420117.401
    Maximum:4638533.240
    Units:meters
    Easting
    Feature location X-Coordinate (NAD83(2011)/UTM Zone 19N) (Source: USGS)
    Range of values
    Minimum:419995.614
    Maximum:4638476.888
    Units:meters
    H_Ortho_m
    Feature orthometric Z-Coordinate (NAVD88) using GEOID 18 (Source: USGS)
    Range of values
    Minimum:-2.630
    Maximum:18.630
    Units:meters
    Latitude
    Feature location latitude (NAD83(2011)) (Source: USGS)
    Range of values
    Minimum:41.89117591
    Maximum:41.89469982
    Units:decimal degrees
    Longitude
    Feature location latitude (NAD83(2011)) (Source: USGS)
    Range of values
    Minimum:-69.96223257
    Maximum:-69.96438619
    Units:decimal degrees
    H_Ell_m
    Feature height above the (NAD83(2011) GRS80) ellipsoid (Source: USGS)
    ValueDefinition
    999Null value
    Range of values
    Minimum:-26.949
    Maximum:-24.545
    Units:meters
    Date
    Feature date (Source: USGS)
    Range of values
    Minimum:20210310
    Maximum:20210317
    Units:YYYYMMDD
    Time_EST
    Feature time of initiation in Eastern Standard Time (EST) (Source: USGS)
    Range of values
    Minimum:10:12:00
    Maximum:15:14:00
    Units:HH:MM:SS EST
    Xvar_mm
    Variance in the x-coordinate from post-processing (Source: USGS)
    ValueDefinition
    999Null value
    Range of values
    Minimum:0.0001
    Maximum:0.0160
    Units:meters
    Xvar_mm
    Variance in the y-coordinate from post-processing (Source: USGS)
    ValueDefinition
    999Null value
    Range of values
    Minimum:0.0002
    Maximum:0.0120
    Units:meters
    Xvar_mm
    Variance in the z-coordinate from post-processing (Source: USGS)
    ValueDefinition
    999Null value
    Range of values
    Minimum:0.0003
    Maximum:0.0180
    Units:meters
    2021022FA_Marconi_Transects.shp
    Shapefile polylines. (Source: U.S. Geological Survey)
    FID
    A unique, long integer to identify each record starting at 0. This ID is managed by ESRI software cannot be changed manually. (Source: ESRI)
    Range of values
    Minimum:0
    Maximum:6
    ID
    An identifier for the transect, corresponds to data ‘Attributes’ TRAN# in the 2021022FA_Marconi_nav_transects.csv (Source: USGS)
    Range of values
    Minimum:1
    Maximum:7
    Entity_and_Attribute_Overview:
    These attribute definitions describe each column of information in the CSV files with the exception of additional information in the last three columns of the 2021022FA_Marconi_nav_AeroPoints.csv. Those columns contain the X, Y, and Z variance, in mm, of the AeroPoint position. Null values (999) indicate the attribute was not calculated or applicable. The shapefile 2021022FA_Marconi_nav_transects.shp has the same attributes as the CSV. Trailing and leading zeros may not appear in the csv and so some values may not display as many significant digits as described. The shapefile 2021022FA_Marconi_Transects contains seven polylines.
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2021-022-FA

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Jin-Si Over
    U.S. Geological Survey
    U.S. Geological Survey
    Woods Hole, MA

    508-548-8700 x2269 (voice)
    jover@usgs.gov

Why was the data set created?

The reference marks can be used for QA/QC in future surveys and navigation and point data can be used to ground truth and georeference the digital elevation model in the larger work citation.

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: 19-Feb-2021 (process 1 of 4)
    Two reference marks were established in the Marconi Beach parking area using 1.5" survey nails. Locations were selected to maximize accessibility. Reference Mark 01 is established in pavement 50 cm in front of the "NO PARKING AT ANY TIME" sign in the northeast section of the parking lot (see 2021022FA_Marconi_PK_Nail_RM1_ParkingLot_ViewS.jpg). Reference Mark 02 is established in pavement on the road closest to the beach access, 20 cm SW from the curb and ~250 cm to the NW of the emergency call box (see 2021022FA_Marconi_PK_Nail_RM2_Road_ViewN.jpg). Each survey nail was occupied with a SP80 receiver (antenna SPP91564_2 None) attached to a tripod base station (antenna height = 1.982 m) set-up over the mark. Reference Mark 01 was occupied for 200 minutes. Reference Mark 02 was occupied for 162 minutes. The G-file’s taken from the SP80 after each occupation were converted to RINEX files using the Spectra Precision RINEX Converter (v. 4.7.1), and the .o files were then decimated using the teqc command ‘teqc -O.dec 30 filename.o’ to be uploaded to OPUS (https://geodesy.noaa.gov/OPUS/) using the Upload to Static option. The OPUS solutions are provided as ASCII text files with coordinates in NAD83(2011), UTM Zone 19N, and Massachusetts State Plane. Elevations are available in height above the NAD83(2011) ellipsoid and in NAVD88 using GEOID 18. Person who carried out this activity:
    Eric Marsjanik
    U.S Geological Survey
    Electronics Technician
    384 Woods Hole Rd
    Woods Hole, MA

    508-458-8700 x2216 (voice)
    emarsjanik@usgs.gov
    Date: 06-Mar-2020 (process 2 of 4)
    The RTK-GNSS data was collected and processed in the following manner: 1. A rover (SP90 Spectra receiver 0025 and controller #2 on a pole) was connected to the MASS CORS network through a portable hotspot. The height of the rover pole is 1.9820 m and was collecting RTK data in NAD83(2011) and NAVD88 Geoid 18. 2. The rover was then walked along the beach along seven shore perpendicular pre-determined transects (2021022FA_Marconi_Transects.shp) keeping at least 2 m on either side of the planned transect; points were taken at least every 1-2 meters along-track and at any noticeable change in slope. Points were also taken on top and at the center of the deployed AeroPoints on March 17. 3. The RTK data was exported as CSV files using SurvCE (http://survce.com/home). 4. Rover data was manually split into two CSV files. The first, 2021022FA_Marconi_nav_transects.csv contains all the data collected to ground truth the survey site; transects, bluff points, and the benchmark measurements. Points collected on the AeroPoints were put into 2021022FA_Marconi_nav_AeroPoints.csv. Person who carried out this activity:
    Jin-Si Over
    U.S Geological Survey
    Geographer
    384 Woods Hole Rd
    Woods Hole, MA

    508-458-8700 x2269 (voice)
    jover@usgs.gov
    Date: 06-Mar-2020 (process 3 of 4)
    The ground control points (AeroPoints) targets were processed with the following steps:
    1. Ten AeroPoints were deployed evenly spaced across the survey area and left on for a minimum of 3 hours to collect GNSS data. A SP80 rover was used to take their positions as a quality control check.
    2. Once connected to Wifi, the AeroPoint data is uploaded and is run through a post-processing kinematic algorithm. The data were exported with X,Y, and Z variances in the horizontal datum NAD83(2011) to produce latitude, longitude, and ellipsoid heights and then GEOID 18 was used to produce orthometric heights. These are exported to a CSV file named 2021022FA_Marconi_nav_AeroPoints.csv. See completeness report for more details. Person who carried out this activity:
    Peter Traykovski
    Woods Hole Oceanographic Institution
    Associate Professor
    226 Woods Hole Rd, #MS 12
    Woods Hole, MA

    508-289-2638 (voice)
    ptraykovski@whoi.edu
    Date: 13-May-2021 (process 4 of 4)
    The 2021022FA_Marconi_nav_transects.csv file was converted to a shapefile using ArcGIS 10.7.1, by right-clicking on the CSV in the catalog window and selecting using Create Feature Class - From XY data. The x-coordinate set to Easting, the y-coordinate set to Northing, and the z-coordinate to H_Ortho_m. The coordinate system of the input coordinates was set to the planar coordinate system NAD83(2011)/UTM Zone 19N and NAVD88. The CSV was saved as the shapefile 2021022FA_Marconi_nav_transects. The shapefile 2021022FA_Marconi_Transects is the shore-perpendicular transect lines that span the bluffs to the shoreline. Person who carried out this activity:
    Jin-Si Over
    U.S Geological Survey
    Geographer
    384 Woods Hole Rd
    Woods Hole, MA

    508-458-8700 x2269 (voice)
    jover@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?
    Positions and elevations are verified by external sources, ex: OPUS Solutions for the receivers, see Positional Accuracy section.
  2. How accurate are the geographic locations?
    OPUS Solution horizontal accuracy is 1 cm. Calculated RTK horizontal positions have an accuracy of +/- 3 centimeters. AeroPoint targets have theoretical 1 cm horizontal absolute accuracy.
  3. How accurate are the heights or depths?
    OPUS Solution vertical accuracy is 1 cm. Calculated RTK vertical positions have an accuracy of +/- 5 centimeters. AeroPoint targets have theoretical 1 cm vertical absolute accuracy.
  4. Where are the gaps in the data? What is missing?
    Points from the SP80 survey were edited for quality control and some points were removed due to obvious errors (such as lack of attribute label or recording point when receiver pole was off the ground), this can explain non-consecutive Point Labels. Two AeroPoint GPS survey targets were deployed but were unable to upload data, the location and elevation data for these were taken using the SP80 RTK equipment so these GCPs can be used in the structure-from-motion process but have a larger uncertainty. The AeroPoint with the Point_ID 632 had to be removed mid-survey due to a rising tide, therefore does not show up in any of the photos in the larger work citation and was removed from the CSV for a total of 9 usable ground control points. Users are advised to read the rest of the metadata record carefully for additional details. Bounding coordinates given above fit all collected data, but the transect shapefile exceeds them.
  5. How consistent are the relationships among the observations, including topology?
    The files contain USGS field activity 2021-022-FA navigation data: two OPUS solutions for reference marks established in January 2021, real-time kinematic satellite (RTK-GNSS) elevation data collected on foot along transects (provided) using a receiver (Spectra Precision SP80) connected to the Mass CORS network on March 10, and ground control points (AeroPoints) deployed on March 17 when the Helikite.

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. Although these data have been processed successfully on a computer system at the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Not for navigational use. Please recognize the U.S. Geological Survey (USGS) as the source of this information.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey
    Attn: Jin-Si Over
    Geographer
    384 Woods Hole Road
    Woods Hole, MA

    508-458-8700 x2269 (voice)
    jover@usgs.gov
  2. What's the catalog number I need to order this data set? 2021022FA_Marconi_navigation.zip contains the CSV files 2021022FA_Marconi_nav_transects.csv and 2021022FA_Marconi_nav_transects.shp. 2021022FA_Marconi_Transects.zip contains the associated shapfiles for the transects. The 2021022FA_Marconi_nav_AeroPoints.csv, and two txt files with the OPUS solutions for the Reference Marks are provided separately.
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    The user must have software capable of uncompressing the zip file and reading the data formats.

Who wrote the metadata?

Dates:
Last modified: 18-Mar-2024
Metadata author:
Jin-Si Over
U.S. Geological Survey
Geographer
U.S. Geological Survey
Woods Hole, MA

508-548-8700 x2269 (voice)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the person is no longer with USGS. (updated on 20240318)
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/field_activities/2021_022_fa/2021022FA_Marconi_Navigation.faq.html>
Generated by mp version 2.9.51 on Wed Apr 24 13:53:38 2024