Comparison of Methods for Estimating Stream Channel Gradient Using GIS

Comparison of Methods for Estimating Stream Channel Gradient Using GIS

Comparison of Methods for Estimating Stream Channel Gradient Using GIS David Nagel, John Buffington, and Daniel Isaak USDA Forest Service, Rocky Mountain Research Station Boise Aquatic Sciences Lab Boise, ID September 14, 2006 Special thanks to Sharon Parkes…. StreamStream ChannelChannel GradientGradient Rate of elevation change High Low ComputingComputing GradientGradient Rise / Run = Slope 2115 m 5 m 2110 m 100 m 5 / 100 = .05 = 5% slope ReasonsReasons forfor ModelingModeling StreamStream GradientGradient • Predictor of channel morphology Pool-riffle Plain-bed Step-pool 1% 3 - 4% 10% ReasonsReasons forfor ModelingModeling StreamStream GradientGradient • Estimate distribution of aquatic organisms “Channel gradient and channel morphology appeared to account for the observed differences in salmonid abundance, which reflected the known preference of juvenile coho salmon Oncorhynchus kisutch for pools.” - Hicks, Brendan J. and James D. Hall, 2003 ReasonsReasons forfor ModelingModeling StreamStream GradientGradient • Predict debris flow transport and deposition “Transportation and deposition of material in confined channels are governed primarily by water content of debris, channel gradient, and channel width.” - Fannin, R. J and T. P. Rollerson, 1993 OurOur PurposePurpose forfor ModelingModeling StreamStream GradientGradient • Estimate stream bed grain size to identify salmon spawning habitat 1−n n 1000ρghS 1000cAρ f Sb aA Grain= Size = ( ) ( ) ρ()s − ρg * τ ρ()s − ρk S = channel slope Grain size 16 – 51 mm StudyStudy AreaArea 10,000 km of rivers and streams ChinookChinook SalmonSalmon SpawningSpawning SitesSites 19951995 -- 20042004 ResearchResearch questionsquestions 1) Where are the optimum spawning sites? 2) Where might spawning expand if populations increased to historical levels? 3) Can grain size prediction be applied elsewhere? 50 km MeasuringMeasuring GradientGradient Directly Remotely DigitalDigital DataData Some preliminary information NecessaryNecessary DataData 1) Elevation - to compute rise 2) Stream lines - to compute run ChooseChoose ElevationElevation DataData Digital Elevation Model Contour lines (DEM) USGS National Elevation Dataset USGS 1:24,000 scale (NED) DEMDEM ProductionProduction ProcessProcess 1) Aircraft 2) Aerial photo 3) Stereo plotter 4) Map production 5) Scan and tag 6) LT4X OriginalOriginal ContoursContours andand 1010 mm DEMDEM ModelModel 500 m LT4X Original 40’ contours 2 m contours derived from 10 m DEM Blue box = 100 m x 100 m OriginalOriginal ContoursContours andand 1010 mm DEMDEM ModelModel LT4X Original 40’ contours 2 m contours derived from 10 m DEM ChooseChoose StreamStream LineLine DataData National Hydrography Synthetic stream lines Dataset (NHD) NHDNHD andand SyntheticSynthetic ComparisonComparison Higher gradient Low gradient SyntheticSynthetic StreamsStreams “Fit”“Fit” thethe DEMDEM Synthetic streams follow NHD streams often fall the flow accumulation on DEM side slopes path and fall within the DEM channel NHD and 10 m DEM Contours 2 m interval Flow NHDNHD andand 1010 mm DEMDEM ContoursContours 2 m interval 2 1 ow Fl NHDNHD StreamsStreams RepresentRepresent SinuositySinuosity MoreMore AccuratelyAccurately ShorteningShortening withwith SyntheticSynthetic StreamsStreams isis SubstantialSubstantial In low gradient areas, synthetic streams can underestimate stream length by approximately 25% 5412 m vs. 4092 m The Dilemma Elevations along synthetic streams consistently flow down hill and represent elevation (rise) more normally However…. Stream channel length, or sinuosity (run) is better represented by NHD stream lines Rise / Run = Slope BestBest DataData ChoicesChoices forfor ComputingComputing StreamStream ChannelChannel GradientGradient 1) 10 m NED DEM 2) NHD stream lines SpatialSpatial AccuracyAccuracy ofof NHDNHD MeasuringMeasuring GradientGradient MeasuringMeasuring GradientGradient We used three approaches dependent on gradient 1) High slope – 3% - 50% gradient 2) Mid-slope – 1.4% mean 3) Main stem – 1.0% or less High slope Mid- Stream channel slope profile Main stem WhyWhy UseUse ThreeThree Approaches?Approaches? DEM accuracy changes depending on the original quad contour spacing and Landscape position PossiblePossible ApproachesApproaches At stream At contour intersections crossings Equal interval WhyWhy NotNot UseUse ContourContour CrossingsCrossings forfor EntireEntire StudyStudy Area?Area? 1) Not available for the entire study area 2) Tag ends and stream intersections create technical problems HighHigh SlopeSlope High slope Mid- slope Main stem We’ll use 100 m equal intervals 1010 mm DEMDEM AccuracyAccuracy inin HigherHigher GradientGradient AreasAreas 2 km For comparison, compute Blue = higher gradient slope using 1:24 k contours streams and DEM ContourContour andand DEMDEM GeneratedGenerated SlopeSlope ComparisonComparison 45 40 35 30 25 20 15 10 DEM Generated Slope (%) Slope Generated DEM 5 0 0 5 10 15 20 25 30 35 40 45 Contour Generated Slope (%) Note divergence at higher slopes SlopeSlope andand SegmentSegment LengthLength 45 40 35 30 25 DEM Slope 20 Contour Slope Slope (%) Slope 15 10 5 0 0 100 200 300 400 500 600 700 800 900 Segment Length (m) Contours get closer together at higher slopes and segment length decreases Note error in DEM model ErrorsErrors vs.vs. StreamStream SegmentSegment LengthLength 8.00 6.00 4.00 2.00 0.00 -2.00 -4.00 -6.00 Error (Contour Slope - DEM Slope) Slope Error (Contour -8.00 0 100 200 300 400 500 600 700 800 900 Segment Length (m) Mean slope error for segment lengths: Greater than 100 m .42% pts Equal to 100 m .68% pts Less than 100 m 1.64% pts MedianMedian StreamStream SegmentSegment LengthLength 40’ Contour Interval Segment length between contours Mean = 147 m Median = 114 m n = 411 70 60 50 40 30 Frequency 20 10 0 20 60 100 140 180 220 260 300 340 380 More Segment Length (m) GradientGradient CalculationCalculation forfor HigherHigher SlopeSlope ReachesReaches –– 100100 mm SpacingSpacing 1) We used 100 m interval spacing along NHD lines with 10 m DEM. 2) Fine enough resolution to detect some natural barriers (slope > 20%) 3) Not so coarse that undesirable averaging occurs Average error = 0.68% pts MainMain StemStem High slope Mid- slope Main stem GradientGradient CalculationCalculation forfor MainMain StemStem ReachesReaches ContourContour SlopeSlope vs.vs. 100100 mm IntervalInterval 6.0 4.0 2.0 0.0 -2.0 3 km -4.0 Error (Contour Slope - DEM Slope) -6.0 0.00 0.20 0.40 0.60 0.80 1.00 1.20 1.40 1.60 1.80 2.00 Slope (%) Average error = .75% pts GradientGradient CalculationCalculation forfor MainMain StemStem ReachesReaches StreamStream IntersectionsIntersections 6.00 4.00 2.00 0.00 -2.00 3 km -4.00 Error (Contour - Slope Str. Int. Slope) -6.00 0.00 0.20 0.40 0.60 0.80 1.00 1.20 1.40 1.60 1.80 2.00 Slope (%) Average error = .39% pts GradientGradient CalculationCalculation forfor MainMain StemStem ReachesReaches atat ContourContour CrossingsCrossings 3 km LiDARLiDAR vs.vs. ContourContour GradientGradient ComparisonComparison Green LiDAR 3 2 Segment Contour LiDAR No. Slope Slope 1 .41% .45% 2 .35% .35% 1 3 .36% .32% 2 km Average error = .03% pts GradientGradient CalculationCalculation forfor MainMain StemStem ReachesReaches • We used quad contour crossings along main stem 3 km • Contour crossings were digitized on-screen from DRGs Average error = .03% pts MidMid--slopeslope High slope Mid- slope Main stem MidMid--slopeslope ReachesReaches MidMid--slopeslope ReachesReaches andand FlatFlat ValleyValley BottomBottom DelineationDelineation Procedure 1) Overlay valley bottom 2) Exclude main stem reaches MidMid--slopeslope ReachesReaches ComputeCompute SlopeSlope BetweenBetween BreakBreak LinesLines andand StreamStream IntersectionsIntersections withwith 1010 mm DEMDEM GradientGradient CalculationCalculation forfor MidMid--slopeslope ReachesReaches 1) We used 10 m DEM elevations at valley bottom break lines and stream intersections 2) Output not validated against contours, but should be better than main stem results at intersections Average error < .39% pts FinalFinal StreamStream GradientGradient MapMap FieldField DataData FieldField CalculatedCalculated vs.vs. GISGIS CalculatedCalculated GradientGradient n = 238 50 km FieldField CalculatedCalculated vs.vs. GISGIS CalculatedCalculated GradientGradient 16.0 14.0 12.0 10.0 8.0 6.0 4.0 GIS Calculated Slope (%) Slope Calculated GIS 2.0 0.0 0.0 2.0 4.0 6.0 8.0 10.0 12.0 Field Calculated Slope (%) Average error = 1.54% pts R-squared = .67 ConclusionsConclusions 1) The most appropriate interval spacing for measuring slope in higher gradient areas is about 100 m when using 10 m DEM data. Average error ~ 0.68% pts. 2) For main stem, low gradient channels, gradient is best computed between quad contour intervals. Average error ~ 0.03% pts. 3) At intermediate slopes, gradient can be computed between valley bottom break lines and stream intersections with 10 m DEM data. Average error < 0.39% pts. RecommendationRecommendation 10 m DEM data have variable accuracy dependent on slope and landscape position Fish and watershed models that incorporate stream gradient should account for these errors Acknowledgements RMRS – Boise Lab John Buffington – Research Geomorphologist Dan Isaak – Research Fisheries Biologist Bruce Rieman – Research Fisheries Biologist Russ Thurow – Research Fisheries Biologist Sharon Parkes – GIS Specialist Dona Horan – Fisheries Biologist Jim McKean – Research Geomorphologist Carolyn Bohn – Hydrologist Bob Smith – Idaho Department of Lands.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    59 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us