Lidar point cloud, elevation models, GPS data, imagery, and orthomosaic, collected during UAS operations at Town Neck Beach, Sandwich, MA on October 8th, 2024

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

Frequently anticipated questions:

What does this data set describe?

Title:
Lidar point cloud, elevation models, GPS data, imagery, and orthomosaic, collected during UAS operations at Town Neck Beach, Sandwich, MA on October 8th, 2024
Abstract:
Small Uncrewed Aircraft Systems (sUAS) were used to collect aerial remote sensing data over Town Neck Beach, Massachusetts. The area is a highly trafficked public beach with a parking lot, boardwalk, and renourishment and dune stabilization plan. On October 15th, 2024, USGS personnel collected natural (RGB) color images, lidar, ground control points, check points, and a vegetation height dataset. These data were processed to produce a high-resolution lidar point cloud, digital elevation models, and a natural-color orthomosaic. The vegetation data can be used to validate the elevation models. Data are related to USGS Field activity 2024-018-FA and support observations of coastal change and lidar data testing.
Supplemental_Information:
For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/services/activity.php?fan=2024-018-FA. Images can be viewed or downloaded on the USGS Imagery Data System here https://cmgds.marine.usgs.gov/idsviewer/data_release/10.5066-P1UBZZFA in the collections 2024_TNB_Oct_YSMP and 2024_TNB_Oct_Vegetation. Note that the bounding coordinates are for the entire area and not individual files.
  1. How might this data set be cited?
    Over, Jin-Si R., and Cramer, Jennifer M., 20250430, Lidar point cloud, elevation models, GPS data, imagery, and orthomosaic, collected during UAS operations at Town Neck Beach, Sandwich, MA on October 8th, 2024: data release DOI:10.5066/P1UBZZFA, 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, Jin-Si R., Cramer, Jennifer M., Farris, Amy, and Sherwood, Christopher R., 2025, Topographic data, imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Town Neck Beach, Sandwich, Massachusetts: data release DOI:10.5066/P1UBZZFA, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Over, J.R., Cramer, J.M., Farris, A., and Sherwood, C.R., 2025, Topographic data, imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Town Neck Beach, Sandwich, Massachusetts: U.S. Geological Survey data release, https://doi.org/10.5066/P1UBZZFA.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.48819822
    East_Bounding_Coordinate: -70.47310383
    North_Bounding_Coordinate: 41.77198992
    South_Bounding_Coordinate: 41.76130878
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/67213f7fd34ed0f827eaaef3?name=2024018FA_TNB_Oct_data_browse.png&allowOpen=true (PNG)
    Data and products of Town Neck Beach: RGB image, lidar point cloud, ortho, and USGS personnel measuring vegetation.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 08-Oct-2024
    Currentness_Reference:
    Ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: point cloud, raster, and tabular digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
    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 0.001
      Ordinates (y-coordinates) are specified to the nearest 0.001
      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.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      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?
    2024018FA_TNB_Oct_YSMP_ImageLocations.csv
    The CSV file contains the approximate position of the YSMP images at the moment of each capture based on post-processed UAS integrated GPS. (Source: producer defined)
    ImageName
    File names of individual images, see the Process Description for file naming convention. (Source: USGS) Character string.
    GPSDateTime
    Date and UTC time in YYYY:MM:DD HH:MM:ss. (Source: Processor defined) Character string.
    Latitude NAD83[2011]
    Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. (Source: USGS)
    Range of values
    Minimum:41.76128859
    Maximum:41.77137234
    Units:decimal degrees
    Longitude NAD83[2011]
    Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. (Source: USGS)
    Range of values
    Minimum:-70.48754404
    Maximum:-70.47247453
    Units:decimal degrees
    Ellipsoid height GRS80
    Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:29.896
    Maximum:38.600
    Units:meters
    Easting 19N
    Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:376361.238
    Maximum:377599.110
    Units:meters
    Northing 19N
    Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4624322.352
    Maximum:4625460.397
    Units:meters
    Altitude NAVD88
    Altitude of the camera at the time of each image capture relative to NAVD88 with GEOID 18 applied. (Source: None)
    Range of values
    Minimum:58.091
    Maximum:66.796
    Units:meters
    2024018FA_TNB_Oct_AeroPoints.csv
    Ground control point positions, elevations, and attributes (Source: USGS)
    FAN
    USGS Field Activity Number (Source: USGS)
    ValueDefinition
    2024-018-FAYear, USGS ID, and Field Activity
    Date
    Calendar date of collection (Source: USGS)
    ValueDefinition
    20241008YYYYMMDD
    Point ID
    Unique point identification number. (Source: Processor defined)
    Range of values
    Minimum:1
    Maximum:7
    Attributes
    Unique identifier for ground control points. Prefix AP-### refers to AeroPoint and the last 3 digits of its identifying code. (Source: producer defined) Character string.
    Latitude NAD83[2011]
    Post-processed latitude of AeroPoint position (NAD83[2011]). (Source: USGS)
    Range of values
    Minimum:41.76403925
    Maximum:41.76851584
    Units:decimal degrees
    Longitude NAD83[2011]
    Post-processed longitude of AeroPoint position (NAD83[2011]). (Source: None)
    Range of values
    Minimum:-70.48498393
    Maximum:-70.47816245
    Units:decimal degrees
    Ellipsoid height GRS80
    Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:-27.566
    Maximum:-23.406
    Units:meters
    Easting 19N
    Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:376570.865
    Maximum:377129.325
    Units:meters
    Northing 19N
    Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4624634.122
    Maximum:4625140.920
    Units:meters
    Orthometric height NAVD88
    Post-processed Z-coordinate of AeroPoint using NAVD88 with Geoid 18 applied. (Source: USGS)
    Range of values
    Minimum:0.618
    Maximum:4.776
    Units:meters
    Xvar mm
    Internal variance in the X-coordinate from post-processing. (Source: producer defined)
    Range of values
    Minimum:0.8
    Maximum:5.2
    Units:millimeters
    Yvar mm
    Internal variance in the Y-coordinate from post-processing. (Source: producer defined)
    Range of values
    Minimum:0.8
    Maximum:8.8
    Units:millimeters
    Zvar mm
    Internal variance in the Z-coordinate from post-processing. No data value is NaN. (Source: producer defined)
    Range of values
    Minimum:2.0
    Maximum:7.7
    Units:millimeters
    Baseline distance km
    Distance to from the AeroPoint to the correcting base. (Source: producer defined)
    Range of values
    Minimum:0.09
    Maximum:11.41
    Units:kilometers
    2024018FA_TNB_Oct_GPS_Emlid_RS3.csv
    GPS Emlid_RS3 check point positions, elevations, attributes, and associated vegetation photo name and heights. (Source: USGS)
    FAN
    USGS Field Activity Number (Source: USGS)
    ValueDefinition
    2024-018-FAYear, USGS ID, and Field Activity
    Date
    Calendar date of collection (Source: USGS)
    ValueDefinition
    20241008YYYYMMDD
    Point ID
    Non-consecutive unique point identification number. Points 1-53 are GCP and ground check points. Points 100-103 are reference mark check points. (Source: Processor defined)
    Range of values
    Minimum:1
    Maximum:102
    Attributes
    Identifies check point type. This includes descriptors for a variety of ground control points; BP# is Big Plywood, AP-### is AeroPoint, folding table, and lidar target; check points associated with vegetation measurements; and survey open and close measurements on Town Neck Beach Big Belly (TNB-BB) reference mark. (Source: producer defined) Character string.
    Associated Photo
    Image name, if taken, associated with each Point ID. GPS points without a photo have a NaN for no-data. (Source: producer defined) Character string.
    Average veg height (cm)
    Approximate average vegetation height next to the GPS pole in the associated photo. GPS points without a photo and vegetation height have a NaN for no-data. (Source: USGS)
    Range of values
    Minimum:25
    Maximum:155
    Units:centimeters
    Latitude NAD83[2011]
    Real-time Kinematic latitude of GPS point (NAD83[2011]). (Source: USGS)
    Range of values
    Minimum:41.76403916
    Maximum:41.76851580
    Units:decimal degrees
    Longitude NAD83[2011]
    Real-time Kinematic longitude of GPS point (NAD83[2011]). (Source: None)
    Range of values
    Minimum:-70.48498380
    Maximum:-70.47816260
    Units:decimal degrees
    Ellipsoid height GRS80
    Real-time Kinematic vertical position of GPS point in relation to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:-27.592
    Maximum:-21.383
    Units:meters
    Easting 19N
    Real-time kinematic X-coordinate of GPS point in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:376570.876
    Maximum:377129.313
    Units:meters
    Northing 19N
    Real-time kinematic Y-coordinate of GPS point in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4624634.112
    Maximum:4625140.915
    Units:meters
    Orthometric height NAVD88
    Real-time kinematic Z-coordinate of GPS point relative to NAVD88 with GEOID 18 applied. (Source: USGS)
    Range of values
    Minimum:0.593
    Maximum:6.807
    Units:meters
    Tilt angle
    The degree of tilt of the GPS Emlid RS3 receiver to nadir. Positions can maintain 2 cm accuracy up to a tilt of 60 degrees. (Source: USGS)
    Range of values
    Minimum:0.0
    Maximum:24.6
    Units:degrees
    H RMS
    Horizontal root mean square error, provides the horizontal precision of the position solution. (Source: producer defined)
    Range of values
    Minimum:0.007
    Maximum:0.030
    Units:meters
    V RMS
    Vertical root mean square error, provides the vertical precision of the position solution. (Source: producer defined)
    Range of values
    Minimum:0.007
    Maximum:0.030
    Units:meters
    2024018FA_TNB_Oct_YSMP_full_LPC.laz
    YSMP lidar point cloud in .laz file format from flight one. This georeferenced point cloud was colorized using the natural color RGB orthomosaic and is not classified. Total point count is 70,744,361. The point density is 194.22 points per square meter, and point spacing is 0.072 m. (Source: producer defined)
    Elevation
    Surface elevation orthometric height NAVD88 (m) using GEOID 18 in NAD83(2011)/UTM Zone 19N. (Source: YellowScan CloudStation)
    Range of values
    Minimum:-1.504
    Maximum:15.352
    Units:meters
    Intensity
    Lidar intensity is recorded as the return strength of a laser beam during data collection. (Source: YellowScan CloudStation)
    Range of values
    Minimum:0
    Maximum:65,025
    Units:none (scaled to 16-bit integer)
    2024018FA_TNB_Oct_YSMP_central_LPC.laz
    YSMP lidar point cloud in .laz file format from flight two. This georeferenced point cloud was colorized using the natural color RGB orthomosaic and is not classified. Total point count is 40,227,769. The point density is 402.83 points per square meter, and point spacing is 0.050 m. (Source: producer defined)
    Elevation
    Surface elevation orthometric height NAVD88 (m) using Geoid 18 in NAD83(2011)/UTM Zone 19N. (Source: YellowScan CloudStation)
    Range of values
    Minimum:-2.006
    Maximum:15.268
    Units:meters
    Intensity
    Lidar intensity is recorded as the return strength of a laser beam during data collection. (Source: YellowScan CloudStation)
    Range of values
    Minimum:0
    Maximum:65,025
    2024018FA_TNB_Oct_YSMP_full_DSM_25cm.tif
    A cloud-optimized digital surface model gridded from the flight one lidar point cloud with encoded elevation values. Pixel resolution is 25 cm. (Source: USGS)
    Value
    Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 19N. (Source: producer defined)
    Range of values
    Minimum:-1.373
    Maximum:15.285
    Units:meters
    2024018FA_TNB_Oct_YSMP_central_DSM_25cm.tif
    A cloud-optimized digital surface model gridded from the flight two lidar point cloud with encoded elevation values. Pixel resolution is 25 cm. (Source: USGS)
    Value
    Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 19N. (Source: producer defined)
    Range of values
    Minimum:-0.953
    Maximum:15.268
    Units:meters
    2024018FA_TNB_Oct_YSMP_SfM_DSM_25cm.tif
    A cloud-optimized SfM digital surface model made from the lidar point cloud images. Pixel resolution is 25 cm. (Source: USGS)
    Value
    Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 19N. (Source: producer defined)
    Range of values
    Minimum:-4.657
    Maximum:14.395
    Units:meters
    2024018FA_TNB_Oct_YSMP_SfM_Ortho_5cm.tif
    True-color (RGB) cloud optimized orthomosaic made from the YSMP images. (Source: USGS)
    Band_1
    Red wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Band_2
    Green wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Band_3
    Blue wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Entity_and_Attribute_Overview:
    The filenames are formatted as "2024018FA_TNB_Oct_sensor/product_ resolution.*** ", where 2024018 is the USGS Field activity ID, location is Town Neck Beach (TNB); sensors include YellowScan Mapper Plus (YSMP), GPS_Emlid_RS3, and AeroPoints; products include structure from motion (SfM) orthomosaics (ortho), digital surface models (DSM), and lidar point cloud (LPC). The horizontal coordinate reference system for all products is NAD83(2011)/UTM19N, the vertical coordinate reference system (VCRS) is NAVD88 using Geoid 18.
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2024-018-FA

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Jin-Si R. Over
    • Jennifer M. Cramer
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Jin-Si R. Over
    U.S. Geological Survey, Northeast Region, Woods Hole Coastal and Marine Science Center
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA

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

Why was the data set created?

The imagery and lidar products were produced to help monitor the movement of sand placed on the beach by the US Army Corps of Engineers in the fall of 2023. These data will also be used to test the ability of the lidar data to penetrate both newly planted dune grass as well as more mature vegetation compared to structure from motion products. The data will also be used to measure the seasonal variability of beach slope and shoreline position.

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: 08-Oct-2024 (process 1 of 7)
    GPS DATA: A GPS rover (Emlid RS3) was set up as a base station in the parking lot to collect Global Navigation Satellite System (GNSS) data to correct the lidar data. A second Emlid RS3 was set up as a rover connected to the Massachusetts Continuously Operating Reference Station (CORS) network and used to take check shots across the study site. At vegetation check points an additional photo was taken with a smart phone and the average height of the vegetation next to the rover pole was recorded. The check points, associated image name, and attributes are provided in 2024018FA_TNB_Oct_GPS_Emlid_RS3.csv. GROUND CONTROL: A variety of test GCPs were placed in the parking lot including two reflective raised circle targets, two big plywood black and white squares, and a folding table on edge. These were surveyed with the GPS rover. Seven AeroPoint GCPs were also spaced out over the field site and left on for at least two hours to collect GNSS data. These were also surveyed at the center with the GPS rover. After collection and connected to Wi-Fi, the AeroPoint data were uploaded and run through a post-processing kinematic algorithm of the CORS network to get a global accuracy. The data were exported with xyz internal variances in the horizontal datum NAD83(2011) to produce latitude, longitude, and ellipsoid heights, and then UTM19N and NAVD88 using GEOID 18 was used to produce easting, northing, and orthometric heights. These were exported to a CSV file and named 2024018FA_TNB_Oct_AeroPoints.csv. Step completed by C. Sherwood, A. Farris, J. Cramer, and J. Over.
    Date: 08-Oct-2024 (process 2 of 7)
    UAS FLIGHTS: The lidar sensor was a 905 nm wavelength Livox Avia with a 70.4/ 4.5 degree horizontal and vertical field of view (FOV). The lidar scanner was set to the repetitive scan pattern, which moves the sensor in a back-and-forth motion and is optimal for non-vegetated areas. The camera module was a SONY UMC - 10RC, a 20.4 megapixel (MP). The system also consists of a Trimble AV18 GNSS antenna mounted to the top of the UAS and connected to the lidar system via GNSS cable. The lidar data was saved to a 256 GB USB thumb drive in three different files: (1) the IMU+GPS data, decimated for quick post-processing, in binary *.ys format, (2) the scanner data in *.lvx format (~600 MB per minute of data collection), (3) and the complete IMU+GPS data in Applanix (Trimble) binary *.t04 format. The RGB images were saved to a 64 GB micro SD card as *.jpg files. A configuration text file (CONFIG.TXT) was pre-loaded onto the USB thumb drive and can be edited to control lidar and camera module settings, including the camera triggering height, the camera triggering interval, and the lidar scan pattern. The YSMP was attached to a DJI Matrice 600 Pro UAS with approved government edition firmware. The YSMP lidar data were collected over two flights. The first flight covered the entire area with the UAS flying at 10 m/s at ~61 meters above ground level at a transect spacing of 50 m for 21 minutes of flight time. The second flight covered just the central vegetated area with the UAS flying at 6.25 m/s at ~61 meters above ground level at a transect spacing of 30 m for 9 minutes of flight time. The SONY camera triggered every 4 seconds. After each flight the lidar data and images were taken off the sensor. Note, the geotagged positions embedded in the Exif information are WGS84 and ellipsoid height, this is how the data are collected. The positions have been converted to NAD83(2011) and NAVD88 GEOID 18 in the imagery locations file (2024018FA_TNB_Oct_YSMP_ImageryLocations.csv). Step completed by J. Cramer and J. Over.
    Date: 16-Dec-2024 (process 3 of 7)
    RAW IMAGERY: YSMP images and ground truthing images were processed to add additional information required by the USGS to the EXIF headers using ExifTools (https://exiftool.org/, version: 12.06), and the files were renamed to a unique identifier using Namexif (http://www.digicamsoft.com/softnamexif.html, version 2.1) to avoid any possibility of duplicate names. These steps are described here. 1. ExifTools was used to tag each photos headers following the Imagery Data System EXIF Guidance. Attributes (e.g. Credit, Copyright, UsageTerms, ImageDescription, Artist, etc) were stored in a *.csv file and written to each image with the command:' exiftool -csv="C:\directory\name\EXIF.csv" C:\directory\name\of\photos *.JPG ' To read out the photo information to a csv when in the directory with the photos the command is: exiftool -csv *.JPG > directory/name/allheaders_out.csv 2. All the UAS images were renamed with Namexif (https://us.digicamsoft.com/softnamexif.html v 2.2 accessed October 2020) to ensure unique filenames and compliance with the USGS Coastal and Marine Hazards and Resources Program's best practices for image naming convention. Images were renamed with the field survey ID prefix; flight number, and ID that distinguishes USGS cameras by make/camera number, the image acquisition date, coordinated universal time (UTC) in ISO8601 format, and a suffix with the original image name. For example, image name '2024018FA_f01r03_20241008T165822Z_DSC#', 2024018FA is the field activity ID, f01 is the flight number, r03 is the camera, 20241008 is the UTC date in the format YYYYMMDD, and a 'T' is used to separate UTC date from UTC time in format HHMMSS followed by a Z. The DSC# is the original raw photo name appended to the end of the new filename. Vegetation photos were renamed to '2024018FA_Oct_TNB_GPS_PointID_#_veg' to denote which GPS point the photo is associated with in file 2024018FA_Oct_TNB_GPS_Emlid_RS3.csv. Step completed by J. Over.
    Date: 06-Dec-2024 (process 4 of 7)
    PHOTOGRAMMETRY: The SfM products were created in Agisoft Metashape v. 2.0.1 using the following general steps (see Over and others, 2021 for a more detailed methodology explanation): 1. A project was created in Metashape and YSMP imagery from both flights were imported. 2. Photos were aligned at a low accuracy and then GCPs were automatically detected in the point cloud. GCP positions (2024018FA_TNB_Oct_AeroPoints.csv) were added to the project in the reference systems NAD83(2011)/UTM Zone 19N and NAVD88 (GEOID 18). The horizontal and vertical accuracies for the GCPs were set to 0.04/0.02 m, respectively, and the camera positions for the images were turned off. The photos were then re-aligned with high accuracy (the pixels were not subsampled) using a keypoint limit of 60,000 and unlimited tie points. 3. The alignment process matched pixels between images to create point clouds and put the imagery into a relative spatial context using the GCPs. The resultant point clouds were filtered using one iteration of the 'Reconstruction uncertainty' filter at a level of 10, one iteration of the 'Projection accuracy' filter at a level of 3, and eight iterations of the 'Reprojection accuracy' filter to get to a level of 0.3. With each filter, iteration points are selected, deleted, and then the camera model was optimized to refine the focal length, cx, cy, k1, k2, k3, p1, and p2 camera model coefficients. 4. At this point, multiple ‘chunks’ were created so that a high-quality dense cloud with a low-frequency filtering algorithm could be made from the images. The dense point cloud was then edited by visual inspection and Metashape’s confidence filter to remove points with a low confidence near the edges and near water bodies. 5. A DSM is built from the dense point cloud and then an orthomosaic is built from the DSM with refined seamlines. The DSM (2024018FA_TNB_Oct_YSMP_SfM_DSM_25cm.tif) and orthomosaic (2024018FA_TNB_Oct_YSMP_SfM_Ortho_5cm.tif) are exported in EPSG:6348 NAD83(2011)/UTM19N, the DSM has a vertical reference system in EPSG:5703 NAVD88 (GEOID 18). Step completed by J. Over.
    Date: 02-Nov-2024 (process 5 of 7)
    LIDAR DATA: The YSMP lidar data were processed in YellowScan CloudStation software integrated with Trimble POSPac UAV 9.0. Base station GNSS data were downloaded from the Emlid_RS3 collecting data on site for the time the UAS was flying. For each flight, the raw scanner data (.ys file) was imported into YellowScan CloudStation, the sensor lidar (.profile) and Camera (.camera) profiles, provided by the vendor, were selected for the project and the project coordinate reference system is set. CloudStation flight trajectories are adjusted manually to select the desired data to be processed. The .T04 file and base station GNSS RINEX file were used to correct and optimize the sensor position trajectories using the GNSS Inertial Processor and produce a Smoothed Best Estimate of Trajectory (SBET) file in .txt ASCII format, which represents the Post Processing Kinematic (PPK) Solution. The lever arm offsets and boresight angle corrections were applied to the Lidar Point Cloud (LPC), along with a strip adjustment between transect swaths using CloudStation's "robust" setting. The LPC was then colorized using the images. The Cut Overlap function was applied to remove redundant points based on the closest parallel flight trajectory. The unclassified LPC model was then exported from CloudStation as a 1.4 *.laz file. The LPCs were brought into Global Mapper (v. 26.0) and manually cleaned of points interpreted to be noise or are above a reasonable elevation threshold based on the surrounding features. Then, the LPCs were adjusted to the GCPs using a planar fit and exported as 2024018FA_TNB_Oct_YSMP_central_LPC.laz and 2024018FA_TNB_Oct_YSMP_full_LPC.laz. The LPCs are then gridded using maximum values and exported (2024018FA_TNB_Oct_YSMP_central_DSM_25cm.tif and 2024018FA_TNB_Oct_YSMP_full_DSM_25cm.tif). All files were exported in EPSG:6348 NAD83(2011)/UTM zone 19N and the vertical datum in EPSG:5703 NAVD88 using GEOID 18. Step completed by J. Over.
    Date: 06-Dec-2024 (process 6 of 7)
    CLOUD OPTIMIZATION: All GeoTIFF products were DEFLATE compressed and turned into a cloud-optimized GeoTIFFs (COG) using gdal_translate with the following command: for %i in (.\*.tif) do gdal_translate %i .\cog\%~ni_cog.tif -of COG -stats -co BLOCKSIZE=256 -co COMPRESS=DEFLATE -co PREDICTOR=YES -co NUM_THREADS=ALL_CPUS -co BIGTIFF=YES (v. 3.1.4 accessed October 20, 2020 https://gdal.org/). Where i is the name of each GeoTIFF section. Step completed by J. Over.
    Date: 06-Jun-2025 (process 7 of 7)
    Additional clarification was added to the completeness report explaining the apparent truncation of the SfM orthomosaic (2024018FA_TNB_Oct_YSMP_SfM_Ortho_5cm.tif) and extent of the SfM DSM (2024018FA_TNB_Oct_YSMP_SfM_DSM_25cm.tif). Step completed by J. Over. (20250508). XML structure error fixed by VeeAnn Cross (20250606) Person who carried out this activity:
    Jin-Si R. Over
    U.S. Geological Survey, Woods Hole Coastal and Marine Science Center
    Geographer
    U.S. Geological Survey
    Woods Hole, MA

    508-548-8700 x2297 (voice)
    jover@usgs.gov
  3. What similar or related data should the user be aware of?
    Over, Jin-Si R., Ritchie, Andrew C., Kranenburg, Christine J., Brown, Jenna A., Buscombe, Daniel D., Noble, Tom, Sherwood, Christopher R., Warrick, Jonathan A., and Wernette, Phillipe A., 2021, Processing coastal imagery with Agisoft Metashape Professional Edition, version 1.6-Structure from motion workflow documentation: Open-File Report 2021-1039, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    This publication includes the general methodology for processing imagery in Metashape to produce digital surface models and ortho products.

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

  1. How well have the observations been checked?
    The horizontal and vertical accuracy of the elevation products (2024018FA_TNB_Oct_YSMP_full_LPC.laz, 2024018FA_TNB_Oct_YSMP_central_LPC.laz 2024018FA_TNB_Oct_YSMP_full_DSM_25cm.tif, 2024018FA_TNB_Oct_YSMP_central_DSM_25cm.tif, 2024018FA_TNB_Oct_YSMP_SfM_DSM_25cm.tif, and 2024018FA_TNB_Oct_YSMP_SfM_Ortho_5cm.tif) were assessed using the ground control points (GCPs; 2024018FA_TNB_Oct_AeroPoints.csv). It should also be noted that accuracy estimates of the products are for areas of bare ground or low vegetation where GCPs were placed, vertical errors are tied to horizontal errors, especially near places with a quick elevation change. Additional sources of error, such as moving objects or poor overlap near the edges of the survey and away from GCPs may cause accuracy estimates to exceed estimates in localized portions of the products.
    Lidar flight paths are corrected using a base station. During the processing of flight one it became clear that part of the IMU was interrupted or corrupted, which prevented the Trimble GNSS Inertial Processer from working and generating a SBET file (see processing steps). This may have been a one-off glitch of the sensor or interference from a solar storm. The resulting lidar point cloud was otherwise processed as normal and is still useable. Note that any lidar returns over water reflect the surface, not the bottom, while the structure from motion (SfM) digital surface model (DSM) does reconstruct a surface below the water.
    GPS point accuracy is assessed based on occupations of a known reference mark and GPS point precision is based on a positioning solution of “FIX” for each point.
  2. How accurate are the geographic locations?
    The GCPs and GPS points have a horizontal accuracy of 2 cm. The LPCs, and by association the lidar derived DSMs, horizontal accuracy was assessed against the central positions of the AeroPoints as seen from the intensity of the LPC and the GPS point of the AeroPoint center. The horizontal accuracy is variable; the full LPC that did not have an SBET is off on average by 1.08 m, and the central LPC is off on average by 20 cm from the known position. It is recommended that users do their own assessment for their own needs. The SfM products were spatially georeferenced using AeroPoints and created using Agisoft Metashape. The horizontal root mean square error (RMSE) of the GCPs (n=7) as reported from the Metashape project are x/y 0.050/0.050 m.
  3. How accurate are the heights or depths?
    The GCPs and GPS points have a vertical accuracy of 3 cm. The LPCs and by association the lidar derived DSMs, were assessed against the USGS 3DEP (https://www.usgs.gov/3d-elevation-program) surface in the parking lot and values fall within 15 cm. As the LPCs were fit to the GCPs (see processing steps) they have a more consistent vertical alignment where the GCPs were placed in the dune and beach area (~5 cm) but may differ up to a meter away from the GCPs. The SfM DSM vertical RMSE as reported from the Metashape project GCPs (n=7) is 0.044 m. Users should take care to check where the DSMs diverge away from the GCPs.
  4. Where are the gaps in the data? What is missing?
    Imagery: UAS images at take-off and landing were removed and two transects of images of just water were also removed. All of these removed images can account for the non-consecutive original file names and results in a total of 375 UAS images. A list of the UAS images and their locations are available in 2024018FA_TNB_Oct_YSMP_ImageLocations.csv. Additional images of vegetation heights on the ground were collected with each GPS vegetation point; the data and associated image names are provided in 2024018FA_TNB_Oct_GPS_Emlid_RS3.csv. Vegetation photos were tagged with the latitude and longitude of the GPS point they are associated with. Lidar: Points were removed from the LPCs in the water where they were sparse. Points identified as flying birds were also removed. LPCs are not classified. Products: GeoTIFF products are cloud-optimized and deflate compressed. Structure from Motion products (2024018FA_TNB_Oct_YSMP_SfM_DSM_25cm.tif and 2024018FA_TNB_Oct_YSMP_SfM_Ortho_5cm.tif) are cropped past the inlet because of the lack of ground control and poor overlap of images in this region. Rectangular gaps in the orthomosaic and DSM are due to poor image overlap.
  5. How consistent are the relationships among the observations, including topology?
    There were two (full and central) UAS M600 flights that used the YellowScan Mapper+ (YSMP) to collect lidar data and images and produced the lidar point clouds (LPC) and gridded DSMs. The images taken by the YSMP were also used to create a SfM DSM and orthomosaic. Seven AeroPoints, two reflective elevated targets, and two plywood GCPs were placed. A Emlid RS3 GPS rover was used to take 53 vegetation and ground check points with associated smart-phone photos. Smartphone images were geotagged with the GPS point position associated with it. All data fall into expected elevation ranges of a low-lying beach and dune system.

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 (CC0-1.0) data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey (USGS) as the source of this information. These data are not intended for navigational use.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? Aerial imaging and mapping of Town Neck Beach includes a lidar point cloud, elevation models, imagery and true-color orthomosaic, and ground control and check points.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by 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. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Not for navigational use.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 06-Jun-2025
Metadata author:
Jin-Si R. Over
U.S. Geological Survey, Northeast Region
Geographer
U.S. Geological Survey
Woods Hole, MA

508-548-8700 x2297 (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.
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P1UBZZFA/2024018FA_TNB_Oct_meta.faq.html>
Generated by mp version 2.9.51 on Wed Jun 11 14:23:35 2025