Elwha PlaneCam - aerial imagery and derivatives from Elwha River (WA) flight on August 26th, 2013

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

Frequently anticipated questions:

What does this data set describe?

Title:
Elwha PlaneCam - aerial imagery and derivatives from Elwha River (WA) flight on August 26th, 2013
Abstract:
This is a set of 642 primarily near-nadir aerial photogrammetric images and their derivatives, collected from the Elwha River, WA, with an intervalometer-triggered digital camera from a crewed light aircraft, for processing using structure-from-motion photogrammetry and machine learning to study coastal geomorphic processes, primarily during and after dam removal on the Elwha River, at high temporal and spatial resolution. JPG files in each folder follow the following naming convention: {YYYYMMDDHHMMSS}_{SN###}_{PreservedFileName}.jpg, where {YYYYMMDDHHMMSS} is the image acquisition time in {YearMonthDayHourMinuteSecond} expressed in 24-hour time, as recorded by the camera’s internal clock or subsequently adjusted and written to the DateTimeOriginal field in the image EXIF data, {SN###} is the last 3 digits of the camera serial number OR 000 in the case the camera doesn't have a serial number, preceded by the letters “SN”, and {PreservedFileName} is the original filename recorded at the time the image was captured. For example, 20120319123426_SN000_IMG_1082.JPG would be the filename for an image with a DateTimeOriginal EXIF time/date stamp of March 19th, 2012, at 12:34:26 pm in Pacific Standard Time (PST) - See attribute accuracy report in platform metadata for details on time accuracy.
Supplemental_Information:
Additional information about the field activities from which these data were derived is available online at: https://cmgds.marine.usgs.gov/fan_info.php?fan=2012-603-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?
    Ritchie, Andrew C., 20250409, Elwha PlaneCam - aerial imagery and derivatives from Elwha River (WA) flight on August 26th, 2013: data service DOI:10.5066/P9M3NYWI, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Ritchie, A.C., 2025, Elwha PlaneCam - aerial imagery and derivatives from Elwha River (WA) flight on March 19th, 2012, in Remote Sensing Coastal Change Simple Data Distribution Service: U.S. Geological Survey data service, accessed [MMMM d, YYYY], at https://doi.org/10.5066/P9M3NYWI. [Data directly accessible at https://cmgds.marine.usgs.gov/data-services/rscc/Elwha_PlaneCam/20120319_Elwha_River/]
    This is part of the following larger work.

    Ritchie, Andrew C., Triezenberg, Peter J., Warrick, Jonathan A., Hatcher, Gerald A., and Buscombe, Daniel D., 20230221, RSCC Simple Data Distribution Service: data service DOI:10.5066/P9M3NYWI, U.S. Geological Survey - Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Ritchie, A.C., Triezenberg, P.J., Warrick, J.A., Hatcher, G.A., and Buscombe, D.D., 2023, Remote Sensing Coastal Change Simple Data Distribution Service: U.S. Geological Survey data service, https://doi.org/10.5066/P9M3NYWI
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -123.6142945
    East_Bounding_Coordinate: -123.5186166
    North_Bounding_Coordinate: 48.1510482
    South_Bounding_Coordinate: 47.9278308
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 26-Aug-2013
    Beginning_Time: 135421
    Ending_Date: 26-Aug-2013
    Ending_Time: 144700
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
  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.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:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    There are no additional attributes besides the embedded EXIF tags associated with these images
    Entity_and_Attribute_Detail_Citation: {USGS_FAN}

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Andrew C. Ritchie
  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?

Recording ground condition at a high temporal and spatial resolution for processing using structure-from-motion photogrammetry and machine learning to study fluvial and coastal geomorphic processes at high temporal and spatial resolution and to improve our understanding of earth surface processes (natural hazards) affecting coastal resources, primarily with regard to the Elwha River response to dam removals.

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: 31-Dec-1999 (process 1 of 7)
    Acquisition -- Aerial imagery was collected using a DOI-contracted aircraft operated by Rite Bros. Aviation. Cameras were mounted in wing inspection plates and triggered with internal software intervalometers to capture imagery. Images were acquired in jpg format. Any position data are added in post-processing and not natively collected, derived through photogrammetry and/or ground-control. Data sources produced in this process:
    • raw imagery
    • raw GNSS data
    Date: 2024 (process 2 of 7)
    Image renaming -- Raw Images are renamed using Phil Harvey's EXIFTOOL with the following command: exiftool -P -r -f -api missingtagvalue="000" -d %Y%m%d%H%M%S "-filename<${DateTimeOriginal}_SN${SerialNumber;$_=substr($_,-3)}_${PreservedFileName;s/\.\w*$//}.%e" -ext jpg . files follow the following naming convention: {YYYYMMDDHHMMSS}_{SN###}_{PreservedFileName}.jpg, where {YYYYMMDDHHMMSS} is the image acquisition time in {YearMonthDayHourMinuteSecond} expressed in 24-hour time, as recorded by the camera’s internal clock or subsequently adjusted and written to the DateTimeOriginal field in the image EXIF data, {SN###} is the last 3 digits of the camera serial number OR 000 in the case the camera doesn't have a serial number, preceded by the letters “SN”, and {PreservedFileName} is the original filename recorded at the time the image was captured. For example, 20120319123426_SN000_IMG_1082.JPG would be the filename for an image with a DateTimeOriginal EXIF time/date stamp of March 19th, 2012, at 12:34:26 pm in Pacific Standard Time (PST) - See attribute accuracy report in platform metadata for details on time accuracy.
    Date: 2024 (process 3 of 7)
    Image QA/QC -- original and renamed images are counted, and the beginning and end of the survey are reviewed to cull extraneous images such as images before takeoff and after landing (see logical consistency section for details). Corruped images are identified using ImageMagick with GNU Parallel. #example command to identify corrupt images: find . -iname "*.jpg"| parallel magick identify -regard-warnings {} >> magick_log.txt 2>>magic_err_log.txt If corrupted images are found, they are replaced from backup sources created when downloading imagery if possible. If corrupted images are not recoverable (for example, original imagery is corrupt) the images are deleted. Note that images of water and sky captured on turns are typically retained in this dataset.
    Date: 2024 (process 4 of 7)
    Position data processing -- because source data are not georeferenced, position data are only derived through ground control (GCPs), or 4D SfM when imagery is coaligned with imagery containing GNSS coordinates (Such as the PCMSC PlaneCam). When collected, GNSS data are post-processed to derive the precise position of ground control points, check points, and/or the GNSS antenna at the time of image acquisition. If necessary for rapid processing, approximate (PROVISIONAL) positions are produced from rapid ephemeris data. After precise ephemerides are available, GNSS data are post-processed to calculate GNSS trajectory, and precise positions are derived from station occupations or event marks recorded with precision timing, placed along the GNSS trajectory. Processing workflows, accuracy estimates, software and version are detailed in GNSS metadata. Camera and ground control positions are post-processed together with images, camera lever arm data and photogrammetric software to derive accurate camera position and pose.
    Date: 2024 (process 5 of 7)
    Photogrammetric Processing -- 3D or 4D structure-from-motion (SfM) processing, as described in Over and others (2021) and Warrick and others (2017), is used to derive camera positions for surveys missing position data if necessary. This processing is done with reduced accuracy to provide approximate location only.
    Date: 2024 (process 6 of 7)
    Imagery EXIF coordinates reconciliation -- Note that EXIF camera positions are not intended to be suitable accuracy for precise photogrammetric surveys, but they are used to populate the EXIF metadata field and locate the image in space relative to other images for reference purposes. GNSS/SfM position data published separately from images should be used for SfM reconstruction if available. CAMERA POSITIONS ARE NOT NECESSARILY PRESENT OR ACCURATE IN EXIF DATA. For this platform, no positions are recorded initially, and if added, the positions may not be the definitive set. Depending on availability of position data, coordinates for image EXIF position data are recorded as follows, with the appropriate indicator written to the EXIF:GPSAreaInformation tag: 1) If no position data are calculated, the EXIF:GPSAreaInformation tag will be blank/absent 2) If image positions have been calculated using 4D_sfm- or GCP-derived photogrammetry, EXIF:GPSAreaInformation="structure-from-motion" 3) If a sequence of images are unaligned from photogrammetry, but can be interpolated (for example, on a turn between lines), EXIF:GPSAreaInformation="interpolated" 4) If a sequence of images are unaligned from photogrammetry at the beginning or end of a flight, they will be extrapolated to the estimated takeoff location, EXIF:GPSAreaInformation="interpolated"
    Date: 2024 (process 7 of 7)
    Image EXIF annotation -- Additional information was added to individual image EXIF tags using the command-line 'exiftool' software with the following command, as appropriate: #tags for provisional data exiftool ^ -P ^ -IPTC:Credit="U.S. Geological Survey" ^ -IPTC:Contact="pcmsc_data@usgs.gov" ^ -EXIF:Copyright="Public Domain" ^ -XMP:UsageTerms="These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data." ^ -overwrite_original *.JPG #tags for approved data exiftool ^ -P ^ -IPTC:Credit="U.S. Geological Survey" ^ -IPTC:Contact="pcmsc_data@usgs.gov" ^ -EXIF:Copyright="Public Domain" ^ -XMP:UsageTerms="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." ^ -EXIF:ImageDescription="[single_image_EXIF_desc]" ^ -XMP:AttributionURL="https://doi.org/10.5066/P9M3NYWI ^ -EXIF:GPSAreaInformation="[position_method]" ^ -EXIF:GPSMapDatum="EPSG:4326 (WGS 84)" ^ -overwrite_original *.JPG tags were then duplicated to XMP headers to increase tag compatibility for image viewing software with the following exiftool command #tag duplication per phil harvey exiftool ^ -P ^ "-XMP-photoshop:Credit<IPTC:Credit" ^ "-XMP-iptcCore:CreatorWorkEmail<IPTC:Contact" ^ "-XMPdc:Rights<EXIF:Copyright" ^ "-XMP-dc:Description<EXIF:ImageDescription" ^ "-XMP-exif:all<GPS:all" ^ "-XMPexif:GPSLatitude<Composite:GPSLatitude" ^ "-XMP-exif:GPSLongitude<Composite:GPSLongitude" ^ "-XMPexif:GPSDateTime<Composite:GPSDateTime" ^ "-XMP-photoshop:DateCreated<EXIF:DateTimeOriginal" ^ "-XMPxmp:ModifyDate<EXIF:ModifyDate" ^ "-XMP-dc:Creator<EXIF:Artist" ^ "-XMP-tiff:Make<EXIF:Make" ^ "-XMPtiff:Model<EXIF:Model" ^ -overwrite_original *.JPG
  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.

    Online Links:

    Warrick, Jonathan A., Ritchie, Andrew C., Adelman, Gabrielle, Adelman, Kenneth, and Limber, Patrick W., 20170101, New Techniques to Measure Cliff Change from Historical Oblique Aerial Photographs and Structure-from-Motion Photogrammetry.

    Online Links:

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

  1. How well have the observations been checked?
    Camera EXIF position data are not present unless added after the flight and are annotated in the EXIF:GPSAreaInformation field with position source. See platform metadata for details
  2. How accurate are the geographic locations?
    A formal accuracy assessment has not been conducted. High-precision positions, when available, are published as a flight derivative product with separate metadata describing their derivation and accuracy.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Data are considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details, and to examine EXIF data for individual flights to determine camera settings such as exposure mode and shutter speed.
  5. How consistent are the relationships among the observations, including topology?
    RGB values are 8-bit, generally not saturated or underexposed. In a few cases of high or low light conditions, some imagery may be under- or over-exposed.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
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.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? Downloadable data in JPEG format. Each JPG file corresponds to a single 3-band 24-bit RGB image with EXIF data locating the image in space and time and describing acquisition parameters including but not limited to camera model, camera settings, lens information, image conversion parameters, and environmental conditions.
  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?
    Downloadable data files are available in a standard image file format. Image processing and viewing software can be used to open and view the files.

Who wrote the metadata?

Dates:
Last modified: 09-Apr-2025
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/DataServices/rscc/Elwha_PlaneCam/20130826_Elwha_River.faq.html>
Generated by mp version 2.9.51 on Fri May 9 14:39:01 2025