Riverbed sidescan sonar and sediment data for the Grand Canyon of the Colorado River, Glen Canyon Dam to Phantom Ranch, Arizona, Aug-Sep, 2000

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

Frequently-anticipated questions:


What does this data set describe?

Title:
Riverbed sidescan sonar and sediment data for the Grand Canyon of the Colorado River, Glen Canyon Dam to Phantom Ranch, Arizona, Aug-Sep, 2000
Abstract:

An experimental water release from the Glen Canyon Dam into the Colorado River above Grand Canyon was conducted in September 2000 by the U.S. Bureau of Reclamation. To determine the sediment characteristics of the Colorado River bed before and after the release, the U.S. Geological Survey (USGS) conducted sidescan sonar surveys between Glen Canyon Dam (mile -15) and Phantom Ranch (mile 87.7), Arizona. The first survey (R3-00-GC, 28 Aug to 5 Sep 2000) was conducted before the release when the river was experiencing its Low Summer Steady Flow (LSSF) of 8,000 cfs. The second survey (R4-00-GC, 10 to 18 Sep 2000) was conducted immediately after the September 2000 experimental release during which average daily flow was as high as 30,800 cfs below Glen Canyon Dam. Riverbed sediment properties interpreted from the sidescan sonar images include sediment type, sandwave fields, and calculated changes in these properties between the two surveys.

Supplemental_Information:

Additional information about the field activities from which this data set was derived are available online at <URL:http://walrus.wr.usgs.gov/infobank/r/r300gc/html/r-3-00-gc.meta.html> <URL:http://walrus.wr.usgs.gov/infobank/r/r400gc/html/r-4-00-gc.meta.html>

Sidescan sonar data were collected at approximately 15 to 20 stretches of the Colorado River and targeting pools between rapids in these sections of the river:

tail waters section (mile -15 to mile 0)
Paria Riffle (Mile 1) to Cathedral Riffle (Mile 3)
small area above Badger Creek Rapid (Mile 7)
Silver Grotto Riffle (Mile 29.3) to South Canyon or
  just above Vasey's Paradise (Mile 31.4)
President Harding Rapid (Mile  44) to between Eminence Break
  to Saddle Canyon (Mile 47)
60 Mile Rapid to the Little Colorado River (Mile 65)
below the Little Colorado River to Crash Canyon (Mile 62-63)
  to Carbon Creek (Mile  64) to Lava Chuar (Mile 65)
Cremation Camp to Grand Canyon Gauge (Mile 87-89)
These pools are part of the Grand Canyon Monitoring and Research Center (GCMRC <http://www.gcmrc.gov/>) physical sciences study.

Maps interpreted from the sidescan sonar images show the distribution of sediment types (bedrock, boulders, pebbles or cobbles, sand) and the extent of fields of sandwaves for each of the pre- and post-flow surveys. In addition, a derived set of data describes the changes that were observed between the two surveys (fining, coarsening, erosion, deposition, change in bedforms).

This data set includes sidescan sonar images and interpreted map files for each of the pre- and post-flow surveys and the changes between for the following sections of river (<URL:http://geopubs.wr.usgs.gov/open-file/of03-265/metadata/indexmap.gif>)

 mile     id   description
 ----     --   -----------
-15 to 0  tw   Glen Canyon Dam to Lees Ferry
 0 to 3   bp   below Paria Riffle, Lees Ferry to Cathedral Wash
 4 to 8   bch  below Cathedral Wash
27 to 29  ts   Tiger Wash to Shinumo Wash
30 to 32  ssc  Shinumo Wash to South Canyon
36 to 39  tp   Thirty-Six Mile to President Harding Rapid
44 to 47  phs  President Harding Rapid to Saddle Canyon
47 to 52  sn   Saddle Canyon to Nankoweap Rapid
60 to 61  slc  Sixty Mile Rapid to Little Colorado River
62 to 69  blcr below Little Colorado River
85 to 87  zc   Zoroaster Rapid to Cremation
File naming convention where xxxx is one of the river segment abbreviations (id above) plus a number:

r300xxxx.tif    R3-00-GC sidescan sonar image, 0.2 m resolution
r300xxxx.tfw    world file for registration of sidescan sonar image
r300xxxx.prj    projection file for sidescan sonar image

r400xxxx.tif    R4-00-GC sidescan sonar image, 0.2 m resolution
r400xxxx.tfw    world file for registration of sidescan sonar image
r400xxxx.prj    projection file for sidescan sonar image

r300xxxx/       interpreted sediment types, R3-00-GC
r300xxxxsw/     sandwave fields, R3-00-GC

r400xxxx/       interpreted sediment types, R4-00-GC
r400xxxxsw/     sandwave fields, R4-00-GC

chgxxxxsw/	 bedform changes between R3-00-GC and R4-00-GC
chgxxxx/        deposition or erosion between R3-00-GC and R4-00-GC
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

Although this Federal Geographic Data Committee-compliant metadata file is intended to document the data set in nonproprietary form, as well as in ArcInfo format, this metadata file may include some ArcInfo-specific terminology.

  1. How should this data set be cited?

    Anima, Roberto J. , Wong, Florence L. , Galanis, Peter, Codianne, Jennifer, Xia, Yu, Bucciarelli, Randy, and Hamer, Michael, 2003, Riverbed sidescan sonar and sediment data for the Grand Canyon of the Colorado River, Glen Canyon Dam to Phantom Ranch, Arizona, Aug-Sep, 2000: preliminary data release 1, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -112.09242
    East_Bounding_Coordinate: -111.47837
    North_Bounding_Coordinate: 36.08593
    South_Bounding_Coordinate: 36.93602

  3. What does it look like?

    <URL:http://geopubs.wr.usgs.gov/open-file/of03-265/metadata/indexmap.gif> (JPEG)
    Index map of Grand Canyon survey blocks.

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: Apr-2003
    Currentness_Reference: Ground Condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: map

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Raster data set. It contains the following raster data types:

      • Dimensions 7295 x 5190, type Pixel

    2. What coordinate system is used to represent geographic features?

  7. How does the data set describe geographic features?

    Entity_and_Attribute_Overview:
    r300xxx.tif, r400xxx.tif - 0.2-meter resolution sidescan
    sonar images with pixel values 0 to 255.  0 represents
    nodata areas.  Image color is black (0) to white (255).
    
    r300xxxx, r400xxxx - polygon coverage of interpreted
    sediment types
    
      Attribute: sedtype
        Values: bedrock, boulders, pebbles_cobbles, sand, shoreline
    
    r300xxxsw, r400xxxsw - polygon coverage of sandwave fields
    
      Attribute: sedtype
        Values: starved_sand
    
    chgxxxsw - polygon coverage of areas of bedform change
    between R3-00-GC and R4-00-GC
    
      Attribute: sedchange
        Values: new sandwaves, sandwaves lost
    
    chg_r4xxx - polygon coverage of areas of fining, coarsening, erosion or
    deposition between R3-00-GC and R4-00-GC
    
      Attribute: sedchange
        Values: fining, coarsening, deposition, erosion
    
    
    Entity_and_Attribute_Detail_Citation: none


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    Florence L. Wong
    United States Geological Survey (USGS)
    Geologist, GIS Coordinator
    USGS, MailStop 999, 345 Middlefield Road
    Menlo Park, CA 94025-3561
    USA

    (650) 329-5327 (voice)
    (650) 329-5190 (FAX)
    fwong@usgs.gov


Why was the data set created?

These data are intended for science researchers, students, policy makers, and the general public. The data can be used with geographic information systems (GIS) software to display geologic information.


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: Sep-2000 (process 1 of 6)
    Two surveys (R3-00-GC and R4-00-GC) were conducted from Glen Canyon Dam to Diamond Creek (224 miles). A Klein 500 kHz side-scanning sonar tow fish was used to conduct the surveys above the Little Colorado River. During the pre-flow survey a large quantity of fine-grained sediment from the Little Colorado attenuated the outgoing sidescan signal so much that the survey had to be stopped. Switching to a 100 kHz tow fish and electronics allowed the surveying to continue to Diamond Creek.

    Date: 2001 (process 2 of 6)
    Sidescan sonar images were processed with the USGS Mini Image Processing System (MIPS) <URL:http://terraweb.wr.usgs.gov/software/mips/>, a set of software tools that are used to convert rectangular blocks of raw data to georeferenced images in UTM 11 coordinates in MIPS "raw" or .bil (band interleaved by line) format. The processed images have pixel values 0 to 255, indicating a range of sonar reflectance from low to high. In grayscale, these values are portrayed as black to white, respectively. The images were converted to TIFFs for use with illustration software. Processor: Peter Galanis (pgalanis@usgs.gov).

    Date: 2002 (process 3 of 6)
    Sidescan sonar tiff images were imported to Adobe Photoshop where the color mapping was inverted so that original 0 to 255 pixel values are gradational from white to black. Interpreted features were drawn as vector layers in Adobe Illustrator. Images were enlarged for interpreting 50 to 100 percent for clarity. The resolution of the sidescan images is 0.2 meter per pixel. Darker features on the inverted images indicate higher reflectivity. For example, bedrock and boulders image as dark reflectors whereas sand and gravel image as various shades of white to dark gray. Processor: Roberto Anima (ranima@usgs.gov).

    Date: 2002 (process 4 of 6)
    Vector layers from Adobe Illustrator files were exported to Arc shapefiles with Avenza Mapublisher. Registration tics were generated from the registration world file of the sidescan sonar images. The upper left tic coordinates and a scale of 567 supplied to Mapublisher produces registered shapefiles. The shapefiles were converted to Arc coverages for editing and tagging. Processors: Jennifer Codianne, Yu Xia, Randy Bucciarelli, and Michael Hamer.

    Date: 2003 (process 5 of 6)

    The coverages were checked and manually registered if the navigation data were insufficient. The image and vector files in UTM 11 coordinates were converted to Arizona State Plane coordinates for conformance to GCMRC requirements. Processor: Florence Wong (fwong@usgs.gov).

    Date: 14-Mar-2003 (process 6 of 6)
    First draft of metadata created by florence using FGDCMETA.AML ver. 1.35 08/02/2000 on ArcInfo data set /we5/florence/gc/bp1a/r3bp1a_az

  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?

    Location data were acquired in two ways. First, a Global Positioning System (GPS) collected location data using two GPS units. The antenna was mounted on a stationary frame that was located within 0.5 meter over the tow fish. The GPS data were collected and stored on hard disk and optical drive for later processing. The second source of location data relied on high-resolution (1-foot pixels) aerial photographs covering the entire river. One crewmember located and marked features observed along the shore on aerial photographs with an identifier and time. The identifier and time were also noted on the paper sidescan sonar record. A GPS fix was taken at the same time on the hand-held units. The aerial photograph data proved essential where the GPS signal was lost to canyon steepness and reflection of the incoming GPS signal on the canyon walls.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Complete.

  5. How consistent are the relationships among the observations, including topology?

    Not applicable for raster data.


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:
These preliminary data are provided for cooperators in the Grand Canyon Monitoring Research Center research program and are not intended for general release without express permission of Roberto J. Anima, USGS (ranima@usgs.gov).

  1. Who distributes the data set? (Distributor 1 of 1)

    United States Geological Survey (USGS)
    c/o Florence L. Wong
    Geologist, GIS Coordinator
    USGS, MailStop 999, 345 Middlefield Road
    Menlo Park, CA 94025-3561
    USA

    (650) 329-5327 (voice)
    (650) 329-5190 (FAX)
    fwong@usgs.gov

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    Please recognize the U.S. Geological Survey (USGS) as the source of this information.

    Although these data have been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data.

    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 this data, software, or related materials.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 22-Apr-2003
Last Reviewed: May-2003
Metadata author:
United States Geological Survey (USGS)
c/o Florence L. Wong
Geologist, GIS Coordinator
USGS, MailStop 999, 345 Middlefield Road
Menlo Park, CA 94025-3561
USA

(650) 329-5327 (voice)
(650) 329-5190 (FAX)
fwong@usgs.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata ("CSDGM version 2") (FGDC-STD-001-1998)


Generated by mp version 2.8.5 on Thu Aug 07 14:54:35 2003