Elwha PlaneCam – Aerial imagery and derivatives from periodic and event-response surveys of the Elwha River, Olympic Mountains, and Washington Coast

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 periodic and event-response surveys of the Elwha River, Olympic Mountains, and Washington Coast
Abstract:
This is a collection of aerial oblique and near-nadir images, ancillary data, and derivatives, from aerial surveys of coastal and near-coastal environments with a crewed light aircraft using the "Elwha PlaneCam" system which consists of one or two cameras mounted in the wing inspection plate(s) of a Cessna 172 flown by Rite Bros. Aviation on flights coordinated through the Department of the Interior's (DOI) Office of Aviation Services (OAS), Olympic National Park, and/or USGS Pacific Coastal and Marine Science Center. Cameras were programmed to take pictures at a set interval. Camera hardware has no GPS capability, and cameras changed through time due to equipment failures and technological progress. Data are collected and produced primarily for monitoring the Elwha River and shoreline response to dam removal using structure-from-motion (SfM) photogrammetry, although a few collections were performed in other areas as opportunities/needs arose. The purpose of this system is to capture ephemeral responses to environmental perturbation at a frequency that improves our understanding of the processes driving both short- and long-term changes in response to one of the largest dam removals in history. These data are being published consistent with U.S. Geological Survey (USGS) Fundamental Science Practices (FSP) in the spirit of producing timely best science. Data products from the Elwha PlaneCam are published in a directory structure with one folder per survey, and within that folder, one folder per product. A process step or steps in metadata for each product describe naming conventions and methodology for each product. A detailed description of methods and naming conventions can be found in the Entity and Attribute Overview and Process Steps of this metadata record.
Supplemental_Information:
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., and Warrick, Jonathan A., 20250420, Elwha PlaneCam – Aerial imagery and derivatives from periodic and event-response surveys of the Elwha River, Olympic Mountains, and Washington Coast: 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., Winter, B.D., and Warrick, J.A., 2025, Elwha PlaneCam – Aerial imagery and derivatives from periodic and event-response surveys of the Elwha River, Olympic Mountains, and Washington Coast, 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
    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.

    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: -124.8157
    East_Bounding_Coordinate: -123.3545
    North_Bounding_Coordinate: 48.4292
    South_Bounding_Coordinate: 46.2179
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 19-Mar-2012
    Ending_Date: Present
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: application/service
  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?
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    This metadata record describes characteristics of an aerial data collection platform (DCP), and the organization and processing steps for data collected from that platform. Data are organized by directory with each directory (folder) corresponding to a single collection effort. Product types (raw imagery, derivatives, and any ancillary products) for each collection effort are organized in subfolders with associated metadata and are populated as data are processed. In some cases, multiple versions or formats of a product may be released, including emergency and provisional data subject to change. Process steps in metadata for each product describe naming conventions, methods, and disclaimers. Directory structure for each survey uses the following naming convention: {YYYYMMDD}_{SurveyDescriptor}[_{SurveyDescriptor}[_{SurveyDescriptor}], where {YYYYMMDD} is the abbreviation for the date the survey occurred and {SurveyDescriptor} is a unique name or names for the survey type (for example “coastal”, or “Elwha_River”) (for example 20130804_Elwha_River_aborted would be the abbreviation for a survey on August 4th, 2020 of the Elwha River which was aborted).
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

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
    • Jonathan A. Warrick
  2. Who also contributed to the data set?
    This data collection was initially started while the author was working as the Project Hydrologist for the Elwha River Restoration Project and continued with the support of the USGS Remote Sensing Coastal Change Project after FY 2016. The collection would not have been possible without the ingenuity and efforts of Jeff Wells of Rite Bros. Aviation, and the financial support of the Elwha River Restoration Project, Olympic National Park, and the Bureau of Reclamation Technical Service Center.
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    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 are provided in an effort to record ground conditions at a high temporal and spatial resolution, and after high-magnitude disturbance events, to improve our understanding of earth surface processes (natural hazards) affecting coastal resources. This platform was developed during the Elwha Restoration Project and has primarily focused on collecting imagery of the Elwha River in 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: Not complete (process 1 of 8)
    Acquisition -- Each image is acquired in Joint Photographic Experts Group (JPEG or JPG) format. Cameras are triggered by an internal intervalometer, either implemented through firmware modifications or using the camera's original software. Camera models are recorded in the EXIF data. Data sources produced in this process:
    • raw imagery
    • raw GNSS data
    Date: Not complete (process 2 of 8)
    Image renaming -- Raw Images are renamed using Phil Harvey's EXIFTOOL (https://exiftool.org) with the following two commands: #first save original filename exiftool -r -P -overwrite_original "-XMP:PreservedFileName<Filename" "-XMP:Title<Filename" "-IPTC:ObjectName<Filename" -ext jpg . #next write the new name 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 attrute accuracy report for details on time accuracy).
    Date: Not complete (process 3 of 8)
    Image reconciliation -- renamed images are compared with Aircraft Use Reports, and date and time are corrected to the flight date and Pacific Standard Time, then corrections are applied to the EXIF data of all relevant images using Phil Harvey's EXIFTOOL (https://exiftool.org) and they are renamed again to incorporate the proper date into the filename
    Date: Not complete (process 4 of 8)
    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: Not complete (process 5 of 8)
    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: Not complete (process 6 of 8)
    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: Not complete (process 7 of 8)
    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, and to produce camera models, camera orientation information, point clouds, surface models, depth maps, and orthocorrected imagery. SfM products are released with metadata detailing processing steps and workflows.
    Date: Not complete (process 8 of 8)
    Machine Learning -- Machine learning techniques as described in Buscombe and others (2022) and Buscombe and Goldstein (2022) are used to build, train and evaluate models, and generate labeled data. Labeled and segmented data products are released with metadata detailing process steps and workflow.
  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: U.S. Geological Survey, Reston, VA.

    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: Journal of Coastal Research vol. 33, issue 1, Coastal Education and Research Foundation, n/a.

    Online Links:

    Other_Citation_Details: pp. 39-55
    Buscombe, D., Goldstein, E.B., Sherwood, C.R., Bodine, C., Brown, J.A., Favela, J., Fitzpatrick, S., Kranenburg, C.J., Over, J.R., Ritchie, A.C., Warrick, J.A., and Wernette, P., 20220304, Human‐in‐the‐Loop Segmentation of Earth Surface Imagery: Earth and Space Science vol. 9, issue 3, American Geophysical Union (AGU), n/a.

    Online Links:

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

  1. How well have the observations been checked?
    No accuracy calculations are performed on raw data. Camera EXIF position data, when present, are derived from SfM calculations or interpolation. Accuracy will vary from roughly cm (SfM) to hundreds of meters (interpolation). Dates and times for images are accurate to mostly within 15 minutes, and likely better. In a few cases, camera are accurate to within a few minutes. Camera clock (date and dime) was reconciled with Aircraft Use Reports (AURs) and aircraft logs and adjusted to be approximately centered to the log time where times differed by >1h by adjusting the image datetime stamps. This was done for <10 percent of the flights. In general, the clock was checked and set before each flight. Some images are over-exposed, some images are under-exposed, and no effort is made to optimize exposure through post-processing, nor to eliminate imagery with acquisition errors. These data represent raw imagery as-collected and subsequently used in Structure-from-Motion (SfM) photogrammetric processing workflows. Accuracy reports and derivation methods for any positions will be published with metadata and position tables within each flight directory.
  2. How accurate are the geographic locations?
    Original imagery has no horizontal position data and any position data that exist in the EXIF are added in post-processing. A formal accuracy assessment of the horizontal positional information in the dataset has not been conducted. If GNSS positions exist in EXIF data they are derived from external sources and will be referenced in position files with metadata found in a subfolder for the relevant flight. The method of position derivation, if present, can be found in the GPSAreaInformation EXIF Tag (Tag ID 0x001c). Interpolated positions will be generated starting and ending at the aircraft departure location (Usually William Fairchild International Airport in Port Angeles, WA) or in the case of aircraft turns, between positions derived with photogrammetric methods.
  3. How accurate are the heights or depths?
    Original imagery has no vertical position data and any position data that exist in the EXIF are added in post-processing. A formal accuracy assessment of the vertical positional information in the dataset has not been conducted. If GNSS positions exist in EXIF data they are derived from external sources and will be referenced in position files with metadata found in a subfolder for the relevant flight. The method of position derivation, if present, can be found in the GPSAreaInformation EXIF Tag (Tag ID 0x001c). Interpolated positions will be generated starting and ending at the aircraft departure location (Usually William Fairchild International Airport in Port Angeles, WA) or in the case of aircraft turns, between positions derived with photogrammetric methods.
  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 metadata record carefully for additional details, and to examine EXIF data for individual flights and images if required to determine camera settings such as exposure mode and shutter speed.
  5. How consistent are the relationships among the observations, including topology?
    Because cameras begin recording immediately when powered up, many images of installation into the wing and the aircraft at rest up to takeoff/after landing were culled from the dataset. In most cases, the camera record for each flight begins at the end of the runway when the aircraft was airborne and ends when the runway comes into view. In some cases due to battery failures or equipment malfunction, the data collection stops before the aircraft leaves the ground. A few ground images were retained for some flights when they were relevant to capturing elements of the historical dataset such as pictures of the aircraft, airport, and in a few cases, takeoff, landing, and install or removal sequences. 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 are available in subfolders. 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. Derivatives and ancillary products may be contained in additional subfolders.
  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?

Who wrote the metadata?

Dates:
Last modified: 20-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/Elwha_planecam_metadata.faq.html>
Generated by mp version 2.9.51 on Fri May 9 14:39:03 2025