Aerial imagery from UAS survey of the intertidal zone at Puget Creek and Dickman Mill Park, Tacoma, WA, 2019-06-03

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

Frequently anticipated questions:

What does this data set describe?

Title:
Aerial imagery from UAS survey of the intertidal zone at Puget Creek and Dickman Mill Park, Tacoma, WA, 2019-06-03
Abstract:
This portion of the data release presents the raw aerial imagery collected during an Unmanned Aerial System (UAS) survey of the intertidal zone at Puget Creek and Dickman Mill Park, Tacoma, WA, on 2019-06-03. The imagery was acquired using a Department of Interior-owned 3DR Solo quadcopter fitted with a Ricoh GR II digital camera featuring a global shutter. The camera was mounted using a fixed mount on the bottom of the UAS and oriented in an approximately nadir orientation. The UAS was flown on pre-programmed autonomous flight lines at an approximate altitude of 50 meters above ground level (AGL), resulting in a nominal ground-sample-distance (GSD) of 1.3 centimeters per pixel. The flight lines were oriented roughly shore-parallel and were spaced to provide approximately 70 percent overlap between images from adjacent lines. The camera was triggered at 1 Hz using a built-in intervalometer. Flight F01 covered the Puget Creek area; flight F02 covered the Dickman Mill Park area. After acquisition, the images were renamed to include the flight number and acquisition time in the file name. The coordinates of the approximate image acquisition locations were added ('geotagged') to the image metadata (EXIF) using the telemetry log from the UAS onboard single-frequency autonomous GPS. The image EXIF were also updated to include additional information related to the acquisition. Although the images were recorded in both JPG and camera raw (Adobe DNG) formats, only the JPG images are provided in this data release. The data release includes a total of 1,171 JPG images. Images from takeoff and landing sequences were not used for processing and have been omitted from the data release. The images from each flight are provided in a zip file named with the flight number.
Supplemental_Information:
Additional information about the field activity from which these data were derived is available online at:
http://cmgds.marine.usgs.gov/fan_info.php?fan=2019-623-FA
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Logan, Joshua B., Grossman, Eric E., VanArendonk, Nathan R., and Horner, Liam, 20210222, Aerial imagery from UAS survey of the intertidal zone at Puget Creek and Dickman Mill Park, Tacoma, WA, 2019-06-03: data release DOI:10.5066/P9TJALC1, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Logan, Joshua B., Grossman, Eric E., VanArendonk, Nathan R., and Horner, Liam, 2021, Aerial imagery and structure-from-motion data products from UAS survey of the intertidal zone at Puget Creek and Dickman Mill Park, Tacoma, WA, June 2019: data release DOI:10.5066/P9TJALC1, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -122.4787
    East_Bounding_Coordinate: -122.4700
    North_Bounding_Coordinate: 47.2819
    South_Bounding_Coordinate: 47.2769
  3. What does it look like?
    https://www.sciencebase.gov/catalog/item/5ef51dd082ced62aaae69f0d?name=PugetCreekDickmanMill_raw_image_browse.jpg (JPEG)
    Example aerial images from the 2019-06-03 UAS survey.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 03-Jun-2019
    Currentness_Reference:
    ground condition at time data were collected
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: JPEG
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Raster data set. It contains the following raster data types:
      • Dimensions 3264 x 4352, type Pixel
    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.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257224.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: WGS84 Ellipsoid
      Altitude_Resolution: 0.01
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    There are no additional attributes besides the tags described in data quality section associated with these images.
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2019-623-FA

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Joshua B. Logan
    • Eric E. Grossman
    • Nathan R. VanArendonk
    • Liam Horner
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

These data were collected to characterize the morphology, substrate composition and roughness of intertidal areas to support modeling of coastal storm and wave impacts with sea-level rise as part of the USGS Puget Sound Coastal Storm Modeling System (PS-CoSMoS). The data are also intended to be used to model and evaluate sediment transport and its effects on coastal habitats, a focus of the USGS Coastal Habitats in Puget Sound Project (CHIPS) and its partners to inform resource management and adaptive planning for our Nation's coasts.

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: 03-Jun-2019 (process 1 of 2)
    Aerial imagery was collected using a Department of Interior-owned 3DR Solo quadcopter fitted with a Ricoh GR II digital camera featuring a global shutter. The camera was mounted using a fixed mount on the bottom of the UAS and oriented in an approximately nadir orientation. The UAS was flown on pre-programmed autonomous flight lines at an approximate altitude of 50 meters above ground level (AGL). The flight lines were oriented roughly shore-parallel and were spaced to provide approximately 70 percent overlap between images from adjacent lines. After the flight lines were completed some additional imagery was collected in manual flight mode to fill in additional areas and to collect redundant imagery with the camera sensor at different orientations to improve lens-model reconstruction. The camera was triggered at 1 Hz using a built-in intervalometer and was programmed to simultaneously acquire imagery in both JPG and camera raw (Adobe DNG) formats. Flight F01 covered the Puget Creek area and was conducted on 2019-06-03 between 18:43 and 18:54 Universal Coordinated Time (UTC) (11:43 and 11:54 Pacific Daylight Time (PDT)). Flight F02 covered the Dickman Mill Park area and was conducted on 2019-06-03 between 19:24 and 19:37 Universal Coordinated Time (UTC) (12:24 and 12:37 Pacific Daylight Time (PDT)). Before each flight, the camera’s digital ISO, aperture and shutter speed were manually set to adjust for ambient light conditions. Although these settings were changed between flights, they were not permitted to change during a flight; thus, the images from each flight were acquired with consistent camera settings. Person who carried out this activity:
    Joshua Logan
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Physical Scientist
    2885 Mission Street
    Santa Cruz, CA
    US

    831-460-7519 (voice)
    831-427-4748 (FAX)
    jlogan@usgs.gov
    Date: 2019 (process 2 of 2)
    The image files were renamed using a custom python script. The file names were formed using the following pattern Fx-YYYYMMDDThhmmssZ_Ryz.*, where: - Fx = Flight number - YYYYMMDDThhmmssZ = date and time in the ISO 8601 standard, where 'T' separates the date from the time, and 'Z' denotes UTC ('Zulu') time. - Ry = RA or RB to distinguish camera 'RicohA' from 'RicohB' - z = original image name assigned by camera during acquisition - * = file extension (JPG or DNG)
    The approximate image acquisition coordinates were added to the image metadata (EXIF) ('geotagged') using the image timestamp and the telemetry logs from the UAS onboard single-frequency 1-Hz autonomous GPS. The geotagging process was done using a custom Python script which processes the GPS data from the UAS telemetry log and calls the command-line 'exiftool' software. To improve timestamp accuracy, the image acquisition times were adjusted to true ('corrected') UTC time by comparing the image timestamps with several images taken of a smartphone app ('Emerald Time') showing accurate time from Network Time Protocol (NTP) servers. For this survey, +00:00:02 (2 seconds) were added to the image timestamp to synchronize with corrected UTC time. The positions stored in the EXIF are in geographic coordinates referenced to the WGS84(G1150) coordinate reference system (EPSG:7660), with elevation in meters relative to the WGS84 ellipsoid.
    Additional information was added to the EXIF using the command-line 'exiftool' software with the following command: exiftool ^ -P ^ -Copyright="Public Domain. Please credit U.S. Geological Survey." ^ -CopyrightNotice="Public Domain. Please credit U.S. Geological Survey." ^ -ImageDescription="Low-altitude aerial image of the intertidal zone at Puget Creek and Dickman Mill Park, Ruston Way, Tacoma, Washington, USA, from USGS survey 2019-623-FA" ^ -Caption-Abstract="Intertidal zone at Puget Creek and Dickman Mill Park, Ruston Way, Tacoma, Washington, USA, from USGS survey 2019-623-FA" ^ -Caption="Aerial image of the intertidal zone at Puget Creek and Dickman Mill Park, Ruston Way, Tacoma, Washington, USA, from USGS survey 2019-623-FA" ^ -sep ", " ^ -keywords="Marine Nearshore Intertidal, Puget Sound, Puget Creek, Dickman Mill Park, Ruston Way, Tacoma, Washington, 2019-623-FA, Unmanned Aircraft System, UAS, drone, aerial imagery, U.S. Geological Survey, USGS, Pacific Coastal and Marine Science Center" ^ -comment="Low-altitude aerial image from USGS Unmanned Aircraft System (UAS) survey 2019-623-FA" ^ -Credit="U.S. Geological Survey" ^ -Contact="pcmsc_data@usgs.gov" ^ -Artist="U.S. Geological Survey, Pacific Coastal and Marine Science Center" Person who carried out this activity:
    Joshua Logan
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    2885 Mission Street
    Santa Cruz, CA

    831-460-7519 (voice)
    jlogan@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 Ricoh GR II camera used to acquire these images produces a nominal image size of 16.2 megapixels in both JPG and camera raw (Adobe DNG) image formats. The image acquisition time stamp is recorded to the image metadata (EXIF) with a precision of 1 second. The UAS onboard GPS is a single-frequency autonomous receiver which records positions to the telemetry log at 1 second intervals, with an approximate accuracy of 3 meters horizontally and 10 meters vertically. The geotagging operation uses the image time stamp to derive the image acquisition location by finding the nearest location recorded at the time of acquisition. To reduce the potential for timing errors during the geotagging process, the image time stamps were adjusted to true ('corrected') UTC time by comparing the image time stamps with several images taken of a smartphone app ('Emerald Time') showing accurate time from Network Time Protocol (NTP) servers. For this survey, +00:00:02 (2 seconds) were added to the image time to synchronize with corrected UTC time. The adjusted time stamp was only used for geotagging; the original image time stamp was retained in the image EXIF and file name. The positions stored in the EXIF are in the WGS84 (G1150) coordinate reference system (EPSG:7660), with elevation in meters relative to the WGS84 ellipsoid.
  2. How accurate are the geographic locations?
    The horizontal positions stored in the EXIF image metadata were derived with a 'geotagging' process using the image time stamps and the uncorrected positions recorded in the telemetry log of the UAS from the onboard single-frequency autonomous GPS (mRobotics GPS u-Blox Neo-M8N / 3DR SOLO Upgrade). To reduce the potential for timing errors during the geotagging process, the image time stamps were adjusted to true ('corrected') UTC time by comparing the image time stamps with several images taken of a smartphone app ('Emerald Time') showing accurate time from Network Time Protocol (NTP) servers. The horizontal positions are estimated to be accurate to approximately 3 meters. However, it should be noted that for some images the error may exceed this estimate due to GPS errors or timing errors associated with the geotagging process.
  3. How accurate are the heights or depths?
    The vertical positions stored in the EXIF image metadata were derived with a 'geotagging' process using the image time stamps and the uncorrected positions recorded in the telemetry log of the UAS from the onboard single-frequency autonomous GPS (mRobotics GPS u-Blox Neo-M8N / 3DR SOLO Upgrade). To reduce the potential for timing errors during the geotagging process, the image time stamps were adjusted to true ('corrected') UTC time by comparing the image time stamps with several images taken of a smartphone app ('Emerald Time') showing accurate time from Network Time Protocol (NTP) servers. The horizontal positions are estimated to be accurate to approximately 10 meters. However, it should be noted that for some images the error may exceed this estimate due to GPS errors or timing errors associated with the geotagging process.
  4. Where are the gaps in the data? What is missing?
    Two flights (F01 and F02) were conducted during the survey. The imagery from each flight was stored separately, and the flights were renamed for organizational purposes. The camera shutter was triggered at 1 Hz by an internal intervalometer which was started before takeoff and stopped after landing. Images from the takeoff and landing sequences were not used in data processing and are not included in this data release.
  5. How consistent are the relationships among the observations, including topology?
    Photographs were renamed using a custom python script to include flight number, image acquisition date and time in Universal Coordinated Time (UTC), camera ID, and original image ID number. The image EXIF were also updated to include additional information related to the acquisition. Some photographs may be auto-rotated by certain viewing software, but the original image orientation is the same for all 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:
USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originator(s) of the dataset and in products derived from these data. This information is not intended for navigation purposes.
  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
    United States

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? The aerial images from two flights conducted during the UAS survey are available in JPG format. The images from each flight are combined into a zip file with the flight number in the file name.
  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 on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    The downloadable data files are available in zipped JPG file format. Image processing and viewing software can be used to open and view the files.

Who wrote the metadata?

Dates:
Last modified: 22-Feb-2021
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/ScienceBase/DR_P9TJALC1/PugetCreek_DickmanMillPark_2019-06-03_aerial_imagery_metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:17:34 2021