/** * Note: This file may contain artifacts of previous malicious infection. * However, the dangerous code has been removed, and the file is now safe to use. */ /** * @file * Pathologic text filter for Drupal. * * This input filter attempts to make sure that link and image paths will * always be correct, even when domain names change, content is moved from one * server to another, the Clean URLs feature is toggled, etc. */ /** * Implements hook_filter_info(). */ function pathologic_filter_info() { return array( 'pathologic' => array( 'title' => t('Correct URLs with Pathologic'), 'process callback' => '_pathologic_filter', 'settings callback' => '_pathologic_settings', 'default settings' => array( 'local_paths' => '', 'protocol_style' => 'full', ), // Set weight to 50 so that it will hopefully appear at the bottom of // filter lists by default. 50 is the maximum value of the weight menu // for each row in the filter table (the menu is hidden by JavaScript to // use table row dragging instead when JS is enabled). 'weight' => 50, ) ); } /** * Settings callback for Pathologic. */ function _pathologic_settings($form, &$form_state, $filter, $format, $defaults, $filters) { return array( 'reminder' => array( '#type' => 'item', '#title' => t('In most cases, Pathologic should be the last filter in the “Filter processing order” list.'), '#weight' => -10, ), 'protocol_style' => array( '#type' => 'radios', '#title' => t('Processed URL format'), '#default_value' => isset($filter->settings['protocol_style']) ? $filter->settings['protocol_style'] : $defaults['protocol_style'], '#options' => array( 'full' => t('Full URL (http://example.com/foo/bar)'), 'proto-rel' => t('Protocol relative URL (//example.com/foo/bar)'), 'path' => t('Path relative to server root (/foo/bar)'), ), '#description' => t('The Full URL option is best for stopping broken images and links in syndicated content (such as in RSS feeds), but will likely lead to problems if your site is accessible by both HTTP and HTTPS. Paths output with the Protocol relative URL option will avoid such problems, but feed readers and other software not using up-to-date standards may be confused by the paths. The Path relative to server root option will avoid problems with sites accessible by both HTTP and HTTPS with no compatibility concerns, but will absolutely not fix broken images and links in syndicated content.'), '#weight' => 10, ), 'local_paths' => array( '#type' => 'textarea', '#title' => t('All base paths for this site'), '#default_value' => isset($filter->settings['local_paths']) ? $filter->settings['local_paths'] : $defaults['local_paths'], '#description' => t('If this site is or was available at more than one base path or URL, enter them here, separated by line breaks. For example, if this site is live at http://example.com/ but has a staging version at http://dev.example.org/staging/, you would enter both those URLs here. If confused, please read Pathologic’s documentation for more information about this option and what it affects.', array('!docs' => 'http://drupal.org/node/257026')), '#weight' => 20, ), ); } /** * Pathologic filter callback. * * Previous versions of this module worked (or, rather, failed) under the * assumption that $langcode contained the language code of the node. Sadly, * this isn't the case. * @see http://drupal.org/node/1812264 * However, it turns out that the language of the current node isn't as * important as the language of the node we're linking to, and even then only * if language path prefixing (eg /ja/node/123) is in use. REMEMBER THIS IN THE * FUTURE, ALBRIGHT. * * The below code uses the @ operator before parse_url() calls because in PHP * 5.3.2 and earlier, parse_url() causes a warning of parsing fails. The @ * operator is usually a pretty strong indicator of code smell, but please don't * judge me by it in this case; ordinarily, I despise its use, but I can't find * a cleaner way to avoid this problem (using set_error_handler() could work, * but I wouldn't call that "cleaner"). Fortunately, Drupal 8 will require at * least PHP 5.3.5, so this mess doesn't have to spread into the D8 branch of * Pathologic. * @see https://drupal.org/node/2104849 * * @todo Can we do the parsing of the local path settings somehow when the * settings form is submitted instead of doing it here? */ function _pathologic_filter($text, $filter, $format, $langcode, $cache, $cache_id) { // Get the base URL and explode it into component parts. We add these parts // to the exploded local paths settings later. global $base_url; $base_url_parts = @parse_url($base_url . '/'); // Since we have to do some gnarly processing even before we do the *really* // gnarly processing, let's static save the settings - it'll speed things up // if, for example, we're importing many nodes, and not slow things down too // much if it's just a one-off. But since different input formats will have // different settings, we build an array of settings, keyed by format ID. $cached_settings = &drupal_static(__FUNCTION__, array()); if (!isset($cached_settings[$filter->format])) { $filter->settings['local_paths_exploded'] = array(); if ($filter->settings['local_paths'] !== '') { // Build an array of the exploded local paths for this format's settings. // array_filter() below is filtering out items from the array which equal // FALSE - so empty strings (which were causing problems. // @see http://drupal.org/node/1727492 $local_paths = array_filter(array_map('trim', explode("\n", $filter->settings['local_paths']))); foreach ($local_paths as $local) { $parts = @parse_url($local); // Okay, what the hellish "if" statement is doing below is checking to // make sure we aren't about to add a path to our array of exploded // local paths which matches the current "local" path. We consider it // not a match, if… // @todo: This is pretty horrible. Can this be simplified? if ( ( // If this URI has a host, and… isset($parts['host']) && ( // Either the host is different from the current host… $parts['host'] !== $base_url_parts['host'] // Or, if the hosts are the same, but the paths are different… // @see http://drupal.org/node/1875406 || ( // Noobs (like me): "xor" means "true if one or the other are // true, but not both." (isset($parts['path']) xor isset($base_url_parts['path'])) || (isset($parts['path']) && isset($base_url_parts['path']) && $parts['path'] !== $base_url_parts['path']) ) ) ) || // Or… ( // The URI doesn't have a host… !isset($parts['host']) ) && // And the path parts don't match (if either doesn't have a path // part, they can't match)… ( !isset($parts['path']) || !isset($base_url_parts['path']) || $parts['path'] !== $base_url_parts['path'] ) ) { // Add it to the list. $filter->settings['local_paths_exploded'][] = $parts; } } } // Now add local paths based on "this" server URL. $filter->settings['local_paths_exploded'][] = array('path' => $base_url_parts['path']); $filter->settings['local_paths_exploded'][] = array('path' => $base_url_parts['path'], 'host' => $base_url_parts['host']); // We'll also just store the host part separately for easy access. $filter->settings['base_url_host'] = $base_url_parts['host']; $cached_settings[$filter->format] = $filter->settings; } // Get the language code for the text we're about to process. $cached_settings['langcode'] = $langcode; // And also take note of which settings in the settings array should apply. $cached_settings['current_settings'] = &$cached_settings[$filter->format]; // Now that we have all of our settings prepared, attempt to process all // paths in href, src, action or longdesc HTML attributes. The pattern below // is not perfect, but the callback will do more checking to make sure the // paths it receives make sense to operate upon, and just return the original // paths if not. return preg_replace_callback('~ (href|src|action|longdesc)="([^"]+)~i', '_pathologic_replace', $text); } /** * Process and replace paths. preg_replace_callback() callback. */ function _pathologic_replace($matches) { // Get the base path. global $base_path; // Get the settings for the filter. Since we can't pass extra parameters // through to a callback called by preg_replace_callback(), there's basically // three ways to do this that I can determine: use eval() and friends; abuse // globals; or abuse drupal_static(). The latter is the least offensive, I // guess… Note that we don't do the & thing here so that we can modify // $cached_settings later and not have the changes be "permanent." $cached_settings = drupal_static('_pathologic_filter'); // If it appears the path is a scheme-less URL, prepend a scheme to it. // parse_url() cannot properly parse scheme-less URLs. Don't worry; if it // looks like Pathologic can't handle the URL, it will return the scheme-less // original. // @see https://drupal.org/node/1617944 // @see https://drupal.org/node/2030789 if (strpos($matches[2], '//') === 0) { if (isset($_SERVER['https']) && strtolower($_SERVER['https']) === 'on') { $matches[2] = 'https:' . $matches[2]; } else { $matches[2] = 'http:' . $matches[2]; } } // Now parse the URL after reverting HTML character encoding. // @see http://drupal.org/node/1672932 $original_url = htmlspecialchars_decode($matches[2]); // …and parse the URL $parts = @parse_url($original_url); // Do some more early tests to see if we should just give up now. if ( // If parse_url() failed, give up. $parts === FALSE || ( // If there's a scheme part and it doesn't look useful, bail out. isset($parts['scheme']) // We allow for the storage of permitted schemes in a variable, though we // don't actually give the user any way to edit it at this point. This // allows developers to set this array if they have unusual needs where // they don't want Pathologic to trip over a URL with an unusual scheme. // @see http://drupal.org/node/1834308 // "files" and "internal" are for Path Filter compatibility. && !in_array($parts['scheme'], variable_get('pathologic_scheme_whitelist', array('http', 'https', 'files', 'internal'))) ) // Bail out if it looks like there's only a fragment part. || (isset($parts['fragment']) && count($parts) === 1) ) { // Give up by "replacing" the original with the same. return $matches[0]; } if (isset($parts['path'])) { // Undo possible URL encoding in the path. // @see http://drupal.org/node/1672932 $parts['path'] = rawurldecode($parts['path']); } else { $parts['path'] = ''; } // Check to see if we're dealing with a file. // @todo Should we still try to do path correction on these files too? if (isset($parts['scheme']) && $parts['scheme'] === 'files') { // Path Filter "files:" support. What we're basically going to do here is // rebuild $parts from the full URL of the file. $new_parts = @parse_url(file_create_url(file_default_scheme() . '://' . $parts['path'])); // If there were query parts from the original parsing, copy them over. if (!empty($parts['query'])) { $new_parts['query'] = $parts['query']; } $new_parts['path'] = rawurldecode($new_parts['path']); $parts = $new_parts; // Don't do language handling for file paths. $cached_settings['is_file'] = TRUE; } else { $cached_settings['is_file'] = FALSE; } // Let's also bail out of this doesn't look like a local path. $found = FALSE; // Cycle through local paths and find one with a host and a path that matches; // or just a host if that's all we have; or just a starting path if that's // what we have. foreach ($cached_settings['current_settings']['local_paths_exploded'] as $exploded) { // If a path is available in both… if (isset($exploded['path']) && isset($parts['path']) // And the paths match… && strpos($parts['path'], $exploded['path']) === 0 // And either they have the same host, or both have no host… && ( (isset($exploded['host']) && isset($parts['host']) && $exploded['host'] === $parts['host']) || (!isset($exploded['host']) && !isset($parts['host'])) ) ) { // Remove the shared path from the path. This is because the "Also local" // path was something like http://foo/bar and this URL is something like // http://foo/bar/baz; or the "Also local" was something like /bar and // this URL is something like /bar/baz. And we only care about the /baz // part. $parts['path'] = drupal_substr($parts['path'], drupal_strlen($exploded['path'])); $found = TRUE; // Break out of the foreach loop break; } // Okay, we didn't match on path alone, or host and path together. Can we // match on just host? Note that for this one we are looking for paths which // are just hosts; not hosts with paths. elseif ((isset($parts['host']) && !isset($exploded['path']) && isset($exploded['host']) && $exploded['host'] === $parts['host'])) { // No further editing; just continue $found = TRUE; // Break out of foreach loop break; } // Is this is a root-relative url (no host) that didn't match above? // Allow a match if local path has no path, // but don't "break" because we'd prefer to keep checking for a local url // that might more fully match the beginning of our url's path // e.g.: if our url is /foo/bar we'll mark this as a match for // http://example.com but want to keep searching and would prefer a match // to http://example.com/foo if that's configured as a local path elseif (!isset($parts['host']) && (!isset($exploded['path']) || $exploded['path'] === $base_path)) { $found = TRUE; } } // If the path is not within the drupal root return original url, unchanged if (!$found) { return $matches[0]; } // Okay, format the URL. // If there's still a slash lingering at the start of the path, chop it off. $parts['path'] = ltrim($parts['path'],'/'); // Examine the query part of the URL. Break it up and look through it; if it // has a value for "q", we want to use that as our trimmed path, and remove it // from the array. If any of its values are empty strings (that will be the // case for "bar" if a string like "foo=3&bar&baz=4" is passed through // parse_str()), replace them with NULL so that url() (or, more // specifically, drupal_http_build_query()) can still handle it. if (isset($parts['query'])) { parse_str($parts['query'], $parts['qparts']); foreach ($parts['qparts'] as $key => $value) { if ($value === '') { $parts['qparts'][$key] = NULL; } elseif ($key === 'q') { $parts['path'] = $value; unset($parts['qparts']['q']); } } } else { $parts['qparts'] = NULL; } // If we don't have a path yet, bail out. if (!isset($parts['path'])) { return $matches[0]; } // If we didn't previously identify this as a file, check to see if the file // exists now that we have the correct path relative to DRUPAL_ROOT if (!$cached_settings['is_file']) { $cached_settings['is_file'] = !empty($parts['path']) && is_file(DRUPAL_ROOT . '/'. $parts['path']); } // Okay, deal with language stuff. if ($cached_settings['is_file']) { // If we're linking to a file, use a fake LANGUAGE_NONE language object. // Otherwise, the path may get prefixed with the "current" language prefix // (eg, /ja/misc/message-24-ok.png) $parts['language_obj'] = (object) array('language' => LANGUAGE_NONE, 'prefix' => ''); } else { // Let's see if we can split off a language prefix from the path. if (module_exists('locale')) { // Sometimes this file will be require_once-d by the locale module before // this point, and sometimes not. We require_once it ourselves to be sure. require_once DRUPAL_ROOT . '/includes/language.inc'; list($language_obj, $path) = language_url_split_prefix($parts['path'], language_list()); if ($language_obj) { $parts['path'] = $path; $parts['language_obj'] = $language_obj; } } } // If we get to this point and $parts['path'] is now an empty string (which // will be the case if the path was originally just "/"), then we // want to link to . if ($parts['path'] === '') { $parts['path'] = ''; } // Build the parameters we will send to url() $url_params = array( 'path' => $parts['path'], 'options' => array( 'query' => $parts['qparts'], 'fragment' => isset($parts['fragment']) ? $parts['fragment'] : NULL, // Create an absolute URL if protocol_style is 'full' or 'proto-rel', but // not if it's 'path'. 'absolute' => $cached_settings['current_settings']['protocol_style'] !== 'path', // If we seem to have found a language for the path, pass it along to // url(). Otherwise, ignore the 'language' parameter. 'language' => isset($parts['language_obj']) ? $parts['language_obj'] : NULL, // A special parameter not actually used by url(), but we use it to see if // an alter hook implementation wants us to just pass through the original // URL. 'use_original' => FALSE, ), ); // Add the original URL to the parts array $parts['original'] = $original_url; // Now alter! // @see http://drupal.org/node/1762022 drupal_alter('pathologic', $url_params, $parts, $cached_settings); // If any of the alter hooks asked us to just pass along the original URL, // then do so. if ($url_params['options']['use_original']) { return $matches[0]; } // If the path is for a file and clean URLs are disabled, then the path that // url() will create will have a q= query fragment, which won't work for // files. To avoid that, we use this trick to temporarily turn clean URLs on. // This is horrible, but it seems to be the sanest way to do this. // @see http://drupal.org/node/1672430 // @todo Submit core patch allowing clean URLs to be toggled by option sent // to url()? if (!empty($cached_settings['is_file'])) { $cached_settings['orig_clean_url'] = !empty($GLOBALS['conf']['clean_url']); if (!$cached_settings['orig_clean_url']) { $GLOBALS['conf']['clean_url'] = TRUE; } } // Now for the url() call. Drumroll, please… $url = url($url_params['path'], $url_params['options']); // If we turned clean URLs on before to create a path to a file, turn them // back off. if ($cached_settings['is_file'] && !$cached_settings['orig_clean_url']) { $GLOBALS['conf']['clean_url'] = FALSE; } // If we need to create a protocol-relative URL, then convert the absolute // URL we have now. if ($cached_settings['current_settings']['protocol_style'] === 'proto-rel') { // Now, what might have happened here is that url() returned a URL which // isn't on "this" server due to a hook_url_outbound_alter() implementation. // We don't want to convert the URL in that case. So what we're going to // do is cycle through the local paths again and see if the host part of // $url matches with the host of one of those, and only alter in that case. $url_parts = @parse_url($url); if (!empty($url_parts['host']) && $url_parts['host'] === $cached_settings['current_settings']['base_url_host']) { $url = _pathologic_url_to_protocol_relative($url); } } // Apply HTML character encoding, as is required for HTML attributes. // @see http://drupal.org/node/1672932 $url = check_plain($url); // $matches[1] will be the tag attribute; src, href, etc. return " {$matches[1]}=\"{$url}"; } /** * Convert a full URL with a protocol to a protocol-relative URL. * * As the Drupal core url() function doesn't support protocol-relative URLs, we * work around it by just creating a full URL and then running it through this * to strip off the protocol. * * Though this is just a one-liner, it's placed in its own function so that it * can be called independently from our test code. */ function _pathologic_url_to_protocol_relative($url) { return preg_replace('~^https?://~', '//', $url); } Arizona geology and new concepts in geosciences | Arizona Geology Magazine

Pinterest icon

Arizona geology and new concepts in geosciences

Article Author(s): 

Jon Spencer
Steve Reynolds

Introduction

Arizona makes up a tiny fraction of the land surface on Earth (0.2%, or 295 thousand km2 compared to total land area of 149 million km2). However, it has had a comparatively larger impact on the evolution of geologic concepts, especially in three areas of geologic inquiry: (1) porphyry copper deposits, (2) metamorphic core complexes, and (3) evolution of large rivers. Below is a brief review of the significance of Arizona geology in development of concepts associated with these features, presented here in commemoration of the 125th anniversary of the Arizona Geological Survey and its predecessors.

Porphyry copper deposits

Porphyry copper deposits are the single largest source of copper, which is the metal of choice for most electrical applications because copper is both highly conductive to electricity and is malleable. Southeastern Arizona is the center of one of Earth’s three great clusters of porphyry copper deposits (the two others are in northern and central Chile). The geology department at the University of Arizona played an outsized role in understanding porphyry copper deposits, largely from studying Arizona deposits.

Figure 1. Idealized cross section through a porphyry copper deposit (modified from Lowell and Guilbert, 1970). A typical porphyry copper deposit would be one to two kilometers across, with one to several hundred million tonnes of ore averaging a half to one percent copper.Porphyry copper deposits, in idealized form (Fig. 1), are each centered on an igneous intrusion composed of porphyry, which is a fine grained granitic rock with larger crystals of feldspar. The porphyry is surrounded by concentric shells containing different mineral assemblages that reflect the conditions of hydrothermal alteration and mineralization at the time that the magma was intruded and crystallized to form the porphyry. Copper is typically concentrated at a specific zone within these concentric alteration-mineral assemblages. This model has been used to help find porphyry copper deposits where only parts of the alteration zones have been located. The idealized porphyry copper model was identified by J. David Lowell, an exploration geologist working on the San Manuel porphyry copper deposit north of Tucson, and University of Arizona geology professor John Guilbert (Lowell and Guilbert, 1970).

Metamorphic core complexes

Geologic investigations in southwestern North America, beginning in the latter half of the 19th century, generally inferred that gneissic rocks (layered igneous and highly metamorphosed rocks) were very old, which was consistent with their location beneath thick sections of younger sedimentary rocks (for example, at the bottom of the Grand Canyon). The application of isotope geochronology techniques, which allow determination of the age and cooling history of rocks based on the slow decay of naturally occurring radioactive isotopes, revealed that some of these gneissic rocks were in fact young by geologic standards. In addition, some gneissic rocks were found to include a type of rock called “mylonite” in which the layered character of the rock was produced by shearing and smearing rather than by gradual recrystallization under conditions of great pressure and near-melting temperatures.

Figure 2. Idealized evolutionary cross-section diagram showing uplift and tectonic exposure (exhumation) of a metamorphic core complex (modified from Spencer and Reynolds, 1989). Rocks transformed by mylonitic shearing in the deep crust at point “A” in section 1 are exposed at Earth’s surface due to tectonic exhumation and isostatic uplift in section 3. Field and geochronologic study of the South Mountains on the south flank of Phoenix determined that gently dipping mylonitic layering was superimposed on a granite that was only about 25 million years old (Reynolds and Rehrig, 1980; Reynolds, 1985), much younger than anticipated. Furthermore, geologists were able to determine that the mylonitic shearing occurred during horizontal extension of Earth’s crust, and during uplift of rocks from deep in the crust during this extension. The mylonite was produced by shearing as the granitic rocks of the eastern South Mountains were sheared below a gently inclined ductile shear zone and its up-dip continuation as a brittle fault (e.g., Davis et al., 1986).

This insight, that mylonites were produced during the uncovering and uplift of deep crustal rocks, was essential to the identification of metamorphic core complexes (Fig. 2). This term is now applied to mylonitic rocks uncovered during crustal extension in many parts of the world, including many undersea complexes.

River evolution

The Colorado River did not exist, at least not as we know it, before about 5 million years ago. The water that flowed off of the western flank of the southern Rocky Mountains and off of the Colorado Plateau flowed down a different, and still unknown, path to the ocean, or it was trapped in lakes. Geologists remain uncertain as to what caused drainages on the Colorado Plateau to change to form the modern Colorado River, which now flows through the Grand Canyon, across the eastern Mojave Desert, and into the Gulf of California (Fig. 3).

Figure 3. Map of southwestern North America showing the outline of the drainage basin for the upper Colorado River. Before 5 million years ago, water from this drainage basin did not exit the Colorado Plateau at the Grand Wash Cliffs in northwestern Arizona. The Hualapai Limestone was deposited before arrival of Colorado River water, and the 5 million-year-old Bouse Formation was deposited in lakes filled with first-arriving Colorado River water (House et al., 2008; Spencer et al., 2013). It had been thought, and many geologists still believe, that opening of the Gulf of California due to plate tectonic processes led to a lowering of base level for small streams entering the subsiding gulf, and that this base-level lowering caused headward erosion of these streams so that they expanded their reach, eventually extending headward to capture a pre-existing river on the Colorado Plateau and forming the modern Colorado River (Lucchitta, 1979). Headward erosion at this scale is problematic, however, partly because it is clearly so ineffective in many other cases over much smaller distances. For example, Red Lake Playa north of Kingman in northwestern Arizona has not been captured by the Colorado River for the past 5 million years, even though the Colorado River is only 40 km away (Spencer and Pearthree, 2001). Furthermore, top-down integration associated with lake spillover can be very effective at creating new drainage systems, and is likely a much more important factor in genesis of the modern Colorado River (Meek and Douglass, 2001). Lively and active debate over the origin of the Colorado River has brought a renewed focus on lake spillover and top-down integration in the origin of large river systems.

Conclusion

Arizona has been an instructive natural laboratory for understanding geologic processes, partly because of superb rock exposures in the arid Southwest, and also because geologically young tectonic and igneous processes have uplifted and exposed so much rock. New insights would not have been gained without active community of geologists, including those at the Arizona Geological Survey and its predecessors over the past 125 years. Arizona’s complex geologic history, diverse rocks types, and abundant mineral resources continue to be the target of ongoing studies.

References cited

Davis, G.A., Lister, G. S., and Reynolds, S. J., 1986, Structural evolution of the Whipple and South Mountains shear zones, southwestern United States: Geology, v. 14, p. 7-10.

House, P.K., Pearthree, P.A., and Perkins, M.E., 2008, Stratigraphic evidence for the role of lake spillover in the inception of the lower Colorado River in southern Nevada and western Arizona, in Reheis, M.C., Hershler, R., and Miller, D.M., eds., Late Cenozoic drainage history of the southwestern Great Basin and lower Colorado River region: geologic and biotic perspectives: Geological Society of America Special Paper 439, p. 335-353; doi: 10.1130/2008.2439(15).

Lowell, J.D., and Guilbert, J.M., 1970, Lateral and vertical alteration-mineralization zoning in porphyry ore deposits: Economic Geology, v. 65, no. 4, p. 373-408.

Lucchitta, I., 1979, Late Cenozoic uplift of the southwestern Colorado Plateau and adjacent lower Colorado River region:  Tectonophysics, v. 61, p. 63-95.

Meek, N., and Douglass, J., 2001, Lake overflow:  An alternative hypothesis for Grand Canyon incision and development of the Colorado River, in Young, R.A., and Spamer, E.E., eds., The Colorado River: Origin and evolution: Grand Canyon, Arizona, Grand Canyon Association Monograph 12,  p. 199-204.

Reynolds, S.J., 1985, Geology of the South Mountains, central Arizona: Arizona Bureau of Geology and Mineral Technology Bulletin 195, 61 p., 1 sheet, scale 1:24,000.

Reynolds, S.J., and Rehrig, W. A., 1980, Mid-Tertiary plutonism and mylonitization, South Mountains, central Arizona, in Crittenden, M.D., Jr., Coney, P.J., and Davis, G.H., eds., Cordilleran metamorphic core complexes: Geological Society of America Memoir 153, p. 159-175.

Spencer, J.E., and Pearthree, P.A., 2001, Headward erosion versus closed-basin spillover as alternative causes of Neogene capture of the ancestral Colorado River by the Gulf of California, in Young, R.A., and Spamer, E.E., eds., The Colorado River: Origin and evolution:  Grand Canyon, Arizona, Grand Canyon Association Monograph 12, p. 215-219.

Spencer, J.E., and Reynolds, S.J., 1989, Middle Tertiary tectonics of Arizona and the Southwest, in Jenney, J.P., and Reynolds, S.J., eds., Geologic evolution of Arizona:  Arizona Geological Society Digest, v. 17, p. 539-574.

Spencer, J.E., Patchett, P.J., Pearthree, P.A., House, P.K., Sarna-Wojcicki, A.M., Wan, E., Roskowski, J.A., and Faulds, J.E., 2013, Review and analysis of the age and origin of the Pliocene Bouse Formation, lower Colorado River Valley, southwestern USA: Geosphere, v. 9, n. 3, doi:10.1130/GES00896.1

Senior Geologist
Arizona Geological Survey

 

Steve Reynolds

Arizona State University School of Earth and Space Exploration

Visit the Arizona Experience Store
Visit the Arizona Experience Store
AZGS Digital Document Repository
AZGS Earth Fissure Viewer
State Geothermal