Jin-Si R. Over Amit Millo 20260518 1.0 point cloud, raster, and tabular digital data data release DOI:10.5066/P1UBZZFA Woods Hole Coastal and Marine Science Center, Woods Hole, MA U.S. Geological Survey, Coastal and Marine Hazards and Resources Program https://doi.org/10.5066/P1UBZZFA https://www.sciencebase.gov/catalog/item/69f4ac22b66b0122e4360ef0 Jin-Si R. Over Jennifer M. Cramer Christopher R. Sherwood Amy S. Farris Amit Millo 2025 2.0 digital data data release DOI:10.5066/P1UBZZFA Reston, VA U.S. Geological Survey Suggested citation: Over, J.R., Cramer, J.M., Sherwood, C.R., Farris, A.S., and Millo, A., 2025, Topographic data, imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Town Neck Beach, Sandwich, Massachusetts (ver. 2.0, May 2026): U.S. Geological Survey data release, https://doi.org/10.5066/P1UBZZFA. https://doi.org/10.5066/P1UBZZFA https://www.sciencebase.gov/catalog/item/67213855d34ed0f827eaae83 A small Uncrewed Aircraft System (sUAS) was used to collect aerial remote sensing data over Town Neck Beach, Sandwich, Massachusetts to monitor landscape change. On June 2nd, 2025, USGS personnel collected lidar, natural (RGB) color images, GPS check points, and ground control points. These data were processed to produce a lidar point cloud, high-resolution digital surface model, and natural-color orthomosaic. These will be used to compare how the site has changed and validate the total water level data. The imagery and lidar products were produced to help the site’s conservation partnership evaluate conditions of the site and landscape change from remediation efforts and potential storm impacts. For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/services/activity.php?fan=2025-015-FA. Images can be viewed or downloaded on the USGS Imagery Data System here https://doi.org/10.5066/P1GG3QSO in the collection 2025_TNB_Jun_Map61. Note that the bounding coordinates are for the entire area and not individual files. 20250602 Ground condition Complete Not planned -70.48755522 -70.47492937 41.77016595 41.76226198 None U.S. Geological Survey USGS Coastal and Marine Hazards and Resources Program CMHRP Woods Hole Coastal and Marine Science Center WHCMSC WingtraOne Gen II Bare Earth Point Cloud UAS AeroPoints orthomosaics digital surface models Aerial Imaging and Mapping Group USGS Thesaurus remote sensing digital elevation models structure from motion image mosaics geospatial datasets image collections ISO 19115 Topic Category geoscientificInformation elevation USGS Metadata Identifier USGS:69f4ac22b66b0122e4360ef0 Geographic Names Information System (GNIS) Atlantic Ocean Cape Cod Bay Commonwealth of Massachusetts Sandwich(616837) Town Neck Beach No access contraints. Please see 'Distribution Information' for details. These data are marked with a Creative Commons CC0 1.0 Universal License. These data are in the public domain and do not have any use constraints. Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations. Please recognize the U.S. Geological Survey (USGS) as the source of this information. These data are not intended for navigational use. Jin-Si R. Over U.S. Geological Survey, Northeast Region, Woods Hole Coastal and Marine Science Center Geographer mailing and physical address

384 Woods Hole Rd.

Woods Hole MA 02543-1598 508-548-8700 x2310 jover@usgs.gov https://www.sciencebase.gov/catalog/file/get/69f4ac22b66b0122e4360ef0?name=2025015FA_TNB_Jun_browse_graphic.jpg&allowOpen=true Data and products of Town Neck Beach in June 2025: Lidar point cloud, RGB image, Wingtra UAS, and orthomosaic. JPEG Agisoft Metashape Pro v. 2.2.0, Emlid Studio v. 1.9, WingtraHub v. 2.18.0, WingtaLidar v. 1.10.1.0, Global Mapper Pro v. 26.0 Jin-Si R. Over Andrew C. Ritchie Christine J. Kranenburg Jenna A. Brown Daniel D. Buscombe Tom Noble Christopher R. Sherwood Jonathan A. Warrick Phillipe A. Wernette 2021 Open-File Report 2021-1039 Reston, VA U.S. Geological Survey This publication includes the general methodology for processing imagery in Metashape to produce digital surface models and ortho products. https://doi.org/10.3133/ofr20211039 GPS: The theoretical internal accuracy of the Emlid RS3 is 2 cm. Points were assumed to be within that tolerance after staking out at known reference mark “big belly” and the values were within 2 cm. The vertical and horizontal root mean square (RMS) internal variances for each point were also reported in 2025015FA_TNB_GPS_Emlid_RS3_checkpoints.csv, values should be less than 2 cm. The AeroPoint2 ground control points (GCPs), referred to as just AeroPoints from here on, have an internal reported variance provided in 2025015FA_TNB_AeroPoints.csv, the global accuracy was calculated and reported below by adding the variance to twice the longest baseline distance. Two AeroPoints were also surveyed by the RS3. GeoTIFFs: The horizontal and vertical accuracy of the products (2025015FA_TNB_WLDR_DSM_25cm.tif and 2025015FA_TNB_MAP61_SfM_Ortho_5cm.tif) were assessed using the AeroPoints and check points. 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 check points taken. Additional sources of error, such as moving objects, may cause accuracy estimates to exceed estimates in localized portions of the products. Lidar: The point cloud (2025015FA_TNB_WLDR_LPC.laz) positional accuracy is based on the GPS/IMU and post positional corrections from the base station but the vertical point spread on a flat surface is about 8 cm. The LPC was colorized from the SfM orthomosaic. Some misalignment in the collected lidar strips may occur. Lidar does not pass through water. Gaps may also exist where there is less scan overlap and point densities were lower. Users are advised to evaluate the data for their own needs. There were three UAS flights and ten AeroPoint. Flight one (16 min) used the MAP61 camera module on the WingtraOne Gen II (W1G2) to collect RGB images. Flight two (13 min) used the same MAP61 camera on the W1G2 and was performed to finish surveying the coastline as some of the shore was missed on the first flight. These two flights were used to generate the orthomosaic. Flight three (12 min) collected lidar data (WLDR) and produced the lidar point cloud (LPC) and digital surface model (DSM). An Emlid RS2+ was set up as a base station and an Emlid RS3 GPS unit was used to collect check points. Imagery: The MAP61 camera triggered every 2 seconds. Images not at the mapping altitude were removed and account for a total of 540 MAP61 images. Products: GeoTIFF products are cloud-optimized and Deflate compressed. The LPC has been cleaned in Global Mapper to remove water points and wave noise. Images: The Wingtra Map61 images were geotagged in WingtraHub v. 2.18.0 using base station data and had an average xy accuracy of 0.03 m. GPS: Emlid RS3 GPS points have a xy RMS (precision) average of 1.7 cm. AeroPoint horizontal global accuracy is 2.8 cm. Lidar: The lidar point cloud, and by association the DSM, horizontal accuracy was assessed against positions of the AeroPoints in the lidar intensity view (not the RGB). The horizontal accuracy is variable and within 10 cm. SfM: The orthomosaic was spatially georeferenced using AeroPoint GCPs (n=10) and created using SfM. The horizontal RMSE of the check points as reported from the Metashape projects were x/y 0.024/0.025 m. Images: The MAP61 images were geotagged in WingtraHub v. 2.18.0 using the base station data and had an average z accuracy of 0.04 m. GPS: Emlid RS3 GPS points have a z RMS (precision) average of 1.8 cm. AeroPoint global vertical accuracy is 3.5 cm. Lidar: The LPC was assessed against the elevations of the AeroPoints and GPS check points: the RMSE (n=74) was 0.05 m. GROUND CONTROL: Ten AeroPoint GCPs were spaced out over the field site and left on for at least 30 minutes to collect GNSS data. After collection, the AeroPoint data were uploaded via a Wi-Fi connection and run through a post-processing kinematic algorithm of the propeller network to get corrected positions. The data were exported in NAD83(2011) (EPSG:6318) to produce latitude, longitude, and ellipsoid heights, and then NAD83(2011)/UTM zone 19N (EPSG:6348) and NAVD88 (EPSP:5703) with GEOID 18 to produce easting and northing and orthometric heights. These were exported to a CSV file and named 2025015FA_TNB_AeroPoints.csv. An Emlid RS2+ was set up as a base station using an RTK FIX on the highest section of boardwalk to record GNSS data for post processing the lidar data. An Emlid RS3 with tilt compensation was connected to the base to take RTK three-second averaged check shots on the parking lot, beach, and AeroPoints, data were provided in 2025015FA_TNB_GPS_Emlid_RS3_checkpoints.csv. UAS FLIGHTS: The lidar sensor was a 905 nm wavelength Hesai XT32-M2X with a 90 / 40.3 degree horizontal and vertical field of view (FOV). It is a rotating sensor, generating up to three returns with an effective point rate for a single return of 160k pts/s. The camera module uses the Wingtra MAP61 61-megapixel (MP) camera with a 17 mm lens. The system uses a NovAtel OEM7500 multi-frequency, high precision GNSS receiver. The lidar data was saved to the 256 GB thumb drive in five different *.data files. The RGB images are saved as *.JPG files. The lidar data were collected with the Wingtra UAS flying 61 meters above ground level with northwest-southeast transect passes. The camera module was set to take images every 2 seconds. After the flights the lidar and RGB data were downloaded off their respective sensor. Note, the geotagged positions embedded in the imagery Exif information were in EPSG:4326, this is the only option in the software. The positions were converted to EPSG:6348 and EPSG:5703 in the imagery locations file (2025015FA_TNB_MAP61_ImageryLocations.csv) and were accounted for when transforming to EPSG:6348 and EPSG:5703 in the products. 20250602 RAW IMAGERY: The W1G2 images were geotagged in WingtraHub using the base station RINEX file and OPUS corrected location of the base. All 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 to avoid any possibility of duplicate names. These steps are described here. 1. ExifTool was used to tag each photo 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 '2025015FA_f01MAP61_20250602T165822Z_#####', 2025015FA is the field activity ID; f01 is the flight number; MAP61 is camera used; 20250601 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 ##### is the original raw photo suffix appended to the end of the new filename. 3. Images are validated and uploaded onto the Imagery Data System. 20250710 PHOTOGRAMMETRY: The ortho product was created in Agisoft Metashape v. 2.2.0 using the following general steps (see Over and others, 2021 for a more detailed SfM methodology explanation): 1. A project was created and imagery was imported along with a csv file containing the following information about the camera when the image was taken: latitude/longitude (WGS84), ellipsoid altitude (m), vertical and horizontal accuracy (m), omega/phi/kappa (°), and accuracy (°). 2. Photos were aligned at a high accuracy 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 PPK geotagged image locations. 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 10, and multiple 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. In a new chunk, a high-quality dense cloud with a low-frequency filtering algorithm was made. The dense point cloud was then edited by visual inspection to remove points with a low confidence near the edges and near water bodies. 5. An interpolated DSM was built from the dense point cloud and then an orthomosaic was built from the DSM with refined seamlines. The orthomosaic is a 3-band orthomosaic exported at 5 cm resolution (2025015FA_TNB_MAP61_SfM_Ortho_5cm.tif). Step processed by J. Over. 20250710 LiDAR DATA: The lidar data were processed in the Wingtra LIDAR app. The .data files were uploaded into the app along with the base station RINEX *.25O file. The OPUS corrected location of the base and the ARP-APC offset were then entered manually. After the processing was complete, the start and end location of each transect was manually identified to clip the paths and remove points obtained when the aircraft was turning. This point cloud product was exported from the Wingtra LIDAR app and was brought into Global Mapper (GM) and manually cleaned of points interpreted to be noise or water. The LPC was colorized in GM with the SfM orthomosaic. Then, the LPC was gridded at 25 cm into a DSM using maximum values binning grid method and the setting 'Grid "No Data" Distance' set to 5; the resulting file was exported as 2025015FA_TNB_WLDR_DSM_25cm.tif. The LPC was exported as 2025015FA_TNB_WLDR_LPC.laz. All files were exported in EPSG:6348 and EPSG:5703 using GEOID 18. 20250711 CLOUD OPTIMIZATION: The DSM was Deflate compressed and turned into a cloud-optimized GeoTIFF (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. The orthomosaic was JPEG compressed and turned into a cog using gdal_translate with the following command: for %i in (.\*.tif) do gdal_translate %i .\%~ni_cog.tif -of COG -stats -co BLOCKSIZE=256 -co COMPRESS=JPEG -co QUALITY=90 -co PREDICTOR=YES -co NUM_THREADS=ALL_CPUS -co BIGTIFF=YES 20250711 Jin-Si R. Over U.S. Geological Survey, Woods Hole Coastal and Marine Science Center Geographer mailing and physical address

U.S. Geological Survey

384 Woods Hole Rd.

Woods Hole MA 02543-1598 508-548-8700 x2310 jover@usgs.gov Universal Transverse Mercator 19 0.999600 -69.000000 0.000000 500000.000000 0.000000 row and column 0.001 0.001 meters North American Datum of 1983 (National Spatial Reference System 2011) GRS_1980 6378137.0 298.257222101 North American Vertical Datum of 1988 0.001 meters Explicit elevation coordinate included with horizontal coordinates 2025015FA_TNB_MAP61_ImageryLocations.csv The CSV file contains the approximate position of the W1G2 images at the moment of each capture. producer defined FileName File names of individual images, see the Process Description for file naming convention. USGS Character string. GPSDateTime Date and UTC time in YYYY:MM:DD HH:MM:ss Processor defined Character string. Latitude NAD83(2011) Latitude (x) of camera based on time of each image capture. Positive values represent North coordinates. USGS 41.76285088 41.76997067 decimal degrees Longitude NAD83(2011) Longitude (y) of camera based on time of each image capture. Negative values represent West coordinates. USGS -70.48698574 -70.47537934 decimal degrees Ellipsoid height GRS80 Altitude of the camera at the time of each image capture relative to the NAD83(2011) reference ellipsoid GRS80. USGS 27.820 42.446 meters Easting 19N Post-processed interpolated X-coordinate of camera based on time of each image capture NAD83(2011)/UTM Zone 19N. USGS 376402.467 377363.080 meters Northing 19N Post-processed interpolated Y-coordinate of camera based on time of each image capture NAD83(2011)/UTM Zone 19N. USGS 4624502.105 4625301.366 meters Orthometric height NAVD88 Altitude of the UAS position at the time of each image capture relative to the vertical datum NAVD88 using geoid 18. USGS 55.992 70.629 meters 2025015FA_TNB_AeroPoints.csv Ground control point positions, elevations, and attributes USGS FA USGS Field Activity Number USGS 2025-015-FA Year, USGS ID, and Field Activity USGS Date Calendar date of collection USGS 20250602 YYYYMMDD USGS Point ID Unique point identification number. Processor defined 1 10 Attributes Unique identifier for ground control points. Prefix AP-### refers to AeroPoint and the last 3 digits of its identifying code. producer defined Character string. Latitude NAD83(2011) Post-processed latitude of AeroPoint position (NAD83(2011)). USGS 41.76406053 41.76821043 decimal degrees Longitude NAD83(2011) Post-processed longitude of AeroPoint position (NAD83(2011)). USGS -70.48532803 -70.47829437 decimal degrees Ellipsoid height GRS80 Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid GRS80. USGS -27.834 -23.309 meters Easting 19N Post-processed X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. USGS 376541.678 377118.400 meters Northing 19N Post-processed Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. USGS 4624636.673 4625107.505 meters Orthometric height NAVD88 Post-processed Z-coordinate of AeroPoint using NAVD88 with GEOID 18 applied. USGS 0.351 4.884 meters X variance (mm) Variance in the X-coordinate from post-processing producer defined 2.3 6.0 millimeters Y variance (mm) Variance in the Y-coordinate from post-processing producer defined 1.6 6.8 millimeters Z variance (mm) Variance in the Z-coordinate from post-processing producer defined 4.1 10.8 millimeters Baseline distance (km) distance of AeroPoint from nearest used processing network base station Propeller 0.01 11.71 kilometers 2025015FA_TNB_GPS_Emlid_RS3_checkpoints.csv GPS positions, elevations, and attributes USGS FA USGS Field Activity Number USGS 2025-015-FA Year, USGS ID, and Field Activity USGS Date Calendar date of collection USGS 20250602 YYYYMMDD USGS Point ID Unique point identification number. NaN assigned to reference point pre-loaded into project. Processor defined 0 99 Attributes Identifier for GPS check shots. Big belly-OPUS refers to the known solution of the reference mark at Town Neck Beach, big belly-Open refers to a stake out check in on the reference mark, AP-### refers to a surveyed AeroPoint, and 'check point' refers to a shot taken on the ground. producer defined Character string. Latitude NAD83(2011) RTK x position of the point relative to (NAD83(2011)). USGS 41.76443611 41.76859043 decimal degrees Longitude NAD83(2011) RTK y position of the point relative to (NAD83(2011)). USGS -70.48566453 -70.47934698 decimal degrees Ellipsoid height RTK z position of the point relative to the NAD83(2011) reference ellipsoid GRS80. USGS -29.489 -21.762 meters Easting 19N RTK x position of the point relative to NAD83(2011)/UTM Zone 19N. USGS 376513.49 377031.618 meters Northing 19N RTK y position of the point relative to NAD83(2011)/UTM Zone 19N. USGS 4624679.878 4625147.183 meters Orthometric height NAVD88 RTK z position of the point relative to NAVD88 with GEOID 18 applied. USGS -1.300 6.427 meters Tilt angle Angle to nadir of the Emlid RS3 USGS 0.0 10.1 degrees Elevation RMS Root mean square in the Z-coordinate producer defined 0.015 0.020 meters Lateral RMS Root mean square in the horizontal XY-coordinate producer defined 0.010 0.022 meters 2025015FA_TNB_WLDR_LPC.laz UAS lidar point cloud in *.laz v. 1.4 file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. There are 30,711,943 points. Point density is 138.43 points per square meter and point spacing is 0.085 m. producer defined Elevation Surface elevation in EPSG:5703 using GEOID 18. Wingtra -1.435 13.998 meters Classification Each lidar point has a classification value assigned to it according to the ASPRS LAS Specification. Global Mapper 0 Data have not been classified. ASPRS LAS Specification Intensity Lidar intensity is recorded as the return strength of a laser beam during data collection. Wingtra 0 255 Return number Return number. Each laser pulse can produce multiple discrete observations as emitted light is reflected by objects in the scene. Wingtra 1 3 Scan angle The scan angle of the laser beam that produced each point where 0 degrees indicates nadir. Wingtra -43 44 Degrees 2025015FA_TNB_WLDR_DSM_25cm.tif A cloud-optimized digital surface model created from the lidar point cloud maximum values with encoded elevation values. Pixel resolution is 25 cm. USGS Value Surface elevation in EPSG:5703 using GEOID 18. No-data value is set to –32767. producer defined -1.426 13.998 meters 2025015FA_TNB_MAP61_SfM_Ortho_5cm.tif Cloud-optimized JPEG compressed true-color orthomosaic. No data is represented by 0 in the Alpha band. USGS Band_1 Red wavelength band Agisoft Metashape 0 255 Band_2 Green wavelength band Agisoft Metashape 0 255 Band_3 Blue wavelength band Agisoft Metashape 0 255 Band_4 Alpha band. 0 is no data, 255 is data. Agisoft Metashape 0 255 The filenames are formatted as "2025015FA_TNB_sensor/product_resolution.*** ", where 2025015 is the USGS Field activity ID, location is Town Neck Beach (TNB), sensor is MAP61, AeroPoints, Emlid RS3, and products include orthomosaic (Ortho), digital surface model (DSM), and lidar point cloud (LPC). USGS Field Activity 2025-015-FA U.S. Geological Survey - ScienceBase mailing and physical address

Denver Federal Center, Building 810, Mail Stop 302

Denver CO 80225 1-888-275-8747 sciencebase@usgs.gov Aerial imaging and mapping of Town Neck Beach includes the imagery (MAP61), orthomosaic, the Wingtra lidar point cloud, digital surface model, Emlid GPS check points, and AeroPoint ground control points. 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. GeoTIFF 1.0.0 Cloud optimized GeoTIFF format 2025015FA_TNB_WLDR_DSM_25cm.tif (15 MB Deflate compressed) is an elevation model and 2025015FA_TNB_MAP61_SfM_Ortho_5cm.tif (67 MB JPEG compressed) is an orthomosaic. 80 https://www.sciencebase.gov/catalog/item/69f4ac22b66b0122e4360ef0 https://www.sciencebase.gov/catalog/file/get/69f4ac22b66b0122e4360ef0 https://doi.org/10.5066/P1UBZZFA 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. CSV Exported from Excel Office 365 16.01 The CSV file 2025015FA_TNB_AeroPoints.csv contains ground control data, 2025015FA_TNB_GPS_Emlid_RS3_checkpoints.csv contains GPS check points, and 2025015FA_TNB_MAP61_ImageryLocations.csv contains a list of the images and their positions. 0.1 https://www.sciencebase.gov/catalog/item/69f4ac22b66b0122e4360ef0 https://www.sciencebase.gov/catalog/file/get/69f4ac22b66b0122e4360ef0 https://doi.org/10.5066/P1UBZZFA 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. JPEG 1.0.0 The MAP61 images. 2180 https://www.sciencebase.gov/catalog/item/69f4ac22b66b0122e4360ef0 https://www.sciencebase.gov/catalog/file/get/69f4ac22b66b0122e4360ef0 https://doi.org/10.5066/P1UBZZFA https://doi.org/10.5066/P1GG3QSO 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. The transfer size is the total, in MB, if you downloaded all images from the IDS, images are not hosted on sciencebase. LAZ 1.4 LAZ (LAserZipped) is an open file format intended for point data records. Use laszip to decompress 260 https://www.sciencebase.gov/catalog/item/69f4ac22b66b0122e4360ef0 https://www.sciencebase.gov/catalog/file/get/69f4ac22b66b0122e4360ef0 https://doi.org/10.5066/P1UBZZFA 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. None. 20260518 Jin-Si R. Over U.S. Geological Survey, Northeast Region Geographer mailing and physical

U.S. Geological Survey

384 Woods Hole Rd.

Woods Hole MA 02543-1598 508-548-8700 x2310 whsc_data_contact@usgs.gov The metadata contact email address is a generic address in the event the person is no longer with USGS. Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 None None