Multibeam Echosounder, Reson T-20P tracklines, collected within Lake Powell UT-AZ during USGS Field Activity 2017-049-FA (Esri polyline shapefile, GCS WGS 84)

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

Frequently anticipated questions:

What does this data set describe?

Title:
Multibeam Echosounder, Reson T-20P tracklines, collected within Lake Powell UT-AZ during USGS Field Activity 2017-049-FA (Esri polyline 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, Multibeam Echosounder, Reson T-20P tracklines, collected within Lake Powell UT-AZ during USGS Field Activity 2017-049-FA (Esri polyline 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: -111.553209
    East_Bounding_Coordinate: -110.426004
    North_Bounding_Coordinate: 37.835644
    South_Bounding_Coordinate: 36.893719
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5b91371ce4b0702d0e8085f3/?name=2017-049-FA_T20P_Tracklines_browse.jpg (JPEG)
    Thumbnail image of multibeam echosounder tracklines collected within Lake Powell, UT-AZ.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 08-Oct-2017
    Ending_Date: 15-Nov-2017
    Currentness_Reference:
    data were collected on the following dates: 20171008-20171022 (Julian day 281-295); 20171024-20171109 (Julian day 297-313); 20171115 (Julian day (319).
  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):
      • string (737)
    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 D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2017-049-FA_T20P_Tracklines
    T20P multibeam echosounder tracklines for survey 2017-049-FA in Lake Powell AZ-UT. (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.
    LineName
    Reson SeaBat User Interface s7k filename for the T20-P MBES trackline in the format: UTC start date and time (YYYYMMDD_HHMMSS format, i.e. '20171008_154610'). The actual files names for the primary and secondary T20-P units are prepended with 'M_' or 'S_', respectively. (Source: U.S. Geological Survey) Character set
    YJD_start
    Year and Julian day at the start of the survey line in the format: YYYY-JD; where 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
    JDUT_start
    Julian day and UTC time at the start 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
    YJD_end
    Year and Julian day (YYYY-JD) at the end of the survey line in the format: YYYY-JD; where 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
    JDUT_end
    Julian day and UTC time at the end 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
    SurveyID
    Woods Hole Coastal and Marine Science Center (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 MBES data. (Source: U.S. Geological Survey) Character set
    Length_km
    Length of swath data line in kilometers (UTM Zone 12N, WGS 84) calculated in the SQLite database. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0.001
    Maximum:9.367
    Units:kilometers
    Resolution:0.001

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 trackline navigation for approximately 2300 kilometers of multibeam echosounder bathymetry and backscatter data collected by the U.S. Geological Survey during cruise 2017-049-FA on Lake Powell in the Glen Canyon National Recreation Area. This information can help spatially correlate the bathymetry and backscatter data with other geophysical data.

How was the data set created?

  1. From what previous works were the data drawn?
    RAW RESON T20-P MULTIBEAM ECHOSOUNDER FILES (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, raw MBES data in s7k format.

    Type_of_Source_Media: disc
    Source_Contribution:
    Multibeam echosounder (MBES) bathymetry and backscatter data were collected using dual-head Reson T20-P sonars. The pair of mills cross transmit and receive arrays were mounted side-by-side within a bracket that oriented them at opposing 30 degree angles (relative to horizontal). The bracket was pole-mounted on the starboard side of the R/V Stephens so that the sonar arrays were oriented athwart ships (primary and secondary arrays facing outward and down to port and starboard, respectively) and located approximately 1.235 m below the waterline when deployed. Vessel navigation and attitude data were acquired using an Applanix POS MV Wavemaster (model 220, V5) configured with two AeroAntenna Technologies GPS antennas located at either end of a 2-m baseline, which was oriented fore and aft and mounted atop the MBES pole approximately midships on the starboard side of vessel, and the wetpod MRU mounted atop the sonar bracket just aft of the pole. An AML Micro X SV mounted on the sonar bracket monitored sound speed near the sonars during acquisition, and an AML Minos X SVPT deployed using an electric downrigger mounted on the port quarter was used to collect water column sound speed profiles 1 to 3 times each survey day (See shapefile 2017-049-FA_SVPdata.shp available from the larger work citation). The Reson SeaBat User Interface (UI)(version 5.0.0.6) was used to control the sonars, which were operated in intermediate mode at full power (220 db), with frequency-modulated pulses between 200 to 300 kHz. The range of the 1024 across track beams formed by the sonars were adjusted manually depending on water depth, and resulted in combined swath widths of 60 to 200 meters or typically 3 to 6 times the water depth. Data were monitored and recorded using the Reson SeaBat User Interface (version 5.0.0.6) and Hypack/Hysweep (version 2017, 17.1.3.0). The SeaBat User Interface logged the navigation, attitude, bathymetry, time-series backscatter, and water column data to s7k format files for each sonar. The line files were created by the Reson UI using the following naming convention: YYYYMMDD_HHMMSS_M/S. The line files were appended with a "M" and "S" suffix to denote the port (or primary) "M" and "S" starboard (or secondary) sonar heads
  2. How were the data generated, processed, and modified?
    Date: Nov-2017 (process 1 of 6)
    PROCESSING STEP 1: CARIS HIPS DATA PROCESSING. Multibeam bathymetry processing within CARIS HIPS (version 10.2) during the survey consisted of the following flow:
    1) Vessel configuration files were created in CARIS for the port ("M"=main, or primary) and starboard ("S"=secondary) sonars (RVStephens_DualT20P_M.hvf, and RVStephens_DualT20P_S.hvf) which included relevant, linear and angular installation offsets for each T20-P unit as well as vendor specified uncertainty values for each of the survey sensors.
    2) A CARIS HIPS project (version 10.2) was created with projection information set to Universal Transverse Mercator (UTM) Zone 12N, NAD 83. Separate HIPS projects were created for the Port (M), and Starboard (S) line files using the two vessel configuration files in #1 above.
    3) Each Reson s7k file (M and S) were imported to the new CARIS projects (M and S respectively) using the Import/Conversion Wizard.
    4) Delayed heave data from raw POS MV files were used to update HIPS survey lines using the import auxiliary data function.
    5) Navigation was reviewed and edited as needed using the Navigation Editor tool.
    6) Sound velocity correction was applied using the CARIS algorithm, a master SVP file containing all the sound velocity profiles collected during the survey and specifying the nearest in distance method, delayed heave source, and use surface sound speed.
    7) Data were merged selecting no tide and the delayed heave source.
    8) 2-m resolution Swath Angle Weighted (SWATH) surfaces were created to incorporate all the files (M and S) as they were processed, and the SWATH surfaces were reviewed for inconsistencies and anomalies.
    9) The swath and subset editors were used to remove spurious points through manual editing and filter application, and the refraction editor was used to adjust sound speed values in areas where velocimeter data did not adequately correct depth profiles, which were obviously influenced by local anomalies in speed of sound through the water column.
    10) Survey lines adjusted for refraction anomalies were remerged, and the respective SWATH surfaces were recomputed to reflect the changes. Processing during the survey was primarily focused on QA/QC during acquisition. Editing processes did require trial and error, and were at times iterative. The contact person for Processing steps 1 and 2 is Brian Andrews. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Brian Andrews
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA
    US

    508-548-8700 x2348 (voice)
    508-457-2310 (FAX)
    bandrews@usgs.gov
    Date: Apr-2018 (process 2 of 6)
    PROCESSSING STEP 2: APPLY POST PROCESSED SBET FILES. Post-survey processing within CARIS HIPS (version 10.4) consisted of the following flow: 1) Post-processed navigation, vessel attitude, and GPS height data from POSPac SBET files, and post-processed RMS attitude error data from POSPac smrmsg files were used to update HIPS survey lines using the import auxiliary data function.
    2) Navigation source was set to Applanix SBET, and navigation was reviewed and edited as needed using the Navigation Editor tool.
    3) GPS tide was computed using delayed heave data, the vessel water line, and a single datum value of 0 m (vertically referencing the data to the WGS 84 Ellipsoid).
    4) Sound velocity correction was reapplied using the CARIS algorithm, the master SVP file containing all the sound velocity profiles collected during the survey and specifying the nearest in distance method, delayed heave source, and use surface sound speed.
    5) Data were remerged selecting the GPS tide and delayed heave sources.
    6) 2-m resolution SWATH surfaces using both the M and S files were created using the Swath Angle method and a maximum footprint of 9.
    7) Additional editing was conducted using the swath and subset editors to minimize inconsistencies and artifacts, and the SWATH surface was recomputed to reflect the changes. Finally, small "no data" holidays were filled using the "Fill Raster Holiday" tool and a 5x5 cell filter using data from a minimum of 5 neighboring cells.
    Date: Apr-2018 (process 3 of 6)
    PROCESSING STEP 3: EXTRACT NAVIGATION. Use Caris printfNav and Python to extract and reformat the navigation fixes stored in the Caris HIPS database and add them to a geospatial SQLite (version 3.21.0) database: 1) Extract navigation for each line in Caris HDCS directory using the Caris program printfNav for all the lines. (Extracted navigation file is tab-delimited in format YYYY-JD HH:MM:SS:FFF DD.LAT DD.LONG SSSSS_VVVVV_YYYY-JD_LLLL AR where YYYY=year, JD=Julian Day, HH=hour, MM=minute, SS=seconds, FFF=fractions of a second, DD.LAT=latitude in decimal degrees, DD.LONG=longitude in decimal degrees, SSSSS=survey name, VVVVV=vessel name, LLLL=linename, AR=accepted or rejected navigation fix). This step creates TXT navigation files for each survey line in the Caris project.
    2) A Python script (pySQLBathNav) runs on the navigation TXT files, creating a new line in the SQLite database (which is created if it does not already exist) for each record, with new fields survey ID, vessel name, and system name. The pySQLBathNav script creates both point and polyline navigation for each survey line. The contact person for Processing steps 3-5 is 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: Apr-2018 (process 4 of 6)
    PROCESSING STEP 4: CREATE ESRI SHAPEFILE CONTAINING THE POLYLINE DATA: The T20P polyline 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 polyline shapefile 2017-049-FA_T20P_Tracklines.shp. Create new string attributes "SurveyID", "VehicleID, and "DeviceID" and populate using the "field calculator" context menu.
    Date: Apr-2018 (process 5 of 6)
    PROCESING STEP 5: RENAME SHAPEFILE ATTRIBUTE TABLE FIELDS:
    XTools Pro (version 12.0) for ArcGIS desktop was used (TABLE OPERATIONS - TABLE RESTRUCTURE) to rename some attribute field headings in the polyline shapefile's attribute table. 'Year_JD_ini' was changed to 'YJD_start', 'JD_UTC_ini' was changed to 'JDUT_start', 'Year_JD_end' was changed to 'YJD_end', and 'JD_UTC_end' was changed to 'JDUT_end'. A new attribute field "Length_km" was added to the shapefile attribute table populated with the length in kilometers of the feature using the "calculate geometry" context menu in ArcMap (v.10.3.1). The UTM 12 WGS 84 coordinate system was used to calculate the lengths of each line. The remaining field headers were unchanged.
    Date: 06-Aug-2020 (process 6 of 6)
    Added keywords section with USGS persistent identifier as theme keyword. 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?
    Navigation data were acquired using the WGS 84 coordinate system with an Applanix POS MV Wavemaster (model 220, V5), which blends Global Navigation Satellite Systems (GNSS) with acceleration data from a Motion Reference Unit (MRU) and GPS azimuthal heading. The POS MV was configured with two AeroAntenna Technologies GPS antennas located at either end of a 2-m baseline, which was oriented fore and aft and mounted atop the MBES pole, approximately midships on the starboard side of vessel. DGPS positions were obtained from the primary antenna located on the forward end of the baseline, and the positional offsets between the antenna and the navigational reference point (the POS MV IMU) were accounted for in the Applanix POSView (version 8.60) acquisition software. DGPS positions are horizontally accurate to 0.5 - 2 meters, but accuracy can increase to less than 10 cm after post-processing with Applanix POSPac (version 8.1).
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Data were not collected on October 23, 2017 while the base of operations was moved from Bullfrog, UT in the northeast to Page, AZ in the southwest. Data were not collected between Nov 10 and 14 because of a cable failure of the Applanix navigation and attitude system. Operations resumed (and were completed) November 15, 2017 after installation of the new cable.
  5. How consistent are the relationships among the observations, including topology?
    Multibeam echosounder (MBES) data were collected almost continuously during daylight survey operations, usually 8-10 hours per day, but acquisition was suspended briefly during file changes or for longer periods during turns and system calibration, malfunction, or troubleshooting. Gaps between the polyline features in this shapefile reflect those time periods where data were not recorded.

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? Multibeam Echosounder, Reson T-20P tracklines, collected within Lake Powell UT-AZ during USGS Field Activity 2017-049-FA includes the shapefile 2017-049-FA_T20P_Tracklines.shp, the browse graphic 2017-049-FA_T20P_Tracklines_browse.jpg, and the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file 2017-049-FA_T20P_Tracklines_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.

Who wrote the metadata?

Dates:
Last modified: 19-Mar-2024
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)
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. (updated on 20240319)
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P90BU2VS/2017-049-FA_T20P_Tracklines_meta.faq.html>
Generated by mp version 2.9.51 on Wed Jun 26 15:25:03 2024