True color and multispectral aerial imagery collected from UAS operations at North Core Banks, NC in October 2022

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

Frequently anticipated questions:

What does this data set describe?

Title:
True color and multispectral aerial imagery collected from UAS operations at North Core Banks, NC in October 2022
Abstract:
These data map in high detail surficial cross-sections of North Core Banks, a barrier island in Cape Lookout National Seashore, NC, in October 2022. U.S. Geological Survey field efforts are part of an interagency agreement with the National Park Service to monitor the recovery of the island from Hurricanes Florence (2018) and Dorian (2019). Three sites of outwash, overwash, and pond formation were targeted for extensive vegetation ground-truthing, sediment samples, bathymetric mapping with a remote-controlled surface vehicle, and uncrewed aerial systems (UAS) flights to collect multispectral imagery. Five semi-permanent ground control points were also installed and surveyed to act as control for additional aerial imagery collected via plane. UAS imagery were processed in Agisoft Metashape (v. 1.8.1) with surveyed temporary ground control points to produce calibrated multispectral (red, blue, green, red edge, near infrared, and panchromatic) orthoimages and digital surface models.
Supplemental_Information:
For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/fan_info.php?fan=2022034FA. Bounding coordinates represent the maximum extent of all the images, not the individual sites. The Altum-PT and Ricoh GRII were flown at the same time; flights 01 and 02 cover the extent of “New Pond 1”, 03 and 04 cover the extent of “New Pond 3” and 05 and 06 cover the extent of “New Pond 0”.
  1. How might this data set be cited?
    Over, Jin-Si R., and Cramer, Jennifer M., 20230328, True color and multispectral aerial imagery collected from UAS operations at North Core Banks, NC in October 2022: data release DOI:10.5066/P99IV3FC, 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.

    Over, Jin-Si R., Sherwood, Christopher R., Cramer, Jennifer M., Evans, Alexandra D., and Zeigler, Sara L., 2023, Topographic, bathymetric, multispectral, vegetation, sediment, and supporting GPS data collected on North Core Banks, Cape Lookout National Seashore, North Carolina in October 2022, U.S. Geological Survey Field Activity 2022-034-FA: data release DOI:10.5066/P99IV3FC, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Over, J.R., Sherwood, C.R., Cramer, J.M., Evans, A.D., and Zeigler, S.L, 2023, Topographic, bathymetric, multispectral, vegetation, sediment, and supporting GPS data collected on North Core Banks, Cape Lookout National Seashore, North Carolina in October 2022, U.S. Geological Survey Field Activity 2022034FA: U.S. Geological Survey data release, https://doi.org/10.5066/P99IV3FC.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -76.27193750
    East_Bounding_Coordinate: -76.22442000
    North_Bounding_Coordinate: 34.92498270
    South_Bounding_Coordinate: 34.88848350
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/63ae1712d34e92aad3ca5bec?name=2022034FA_NCB_imagery_browse.JPG&allowOpen=true (JPEG)
    Browse graphic of the six different images provided from the MicaSense Altum-PT. All are single bands presented in grayscale.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 19-Oct-2022
    Currentness_Reference:
    Ground condition; multiple survey days.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference: embedded in EXIF
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 18
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -75.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.000000.
      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, using geoid 18
      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?
    2022034FA_NCB_Altum-PT_ImageLocations.csv
    The CSV file contains the approximate position of the Altum-PT camera at the moment of each image capture. Note that the positions for each of the six band images is the same, so only the information for one band is provided. CSV contains 2,167 data records. (Source: USGS)
    ImageName
    File names of individual images, see the Data Quality Information and Process Description for file naming convention. (Source: USGS) Character string.
    Date
    Date in MM/DD/YYYY of each image. (Source: Processor defined) Character string.
    Time_UTC
    Time in HH:MM:SS of each camera position in UTC. (Source: Processor defined) Character string.
    Latitude_NAD83[2011]
    Latitude (x) of UAS based on time of each image capture relative to (NAD83[2011]). Positive values represent North coordinates. (Source: USGS)
    Range of values
    Minimum:34.88848350
    Maximum:34.92498270
    Units:decimal degrees
    Longitude_NAD83[2011]
    Longitude (y) of UAS based on time of each image capture relative to (NAD83[2011]). Negative values represent West coordinates. (Source: USGS)
    Range of values
    Minimum:-76.27193750
    Maximum:-76.22442000
    Units:decimal degrees
    Ellipsoid_NAD83_2011
    Altitude of the UAS position at the time of each image capture relative to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:-52.975
    Maximum:42.309
    Units:meters
    Northing_UTM18N
    The X-coordinate of the UAS in NAD83(2011)/UTM Zone 18N. (Source: USGS)
    Range of values
    Minimum:3861411.663
    Maximum:3865411.365
    Units:meters
    Easting_UTM18N
    The Y-coordinate of the UAS in NAD83(2011)/UTM Zone 18N. (Source: USGS)
    Range of values
    Minimum:383776.129
    Maximum:388163.938
    Units:meters
    Orthometric_height_NAVD88
    The Z-coordinate of the UAS relative to NAVD88 (geoid 18). (Source: USGS)
    Range of values
    Minimum:-15.123
    Maximum:80.159
    Units:meters
    2022034FA_NCB_Ricoh_ImageLocations.csv
    The CSV files contains 1,941 data records of the approximate position of the Ricoh camera at the moment of each image capture. (Source: USGS)
    ImageName
    File names of individual images, see the Data Quality Information and Process Description for file naming convention. (Source: USGS) Character string.
    Date
    Date in MM/DD/YYYY of each image. (Source: Processor defined) Character string.
    Time_UTC
    Time in HH:MM:SS of each camera position in UTC. (Source: Processor defined) Character string.
    Latitude_NAD83[2011]
    Latitude (x) of UAS based on time of each image capture relative to (NAD83[2011]). Positive values represent North coordinates. (Source: USGS)
    Range of values
    Minimum:34.88844270
    Maximum:34.92498850
    Units:decimal degrees
    Longitude_NAD83[2011]
    Longitude (y) of UAS based on time of each image capture relative to (NAD83[2011]). Negative values represent West coordinates. (Source: USGS)
    Range of values
    Minimum:-76.27191680
    Maximum:-76.22440680
    Units:decimal degrees
    Ellipsoid_NAD83[2011]
    Altitude of the UAS position at the time of each image capture relative to the NAD83(2011) reference ellipsoid. (Source: None)
    Range of values
    Minimum:-29.495
    Maximum:33.550
    Units:meters
    Northing_UTM18N
    The X-coordinate of the UAS in NAD83(2011)/UTM Zone 18N. (Source: USGS)
    Range of values
    Minimum:3861407.118
    Maximum:3865411.952
    Units:meters
    Easting_UTM18N
    The Y-coordinate of the UAS in NAD83(2011)/UTM Zone 18N. (Source: USGS)
    Range of values
    Minimum:383778.049
    Maximum:388163.134
    Units:meters
    Orthometric_height_NAVD88
    The Z-coordinate of the UAS relative to NAVD88 (geoid 18). (Source: USGS)
    Range of values
    Minimum:8.340
    Maximum:71.384
    Units:meters
    Entity_and_Attribute_Overview:
    The attributes cover both image location files, which have the same headers. The Altum-PT images are 16-bit, RGB-RE-NIR and panchromatic, TIFF images. Each image is a single wavelength so will appear grayscale when viewed independently. The image location files contain the positions for all flights, though only one band position is provided as all six bands per time of capture have the same location. The Altum-PT image location headers GPSLatitude, GPSLongitude, and GPSAltitude, which are embedded in the images, are the original MicaSense GPS positions in WGS 84 + EGM 96 height, the image locations file is provided for ease of use in the commonly used USGS reference systems. The Ricoh GRII images are JPEGs and have been geotagged with the reconstructed locations in NAD83(2011) and the reference ellipsoid. But note that all of these positions have an overall poor accuracy and it is recommended that the ground control points available in the larger work citation are used to georeferenced any photogrammetry products rather than the using the image positions.
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2022-034-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
    • Jennifer M. Cramer
  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
    384 Woods Hole Rd.
    Woods Hole, MA

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

Why was the data set created?

Multispectral and true-color images were collected with appropriate resolution and overlap to permit high-quality photogrammetry and generation of reflectance imagery and multispectral indices, which can be used for identification of vegetation and other groundcover.

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: 20-Oct-2022 (process 1 of 2)
    The Altum-PT and Ricoh GRII sensors were attached to the bottom of the DJI Matrice 600 pointing nadir. The Altum-PT was wired to a downwelling light sensor and GPS attached to the top of the UAS. A MicaSense reflection calibration panel was placed in view of the Altum-PT before and after take-off so the sensor captured the panel in the images. For flight, both sensors were set to record images at 2-second intervals, activated before takeoff and deactivated after landing. Flights were flown along pre-planned lines and lasted the duration of the UAS battery life (approximately 15 minutes) or until the flight was completed or aborted. The sensors were not mounted on a gimbal so capture scenes were dependent on the attitude of the UAS. The Altum-PT received power from a connection to the UAS. The downwelling light sensor measured ambient light for each of the spectral bands captured by the camera. For each camera shutter trigger, camera settings (focal length, ISO, etc), spectral irradiance, roll, pitch, yaw, gain, exposure time, and GPS position data were automatically incorporated into the Exif data for each image.
    Date: 16-Dec-2022 (process 2 of 2)
    A new reformatted SD card was used for each flight. The images acquired with the sensors 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. (.*jpg was used for Ricoh images) 1. ExifTools was used to tag each photo with the following headers: Credit, Copyright, UsageTerms, ImageDescription, and Artist; where the name of each file and the header information was 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 *.tif ' Additional keywords were added with the following command in the directory with all the photographs: exiftool -keywords="UAS imagery" -keywords="North Core Banks, Cape Lookout National Seashore" -keywords="North Carolina" -keywords="2022034FA" -keywords="USGS" -overwrite_original *.tif To read out the photo information to a csv when in the directory with the photos the command is: exiftool -csv *.tif > 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 '2022034FA_f01aPT_20221020T165822Z_IMG_####_#', 2022034FA is the survey ID, f01 is the flight number, aPT is the camera make Altum-PT and r03 is the Ricoh GRII ID, and 20221020 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 IMG_####_#.tif is the original raw photo name appended to the end of the new filename. 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?

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

  1. How well have the observations been checked?
    The first sensor, a MicaSense Altum-PT, acquired 3.2 (RBG, NIR, RE) and 12.4 (panchromatic) megapixel photos, with file sizes generally between 6 and 24 MB on disc, depending on image complexity and band. All images were tagged with an internal GPS, this provides xyz and roll, pitch, and yaw positional information and accuracies. These values are accessible by reading the exif information; see below for instructions on how to access them. Band information and camera settings are also available through this method. The accuracy of the multispectral sensors were determined using a MicaSense Reflectance Panel and two calibrated reflective tarps that were visible in the imagery. The second sensor, a Ricoh GRII, acquired 3.2 megapixel photos, with file sizes generally around 6 MB on disc. Images that aligned in the Agisoft Metashape projects are geotagged with reconstructed locations (note that this means some images provided that did not align do not have location information). See the orthoimage metadata for more information, available in the larger work citation.
  2. How accurate are the geographic locations?
    Though the images do not represent spatial data, the latitude and longitude are embedded in the photos and available in the EXIF header of each image and also in UTM coordinates provided in the files (2022034FA_NCB_Altum-PT_ImageLocations.csv and 2022034FA_NCB_Ricoh_ImageLocations.csv). The Altum-PT location information was acquired from an internal GPS receiver in the Altum-PT and has an average horizontal accuracy of 1 meter; individual image xy accuracies are embedded in the exif information. Ricoh location information is derived from Agisoft Metashape reconstructed locations and are likely accurate to within 5 meters. Accuracies may be lower than reported when the UAS system executed tight turns near the edges of the flight paths and when landing and taking off. It is recommended to use the ground control points provided in the larger work citation for georeferencing.
  3. How accurate are the heights or depths?
    Though the images do not represent spatial data, the altitude of each image is embedded in the photos and available in the EXIF header of each image. The vertical position values are also provided in the files 2022034FA_NCB_Altum-PT_ImageLocations.csv and 2022034FA_NCB_Ricoh_ImageLocations.csv. The Altum-PT altitude information was acquired from an internal GPS receiver and has an average vertical accuracy of 1.5 meters; individual image z accuracies are embedded in the exif information. Accuracies may be lower than reported (up to 20 meters different) when the UAS system executed tight turns near the edges of the flight paths and when landing and taking off. Ricoh location information is derived from Agisoft Metashape reconstructed locations and are likely accurate to within 5 meters. It is recommended to use the ground control points provided in the larger work citation for georeferencing.
  4. Where are the gaps in the data? What is missing?
    Once turned on the sensors triggered every 2 seconds. The Altum-PT took 7 individual images per band each time, distinguished by a suffix of _1 to _7. All images with a suffix of _7 were removed from this dataset; these are the thermal (LWIR) images that did not have a calibration check source nor are relevant to the goals of the field activity. One to five sets of the MicaSense Calibration panel at the beginning and end of each flight were kept, but additional sets of images were removed for redundancy and space. Images at take-off and landing that contained no panel were also removed for space. All of these removed images can account for the non-consecutive original file names and results in a total of 15,176 Altum-PT images and 2,068 Ricoh GRII images that are provided in zipped files by flight number. Not all Ricoh photos included have location information.
  5. How consistent are the relationships among the observations, including topology?
    Six flights were flown in total for the field activity. Each flight produced images from the Altum-PT and Ricoh GRII. Images were renamed to the format 2022034FA_f##aPT_YYYYMMDDTHHMMSSZ_originalFilename, where 2022034FA is the field activity, f## is the flight number, aPT stands for the Altum-PT sensor and r03 is the Ricoh GRII ID, then the date and time (UTC) separated by a T and Z, respectively; and then the original file name where the following suffixes of each file correspond to the following bands: _1 is the blue band; _2 is the green band; _3 is the red band; _4 is the near infrared (NIR) band; _5 is the red edge band; and _6 is the panchromatic band. Ricoh images do not have a band suffix. The coordinate reference system embedded in the Altum-PT image headers is WGS84 + EGM96 height. Additional transformed coordinate systems, using VDatum (https://vdatum.noaa.gov/vdatumweb/), are provided in the 2022034FA_NCB_Altum-PT_ImageLocations.csv and 2022034FA_NCB_Ricoh_ImageLocations.csv in NAD83(2011) and in UTM18N + NAVD88 (geoid 18) for ease of use. Images were zipped to reduce download size (less than 10 GB per zip folder), zip folders are named using the convention 2022034FA_NCB_Altum-PT_f##a-c, where ## is the flight number and folders of the same flight are distinguished with an a, b, or c.

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. 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? This data release includes raw data in the form of geotagged multispectral and true-color aerial images in TIFF and JPEG format. The Windows 10 zipped folders 2022034FA_NCB_Altum-PT_f01a.zip contains 1,332 TIFF images (9.0 GB), 2022034FA_NCB_Altum-PT_f01b.zip contains 1,272 TIFF images (8.6 GB), 2022034FA_NCB_Altum-PT_f02a.zip contains 1,267 TIFF images (8.6 GB), 2022034FA_NCB_Altum-PT_f02b.zip contains 1,212 TIFF images (8.2 GB), 2022034FA_NCB_Altum-PT_f03a.zip contains 1,014 TIFF images (6.9 GB), 2022034FA_NCB_Altum-PT_f03b.zip contains 1,050 TIFF images (7.1 GB), 2022034FA_NCB_Altum-PT_f03c.zip contains 1,050 TIFF images (7.3 GB), 2022034FA_NCB_Altum-PT_f04.zip contains 1,206 TIFF images (8.0 GB), 2022034FA_NCB_Altum-PT_f05a.zip contains 1,032 TIFF images (7.0 GB), 2022034FA_NCB_Altum-PT_f05b.zip contains 1,074 TIFF images (7.5 GB), 2022034FA_NCB_Altum-PT_f06a.zip contains 774 TIFF images (5.3 GB), 2022034FA_NCB_Altum-PT_f06b.zip contains 726 TIFF images (5.0 GB) and 2022034FA_NCB_Altum-PT_ImageLocations.csv contains the navigation data for each image. The Windows 10 zipped folders 2022034FA_NCB_Ricoh_f01.zip contains 429 JPEG images (2.4 GB), 2022034FA_NCB_ Ricoh_f02.zip contains 399 JPEG images (2.2 GB), 2022034FA_NCB_Ricoh_f03.zip contains 493 JPEG images (2.8 GB), 2022034FA_NCB_Ricoh_f04.zip contains 182 JPEG images (1 GB), 2022034FA_NCB_Ricoh_f05.zip contains 351 JPEG images (2 GB), 2022034FA_NCB_Ricoh_f06.zip contains 213 JPEG images (1.2 GB), and 2022034FA_NCB_Ricoh_ImageLocations.csv contains the navigation data for each aligned image.
  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 zipped files and reading TIFF and JPEG images and, if desired, capable of reading the associated EXIF information. Additionally, the location information is provided in a CSV file for the user to utilize with appropriate software.

Who wrote the metadata?

Dates:
Last modified: 28-Mar-2023
Metadata author:
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)
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_P99IV3FC/2022034FA_NCB_UAS_Imagery_meta.faq.html>
Generated by mp version 2.9.51 on Tue Mar 28 17:25:49 2023