Baseline coastal oblique aerial photographs collected U.S. Army Corps of Engineers Field Research Facility, Duck, North Carolina, June 9, 2017

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

Frequently anticipated questions:


What does this data set describe?

Title:
Baseline coastal oblique aerial photographs collected U.S. Army Corps of Engineers Field Research Facility, Duck, North Carolina, June 9, 2017
Abstract:
The U.S. Geological Survey (USGS) conducts baseline and storm-response photography missions to document and understand the changes in the vulnerability of the Nation's coasts to extreme storms. On June 09, 2017, the USGS conducted an oblique aerial photographic survey of the U.S. Army Corps of Engineers Field Research Facility (USACE FRF), located in Duck, North Carolina, aboard a Cessna 182 aircraft at an altitude of approximately 1000 feet (ft). This mission was conducted to collect data for USACE FRF Duck Unmanned Aerial Systems (UAS) Open Field Experiment, carried out June 5–21, 2017. The photographs provided are Joint Photographic Experts Group (JPEG) and Nikon Electronic Format (NEF) images. The photograph locations are an estimate of the aircraft's position and do not indicate the location of the feature in the images. These photographs document the configuration of the USACE FRF at the time of the survey. ExifTool (version 4.0) was used to add the following to the header of each photograph: time of collection, GPS latitude, GPS longitude, keywords, credit, artist (photographer), caption, copyright, and contact information. JPEG photographs can be opened with any JPEG-compatible image viewer. All image times are recorded in Coordinated Universal Time (UTC). In addition to the photographs, a Google Earth Keyhole Markup Language (KML) file is provided and can be used to view the images by clicking on the marker and then the thumbnail or the link above the thumbnail. This KML, 2017-033-FA.kml, can be found in 2017-033-FA-SupplementalFiles.zip.
Supplemental_Information:
For a summary of field activity 2017-033-FA please see https://cmgds.er.usgs.gov/fan_info.php?fan=2017-033-FA. Bounding coordinates for the oblique aerial survey are derived from the overall flight path found in the raw GPS data.
  1. How might this data set be cited?
    Morgan, Karen L.M., Sherwood, Christopher R., and Brosnahan, Sandra M., 20180910, Baseline coastal oblique aerial photographs collected U.S. Army Corps of Engineers Field Research Facility, Duck, North Carolina, June 9, 2017: U.S. Geological Survey Data Release doi:10.5066/P97O8O40, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -75.795787
    East_Bounding_Coordinate: -75.718103
    North_Bounding_Coordinate: 36.228165
    South_Bounding_Coordinate: 36.129875
  3. What does it look like?
    https://coastal.er.usgs.gov/data-release/doi-P97O8O40/data/2017-033-FA-LocationMaps.zip (2017-033-FA-Survey-Map.jpg) (JPEG)
    Map of survey area during USGS field activity 2017-033-FA.
    https://coastal.er.usgs.gov/data-release/doi-P97O8O40/data/2017-033-FA-LocationMaps.zip (JPEG)
    Maps showing the extent of each area and 5-minute segment can be found in the 2017-033-FA-LocationMaps.zip file. The maps in this survey are: 2017-033-FA-Map-Area01.jpg, Area 1 showing the east/west aircraft passes over the U.S. Army Corps of Engineers Field Research Facility, Duck, North Carolina; and 2017-033-FA-Map-Area02.jpg, Area 2, showing the north/south passes. The flight path, divided into 5-minute segments, is represented by the alternating purple and yellow lines, by time. The camera was located on the left side of the aircraft. Thus, for each eastbound pass, the camera looked northward, while during a westbound pass, the camera looked southward. Similarly, northbound passes looked westward, while southbound passes looked eastward.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 09-Jun-2017
    Beginning_Time: 163118
    Ending_Date: 09-Jun-2017
    Ending_Time: 175707
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Raster and tabular digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Point (762)
    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.0197878497. Longitudes are given to the nearest 0.0227728255. Latitude and longitude values are specified in Decimal Degrees. The horizontal datum used is North American Datum of 1983.
      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.
  7. How does the data set describe geographic features?
    2017-033-FA-Flightpath.csv, 2017-033-FA-Photolocation.csv
    The "*Flightpath.csv" file contains the processed GPS information collected during the flight, while the "*Photolocations.csv" file contains a latitude position, longitude position, time, and image name for each image. (Source: USGS)
    PHOTO_ID
    Photograph identification number, using the filename format yyyy_mmdd_hhmmssd.jpg (Source: USGS) Oblique Images
    URL
    Path to low resolution version of the image. (Source: USGS) URL path defining the features.
    ZIPFILENAME
    Name of zip files containing high-resolution the images. (Source: USGS) Zip file name.
    LONGITUDE
    Longitude of photograph location, in decimal degrees (NAD83). (Source: USGS) Coordinates defining the features.
    LATITUDE
    Latitude of photograph location, in decimal degrees (NAD83). (Source: USGS) Coordinates defining the features.
    DATE_FLOWN
    Date images was captured, in yyyymmdd format. (Source: USGS) Date defining the features.
    TIME_UTC
    Time photograph was collected, in xxhxxmxxs format. Times were recorded in Coordinated Universal Time (UTC), where "xx" is the number and "h" is hours, "m" is minutes, and "s" is seconds at the time of capture. (Source: USGS) Time defining the features.
    GEO_AREA
    The geographic area of the mission. (Source: USGS) States partially covered in the oblique photographic mission.
    STATES
    The states included in the survey area of the mission. (Source: USGS) States or regions partially covered in the oblique photographic mission.
    SURVEY
    USGS mission tracking number; also known as a field activity number. (Source: USGS) Mission number utilized by the USGS Coastal and Marine Geology program’s data catalog, Compass, to track survey details and associated data.
    PRE_POST
    Identifies the flight as being pre-storm or post-storm. (Source: USGS)
    ValueDefinition
    PreFlight was prior to a storm.
    PostFlight was after a storm.
    STORM
    If the flight was conducted due to a storm, the name of the storm is listed. Name of Storm (or Baseline). (Source: USGS) The storm name is listed, if the flight was conducted pre- or post-storm, otherwise "Baseline" is entered.
    Entity_and_Attribute_Overview:
    Navigation files: The flightline navigation file is 2017-033-FA-Flightpath.csv, the photo locations are in 2017-033-FA-Photolocations.csv, and are contained within the 2017-033-FA-ProcessedNav.zip file. The raw GPS is in 2017-033-FA-RawGPSNav.txt, which is contained within the 2017-033-FA-RawGPSNav.zip file. These zip files can be found in the data download table. The files (.csv and .txt) are comma-delimited CSV files and an ASCII formatted text file.
    Entity_and_Attribute_Overview:
    Graphic Image Files: The index map (2017-033-FA-Survey-Map.jpg) is a JPEG image. This map shows the baseline coastal oblique aerial photographs collected U.S. Army Corps of Engineers Field Research Facility, June 9, 2017. It also shows two areas, which show more detail and indicate how the full-size photographs are divided into each area. The area maps can be found in the 2017-033-FA-LocationMaps.zip file.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information was generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Karen L.M. Morgan
    • Christopher R. Sherwood
    • Sandra M. Brosnahan
  2. Who also contributed to the data set?
    Funding and support for this study were provided by the USGS Coastal and Marine Geology Program (CMGP). The author wishes to thank pilot Lee and Carol McManus for their assistance with data collection. Native_Data_Set_Environment: Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3. This report benefited from the comments and review of Robert L. Jenkins with the USGS St. Petersburg Coastal and Marine Science Center (SPCMSC), St. Petersburg, FL.
  3. To whom should users address questions about the data?
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    kmorgan@usgs.gov

Why was the data set created?

To provide access to digital photographs taken as part of the June 9, 2017, baseline oblique aerial survey collected during the USACE FRF Duck UAS Open Field Experiment June 5–21, 2017, and to provide access to attribute data that documents the time and location where each photograph was taken.

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: 09-Jun-2017 (process 1 of 6)
    Image Acquisition: Images were taken with a Nikon D810 digital camera and written to internal camera cards. Image size is approximately 36 megapixels. Images in JPEG format were saved using the filename format yyyy_mmdd_hhmmssd.jpg (where the "d" signifies digital acquisition using the Nikon D810). The names provide information about the photograph's year, month, day, hour, minute, and second. For example, image 2017_0609_133636d.jpg was taken June 9, 2017, at 13:36:36 UTC. Some images have a "d2", instead of a "d" in their image name. These images were taken within the same second as the previous image, based on the camera's internal clock. There are 69 images which contain a "d2" within their name. Best attempts were made to set the Nikon D810's internal clock to within 1 second of UTC at the beginning of the flight. Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
    Date: 09-Jun-2017 (process 2 of 6)
    Navigation processing: Using a custom Practical Extraction and Reporting Language (Perl) script written by Karen Morgan, USGS, GPS data and image files were used to generate a CSV file containing a latitude, longitude, and time record for each image. Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
    Date: 09-Jun-2017 (process 3 of 6)
    Camera settings during collection: Focal length: 50 mm (Prime Lens); Sensor type: CMOS (Complementary metal–oxide–semiconductor); Pixel width (x): 7379 max, Pixel height (y): 4912 max; Sensor width: 35.9 mm, Sensor height: 24.0 mm; Pixel size (x) 4.88 microns, Pixel size (y) 4.88 microns; Mode: Manual; F-Stop: 5.6; Exposure Comp: -0.3; ISO: 64; Interval Timer: 1-sec interval Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
    Date: 30-Apr-2018 (process 4 of 6)
    Survey map creation: The survey maps provided in this archive were created with Environmental Systems Research Institute (Esri) ArcGIS 10.3 software and saved as Adobe Illustrator (*.ai) files. Survey maps were edited using Adobe Illustrator CC and exported in JPEG format. Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
    Date: 30-Apr-2018 (process 5 of 6)
    The imagery in this release was divided into manageable sized (< 475 MB) zip files for ease of download and review. Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
    Date: 09-Jun-2017 (process 6 of 6)
    EXIF headers: Exchangeable Image File (EXIF) and International Press Telecommunications Council (IPTC) headers were populated from the command prompt using ExifTool (http://www.sno.phy.queensu.ca/~phil/exiftool, 2017) as part of the post flight processing using a Perl script written by Karen Morgan, USGS, St. Petersburg, FL. ExifTool added the following data to the EXIF Header: time of collection, GPS latitude, GPS longitude, keywords, credit, artist (photographer), caption, copyright, and contact information. Person who carried out this activity:
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@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?
    Best attempts were made to set the camera to UTC time on the GPS receivers at the beginning of each flight. Latitude, longitude, and time were collected at an interval of approximately once every 3 to 15 seconds. Note: Latitude and longitude positions in this data release refer to the position of the aircraft, not the position of the landmarks photographed. Refer to the Process Steps below for more detail.
  2. How accurate are the geographic locations?
    None.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This dataset is considered complete for the information presented, as described in the abstract section. 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?
    Data presented here include the digitally collected photographs in JPEG format with the Exchangeable Image File (EXIF) header embedded with the individual photograph's location along the flight path of the baseline coastal oblique aerial photographic survey of the coast, taken at the U.S. Army Corps of Engineers Field Research Facility. This mission was flown on June 9, 2017, aboard a Cessna 182 aircraft, tail number N8479S. Crew members, contracted by the USGS in St. Petersburg, FL, included Carol McManus, photography contractor, and pilot Lee McManus of Top Cover Virginia, LLC. The GPS receiver used to provide navigation is of unknown accuracy. Still photography was collected along the coast during this survey. GPS Data Collection—Instrument: Garmin GPSMAP 696. Data Collection Interval: Variable, every 5-15 seconds. Data File Format: ASCII; Number of files created: 1. The GPS unit was used to record navigation fixes of the aircraft, not the position of the features imaged.

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 as the originator of the dataset.
  1. Who distributes the data set? (Distributor 1 of 1)
    Karen L.M. Morgan
    USGS
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8000 (voice)
    kmorgan@usgs.gov
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    This publication was prepared by an agency of the United States Government. Although these data were processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, nor shall the act of distribution imply any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: CSV: Comma-separated values files representing table information collected during the flight. JPEG: Images can be opened directly with any JPEG-compatible image viewer. TXT: ASCII formatted metadata files. XML: Extensible Markup Language formatted metadata files. in format CSV, JPEG, TXT, XML
      Network links: https://coastal.er.usgs.gov/data-release/doi-P97O8O40
    • Cost to order the data: None.


Who wrote the metadata?

Dates:
Last modified: 10-Sep-2018
Metadata author:
Karen L.M. Morgan
USGS
Geologist
600 4th Street South
St. Petersburg, FL
USA

727-502-8000 (voice)
kmorgan@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/2017-033-FA-metadata.faq.html>
Generated by mp version 2.9.49 on Fri Sep 13 15:01:24 2019