Metadata: Identification_Information: Citation: Citation_Information: Originator: Jin-Si R. Over Originator: Jennifer M. Cramer Publication_Date: 2025 Title: Lidar point cloud, elevation models, GPS data, imagery, and orthomosaic, collected during UAS operations at Town Neck Beach, Sandwich, MA on April 15th, 2024 Edition: 1.0 Geospatial_Data_Presentation_Form: point cloud, raster, and tabular digital data Series_Information: Series_Name: data release Issue_Identification: DOI:10.5066/P1UBZZFA Publication_Information: Publication_Place: Woods Hole Coastal and Marine Science Center, Woods Hole, MA Publisher: U.S. Geological Survey, Coastal and Marine Hazards and Resources Program Online_Linkage: https://doi.org/10.5066/P1UBZZFA Online_Linkage: https://www.sciencebase.gov/catalog/item/67213f45d34ed0f827eaaef0 Larger_Work_Citation: Citation_Information: Originator: Jin-Si R. Over Originator: Jennifer M. Cramer Originator: Amy Farris Originator: Christopher R. Sherwood Publication_Date: 2025 Title: Topographic data, imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Town Neck Beach, Sandwich, Massachusetts Edition: 1.0 Geospatial_Data_Presentation_Form: digital data Series_Information: Series_Name: data release Issue_Identification: DOI:10.5066/P1UBZZFA Publication_Information: Publication_Place: Reston, VA Publisher: U.S. Geological Survey 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. Online_Linkage: https://doi.org/10.5066/P1UBZZFA Online_Linkage: https://www.sciencebase.gov/catalog/item/67213855d34ed0f827eaae83 Description: 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 April 15th, 2024, USGS personnel collected natural (RGB) color images, lidar, check points, and ground control points. These data were processed to produce a high-resolution lidar point cloud, digital elevation models, and a natural-color orthomosaic. Data are related to USGS Field activity 2024-018-FA and support observations of coastal change and lidar data testing. Purpose: 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. 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 collection 2024_TNB_Apr_YSMP. Note that the bounding coordinates are for the entire area and not individual files. Time_Period_of_Content: Time_Period_Information: Single_Date/Time: Calendar_Date: 20240415 Currentness_Reference: Ground condition Status: Progress: Complete Maintenance_and_Update_Frequency: Not planned Spatial_Domain: Bounding_Coordinates: West_Bounding_Coordinate: -70.48819822 East_Bounding_Coordinate: -70.47310383 North_Bounding_Coordinate: 41.77198992 South_Bounding_Coordinate: 41.76130878 Keywords: Theme: Theme_Keyword_Thesaurus: None Theme_Keyword: U.S. Geological Survey Theme_Keyword: USGS Theme_Keyword: Coastal and Marine Hazards and Resources Program Theme_Keyword: CMHRP Theme_Keyword: Woods Hole Coastal and Marine Science Center Theme_Keyword: WHCMSC Theme_Keyword: YellowScan Mapper Plus Theme_Keyword: DJI Matrice 600 Theme_Keyword: Point Cloud Theme_Keyword: UAS Theme_Keyword: AeroPoints Theme_Keyword: digital surface model Theme_Keyword: orthomosaics Theme_Keyword: Aerial Imaging and Mapping Group Theme: Theme_Keyword_Thesaurus: USGS Thesaurus Theme_Keyword: remote sensing Theme_Keyword: digital elevation models Theme_Keyword: structure from motion Theme_Keyword: image mosaics Theme_Keyword: geospatial datasets Theme_Keyword: image collections Theme: Theme_Keyword_Thesaurus: Data Categories for Marine Planning Theme_Keyword: Physical Habitats and Geomorphology Theme: Theme_Keyword_Thesaurus: ISO 19115 Topic Category Theme_Keyword: geoscientificInformation Theme_Keyword: elevation Theme: Theme_Keyword_Thesaurus: USGS Metadata Identifier Theme_Keyword: USGS:67213f45d34ed0f827eaaef0 Place: Place_Keyword_Thesaurus: Geographic Names Information System (GNIS) Place_Keyword: Atlantic Ocean Place_Keyword: Commonwealth of Massachusetts Place_Keyword: Sandwich (616643) Place_Keyword: Town Beach (616661) Place_Keyword: Town Neck (616663) 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. Point_of_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jin-Si R. Over Contact_Organization: U.S. Geological Survey, Northeast Region, Woods Hole Coastal and Marine Science Center Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical address Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2297 Contact_Electronic_Mail_Address: jover@usgs.gov Browse_Graphic: Browse_Graphic_File_Name: https://www.sciencebase.gov/catalog/file/get/67213f45d34ed0f827eaaef0?name=2024018FA_TNB_Apr_data_browse.png&allowOpen=true Browse_Graphic_File_Description: Data and products of Town Neck Beach: RGB image, lidar point cloud, ortho, and USGS personnel. Browse_Graphic_File_Type: PNG Native_Data_Set_Environment: Agisoft Metashape Pro v. 2.0.1, Emlid Studio v. 1.8, Trimble PosPac UAV v. 9.0, YellowScan CloudStation v. 2405.0.0, Global Mapper Pro v. 26.0 Cross_Reference: Citation_Information: Originator: Jin-Si R. Over Originator: Andrew C. Ritchie Originator: Christine J. Kranenburg Originator: Jenna A. Brown Originator: Daniel D. Buscombe Originator: Tom Noble Originator: Christopher R. Sherwood Originator: Jonathan A. Warrick Originator: Phillipe A. Wernette Publication_Date: 2021 Title: Processing coastal imagery with Agisoft Metashape Professional Edition, version 1.6-Structure from motion workflow documentation Series_Information: Series_Name: Open-File Report Issue_Identification: 2021-1039 Publication_Information: Publication_Place: Reston, VA Publisher: U.S. Geological Survey Other_Citation_Details: This publication includes the general methodology for processing imagery in Metashape to produce digital surface models and ortho products. Online_Linkage: https://doi.org/10.3133/ofr20211039 Data_Quality_Information: Attribute_Accuracy: Attribute_Accuracy_Report: The horizontal and vertical accuracy of the elevation products (2024018FA_TNB_Apr_YSMP_LPC.laz, 2024018FA_TNB_Apr_YSMP_DSM_25cm.tif, 2024018FA_TNB_Apr_YSMP_SfM_DSM_25cm.tif, and 2024018FA_TNB_Apr_YSMP_SfM_Ortho_5cm.tif) were assessed using the ground control points (GCPs; 2024018FA_TNB_Apr_AeroPoints.csv) and GPS check points (2024018FA_TNB_Apr_GPS_SP80.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 or GPS points taken, vertical errors are tied to horizontal errors, especially near places such as a scarp. 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. 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. Logical_Consistency_Report: There were two UAS M600 flights that used the YellowScan Mapper+ (YSMP) to collect lidar data and images and produced the lidar point cloud (LPC) and gridded DSM. The images taken by the YSMP were also used to create a SfM DSM and orthomosaic. Ten AeroPoints were placed, but only six were properly turned on. A SP80 GPS rover was used to take 77 ground check points. All data fall into expected elevation ranges of a low-lying beach and dune system. Completeness_Report: Imagery: Images at take-off and landing were removed. All of these removed images can account for the non-consecutive original file names and results in a total of 688 images. A list of the images and their locations are available in 2024018FA_TNB_Apr_ImageLocations.csv. Lidar: Points were removed from the LPC in the water where they were sparse. Points identified as flying birds were also removed. LPC is not classified. Products: GeoTIFF products are cloud-optimized and deflate compressed. GPS: Four AeroPoints did not collect data but show up in the imagery. This causes the SfM products to have a lower positional accuracy than expected due to the poor spatial distribution of the working GCPs. Positional_Accuracy: Horizontal_Positional_Accuracy: Horizontal_Positional_Accuracy_Report: The GCPs and GPS points have a horizontal accuracy of 4 cm. The LPC, and by association the lidar derived DSM, horizontal accuracy was assessed against positions of the AeroPoints. The horizontal accuracy is variable; based on intensity the AeroPoint centers are on average 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=6) as reported from the Metashape project are x/y 0.054/0.091 m. Vertical_Positional_Accuracy: Vertical_Positional_Accuracy_Report: The GCPs and GPS points have a vertical accuracy of 2 cm. The LPC and by association the lidar derived DSM, was assessed against the USGS 3DEP (https://www.usgs.gov/3d-elevation-program) surface in the parking lot and values fall within 10 cm. The LPC was also assessed against the elevations of the AeroPoints and GPS points, and the RMSE (n=83) was 0.113 m. The SfM DSM vertical RMSE as reported from the Metashape project GCPs (n=6) is 0.060 m. The vertical RMSE compared to the GPS check points (n=83) = 0.327 m. This larger vertical error is driven by points (n=11) on the edge of the DSM where there is poor ground control, with these outlier check points removed, the RMSE = 0.157 m. Users should take care to check where the DSMs diverge. Lineage: Process_Step: Process_Description: GROUND CONTROL: Ten AeroPoint GCPs were spaced out over the field site and left on for at least two hours to collect Global Navigation Satellite System(GNSS) data, however four were not properly turned on. After collection and connected to Wi-Fi, the AeroPoint data were uploaded and run through a post-processing kinematic algorithm of the Continuously Operating Reference Station (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_Apr_AeroPoints.csv. GPS DATA: A Spectra Precision 80 (SP80) was set up as a base station in the parking lot to collect RINEX data to correct the lidar data. A second SP80 was set up as a rover connected to the Massachusetts CORS network and used to take check shots across the study site. The check points are provided in 2024018FA_TNB_Apr_GPS_SP80.csv. Step completed by C. Sherwood, A. Farris, J. Cramer, and J. Over. Process_Date: 20240415 Process_Step: Process_Description: 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 *.jpeg 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 with the UAS flying at 7 m/s at ~61 meters above ground level at a transect spacing of 45 m for a total of 42 minutes of flight time. The SONY camera triggered every 2 seconds. After each flight the lidar data 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_Apr_ImageryLocations.csv). Step completed by J. Cramer and J. Over. Process_Date: 20240415 Process_Step: Process_Description: RAW IMAGERY: YSMP 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 photo 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 images were renamed with Namexif (https://us.digicamsoft.com/softnamexif.html v 2.2 accessed April 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_20240415T165822Z_DSC#', 2024018FA is the field activity ID, f01 is the flight number, r03 is the camera, 20240415 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. Step completed by J. Cramer and J. Over. Process_Date: 20240416 Process_Step: Process_Description: 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 was imported. 2. Photos were aligned at a low accuracy and then GCPs were automatically detected in the point cloud. GCP positions (2024018FA_TNB_Apr_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_Apr_YSMP_SfM_DSM_25cm.tif) and orthomosaic (2024018FA_TNB_Apr_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. Process_Date: 20241206 Process_Step: Process_Description: 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 SP80 collecting data on site for the time the UAS was flying. 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 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 is 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 is exported from CloudStation as a 1.4 *.laz file. The LPC is 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 LPC is adjusted to the GCPs using a planar fit and exported as 2024018FA_TNB_Apr_YSMP_LPC.laz. The LPC is then gridded using maximum values and exported (2024018FA_TNB_Apr_YSMP_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. Process_Date: 20241102 Process_Step: Process_Description: 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. Process_Date: 20241206 Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jin-Si R. Over Contact_Organization: U.S. Geological Survey, Woods Hole Coastal and Marine Science Center Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical address Address: U.S. Geological Survey Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2297 Contact_Electronic_Mail_Address: jover@usgs.gov Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Planar: Grid_Coordinate_System: 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_Coordinate_Information: Planar_Coordinate_Encoding_Method: row and column Coordinate_Representation: Abscissa_Resolution: 0.001 Ordinate_Resolution: 0.001 Planar_Distance_Units: meters Geodetic_Model: Horizontal_Datum_Name: North American Datum of 1983 (National Spatial Reference System 2011) Ellipsoid_Name: GRS_1980 Semi-major_Axis: 6378137.0 Denominator_of_Flattening_Ratio: 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 Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_ImageLocations.csv Entity_Type_Definition: The CSV file contains the approximate position of the YSMP images at the moment of each capture based on post-processed UAS integrated GPS/IMU. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: ImageName Attribute_Definition: File names of individual images, see the Process Description for file naming convention. Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSDateTime Attribute_Definition: Date and UTC time in YYYY:MM:DD HH:MM:ss. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Latitude NAD83[2011] Attribute_Definition: Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 41.76183024 Range_Domain_Maximum: 41.77147449 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Longitude NAD83[2011] Attribute_Definition: Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -70.48772814 Range_Domain_Maximum: -70.47281292 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Ellipsoid height GRS80 Attribute_Definition: Altitude of the camera at the time of each image capture relative to the NAD83(2011) reference ellipsoid Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 19.859 Range_Domain_Maximum: 34.242 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting 19N Attribute_Definition: UTM X coordinate of camera based on time of each image capture. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 376346.825 Range_Domain_Maximum: 377574.562 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Northing 19N Attribute_Definition: UTM Y coordinate of camera based on time of each image capture. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4624384.857 Range_Domain_Maximum: 4625471.845 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Altitude NAVD88 Attribute_Definition: Altitude of the camera at the time of each image capture relative to NAVD88 with GEOID 18 applied. Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 48.040 Range_Domain_Maximum: 62.416 Attribute_Units_of_Measure: meters Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_AeroPoints.csv Entity_Type_Definition: Ground control point positions, elevations, and attributes Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: FAN Attribute_Definition: USGS Field Activity Number Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 2024-018-FA Enumerated_Domain_Value_Definition: Year, USGS ID, and Field Activity Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Date Attribute_Definition: Calendar date of collection Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 20240415 Enumerated_Domain_Value_Definition: YYYYMMDD Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Point ID Attribute_Definition: Unique point identification number. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1 Range_Domain_Maximum: 6 Attribute: Attribute_Label: Attributes Attribute_Definition: Unique identifier for ground control points. Prefix AP-### refers to AeroPoint and the last 3 digits of its identifying code. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Latitude NAD83[2011] Attribute_Definition: Post-processed latitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 41.76489019 Range_Domain_Maximum: 41.7680074 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Longitude NAD83[2011] Attribute_Definition: Post-processed longitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -70.48537207 Range_Domain_Maximum: -70.47754726 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Ellipsoid height GRS80 Attribute_Definition: Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid. Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -28.303 Range_Domain_Maximum: -22.993 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting 19N Attribute_Definition: Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 376537.628 Range_Domain_Maximum: 377182.087 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Northing 19N Attribute_Definition: Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4624727.722 Range_Domain_Maximum: 4625085.026 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Orthometric height NAVD88 Attribute_Definition: Post-processed Z-coordinate of AeroPoint using NAVD88 with GEOID 18 applied. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -0.126 Range_Domain_Maximum: 5.193 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Xvar mm Attribute_Definition: Internal variance in the X-coordinate from post-processing. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1.7 Range_Domain_Maximum: 5.0 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Yvar mm Attribute_Definition: Internal variance in the Y-coordinate from post-processing. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1.4 Range_Domain_Maximum: 6.5 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Zvar mm Attribute_Definition: Internal variance in the Z-coordinate from post-processing. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 2.9 Range_Domain_Maximum: 13.1 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Baseline distance km Attribute_Definition: Distance to from the AeroPoint to the correcting base. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.33 Range_Domain_Maximum: 11.92 Attribute_Units_of_Measure: kilometers Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_GPS_SP80.csv Entity_Type_Definition: GPS SP80 check point positions, elevations, and attributes Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: FAN Attribute_Definition: USGS Field Activity Number Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 2024-018-FA Enumerated_Domain_Value_Definition: Year, USGS ID, and Field Activity Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Date Attribute_Definition: Calendar date of collection Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 20240415 Enumerated_Domain_Value_Definition: YYYYMMDD Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Point ID Attribute_Definition: Unique point identification number. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1 Range_Domain_Maximum: 77 Attribute: Attribute_Label: Attributes Attribute_Definition: Identifies check point type. This includes T# for Transect and number, groin, parking lot, boardwalk, grass, stick, camera, roses, and AeroPoint (AP). Attribute_Definition_Source: producer defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Latitude NAD83[2011] Attribute_Definition: Post-processed latitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 41.76480479 Range_Domain_Maximum: 41.76872862 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Longitude NAD83[2011] Attribute_Definition: Post-processed longitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -70.48538118 Range_Domain_Maximum: -70.47552819 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Ellipsoid height GRS80 Attribute_Definition: Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid. Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -29.340 Range_Domain_Maximum: -21.415 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting 19N Attribute_Definition: Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 376537.707 Range_Domain_Maximum: 377350.157 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Northing 19N Attribute_Definition: Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4624715.780 Range_Domain_Maximum: 4625164.250 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Orthometric height NAVD88 Attribute_Definition: Post-processed Z-coordinate of AeroPoint using NAVD88 with GEOID 18 applied. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -1.168 Range_Domain_Maximum: 6.772 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: HSDV m Attribute_Definition: Horizontal standard deviation, provides the horizontal precision of the position solution. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.008 Range_Domain_Maximum: 0.033 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: VSDV m Attribute_Definition: Vertical standard deviation, provides the vertical precision of the position solution. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.014 Range_Domain_Maximum: 0.054 Attribute_Units_of_Measure: meters Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_YSMP_LPC.laz Entity_Type_Definition: YSMP lidar point cloud in .laz file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. Total point count is 117,127,028. The point density is 310.1 points per square meter, and point spacing is 0.057 m. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: Elevation Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using GEOID 18 in NAD83(2011)/UTM Zone 19N. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -2.100 Range_Domain_Maximum: 14.891 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Intensity Attribute_Definition: Lidar intensity is recorded as the return strength of a laser beam during data collection. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 65,025 Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_YSMP_DSM_25cm.tif Entity_Type_Definition: A cloud-optimized digital surface model gridded from the lidar point cloud with encoded elevation values. Pixel resolution is 25 cm. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: Value Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 19N. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -2.141 Range_Domain_Maximum: 14.914 Attribute_Units_of_Measure: meters Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_YSMP_SfM_DSM_25cm.tif Entity_Type_Definition: A cloud-optimized SfM digital surface model made from the lidar point cloud images. Pixel resolution is 25 cm. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: Value Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 19N. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -6.982 Range_Domain_Maximum: 15.023 Attribute_Units_of_Measure: meters Detailed_Description: Entity_Type: Entity_Type_Label: 2024018FA_TNB_Apr_YSMP_SfM _Ortho_5cm.tif Entity_Type_Definition: True-color (RGB) cloud optimized orthomosaic made from the YSMP images. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: Band_1 Attribute_Definition: Red wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute: Attribute_Label: Band_2 Attribute_Definition: Green wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute: Attribute_Label: Band_3 Attribute_Definition: Blue wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Overview_Description: Entity_and_Attribute_Overview: The filenames are formatted as "2024018FA_TNB_Apr_sensor/product_ resolution.*** ", where 2024018 is the USGS Field activity ID, location is Town Neck Beach (TNB); sensors include YellowScan Mapper Plus (YSMP), GPS_SP80, 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 Distribution_Information: Distributor: Contact_Information: Contact_Organization_Primary: Contact_Organization: U.S. Geological Survey - ScienceBase Contact_Address: Address_Type: mailing and physical address Address: Denver Federal Center, Building 810, Mail Stop 302 City: Denver State_or_Province: CO Postal_Code: 80225 Contact_Voice_Telephone: 1-888-275-8747 Contact_Electronic_Mail_Address: sciencebase@usgs.gov Resource_Description: 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. Distribution_Liability: 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. Standard_Order_Process: Digital_Form: Digital_Transfer_Information: Format_Name: GeoTIFF Format_Version_Number: 1.0.0 Format_Specification: Cloud optimized GeoTIFF format Adobe deflate compressed Format_Information_Content: 2024018FA_TNB_Apr_YSMP_DSM_25cm.tif (26 MB) and 2024018FA_TNB_Apr_YSMP_SfM_DSM_25cm.tif (36 MB) have encoded surface elevations and 2024018FA_TNB_Apr_YSMP_SfM_Ortho_5cm.tif (372 MB) is an orthomosaic. Transfer_Size: 408 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://doi.org/10.5066/P1UBZZFA Access_Instructions: The first link in the list above is to the child page where files can be downloaded individually, the second link is to directly download all the data on the page, and third link is to the doi to the main publication. Digital_Form: Digital_Transfer_Information: Format_Name: CSV Format_Version_Number: Exported from Excel Office 365 16.01 Format_Information_Content: The CSV file 2024018FA_TNB_Apr_AeroPoints.csv contains ground control data, 2024018FA_TNB_Apr_GPS_SP80.csv contains GPS check points, and 2024018FA_TNB_Apr_ImageLocations.csv contains a list of the images and their positions. Transfer_Size: 0.1 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://doi.org/10.5066/P1UBZZFA Access_Instructions: The first link in the list above is to the child page where files can be downloaded individually, the second link is to directly download all the data on the page, and third link is to the doi to the main publication. Digital_Form: Digital_Transfer_Information: Format_Name: JPEG Format_Version_Number: 1.0.0 Format_Information_Content: The YSMP images. Transfer_Size: 4480 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://doi.org/10.5066/P1GG3QSO Network_Resource_Name: https://doi.org/10.5066/P1UBZZFA Access_Instructions: The first link in the list above is to the child page where files can be downloaded individually, the second link is to directly download all the data on the page, and the third link is to the Imagery Data System where the photos can be viewed and downloaded individually (filter by FA, date, and sensor type), and the fourth link is to the doi to the main publication. Transfer size refers to the total size of all images in MB if downloaded from the IDS, images are not hosted on sciencebase. Digital_Form: Digital_Transfer_Information: Format_Name: LAZ Format_Version_Number: 1.4 Format_Information_Content: LAZ (LAserZipped) is an open file format intended for point data records. File_Decompression_Technique: Use laszip to decompress Transfer_Size: 1220 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67213f45d34ed0f827eaaef0 Network_Resource_Name: https://doi.org/10.5066/P1UBZZFA Access_Instructions: The first link in the list above is to the child page where files can be downloaded individually, the second link is to directly download all the data on the page, and third link is to the doi to the main publication. Fees: None. Metadata_Reference_Information: Metadata_Date: 20250430 Metadata_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jin-Si R. Over Contact_Organization: U.S. Geological Survey, Northeast Region Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical Address: U.S. Geological Survey Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2297 Contact_Electronic_Mail_Address: 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_Name: Content Standard for Digital Geospatial Metadata Metadata_Standard_Version: FGDC-STD-001-1998 Metadata_Access_Constraints: None Metadata_Use_Constraints: None