Low-altitude aerial imagery collected from a kite at Head of the Meadow Beach, Truro during field activity 2020-015-FA on March 6, 2020

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

Frequently anticipated questions:

What does this data set describe?

Title:
Low-altitude aerial imagery collected from a kite at Head of the Meadow Beach, Truro during field activity 2020-015-FA on March 6, 2020
Abstract:
The data in this release map the beach and nearshore environment at Head of the Meadow Beach in Truro, MA and provide environmental context for the camera calibration information for the 2019 CoastCam installation that looks out at the coast shared by beachgoers, shorebirds, seals, and sharks. This is related to the field activity 2020-015-FA and a collaboration with the National Park Service at Cape Cod National Seashore to monitor the region that falls within the field of view of the CoastCam, which are two video cameras aimed at the beach. On March 4, 6, and 10, 2020, U.S Geological Survey and Woods Hole Oceanographic Institution (WHOI) scientists conducted field surveys to collect position and orientation information for the CoastCam cameras and map the field of view. Elevation data were collected using a real time kinematic – satellite navigation system (RTK-GNSS) receiver attached to a pole and walked on the beach. Point data of the beach face were collected along transects and at periodic locations of plywood targets moved throughout the day within the CoastCam view. Grain-size analysis was performed on sediment samples collected with a spade along multiple profiles from the bluff base to the intertidal zone. Images of the beach were taken with a camera (Ricoh GRII) and a post-processed kinematic (PPK) system attached to a kitesurfing kite, and high-precision targets (AeroPoints) were used as ground control points. Bathymetry was collected in the nearshore using a single-beam echosounder mounted on a surf capable self-righting electric autonomous survey vehicle. Agisoft Metashape (v. 1.6.1) was used to create a digital elevation model with the collected imagery and this was merged with the bathymetry in MatLab (v. 2020) to create a continuous topobathy product.
Supplemental_Information:
For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/fan_info.php?fan=2020-015-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 2021, Low-altitude aerial imagery collected from a kite at Head of the Meadow Beach, Truro during field activity 2020-015-FA on March 6, 2020: data release DOI:10.5066/P9KSG1RQ, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Sherwood, C., Traykovski, P., Over, J., Borden, J., Brosnahan, S., Marsjanik, E., and Martini, M., 2021, Topographic and bathymetric data, sediment samples, and imagery collected at Head of the Meadow Beach, Truro in March 2020, U.S Geological Survey Field Activity 2020-015-FA: data release DOI:10.5066/P9KSG1RQ, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Over, J.R., Sherwood, C.R., Traykovski, P., Brosnahan, S.M., Martini, M.A., Marsjanik, E., Borden, J., 2021, Topographic and bathymetric data, sediment samples, and beach imagery collected at Head of the Meadow, Truro in March 2020, U.S Geological Survey Field Activity 2020-015-FA: U.S Geological Survey data release, https://doi.org/10.5066/P9KSG1RQ.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.07913475
    East_Bounding_Coordinate: -70.07551904
    North_Bounding_Coordinate: 42.05311493
    South_Bounding_Coordinate: 42.05026525
  3. What does it look like?
    2020015FA_Truro_beachimages_browse.JPG (JPG)
    Example still image of Head of the Meadow Beach, Truro MA
    2020015FA_Truro_CameraGNSS_browse.JPG (JPG)
    Photograph showing how the Camera is connected to the GNSS receiver on a plastic flange.
    2020015FA_Truro_KiteCameraAttachment_browse.JPG (JPG)
    Photograph shoing how the camera, GNSS, and antenna configuration attaches to the kitesurfing kite pole.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 06-Mar-2020
    Ending_Date: 06-Mar-2020
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: digital files
  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?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.00000001. Longitudes are given to the nearest 0.00000001. Latitude and longitude values are specified in Decimal degrees. 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?
    2020015FA_Truro_f1_photolocations.csv contains 719 data records and 2020015FA_Truro_f2_photolocations.csv contains 313 data records
    The CSV files, within the zip file, contain the post-processed kite navigation GNSS data (approximate position of the camera at the moment of each image capture). The following attributes are treated as if both CSV files in the zip are merged. (Source: USGS)
    ImageName
    File names of individual images, see the Data_Quality_Information and Process_Description for file naming convention. (Source: USGS) Character string.
    UTCTime
    Time in HH:MM:SS of each corrected camera position in coordinated universal time (UTC). (Source: Processor defined)
    Range of values
    Minimum:16:58:31
    Maximum:18:59:39
    Latitude
    Post-processed interpolated latitude of kite GNSS antenna position based on time of each image capture, in decimal degrees (NAD83(2011)). (Source: USGS)
    Range of values
    Minimum:42.05026576
    Maximum:42.05311101
    Units:decimal degrees
    Longtitude
    Post-processed interpolated longitude of kite GNSS antenna position based on time of each image capture, in decimal degrees (NAD83(2011)). (Source: None)
    Range of values
    Minimum:-70.07551904
    Maximum:-70.07913481
    Units:decimal degrees
    H_Ell_m
    Post-processed height in meters of kite GNSS antenna position based on time of each image capture based on the reference ellipsoid. (Source: None)
    Range of values
    Minimum:-8.485
    Maximum:27.118
    Units:meters
    Northing
    Post-processed interpolated X-coordinate of kite GNSS antenna position based on time of each image capture, in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4655917.663
    Maximum:4656235.569
    Units:meters
    Easting
    Post-processed interpolated Y-coordinate of kite GNSS antenna position based on time of each image capture, in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:410701.803
    Maximum:410999.635
    Units:meters
    H_Ortho_m
    Post-processed interpolated Z-coordinate of kite GNSS antenna position based on time of each image using NAVD88 correction with Geoid 12B. (Source: USGS)
    Range of values
    Minimum:18.9684
    Maximum:54.6720
    Units:meters
    Entity_and_Attribute_Overview:
    The images are also divided into two groups based on the flight number. The zip file 2020015FA_Truro_f1.zip contains 719 images from flight 1 and 2020015FA_Truro_f2.zip contains 313 images from flight 2. The attributes Latitude, Longitude, and UTCTime are included in the image headers as GPSLatitude, GPSLongitude, and GPSTimeStamp, respectively. A GPSMapDatum header is also included in the images that specifies the latitude and longitude are in NAD83(2011).
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2020-015-FA

Who produced the data set?

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

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

Why was the data set created?

These RGB 3-band images were collected of the waterline, beach, and bluffs with sufficient overlap to produce structure-from-motion photogrammetry products to create a model of Head of the Meadow Beach.

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: 06-Mar-2020 (process 1 of 3)
    These JPG images were collected with a camera (Ricoh GRII HD) labeled 'r##', where 'r' indicates a Ricoh camera, and the following 2 digits normally indicate the camera ID. The camera was wired to the GNSS receiver and duct taped to a PVC flange (2020015FA_Truro_CameraGNSS_browse.JPG), which was mounted with the multi-band GNSS antenna on the back of the camera on an 11 meter Ozone Enduro V2 kitesurfing kite (2020015FA_Truro_KiteCameraAttachment_browse.JPG) for the first flight and then switched to a 9 meter Ozone Reo V5 kite for the second flight when the wind picked up. The kites were on a 50 meter string and Ozone Contact Water V4 control bar, the latter which was walked down the beach. The camera orientation for all flights was oblique based on the nature of maintaining control of the kite. Horizontal positions and elevations of each image (2020015FA_Truro_f1_photolocations.csv and 2020015FA_Truro_f2_photolocations.csv) were recorded from an GNSS receiver (EMLID Reach M2), which were processed in PPK mode with a base station (JAVAD Triumph-1). The navigation data is added to the image EXIF information after the flight as described in the process steps. These JPG images may be used with photogrammetric software to produce geolocated point clouds, digital elevation models, orthomosaics, and other products. It is recommended when using the software to also use the navigation positions and the Aeropoint locations (see larger work citation Navigation: 2020015FA_Truro_nav_AeroPoints.csv) as ground control points. Note that not all images may align when processed in photogrammetry software.
    Date: 13-Mar-2020 (process 2 of 3)
    The GNSS navigation data was processed in Inertial Explorer (https://novatel.com/products/waypoint-software/inertial-explorer, version 8.70.8722). In the software, the data were processed using an 'Antenna Height' of 0.0 m to indicate that there was no offset from the camera. The positions were processed in the NAD83(2011) datum, providing the Latitude, Longitude, and H_Ell_m attributes and then Geoid 12B was applied using NAVD88 as the vertical datum in the UTM Zone 19N to produce the Northing, Easting, and H_Ortho_m attributes.
    All of the attributes here are provided in the 2020015FA_Truro_f1_photolocations.csv and 2020015FA_Truro_f2_photolocations.csv but only the latitude and longitude are put in the image EXIF data with the horizontal datum. Person who carried out this activity:
    Peter Traykovski
    Woods Hole Oceanographic Institute
    Associate Scientist
    226 Woods Hole Rd, MS #12
    Woods Hole, MA

    508-289-2638 (voice)
    ptraykovski@whoi.edu
    Date: 01-Mar-2021 (process 3 of 3)
    The images acquired with the camera were geotagged and 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 geotag each photo with the GPSDateStamp, GPSTimeStamp, GPSLatitude, and GPSLongitude with the command: exiftool -csv=directoryname\EXIF_tags.csv ; where the CSV file has the following headings and information (anything in () is format based and is only provided to give more context) -Credit="U.S. Geological Survey " -Contact="WHSC_data_contact@usgs.gov " -Copyright="Public Domain " -ImageDescription="Photographs of Head of the Meadow Beach, Truro, Massachusetts, USA from USGS field survey 2020-015-FA " -Attribution="https://doi.org/10.5066/P9KSG1RQ " -Event="USGS Field Activity 2020-015-FA " -GPSAreaInformation="position post-processed from nearby GPS " -GPSMapDatum="ESPG: 6317 (NAD83(2011)) " -GPSDateStamp="2020:03:06 " -GPSTimeStamp="(HH:MM:SS) " -GPSLatitude="(in decimal degrees) " -GPSLatitudeRef="N " -GPSLongitude="(in decimal degrees)" -GPSLongitudeRef="W " -Artist="Peter Traykovski (WHOI)" -Comment="flight number # of 2 (where # is either 1 or 2) " -OriginalFilename="M#######.JPG (where # combinations are unique) " *.JPG
    Keywords were added with the following exiftool -sep ", " -iptc:keywords="Head of the Meadow Beach, Massachusetts, 2020-015-FA, Ricoh, USGS, aerial imagery" *.JPG
    To read out the photo information to a csv the command is exiftool -csv -f -filename -GPSDateStamp -GPSTimeStamp -GPSLongitude -GPSLatitude -n -Artist -Contact -Comment -Credit -Copyright -ImageDescription -OriginalFileName -AttributionURL -Event -GPSAreaInformation -GPSMapDatum *.JPG > directoryname/out.csv Fewer tags or additional tags may be taken out with this command from those written above.
    2. All the JPG images were renamed with Namexif 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 a field survey ID prefix; a flight number and ID that distinguishes among USGS cameras by make, model, and camera number; the image acquisition date and coordinated universal time (UTC) in ISO8601 format, and a suffix with the original image name. For example, image name '2020015FA_f01r02_20200306T165822Z_M1040356.JPG', 2020015FA is the survey ID, f01 is the flight number, r02 is the internal camera ID, 20200306 is the UTC date in the format YYYYMMDD. A 'T' is used to separate UTC date from UTC time in format HHMMSS followed by a Z, and M1040356.JPG is the original raw photo name appended to the end of the new filename. Person who carried out this activity:
    Jin-Si Over
    U.S. Geological Survey
    Geographer
    U.S. Geological Survey
    Woods Hole, MA

    508-548-8700 x2269 (voice)
    jover@usgs.gov
  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?
    The camera (Ricoh GRII HD) used on the kite acquires photos at 16.2 Megapixels, with file sizes generally between 4 and 6 MB on disc, depending on image complexity. The GPS used on the kite has theoretical vertical and horizontal accuracies of 5 meters.
  2. How accurate are the geographic locations?
    Though the images do not represent spatial data, the spatial information is available in the EXIF header of each image, which is derived from the provided kite navigation files (2020015FA_Truro_f1_photolocations.csv and 2020015FA_Truro_f2_photolocations.csv). The location information was acquired from a GNSS receiver (EMLID Reach M2) in PPK mode with a Multi-band GNSS antenna and hotshoe adapter with an estimated horizontal accuracy of 5 m.
  3. How accurate are the heights or depths?
    Though the images do not represent spatial data, the spatial information is available in the EXIF header of each image, which is derived from the provided kite navigation files (2020015FA_Truro_f1_photolocations.csv and 2020015FA_Truro_f2_photolocations.csv). The location information was acquired from a GNSS receiver (EMLID Reach M2) in PPK mode with a multi-band GNSS antenna and hotshoe adapter with an estimated vertical accuracy of 5 m.
  4. Where are the gaps in the data? What is missing?
    Two flights were conducted to map the Head of the Meadow Beach shoreline and bluff face in Truro, MA, on March 6, 2020. Photographs were captured every 5 seconds. Photos were removed for quailty control purposes if they were considered to be useless for photogrammetry purposes (taken when landing or raising the kites), this may explain the nonconsecutive unique image names. All photos included have location information. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Two flights, separated by 35 minutes, were flown at a target elevation of 40-50 m. The first flight, consisting of 719 images, was flown with the camera facing southeast towards the bluff at a low oblique angle and overlap was achieved by zigzagging from the ocean to the beach from the southeast to the northwest. The second flight, consisting of 313 images was flown with the camera facing northwest towards the beach and ocean with one pass alongshore at a higher oblique angle before resuming a pattern and angle similar to the first flight. There are a total of 1,032 JPG images.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None
Use_Constraints:
Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey (USGS) as the source of this information.
  1. Who distributes the data set? (Distributor 1 of 1)
    Jin-Si Over
    U.S. Geological Survey
    geographer
    U.S. Geological Survey
    Woods Hole, MA

    508-548-8700 x2269 (voice)
    jover@usgs.gov
  2. What's the catalog number I need to order this data set? The Windows 10 zip file 2020015FA_Truro_imagery.zip has the following files: the 2020015FA_Truro_f1.zip contains 719 JPG images, the 2020015FA_Truro_f2.zip contains 313 JPG images (where f# indicates the flight number), the kite PPK navigation files 2020015FA_Truro_f1_photolocations.csv and 2020015FA_Truro_f2_photolocations.csv, the photographs 2020015FA_Truro_CameraGNSS_browse.JPG and 2020015FA_Truro_KiteCameraAttachment_browse.JPG.
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    Use of these files requires software capable of opening JPG images and, if desired, capable or reading the associated EXIF information. Additionally, the location information is provided in CSV files for the user to utilize with appropriate software.

Who wrote the metadata?

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

508-548-8700 x2269 (voice)
jover@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/field_activities/2020_015_fa/2020015FA_Truro_imagery.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:16 2021