Lidar and photogrammetry point clouds with supporting imagery and GPS information collected during UAS operations at Great Sippewissett Marsh, Cape Cod, Massachusetts in November 2022

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

Frequently anticipated questions:

What does this data set describe?

Title:
Lidar and photogrammetry point clouds with supporting imagery and GPS information collected during UAS operations at Great Sippewissett Marsh, Cape Cod, Massachusetts in November 2022
Abstract:
These lidar point clouds and images cover, in high detail, the terrain at Great Sippewissett Marsh, Cape Cod, MA on November 2nd, 2022. USGS researchers tested different sensors that collected lidar and images for photogrammetry point cloud data using Uncrewed Aerial Systems (UAS) to look at differences in coverage and elevation accuracy. The lidar data were acquired with a YellowScan Mapper lidar scanner, which consists of the Livox Horizon scanner and Applanix 15 inertial measurement unit; and a YellowScan VX20-100 lidar scanner, which consists of the Riegl minivux-1uav scanner and Applanix 20 inertial measurement unit. The YellowScan Mapper Sony UMC-R10C camera and a Ricoh GRII camera were used to take photos for structure from motion processing and to compare point clouds. The lidar data was post-processed to a R8s Trimble base station. Smart AeroPoint ground control points (GCPs) and ground truthing GPS points were used for vertical validation.
Supplemental_Information:
For more information about the WHCMSC Field Activity (FA), see https://cmgds.marine.usgs.gov/services/activity.php?fan=2022-022-FA. Images can be viewed or downloaded on the USGS Imagery Data System here: https ://doi.org/10.5066/P14UWEQB. 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., Bauer, Mark A., Burgess, Matthew A., Cramer, Jennifer M., Brosnahan, Sandra M., Ackerman, Seth D., and Evans, Alexandra D., 20250317, Lidar and photogrammetry point clouds with supporting imagery and GPS information collected during UAS operations at Great Sippewissett Marsh, Cape Cod, Massachusetts in November 2022: data release DOI:10.5066/P13PSF3S, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Other_Citation_Details:
    Over, J.R., Bauer, M.A., Burgess, M.A., Ackerman, S.D., Brosnahan, S.M., Cramer, J.M., and Evans, A.D., 2025, Lidar and photogrammetry point clouds with supporting imagery and GPS information collected during UAS operations at Great Sippewissett Marsh, Cape Cod, Massachusetts in November 2022: U.S. Geological Survey data release, https://doi.org/10.5066/P13PSF3S
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.64526212
    East_Bounding_Coordinate: -70.63592988
    North_Bounding_Coordinate: 41.58906136
    South_Bounding_Coordinate: 41.58256432
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/65bbbe96d34e18c6baf2e61f?name=2022022FA_GSM_lidar_browse.JPG&allowOpen=true (JPEG)
    Example lidar point cloud of Great Sippewissett Marsh.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 27-Oct-2022
    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?
    2022022FA_GSM_ImageryLocations.csv
    The CSV file contains the approximate position of the YSM and Ricoh images at the moment of each capture. (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 UAS based on time of each image capture. Positive values represent North coordinates. (Source: USGS)
    Range of values
    Minimum:41.58256432
    Maximum:41.58906136
    Units:decimal degrees
    Longitude NAD83[2011]
    Longitude (y) of UAS based on time of each image capture. Negative values represent West coordinates. (Source: USGS)
    Range of values
    Minimum:-70.64526212
    Maximum:-70.63592988
    Units:decimal degrees
    Ellipsoid GRS 1980
    Altitude of the UAS position at the time of each image capture relative to the ellipsoid. (Source: None)
    Range of values
    Minimum:19.730
    Maximum:59.629
    Units:meters
    Easting 19N
    UTM X coordinate of UAS based on time of each image capture. (Source: USGS)
    Range of values
    Minimum:362863.874
    Maximum:363643.685
    Units:meters
    Northing 19N
    UTM Y coordinate of UAS based on time of each image capture. (Source: USGS)
    Range of values
    Minimum:4604734.580
    Maximum:4605457.917
    Units:meters
    Orthometric NAVD88
    Altitude of the UAS position at the time of each image capture relative to the NAVD88 vertical datum. (Source: None)
    Range of values
    Minimum:48.438
    Maximum:88.338
    Units:meters
    2022022FA_GSM_GPS.csv
    Ground control points and ground truthing positions, elevations, and attributes (Source: USGS)
    FAN
    USGS Field Activity Number (Source: USGS)
    ValueDefinition
    2022-022-FAYear, USGS ID, and Field Activity
    Date
    Calendar date of collection (Source: USGS)
    ValueDefinition
    2022:11:02YYYY:MM:DD
    Point ID
    Unique point identification number. (Source: Processor defined)
    Range of values
    Minimum:1
    Maximum:76
    GPS
    Type of point (Source: USGS)
    ValueDefinition
    RTKReal time kinematic data from the SP80 rover
    PropellerPropeller AeroPoint data
    Attributes
    Unique identifier for ground control points. Prefix AP-### refers to AeroPoint and the last 3 digits of its identifying code. The prefix V# is for Vinyl targets, GSM-RM is the local reference mark, and ground truthing points are ‘gt’. (Source: producer defined) Character string.
    Latitude NAD83[2011]
    Post-processed latitude position (NAD83[2011]). Positive values represent North coordinates. (Source: USGS)
    Range of values
    Minimum:41.58505341
    Maximum:41.58925941
    Units:decimal degrees
    Longitude NAD83[2011]
    Post-processed longitude position (NAD83[2011]). Negative values represent West coordinates. (Source: None)
    Range of values
    Minimum:-70.64466529
    Maximum:-70.63717855
    Units:decimal degrees
    Ellipsoid GRS 1980
    Post-processed height in relation to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:-29.010
    Maximum:-25.600
    Units:meters
    Easting 19N
    Post-processed UTM X-coordinate in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:362918.055
    Maximum:363534.849
    Units:meters
    Northing 19N
    Post-processed UTM Y-coordinate in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4605009.442
    Maximum:4605479.966
    Units:meters
    Orthometric NAVD88
    Post-processed Z-coordinate relative to NAVD88 with GEOID18 applied. (Source: USGS)
    Range of values
    Minimum:-0.303
    Maximum:3.105
    Units:meters
    2022022FA_GSM_YSM_LPC.laz
    UAS lidar point cloud in .LAZ file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. Point density is 841 points per square meter and point spacing is 0.034. (Source: producer defined)
    Elevation
    Surface elevation in EPSG:5703 using GEOID18. (Source: YellowScan CloudStation)
    Range of values
    Minimum:-0.868
    Maximum:19.027
    Units:meters
    2022022FA_GSM_YSM_SfM_PC.laz
    SfM dense point cloud in .LAZ file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. Point density is 505 points per square meter and point spacing is 0.044 m. (Source: producer defined)
    Elevation
    Surface elevation in EPSG:5703 using GEOID18. (Source: Agisoft Metashape)
    Range of values
    Minimum:-1.878
    Maximum:18.968
    Units:meters
    2022022FA_GSM_VX20_LPC.laz
    UAS lidar point cloud in .LAZ file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. Point density is 170 points per square meter and point spacing is 0.077 m. (Source: producer defined)
    Elevation
    Surface elevation in EPSG:5703 using GEOID18. (Source: YellowScan CloudStation)
    Range of values
    Minimum:-1.032
    Maximum:19.122
    Units:meters
    2022022FA_GSM_Ricoh_SfM_PC.laz
    SfM dense point cloud in .LAZ file format. This georeferenced point cloud was colorized using natural color RGB image values and is not classified. Point density is 333 points per square meter and point spacing is 0.055 m. (Source: producer defined)
    Elevation
    Surface elevation in EPSG:5703 using GEOID18. (Source: Agisoft Metashape)
    Range of values
    Minimum:-2.330
    Maximum:20.051
    Units:meters
    Entity_and_Attribute_Overview:
    The filenames are formatted as "2022022FA_GSM_sensor/product.*** ", where 2022022 is the USGS Field activity ID, location is Great Sippewissett Marsh (GSM), sensors are YellowScan Mapper (YSM), Yellow Scan VX20 (VX20), Ricoh GRII (Ricoh), and products include lidar point clouds (LPC) and structure from motion point clouds (SfM_PC).
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2022-022-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
    • Mark A. Bauer
    • Matthew A. Burgess
    • Jennifer M. Cramer
    • Sandra M. Brosnahan
    • Seth D. Ackerman
    • Alexandra D. Evans
  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 lidar and photogrammetry point clouds cover roughly the same area and will be used to compare different techniques to collect terrain data.

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: 27-Oct-2022 (process 1 of 6)
    GROUND CONTROL: The reference mark was established prior the field activity on October 27, 2022. A Parker-Kalon nail was hammered into the center of a cement post near the parking lot and occupied with a SP80 for three and a half hours. The GFILE off of the base was converted to RINEX format 2.11 and uploaded to OPUS after 24 hours had passed. The OPUS solution is provided unedited as a text file.
    Date: 02-Nov-2022 (process 2 of 6)
    GROUND CONTROL: Eight AeroPoint GCPs were spaced out over the field site and left on for at least 60 minutes to collect GNSS data. After collection the AeroPoints data were uploaded via a Wi-Fi connection and run through a post-processing kinematic algorithm of the CORS network to get corrected positions. A SP80 rover connected to MASS CORs was used to take ground truthing points in the marsh. 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 GEOID18 to produce easting and northing and orthometric heights. These were exported to a CSV file and named 2022022FA_GSM_GPS.csv.
    Date: 02-Nov-2022 (process 3 of 6)
    UAS FLIGHTS: The YellowScan Mapper (YSM) lidar sensor was a 905 nm wavelength Livox Horizon with a 70.4/ 4.5 degree horizontal and vertical field of view (FOV) and Applanix 15 inertial measurement unit. A configuration text file (CONFIG.TXT) that controls camera triggering height, the camera triggering interval, and the lidar scan pattern was pre-loaded onto a 256 GB USB thumb drive. The camera module is a SONY UMC - 10RC collecting at 20.4 megapixels (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 the thumb drive in three different files: (1) the IMUPGPS 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 IMUPGPS data in Applanix (Trimble) binary *.t04 format. The RGB images are saved to a 64 GB micro SD card as *.jpg files. The YellowScan VX20-100 lidar scanner consists of the Riegl minivux-1uav scanner and Applanix 20 inertial measurement unit. All sensors (YSM, VX20-100, and Ricoh) were attached to an DJI Matrice 600 Pro UAS with approved government edition firmware. The YSM lidar data were collected with the UAS flying at 10 m/s at 61 meters above ground level with north-south and east-west transect passes with the scan angle set to +41/-41 to cover a ~110 m swath. The camera module was set to take images every 2 seconds. The VX20-100 lidar data were collected with the UAS flying at 10 m/s at 61 meters above ground level with north-south and east-west transect passes with the scan angle set to +45/-45 to cover a ~110 m swath. The camera module was set to take images every 2 seconds. After the flight the lidar data were taken off the sensor. The Ricoh data were collected with the UAS flying at 10 m/s at 81 meters above ground level with north-south and east-west transect passes that achieve ~80% forelap and sidelap. Image sets were taken every 2 seconds. After the flight, the UAS was powered off, the SD card was removed, and all images and files relating to the survey were downloaded to a field computer.
    Note, the YSM photos were collected in EPSG:4326 (WGS84) The positions were converted to EPSG:6348 and EPSG:5703 in the imagery locations file (2022022FA_GSM_ImageryLocations.csv) and were accounted for when transforming to EPSG:6348 and EPSG:5703 in the products.
    Date: 31-Dec-2024 (process 4 of 6)
    RAW IMAGERY: All images were processed to add additional information required by the USGS to the Exchangeable Image File Format (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 internal Imagery Data System EXIF Guidance (see metadata contact for more information). 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 '2022022FA_f07r02_20221102T165822Z_IMG_####', 2022022FA is the field activity ID; f07 is the flight number; YSM is the camera on the YellowScan Mapper and r02 is the Ricoh; 20221102 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 IMG_#### is the original raw photo name appended to the end of the new filename. 3. Images are validated and uploaded onto the Imagery Data System based on sensor and image type.
    Date: 02-Sep-2024 (process 5 of 6)
    SfM PROCESSING: The two sets of imagery were processed in Agisoft Metashape 1.8.0 to produce point clouds following these general steps (see Over and others, 2021 for a more detailed SfM methodology explanation). 1. For each image type (Ricoh and YSM) a project was created and imagery was imported. 2. Photos were aligned at a low accuracy and then GCPs were automatically detected in the point cloud. GCP positions (AeroPoints and vinyl targets in 2022022FA_GSM_GPS.csv) were added to the project in the reference systems EPSG:6348 and EPSG:5703 using GEOID18. The horizontal and vertical accuracies for the GCPs were set to 0.01/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 5, and three 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, for each project multiple ‘chunks’ were created so that independent high quality dense clouds with a low-frequency filtering algorithm could be made. The dense point clouds were then edited by visual inspection to remove points with a low confidence near the edges and near water bodies. 5. The colorized dense point clouds were then exported as 2022022FA_GSM_YSM_SfM_PC.laz and 2022022FA_GSM_Ricoh_SfM_PC.laz. 6. Point clouds were then brought into Global Mapper and manually cleaned of points interpreted to be noise or are above a reasonable elevation threshold based on the surrounding features before the data were QA/QC’d with 3DEP, GCPs, and check points.
    Date: 02-Sep-2024 (process 6 of 6)
    LiDAR DATA: The lidar data were processed in YellowScan CloudStation software integrated with Trimble POSPac UAV 9.0. 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 was set to EPSG:6318. CloudStation flight trajectories were 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 LPCs, along with a strip adjustment between transect swaths using CloudStation's "robust" setting. The YSM LPC was colored by the YSM camera based on the photo timestamp. The LPCs were then brought into Global Mapper and manually cleaned of points interpreted to be noise or are above a reasonable elevation threshold based on the surrounding features before the data were QA/QC’d with 3DEP, GCPs, and check points. The LPCs were then exported as 2022022FA_GSM_YSM_LPC.laz and 2022022FA_GSM_VX20_LPC.laz. All files were exported in EPSG:6348 and EPSG:5703 using GEOID18. 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?
    GPS: The theoretical internal accuracy of the SP80 rover using Real-time Kinematic (RTK) positioning from the Continuously Operating Reference Systems (CORS) is 2 cm. Points that had a FIX were assumed to be within that tolerance. The AeroPoint ground control points (GCPs) have an internal reported variance provided in 2022022FA_GSM_GPS.csv, the global accuracy was calculated and reported below by adding the variance to two times the longest baseline distance. The GSM reference mark was established over four hours of occupation with a Trimble R8 and uploaded to the static Online Positioning User Service (https://geodesy.noaa.gov/OPUS/) and the solution is provided as 2022022FA_GSM_OPUS.txt.
    Imagery: The Rioch GRII image locations are based off of the Metashape project estimated positions after SfM processing. The SONY UMC-R10C image locations are derived from post processing kinematic positions using the drone observation file and the base station observation files.
    Lidar: Lidar point clouds (LPC) were corrected using the base station observation files and assessed using the GCPs and GPS ground truthing points. Note that lidar returns over water reflect the surface, not the bottom, whereas the structure from motion (SfM) does reconstruct a surface below the water.
  2. How accurate are the geographic locations?
    Images: The YSM images were geotagged with the post-processed lidar .T04 file and base station data and had an average xy accuracy of 0.02 m. The Ricoh images were tagged with the SfM best estimate after alignment and have an accuracy less than 1 meter.
    GPS: AeroPoint horizontal global accuracy is 3 cm.
    Lidar: The LPCs horizontal accuracy was assessed against positions of the AeroPoints in the point cloud intensity map. The horizontal accuracy is variable and within 20 cm.
  3. How accurate are the heights or depths?
    Images: The YSM images were geotagged with the post-processed lidar .T04 file and base station data and had an average vertical accuracy of 0.02 m. The Ricoh images were tagged with the SfM best estimate after alignment and have an accuracy less than 1 meter.
    GPS: AeroPoint vertical global accuracy is 3 cm.
    Lidar: The LPCs were assessed against the GCPs and the root mean square error (RMSE) (n=8) was 0.043 m for the YSM LPC, 0.019 m for the VX20 LPC, 0.030 m for the YSM SfM point cloud, and 0.055 m for the Ricoh SfM point cloud.
  4. Where are the gaps in the data? What is missing?
    Imagery: YSM and Ricoh cameras triggered every 2 seconds. Images not at the mapping altitude were removed from all sensors for file space. All of these removed images can account for the non-consecutive original file names and results in a total of 655 YSM images and 752 Ricoh GRII images.
  5. How consistent are the relationships among the observations, including topology?
    There were eight AeroPoints placed, four vinyl targets, and 63 ground truthing points. There were seven UAS flights. Flights 1-3 (15, 15, and 20 min) used the VX20-100 on the M600 to collect lidar in north-south and east-west transects. Flights 4-5 (16 and 15 min) used the YellowScan Mapper (YSM) on the M600 to collect true-color red green blue (RGB) images and lidar. Flights 6-7 (20 and 21 min) used a Ricoh GRII on the M600 to collect RGB images every 2 seconds. Images taken during the flight were renamed to have the flight number included, as the first three flights did not take images, the numbers start at flight 4 (f04).

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 Great Sippewissett Marsh includes the imagery, lidar data, and supporting GPS data.
  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: 17-Mar-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_P13PSF3S/2022022FA_GSM_metadata.faq.html>
Generated by mp version 2.9.51 on Tue Apr 1 09:58:14 2025