<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="351" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://cpw.cvlcollections.org/items/show/351?output=omeka-xml" accessDate="2026-04-15T01:23:05+00:00">
  <fileContainer>
    <file fileId="565">
      <src>https://cpw.cvlcollections.org/files/original/6ddc8342f0055579244e64f6fd246ee1.pdf</src>
      <authentication>9178e88f0a75ca33bcfc1bf82fd6172b</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="92">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="5938">
                  <text>C O L O R A D O

P A R K S

&amp;

W I L D L I F E

Whitewater Park Studies
RESEARCH RESULTS AND DESIGN GUIDELINES

Whitewater Park Research
With over 30 whitewater parks (WWPs) either completed or in the
planning phases, Colorado is the epicenter for WWP development in the
United States. Although WWPs provide economic and recreational
benefits for local communities (Hagenstad et al. 2000; Loomis and
McTernan 2011), they may have unintended impacts on instream biota
and stream functions, particularly when the hydraulic conditions formed
by the WWP are different from those naturally found in the surrounding
river. The impact of WWPs on habitat connectivity and instream habitat
quality have been the focus of several recent studies. Although these
studies have primarily focused on fish passage and habitat, impacts to
aquatic insects and sediment transport may also occur at WWPs.

Fish Passage Impacts
The elements that create a desirable surf wave (increased velocity,
decreased depth, a hydraulic jump, and a stable, often grouted stream
channel) create conditions that can impede fish movement. Swimming
speeds and jumping ability vary greatly between fish species.
Suppression of upstream trout movement has been documented at WWP
structures, but the degree of impact varied by fish size and characteristics
of the individual structure (Stephens et al. 2015; Fox et al. 2016). As trout
are among the strongest swimming and jumping fish species in Colorado,
small-bodied and weaker-swimming fish native to Colorado streams are
even more susceptible to habitat fragmentation associated with WWP
development.

Brown Trout

Mottled Sculpin

Fish Habitat Impacts
Although WWPs create deep pools, observed fish densities were significantly higher in natural pools than in WWP pools
(Kolden et al. 2015; Kondratieff et al. in preparation). Habitat degradation in WWPs was associated with the unnatural
hydraulics created by the recreational features and conversion of riffle habitat to drops over the wave structures.

Design Guidelines
CPW recommends that adequate environmental safeguards be included in the design and construction of WWPs to ensure
that stream functions, fisheries, and recreational fishing are not adversely impacted. Each structure must be examined on a
case-by-case basis, and monitoring and adaptive management should be included in the proposed project budget.

COLORADO PARKS &amp; WILDLIFE • 1313 Sherman St., Denver, CO 80203 • (303) 297-1192 • cpw.state.co.us

�Site Selection




Design and construction of WWPs should preserve the
natural aesthetic qualities of the river. WWPs should be
located in degraded reaches when possible and should aim
to improve the natural functions of the reach rather than
maintain degraded conditions. WWPs should not be
constructed in natural, un-modified river channels
(American Whitewater 2007).
WWP sites should be selected to minimize recreational
conflicts with anglers. There is increased potential for
boaters to displace anglers at WWP sites, especially during
the summer months. If WWP construction affects a popular
fishing location, mitigation such as new fishing access or
habitat improvements should be considered.

Ecological Design Considerations







WWP structures must be designed to allow upstream fish passage for all life stages of native and sport fishes present
throughout the annual hydrologic cycle. Fish passage is dependent on water velocity, water depth, vertical height of
structures, linear distance of the passage corridor, surface roughness, and attraction flow.
Hydraulic characteristics at WWP features generally conflict with ideal conditions for fish passage. Therefore, a fish
passage channel separate from the WWP structure may be necessary. The passage channel should meet hydraulic design
criteria for target species across a range of flows.
Hydraulic modeling of the proposed structure should be conducted during the initial design phase to evaluate potential
impacts to fish passage and habitat.
Streambed and bank disturbance due to construction activities should be scheduled for a time of year when egg
incubation is not occurring. An increase in fine sediment to the stream during incubation can suffocate developing
embryos. Erosion control and revegetation plans utilizing native riparian species should be required for each project.
WWP structures should not cause sediment deposition upstream or downstream of the structure. Sediment deposition
can eliminate fish and benthic macroinvertebrate habitats, create favorable conditions for the spread of whirling disease
in trout, and increase flooding risk if sediment deposition decreases channel capacity.
Recreational In-channel Diversion (RICD) water rights can be acquired for WWPs to provide recreational experiences
in and on the water. These protected flows should be managed to benefit boating recreation as well as conservation and
management of native and sport fish. Flows deviating from the natural flow regime, such as water calls during spawning
periods, could have adverse impacts on stream ecology (Poff et al. 1997).

References
American Whitewater, 2007. Whitewater Parks – Considerations and Case Studies.
https://www.americanwhitewater.org/content/Wiki/stewardship:whitewater_parks
Fox, B. D., B. P. Bledsoe, E. Kolden, M. C. Kondratieff, and C. A. Myrick. 2016. Ecohydraulic evaluation of whitewater parks as a fish passage barrier. Journal of the American
Water Resources Association. DOI: 10.1111/1752-1688.12397.
Hagenstad, M., J. Henderson, R. S. Raucher, J. Whitcomb. 2000. Preliminary evaluation of
the beneficial value of waters diverted in the Clear Creek Whitewater Park in the City of
Golden. Stratus Consulting.
Kolden, E., B. D. Fox, B. P. Bledsoe, and M. C. Kondratieff. 2016. Modelling whitewater
park hydraulics and fish habitat in Colorado. River Research and Applications. DOI:
10.1002/rra.2931.
Kondratieff, M. C., K. Kinzli, and E. R. Fetherman. In preparation. Eco-hydraulic evaluation
of whitewater parks as fish habitat in Colorado.
Loomis, J., and J. McTernan. 2011. Fort Collins Whitewater Park economic assessment.
Department of Agricultural and Resource Economics, Colorado State University.
Poff, N. L., J. D. Allan, M. B. Bain, J. R. Karr, K. L. Prestegaard, B. D. Richter, R. E. Sparks,
and J. C. Stromberg. 1997. The natural flow regime: a paradigm for river conservation and
restoration. BioScience 47(11): 769-784.
Stephens, T. A., B. P. Bledsoe, B. D. Fox, E. Kolden, and M. C. Kondratieff. 2016. Effects
of whitewater parks on fish passage: a spatially explicit hydraulic analysis. Ecological
Engineering 83: 305–318.

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="20">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7200">
                <text>Fact Sheets</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7201">
                <text>Fact Sheet</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7202">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7210">
                <text>CPW Fact Sheets</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5928">
              <text>Whitewater park studies</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5929">
              <text>With over 30 whitewater parks (WWPs) either completed or in the&#13;
planning phases, Colorado is the epicenter for WWP development in the&#13;
United States. Although WWPs provide economic and recreational&#13;
benefits for local communities (Hagenstad et al. 2000; Loomis and&#13;
McTernan 2011), they may have unintended impacts on instream biota&#13;
and stream functions, particularly when the hydraulic conditions formed&#13;
by the WWP are different from those naturally found in the surrounding&#13;
river. The impact of WWPs on habitat connectivity and instream habitat&#13;
quality have been the focus of several recent studies. Although these&#13;
studies have primarily focused on fish passage and habitat, impacts to&#13;
aquatic insects and sediment transport may also occur at WWPs.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5930">
              <text>Colorado Parks and Wildlife</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5931">
              <text>Whitewater parks</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="78">
          <name>Extent</name>
          <description>The size or duration of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="5932">
              <text>2 pages</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="56">
          <name>Date Created</name>
          <description>Date of creation of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="5933">
              <text>2016</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5934">
              <text>http://rightsstatements.org/vocab/InC/1.0/</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5935">
              <text>Fact Sheet</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5936">
              <text>application/pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5937">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="70">
          <name>Is Part Of</name>
          <description>A related resource in which the described resource is physically or logically included.</description>
          <elementTextContainer>
            <elementText elementTextId="5939">
              <text>Fact Sheets</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
