watervulnerability

watervulnerability watervulnerability

18.01.2013 Views

Assessment of Watershed Vulnerability to Climate Change Umatilla National Forest March, 2012 Prepared by: Caty Clifton, Forest Hydrologist Kate Day, Hydrologist Allison Johnson, Fishery Biologist Umatilla National Forest Pendleton, Oregon and Ukiah, Oregon 210 Assessing the Vulnerability of Watersheds to Climate Change

Umatilla National Forest Watershed Vulnerability Assessment, Pacific Northwest Region (R6) BACKGROUND AND FOREST CONTEXT National Forests across the country are evaluating the risk posed by climate change to important water resources on the forests and adjoining lands. These evaluations are focused on climate-induced hydrologic change, impacts on water diversions and aquatic species, and interactions with infrastructure. These Watershed Vulnerability Assessments (WVAs) provide real world examples of issue-based and landscape-specific approaches to assessing the vulnerability of national forest watersheds and resources to climatic changes, and planning and implementing effective adaptation. The general intent is to display, for managers, the relative vulnerability of watersheds to climate change, and identify watersheds containing water “values,” or systems that may be susceptible to changes in hydrologic conditions (Hurd et al. 1999; Furniss et al. 2010). On the Umatilla National Forest (UNF), vulnerability was considered at the following two landscape and issue scales. 1. Forestwide at the HU12 scale (162 subwatersheds have UNF ownership from

Assessment of Watershed Vulnerability<br />

to Climate Change<br />

Umatilla National Forest<br />

March, 2012<br />

Prepared by:<br />

Caty Clifton, Forest Hydrologist<br />

Kate Day, Hydrologist<br />

Allison Johnson, Fishery Biologist<br />

Umatilla National Forest<br />

Pendleton, Oregon and Ukiah, Oregon<br />

210 Assessing the Vulnerability of Watersheds to Climate Change

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!