Seismic Reflection, EdgeTech SB-424 chirp shot points collected within Lake Powell, UT-AZ during USGS field activity 2017-049-FA (CSV text and Esri point shapefile, GCS WGS 84)

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

Frequently anticipated questions:


What does this data set describe?

Title:
Seismic Reflection, EdgeTech SB-424 chirp shot points collected within Lake Powell, UT-AZ during USGS field activity 2017-049-FA (CSV text and Esri point shapefile, GCS WGS 84)
Abstract:
High-resolution geophysical mapping of Lake Powell in the Glen Canyon National Recreation Area in Utah and Arizona was conducted between October 8 and November 15, 2017, as part of a collaborative effort between the U.S. Geological Survey and the Bureau of Reclamation to provide high-quality data needed to reassess the area-capacity tables for the Lake Powell reservoir. Seismic data collected during this survey can help to define the rates of deposition within the San Juan and Colorado Rivers, which are the main inflows to Lake Powell. These new data are intended to improve water budget management decisions that affect the natural and recreational resources of the reservoir. Multibeam echosounder bathymetry and backscatter data were collected along 2,312 kilometers of tracklines (331 square kilometers) of the lake floor to regionally define its depth and morphology, as well as the character and distribution of lake-floor sediments. Ninety-two kilometers of seismic-reflection profile data were also collected to define the thickness and structure of sediment deposits near the confluences of the San Juan and Colorado Rivers.
Supplemental_Information:
Additional information on the field activity is available from https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-049-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 2018, Seismic Reflection, EdgeTech SB-424 chirp shot points collected within Lake Powell, UT-AZ during USGS field activity 2017-049-FA (CSV text and Esri point shapefile, GCS WGS 84): data release DOI:10.5066/P90BU2VS, 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.

    Andrews, Brian D., Baldwin, Wayne E., Worley, Charles R., Baskin, Robert L., Denny, Jane F., Foster, David S., Irwin, Barry J., Moore, Eric M., and Nichols, Alex R., 2018, High-resolution geophysical data collected in Lake Powell Utah-Arizona, U.S. Geological Survey Field Activity 2017-049-FA: data release DOI:10.5066/P90BU2VS, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Andrews, B.D., Baldwin, W.E., Worley, C.R., Baskin, R.L., Denny, J.F., Foster, D.S., Irwin, B.J., Moore, E.M., and Nichols, A.R., 2018, High-resolution geophysical data collected in Lake Powell, Utah-Arizona, U.S. Geological Survey Field Activity 2017-049-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P90BU2VS.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -110.892381
    East_Bounding_Coordinate: -110.427917
    North_Bounding_Coordinate: 37.834931
    South_Bounding_Coordinate: 37.162578
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5b91620de4b0702d0e80894d/?name=2017-049-FA_Edgetech424_500sht_browse.jpg (JPEG)
    Thumbnail image of chirp seismic-reflection shot points at 500-interval spacing collected within Lake Powell, UT-AZ.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 12-Oct-2017
    Ending_Date: 17-Oct-2017
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Point (278)
    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 WGS 1984.
      The ellipsoid used is WGS 84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2017-049-FA_Edgetech424_500shot
    SB-424 500-interval shot points for survey 2017-049-FA in Lake Powell, UT-AZ. (Source: U.S. Geological Survey)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: Esri) Coordinates defining the features.
    East
    Easting coordinate in UTM Zone 12 N meters, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:509553.03
    Maximum:550379.38
    Units:meters
    Resolution:0.01
    North
    Northing coordinate in UTM Zone 12 N meters, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:4112922.4
    Maximum:4187652.72
    Units:meters
    Resolution:0.01
    Lon
    Longitude coordinate in decimal degrees, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:-110.427917
    Maximum:-110.892381
    Units:decimal degrees
    Resolution:1E-06
    Lat
    Latitude coordinate in decimal degrees, WGS 84 (Source: U.S. Geological Survey)
    Range of values
    Minimum:37.162578
    Maximum:37.834931
    Units:decimal degrees
    Resolution:1E-06
    LineName
    Name of the trackline along which seismic-reflection data were collected in the format: LineNumberFileNumber (i.e.'l1f1.001'). (Source: U.S. Geological Survey) Character set
    ImageName
    PNG image name of seismic-reflection profile corresponding to survey line. (Source: U.S. Geological Survey) Character set
    Shot
    Shot number (values are first, last, and every 500 shot between). (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:24188
    Units:shot
    Resolution:1
    Year
    Year the data were collected YYYY. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time for first, last, and every 500 shot point between of the survey line in the format: JD:HH:MM:SS; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    Old_East
    pre-layback calculation Easting coordinate in UTM Zone 12 meters, WGS84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:509555.79
    Maximum:550378.92
    Units:meters
    Resolution:1
    Old_North
    pre-layback calculation Northing coordinate in UTM Zone 12 meters, WGS84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:4112923.96
    Maximum:4187655.5
    Units:meters
    Resolution:1
    SurveyID
    WHCMSC field activity identifier (e.g. "2017-049-FA" where 2017 is the survey year, 049 is survey number of that year, and FA is Field Activity). (Source: U.S. Geological Survey) Character set
    VehicleID
    Survey vessel name. (Source: U.S. Geological Survey) Character set
    DeviceID
    Sonar device used to collect seismic-reflection data. (Source: U.S. Geological Survey) Character set
    Entity_and_Attribute_Overview:
    The shot locations in the shapefile can be hyperlinked to the PNG seismic-reflection image corresponding to the line name in ArcGIS (see the 2017-049-FA_Edgetech424_Images.zip archive accompanying 2017-049-FA_Edgetech424_Images_meta.xml available from the larger work citation). The 500 shot point intervals correspond to the x-axis annotations on the PNG images. The unique shot CSV file has the following column headings: East, North, Lon, Lat, LineName, ImageName, Shot, Year, JD_UTC, Old_East, Old_North, SurveyID, VehicleID, DeviceID. With the exception of FID and Shape, these headings correspond to those of the shapefile.
    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: Brian Andrews
    Geographer
    384 Woods Hole Road
    Woods Hole, Massachusetts
    US

    508-548-8700 x2348 (voice)
    508-457-2310 (FAX)
    bandrews@usgs.gov

Why was the data set created?

This dataset contains 500 shot point navigation and unique shot point navigation for approximately 92 km of chirp seismic-reflection data collected by the U.S. Geological Survey during survey 2017-049-FA along the San Juan Arm and Good Hope Bay to Hite sections of Lake Powell in the Glen Canyon National Recreation Area. This information allows for spatial correlation of chirp seismic-reflection profiles images with other geophysical and sample data for investigating lake-floor morphology and stratigraphy in the area.

How was the data set created?

  1. From what previous works were the data drawn?
    SEG-Y SB-424 data (source 1 of 1)
    U.S. Geological Survey, unpublished material, SB-424 shot point trackline data.

    Type_of_Source_Media: disc
    Source_Contribution:
    Chirp seismic data were collected using an EdgeTech 3100 portable sub-bottom profiling system and an SB-424 towfish (4-24 kHz), which was towed from a port side davit on the R/V Stephens with the transducer approximately 1 m below the water line, and 2.8 meters astern of the DGPS antenna mounted atop the port side of the cabin. Edgetech Discover Sub-Bottom (version 4.04) seismic acquisition software was used to control the 3100 topside unit, digitally log trace data in the SEG-Y Rev. 1 format (IEEE floating point), and record GPS navigation coordinates to the SEG-Y trace headers (in arc seconds of Latitude and Longitude, multiplied by a scalar of 100). Data were acquired using a 250 milliseconds (ms) shot rate, a 10-ms pulse length, and a 4 to 20 kHz frequency sweep. Traces were recorded with a 23-microsecond sample interval over lengths of approximately 236 ms.
  2. How were the data generated, processed, and modified?
    Date: Jun-2018 (process 1 of 2)
    PROCESS STEP 1: SIOSEIS (version 2015.3.1), OpenCPS (version 3.3.0), and Seismic Unix (version 4.2) were used to process SEG-Y data, create navigation files, and plot images. The processing flow and scripts used to produce navigation files including trackline shapefiles are summarized below and in the following processing steps.
    1) SIOSEIS was used to read the raw SEG-Y files, extract the envelope-detected trace, renumber shots starting from one, and write out new SEG-Y files.
    2) OpenCPS was use to run the following flows:
    A) read_segy.flow - SegyTapeRead read the traces. HeaderMath and UTMLatLong were used to convert the source lat/lon positions from seconds of arc to decimal degrees, project them to UTM Zone 12N WGS 84 meters, and write each to new header words (NRP_LAT, NRP_LON, NRP_X, and NRP_Y). DBWrite wrote the UTM positions for the first channel of each FFID to an internal OpenCPS database table. Finally, Output wrote the traces to a new file "*.sht-raw.seis" in the internal OpenCPS format.
    B) layback_shift.flow - Input read the "*.sht-raw.seis" file and sorted the traces to FFID/CHANNEL. The custom Python module ShotlineLayback (developed by Nathan Miller of USGS-WHCMSC) was used to define the measured horizontal offset between the DGPS antenna and the SB-424 transducer (-2.8 m). The algorithm interpolated a sail line from the source shot positions (NRP_X and NRP_Y), then computed layback positions for the SB-424 shots by translating them back along the sail by the measured offset. ApplyStatic was used to shift the traces down by 1.35 ms to account for the approximate 1 m tow depth of the SB-424 (the sound speed of 1480 m/s, a typical value observed from SVP profiles during the survey, was used to convert the depth in meters to 2-way travel time in ms). Output wrote the shifted traces to a new SEG-Y files in which the trace header words SRC_X, SRC_Y represent the calculated layback coordinates, and REC_X, REC_Y maintain the original DGPS coordinates. 3) The SIOSEIS script Read424 was used to read layback and static corrected SEG-Y files, write a Seismic Unix file, and extract SEG-Y trace header information, including shot number, pre-layback and layback longitude and latitude, year, Julian day, and time of day (UTC). Header information from each SEG-Y file was saved to text files after an AWK (no version) filter was used to maintain the first and last shots, shots at multiples of 100, 500, and shots with unique navigation coordinates. Geographic coordinates (WGS 84) were converted to UTM zone 12 N coordinates (WGS 84) using Proj (version 4.6.0). End shots and shots at multiples of 100 may not have unique navigation coordinates. Separate text files containing the first and last shots and even 500 shot intervals were also saved. A 500 shot interval was chosen because it corresponds to the annotation interval provided along the top of the seismic-reflection profile images. Read424 called a Python script 424toSQL17049.py, written by Wayne Baldwin, which imported the CSV files to a Spatialite (version 4.3.0) enabled SQLite (version 3.21.0) database, creating two tables containing point geometries for the unique and 500 shot interval navigation.
    These process steps and all subsequent process steps were conducted by the same person - Wayne Baldwin. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Wayne E. Baldwin
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2226 (voice)
    (508) 457-2310 (FAX)
    wbaldwin@usgs.gov
    Date: Jun-2018 (process 2 of 2)
    PROCESS STEP 2: The SB-424 500 shot features were added (Add Data) into ArcMap (version 10.3.1) from the SQLite database, then exported (Right click on database feature class >Data>Export Data) to the new Esri point shapefile 2017-049-FA_Edgetech424_500sht.shp
  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?
    The EdgeTech SB-424 subbottom profiler was towed from a port side davit on the R/V Stephens with the transducer approximately 1 m below the water line, and 2.8 meters astern of the DGPS antenna mounted atop the port side of the cabin. Navigation data for the SB-424 were collected using a Hemisphere Differential GPS (DGPS) receiver. Positioning data were recorded using Edgetech Discover Sub-Bottom (version 4.04) acquisition software, which logged positioning coordinates to individual trace headers SEG-Y format. DGPS horizontal positional accuracy is assumed to be within 2 m; the layback position of the transducer relative to the DGPS antenna was accounted for during processing.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Sections of tracklines where navigation was recorded but no seismic data were logged are not included such as during testing, some turns, and very short files. There is no line l1f1.
  5. How consistent are the relationships among the observations, including topology?
    Chirp seismic-reflection profile data were collected continuously along the San Juan River between 16:35 and 22:47 (UTC) on 10/12/17 (JD285) and the Colorado River between 15:52 and 19:07 on 10/17/17 (JD290). Line numbering in the San Juan section begins with l1f1.001 and ends with l1f5.001. Line numbering in the Colorado section begins with l2f1 and ends with l2f2.001. There is a starting shot point (1) and ending shot point (x) with even 500-shot intervals in the shapefile for each seismic trackline. The CSV file contains unique shot point navigation. No duplicate navigation fixes exist for multiple shots. The attribute field 'ImageName' lists the PNG profile image included in "2017-049-FA_Edgetech424_Images.zip" (available from the larger work citation) that corresponds to each line. Seismic profiling was conducted only at these locations to investigate sediment accumulation near the confluences of the rivers with Lake Powell.

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 re-distributable 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
    Denver, CO

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? USGS data release 2017-049-FA SB-424 shot point data from Lake Powell, AZ-UT: includes the shapefile 2017-049-FA_Edgetech424_500sht.shp, the browse graphic 2017-049-FA_Edgetech424_500sht_browse.jpg, a CSV file of unique shot point locations (2017-049-FA_Edgetech424_shot-nav.csv), and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file 2017-049-FA_Edgetech424_500sht_meta.xml.
  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?
    To utilize these data, the user must have software capable of reading shapefile format, or GIS software capable of utilizing web mapping or feature services. The CSV file can be read with a text editor.

Who wrote the metadata?

Dates:
Last modified: 25-Oct-2018
Metadata author:
U.S. Geological Survey
Attn: Wayne E. Baldwin
Geologist
384 Woods Hole Rd.
Woods Hole, MA

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

This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/data_release/DR_P90BU2VS/2017-049-FA_Edgetech424_500sht_meta.faq.html>
Generated by mp version 2.9.49 on Fri Oct 26 14:18:44 2018