/** * 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); } Southwest Fire Science Consortium Field Trip to the Chiricahua National Monument: Discussion of the Impacts of the 2011 Horseshoe 2 Fire | Arizona Geology Magazine

Environmental Geology

Pinterest icon

Southwest Fire Science Consortium Field Trip to the Chiricahua National Monument: Discussion of the Impacts of the 2011 Horseshoe 2 Fire

Article Author(s): 

Leanndra Arechederra-Romero

 

Figure 1: Post-Horseshoe 2 Fire burned area of Chiricahua Mountains (Arechederra-Romero 2012).On November 8th, 2012, the Southwest Fire Science Consortium hosted a field trip to the Chiricahua National Monument in southeastern Arizona. The Southwest Fire Science Consortium comprises scientists, land managers and policy makers who interact and share science in one of the regions most dominated by fire in the United States. Representatives from the University of Arizona, Northwest Fire District, Tecnológico de Monterrey, Arizona State Forestry Division, Arizona Game and Fish Department, Cochise County LEPC/RACES/Search & Rescue, Arizona Game and Fish, ACME Services, US Forest Service, Rocky Mountain Research Station, Coronado National Forest, Arizona Geological Survey, National Parks Service - Southeast Arizona Group, National Park Service, Student Conservation Association, Bureau of Land Management, Gila National Forest, Prescott National Forest, and Sky Island Alliance attended and discussed the implications of the Horseshoe 2 Fire on debris flows, bark beetle distribution, and ecosystems in the Chiricahua Mountains (Figure 1). The consortium also discussed how to handle and prevent future wildfires in the Southwestern U.S. in the face of a decade-long drought.

The Horseshoe 2 Fire

On May 8th, 2011, at 11:00 a.m. the Horseshoe 2 Fire, one of the largest wildfires in Arizona history, started in the Coronado National Forest near the Chiricahua Mountains of southeastern Arizona (Figure 2). The Horseshoe 2 Fire originated in Horseshoe Canyon. Figure 2: Satellite image of 2011 Horseshoe 2 Fire from May 15th in the Chiricahua Mountains (NASA 2011).  North is to the top of the image. The human-caused fire scorched about 222,954 acres of land and destroyed 23 structures (Table 1). By the time it was 100% contained on June 25th, 2011, it was the fourth largest wildfire in Arizona history.  Over 1,379 personnel aided in containing the fire, including 38 crews, 66 engines, 36 water tenders, 4 dozers, 9 helicopters, 3 heavy airtankers and 3 heavy helitankers. The total cost of suppressing the fire topped $50 million.

At the onset fire crews thought the fire would consume no more than 35,000 acres due to informed estimates from the Horseshoe 1 Fire of 2010.  The first sign that the Horseshoe 2 Fire proposed a major challenge occurred when the fire raced down a canyon in 12 hours as opposed to the anticipated 18 hours. Kristy Lund from the Coronado National Forest recalls asking the question, “Really, it’s going to come down hill nine miles?” (Watch Kristy Lund from the Coronado National forest recalls the adverse variability of the Horseshoe 2 Fire at the Southwest Fire Science Consortium field trip held on November 8, 2012 in the Chiricahua Mountains.) The fire reached the bottom of the canyon and the town of Portal, Arizona, was evacuated.  After the fire was 100% contained the U.S. Forest Service Burned Area Emergency Response (BAER) team assembled to quickly assess the situation and help develop plans to address where post-wildfire impacts, such as hill slope erosion and flooding, posed immediate and significant threats to human life and property.

2011 Horseshoe 2 Fire At-A-Glance
Dates: 8 May to 25 June, 2011 Cause: Human
Location: Near Portal, AZ in the Chiricahua Mountains.
Total Size: 222,954 acres. Acres by ownership: Private 13,934; State 2,874; USFS 192,647; BLM 1,336; NPS 12, 163
Vegetation types: Mixed conifer, oak brush, pinyon, juniper, ponderosa pine and grasses
Burn Severity Acres % of Area
High 27,730 12.4%
Moderate 66,226 29.7%
Low 84,852 38.0%
Unchanged 44,146 19.8%

Table 1. 2011 Horseshoe 2 Fire statistics (Southwest Fire Consortium)

Why was the Fire so Severe?

High intensity wildfires increased in the last century due to suppression of fires and lack of active forest management. Research shows frequent, low temperature fires are important to a forests health by maintaining natural plant conditions and reducing the buildup of fuels. During the last century fire suppression caused forests to become extremely dense in the West. The combination of increased fuel and droughts make forests in the West susceptible to severe wildfires.

Figure 3: Map of Horseshoe 2 Fire final soil burn severity (Coronado National Forest 2011).Direct causes for the severity of the Horseshoe 2 Fire included a “100 years freeze,” which occurred in February 2010. A multitude of trees, and low desert vegetation including cacti were killed. The large amount of available fuel resulting from the heavy freeze and low moisture content fed the intensity and unpredictable behavior of the fire and producing a soil burn severity pattern that was large and complex (Figure 3).

Fire Impacts on Land and Ecosystems

Joel McMillan from Northern Arizona University describing the behavior of certain species of bark beetles noted that the Douglas-fir beetle infested fire-damaged trees while other species show no preference between a fire-damaged tree and a tree not damaged by fire. Douglas-fir trees are habitat for the Mexican spotted owl and further post-fire tree mortality by the Douglas-fir beetle could threaten its habitat. Currently, the Arizona Zone of Forest Health Protection is monitoring populations of Douglas-fir beetles in the Chiricahua Mountains. In the future they may recommend using a species-offensive pheromone as a “No Vacancy” signal to protect stands of trees.

Pre- and post-fire observations by ecologist Jim Malusa from the University of Arizona in Pinery Canyon at elevations of 5,700 and 6,050 feet show rapid recovery of  vegetation in the scorched areas.  Even areas where soil burn severity was high to moderate, notably the 6,050 feet level near Methodist Road, show signs of recovery among woodland stands of Chihuahuan pine and oaks. 

One of the last presentations of the field trip involved Ann Youberg, research geologist at the Arizona Geological Survey, discussing post-fire debris flows in the Upper Pine Canyon gully. Ann showed how the canyon went from being gully-free in May 2011 to a hosting a visible gully in August 2011, following substantial rainfall. The newly formed gully’s measured 4.5m to 8m wide. Rates of soil regeneration are lower in post fire environments with rates decreasing with increasing slopes.

How to Manage Future Wildfires

Preparing for wildfires is a difficult and chancy business.  To ensure the best possible outcome it is essential to document the progression and impacts of wildfires; how rapidly they grow, their geographic pathways and distribution, and the impact or severity on vegetation and soil. 

As the Southwestern US climate becomes warmer and more arid the frequency and size of wildfires may increase.  The potential rise in wildfires could produce devastating impacts both locally and nationally. Forests, grasslands and other ecosystems in the West are essential to sequestering over 100 million tons of carbon each year, counterbalancing anthropogenic emissions. With the advent of more frequent large fires and climate change, ecosystems of western U.S. may not serve to sequester CO2 as they have in the past

The Southwest Fire Science Consortium fieldtrip offered food for thought concerning wildfires and their impact in the Southwestern U.S. As Kristy Lund from the Coronado National Forest stated, “I think the field trip re-emphasized to me that we often have a skewed perspective of a wildfire while it’s occurring, and in the short term. We often perceive that higher fire intensities are very destructive, and that the damage is so great that the ecosystem recovery will take many years. The reality is that our ecosystems are inherently resilient and begin to recover more quickly than we expect.” Lund’s comments show how much we still have to learn and share about wildfire processes and their intrinsic role in the health and well-being of forests of the arid SW.  Wildfires serve, in part, to rejuvenate forests and it is due largely to human suppression coupled with drought that voracious mega-wildfires have become the new normal in the arid Western U.S .

*To learn more about the Horseshoe 2 Fire or the Southwest Fire Science Consortium feel free to visit their website at http://swfireconsortium.org

 

References & Resources

Kuyumjian, G., 2004, BAER Team: Responding to Post-Fire Threats.  Southwest Hydrology, p. 14-16.  (http://www.swhydro.arizona.edu/archive/V3_N5/feature1.pdf)

U.S. Dept. of the Interior, 12/05/2012, Interior Releases Study of Carbon Storage and Sequestration in Western Ecosystems as Part of National Assessment.  Press Release -  http://www.doi.gov/news/pressreleases/interior-releases-study-of-carbon-storage-and-sequestration-in-western-ecosystems-as-part-of-national-assessment.cfm?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+UsgsNewsroom+%28Newsroom+-+National+Releases%29

InciWeb, 6/27/2010, Final Horseshoe Fire Update.  http://www.inciweb.org/incident/article/1966/10071/

InciWeb, 2011, BAER Soil Burn Severity Map – Horseshoe 2. http://www.inciweb.org/incident/map/2225/0/

NASA Earth Observatory, 5/21/2011, Horseshoe 2 Fire, Arizona.  http://earthobservatory.nasa.gov/IOTD/view.php?id=50676

Southwest Fire Science Consortium.  http://swfireconsortium.org

U.S. Forest Service, 2002, Healthy Forests: An Initiative for Wildfire Prevention and Stronger Communities, 22 p.  http://www.fs.fed.us/projects/documents/HealthyForests_Pres_Policy%20A6_v2.pdf

VIDEO: Kristy Lund from the Coronado National forest recalls the adverse variability of the Horseshoe 2 Fire at the Southwest Fire Science Consortium field trip held on November 8, 2012 in the Chiricahua Mountains (Arechederra-Romero 2012).

 

Recent Graduate of University of Arizona's Geosciences Department, Working as a volunteer at the Arizona Geological Survey

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