<?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>Luke McGuire</dc:contributor>
  <dc:contributor>Brian A. Ebel</dc:contributor>
  <dc:contributor>G. E. Tucker</dc:contributor>
  <dc:creator>Francis K. Rengers</dc:creator>
  <dc:date>2018</dc:date>
  <dc:description>The transition of a colluvial hollow to a fluvial channel with discrete steps was observed after two landscape-scale disturbances. The first disturbance, a high-severity wildfire, changed the catchment hydrology to favor overland flow, which incised a colluvial hollow, creating a channel in the same location. This incised channel became armored with cobbles and boulders following repeated post-wildfire overland flow events. Three years after the fire, a record rainstorm produced regional flooding and generated sufficient fluvial erosion and sorting to produce a fluvial channel with periodically spaced steps. An analysis of the step spacing shows that after the flood, newly formed steps retained a similar spacing to the topographic roughness spacing in the original colluvial hollow (prior to channelization). This suggests that despite a distinct change in channel form roughness and bedform morphology, the endogenous roughness periodicity was conserved. Variations in sediment erodibility helped to create the emergent steps as the largest particles ( &gt;D84) remained immobile, becoming step features, and downstream soil was easily winnowed away.</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:identifier>10.1016/j.geomorph.2018.01.003</dc:identifier>
  <dc:language>en</dc:language>
  <dc:publisher>Elsevier</dc:publisher>
  <dc:title>The evolution of a colluvial hollow to a fluvial channel with periodic steps following two transformational disturbances: A wildfire and a historic flood</dc:title>
  <dc:type>article</dc:type>
</oai_dc:dc>