Independent transect point locations (coordinates only) associated with images collected during unmanned aerial systems (UAS) flights over Coast Guard Beach, Nauset Spit, Nauset Inlet, and Nauset Marsh, Cape Cod National Seashore, Eastham, Massachusetts on 1 March 2016 (Text file)

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

Frequently anticipated questions:


What does this data set describe?

Title:
Independent transect point locations (coordinates only) associated with images collected during unmanned aerial systems (UAS) flights over Coast Guard Beach, Nauset Spit, Nauset Inlet, and Nauset Marsh, Cape Cod National Seashore, Eastham, Massachusetts on 1 March 2016 (Text file)
Abstract:
This dataset contains the locations of independent survey points acquired on the same day that images were obtained from unmanned aerial systems (UAS) flown in the Cape Cod National Seashore. The overall objective of the field work was to evaluate the quality and cost of mapping from UAS images. Low-altitude (approximately 120 meters above ground level) digital images were obtained from cameras in a fixed-wing unmanned aerial vehicle (UAV) flown from the lawn adjacent to the Coast Guard Beach parking lot on 1 March, 2016. U.S. Geological Survey technicians deployed and mapped 28 targets that appear in some of the images for use as ground control points. All activities were conducted according to Federal Aviation Administration regulations and under a National Park Service Scientific Research and Collecting Permit, study number CACO-00285, permit number CACO-2016-SCI-003. This dataset contains locations of both in place and placed targets that may be used as ground control to constrain photogrammetric reconstructions. One hundred and forty-four (144) points were measured along several cross-shore transects on the beach. These points were measured with real-time differential global positioning system (GPS) and have horizontal and vertical uncertainties of approximately +/ 0.03 m. These points were not used in photogrammetric processing, so they can be used for independent evaluation of photogrammetric products. The independent survey points are listed in file CACO_transect_Points_20160301.csv.
  1. How might this data set be cited?
    U.S. Geological Survey, 2016, Independent transect point locations (coordinates only) associated with images collected during unmanned aerial systems (UAS) flights over Coast Guard Beach, Nauset Spit, Nauset Inlet, and Nauset Marsh, Cape Cod National Seashore, Eastham, Massachusetts on 1 March 2016 (Text file): data release DOI:10.5066/F7CN721H, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Sherwood, Christopher R., 2016, Low-altitude aerial imagery and photogrammetric products obtained with unmanned aerial systems (UAS) flights over Coast Guard Beach, Nauset Spit, Nauset Inlet, and Nauset Marsh, Cape Cod National Seashore, Eastham, Massachusetts on 1 March 2016: data release DOI:10.5066/F7CN721H, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -69.9478
    East_Bounding_Coordinate: -69.9442
    North_Bounding_Coordinate: 41.8479
    South_Bounding_Coordinate: 41.8363
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/57a0b1eae4b060ce18fbf348?name=CACO_transect_points_map_20160301.jpg (JPEG)
    Map of transect point locations.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 01-Mar-2016
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: digital text data
  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 North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988 (NAVD88)
      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:
    The text file CACO_transect_points_20160301.csv contains 144 lines with no header information. Each line contains nine columns of comma-separated values. The columns contain, in order, point number (ranging from 108 to 252), easting, northing, elevation, transect name, latitude, longitude, date, and time. Easting and northing are UTM Zone 19 North (meters) in the NAD83(2011) coordinate system. Elevation is in meters referenced to NAVD88. Latitude and longitude are in decimal degrees, also in NAD83(2011). Date and time are in local time (Eastern Standard Time = UTC-5).
    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)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Christopher R. Sherwood
    Research Oceanographer
    384 Woods Hole Road
    Woods Hole, Massachusetts

    508-548-8700 x2269 (voice)
    508-457-2310 (FAX)
    csherwood@usgs.gov

Why was the data set created?

The objective of obtaining these transect survey points was to provide independent topographic measurements for evaluation of photogrammetric products.

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: 01-Mar-2016 (process 1 of 2)
    One hundred and forty-four (144) transect point locations were measured along nine cross-beach transects by a technician on foot. The transects were determined by eye, and the spacing of the points by pace, and the precisely measured points provide roughly east-west trending profiles of cross-shore topography from the waters edge (near low tide) to the dune crest. Horizontal and vertical positions were determined with a GNSS rover receiving real-time differential corrections from a base station. For details, see Horizontal and Vertical Positional Accuracy sections. Transect point measurements were converted to NAD83 2010(2011) and NAVD88 (Geoid 12a) as the data were collected. The measurements were exported from the data collector as UTM Zone 19 (meters), NAVD88 (meters), and latitude and longitude (decimal degrees), along with date and time, in a text file (CACO_transect_points_20160301.csv). Person who carried out this activity:
    U.S. Geological Survey
    Attn: Barry Irwin
    Geographic information system technician
    384 Woods Hole Road
    Woods Hole, Massachusetts

    508-548-8700 x2272 (voice)
    508-457-2310 (FAX)
    birwin@usgs.gov
    Data sources used in this process:
    • None
    Data sources produced in this process:
    • independent transect points
    Date: 20-Jul-2018 (process 2 of 2)
    USGS Thesaurus keywords added to the keyword section. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@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?
  2. How accurate are the geographic locations?
    Horizontal positions were determined with a GNSS rover receiving real-time differential corrections from a GNSS base station established over a temporary benchmark on the lawn of the NEED building at Coast Guard Beach. The base station was a Spectra model SP80 GNSS receiver with UHF radio and external antenna mounted on a separate tripod. The antenna height was 2.25 m. The coordinates of the reference point (named CGB_OPUS) were determined from an ultra-rapid precise orbit On-line Positioning User Service (OPUS) solution based on GPS data from a five-hour occupation on January 11, 2016. Coordinates in NAD83 2010(2011) UTM Zone 19, elevation NAVD88 (geoid 12a) for the reference point are: Northing (m) 4632792.698 (+/-0.002), Easting (m) 421296.521 (+/-0.003), Orthometric elevation (m) 12.880 (+/-0.012). The uncertainties in parentheses represent peak-to-peak values. The rover was a Spectra Precision model ProMark 800 GNSS receiver linked via Bluetooth to a data collector (Carlson CHC LT30 Handheld Terminal running Carlson SurvCE v. 4.06 software under Windows Mobile v. 6.1 Professional operating system). This instrument was operated by Barry Irwin. The rover antenna was mounted on 2-m survey rods with bubble level and 5-cm (2-inch) sand foot. The instruments were used to stake three reference points established near the base station at the beginning and end of the day. The average absolute deviation largest horizontal or vertical difference measured was +0.03 m. Conversions from satellite coordinates to NAD83(2011) UTM Zone 19 and NAVD88 were made by Carlson SurvCE software in the data collector.
  3. How accurate are the heights or depths?
    Vertical positions were determined with one of two GNSS rovers receiving real-time differential corrections from a GNSS base station established over a temporary benchmark on the lawn of the NEED building at Coast Guard Beach (see Horizontal_Positional_Accuracy_Report for a complete description of the survey methods). The instruments were used to stake three reference points established near the base station at the beginning and end of the day. The average absolute deviation largest horizontal or vertical difference measured was +0.03 m. Conversions from satellite coordinates to NAD83(2011) UTM Zone 19 and NAVD88 were made by Carlson SurvCE software in the data collector.
  4. Where are the gaps in the data? What is missing?
    Locations of all of the transect points are listed in the .csv file. No ground photos of these points are available.
  5. How consistent are the relationships among the observations, including topology?
    The text file CACO_transect_points_20160301.csv contains the locations (coordinates in UTM Zone 19 meters and latitude and longitude) of transect points. All points were mapped using a differential GPS rover instrument operated by Barry Irwin. Points are labelled TSn, where n refers to cross-shore transect number, ranging from 1 to 9. Point numbers begin at 108 and ascend to 252, but gaps in the numbers occur when other features such as ground control points were mapped.

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)
    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? The zip file contains the CSV file CACO_transect_points_20160301.csv. The CSV file contains 144 lines with no header information. Each line contains nine columns of comma-separated values. The columns contain, in order, point number (ranging from 108 to 252), easting, northing, elevation, transect name, latitude, longitude, date, and time. Easting and northing are UTM Zone 19 North (meters) in the NAD83(2011) coordinate system. Elevation is in meters referenced to NAVD88. Latitude and longitude are in decimal degrees, also in NAD83(2011). Date and time are in local time (Eastern Standard Time = UTC-5). In addition to the CSV file, the zip file also contains a browse graphic (CACO_transect_points_map_20160301.jpg) and the FGDC CSDGM metadata in XML and HTML formats.
  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 USGS 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?
    The .csv file is plain text with comma-separated-values. This can be read with most editors and spreadsheet programs.

Who wrote the metadata?

Dates:
Last modified: 20-Jul-2018
Metadata author:
U.S. Geological Survey
Attn: Christopher R. Sherwood
Research Oceanographer
384 Woods Hole Road
Woods Hole, Massachusetts

508-548-8700 x2269 (voice)
508-457-2310 (FAX)
csherwood@usgs.gov
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/data_release/DR_F7CN721H/CACO_UAS_transect_points.faq.html>
Generated by mp version 2.9.49 on Fri Sep 13 15:01:46 2019