<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Gary J. Tuttle</dc:contributor>
  <dc:contributor>Jackie M. Williams</dc:contributor>
  <dc:contributor>Jeffrey E. Lucius</dc:contributor>
  <dc:creator>Karl J. Ellefsen</dc:creator>
  <dc:date>2005</dc:date>
  <dc:description>An S-wave refraction survey was conducted in the Yampa River valley near Steamboat Springs, Colo., to determine how well this method could map alluvium, a major source of construction aggregate. At the field site, about 1 m of soil overlaid 8 m of alluvium that, in turn, overlaid sedimentary bedrock. The traveltimes of the direct and refracted S-waves were used to construct velocity cross sections whose various regions were directly related to the soil, alluvium, and bed-rock. The cross sections were constrained to match geologic logs that were developed from drill-hole data. This constraint minimized the ambiguity in estimates of the thickness and the velocity of the alluvium, an ambiguity that is inherent to the S-wave refraction method. In the cross sections, the estimated S-wave velocity of the alluvium changed in the horizontal direction, and these changes were attributed to changes in composition of the alluvium. The estimated S-wave velocity of the alluvium was practically constant in the vertical direc-tion, indicating that the fine layering observed in the geologic logs could not be detected. The S-wave refraction survey, in conjunction with independent information such as geologic logs, was found to be suitable for mapping the thickness of the alluvium.</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:identifier>10.3133/sir20055012</dc:identifier>
  <dc:language>en</dc:language>
  <dc:title>S-wave refraction survey of alluvial aggregate</dc:title>
  <dc:type>reports</dc:type>
</oai_dc:dc>