meeting

2/26/98 Presentation Outline
2/19/98 Project "check in"
2/12/98 Meeting with Laura Vaugeois
2/10/98 Initial Brainstorm Session/Objectives

2/26/98 Presentation Outline

Note: This is only a rough outline with approximate time allotments. Changes will probably be made as the entire class brings the presentation together.

I. Introduction (Kai, 5 minutes)

A. Objective- find critical areas in watershed for the purposes of FE 450

B. Clarify that this is not a "watershed analysis" as much as an exercise to find specific information for FE 450

C. Outline the order of the rest of the presentation

D. General overview, information, site description

II. General Meta Data (Luke, 10 minutes)

A. What does data mean?

B. Where does data come from?

C. How was the data collected?

III. 6 modules

A. Where does data come from? (discuss inputs)

B. How does this compare to standard methodology?

C. What is the process that is being modeled?

D. How does this area affect watershed as a whole?

E. What are the critical areas and potential hazards?

Mass Wasting (Abby, 8 minutes)

Surface Erosion and Hydrology (Rachel, 10 minutes)

Fish and Channel (Jon, 10 minutes)

Riparian (Candace, 8 minutes)

IV. Conclusion (Kai, 5 minutes)

A. Summary

B. Suggestions for change (i.e. data collection)

V. Discussion/Questions with Peter as moderator (30-40 minutes)

2/19/98 Project "check in"

Reminder!! Make space in the U drive! There is only 1% of the capacity left. Please look through your folders and clean it out!

I. Deadlines

A. Report due Wednesday, March 11

B. Presentation on Wednesday, March 18

1. Allot 60-70 minutes for presentation and 40-50 minutes for questions/discussion

2. Presumably we will be presenting to the same crew that the FE seniors will be working with throughout Spring Quarter

3. To make it less confusing, there is a suggestion that 6 or 7 people be designated as presentors as opposed to the entire class. Are there any
volunteers?

II. Suggested Guideline for Webpage format

A. Introduction- Why would you want to read this?

B. Method- How did you accomplish? (with your intended audience being the FE 423 class of '99) Also include your AML code here

C. Results- What?

D. Discussion- Who cares? Why?

III. Technical info

A. Covgrid created for importing coverages

B. Need to document codes

C. Add clip function to cov grid

D. Connect all AMLs in window format

IV. Soils- still need to extend boundaries

V. DEM- change to 10 m?

VI, Ortho- no new information

VII. Hydrology input- no new information

VIII. Channel- no new information

IX. Transportation

A. Road type- paved, unpaved, or trails

B. All roads are older than 2 years

C. Include access to major roads

X. Hydrology module- no new information

XI. LULC

A. Land cover- old growth to clearcuts (5 categories)

B. Extend LULC? (with Ortho)

XII. Mass Wasting (Lab #3 and Lab #6)

A. Use LULC to model thinning

B. Use soil inventory and data dictionary to test unstable areas identified by grid

C. Volume of sediment that would reach stream if road fails

D. If area slides, does it deliver to a stream?

E. If it reaches stream, does it create a debris flow?

XIII. Surface Erosion

A. Identify proximity to streams (Luke)

XIV. Riparian (using LULC input)

A. Identify trees (is large woody debris going to be available?)

B. Soil conditions for migration hazards

C. Look at orthophoto for past conditions

D. Place where riparian management zone needs to be increased beyond forest practice act

E. Use ortho photos to give current width of RMZ

XV. Fish

A. Species and spawning season

B. Connect with channel

Technical Hints

A reminder: Don't just plug and chug. Think about the data that you are using. Some questions to ask:

a. Where does the data come from?

b. How was the data collected?

c. What was the original purpose of the data?

d. How reasonable is it to use this data for your purposes?

Grid sizes should be approximately the same size in each coverage. This ensures the best matching of coverages as possible
Attempts to make our data have a finer resolution w/o actually changing the raw data will not give much benefit. All this really does is make our grid size larger which gives the computer more data to process which increases computer time.
Document your AMLs! Include a heading that answers the following questions:

a. Why did you make this program?

b. What does it do?

c. Where did you get your variables from?

d. Who are you?

e. When did you write this program?

Basically, write the program so anyone can understand it and be able to duplicate what you did. This may come in handy 2 months from now at Pack when you are trying to figure out your program!

Code tables are defined in a notebook left by Laura. These codes could be input into the computer. Does anyone think this is necessary?

2/10/98 Brainstorm Session

For all modules- zoom in on Watershed area (4 townships?)

Technical assistance?? Ask Luke!

Input Data

I. DEM Objectives

A. Classification of Slope Class

1. 0-30%

2. 30-70%

B. Shade Map for presentation purposes

C. Terrain Classification

D. Elevation data of stream channels

E. Metadata--where did the data come from?

II. Soils Objectives

A. Calculations--k values, cohesion, slope angle

B. Table of values in WSA handbook--put information on webpage?

C. Need to extend boundaries; approximate areas that are not included in DEM

D. Parent Material grid

III. LULC Objectives

No information obtained

IV. Ortho Objectives

A. Can any information be obtained from the gray scale?

1. Can relationships be obtained? (i.e. timber typing)

2. Are there any measurement relationships? (i.e. can distances be measured?)

B. Use as a background to be overlayed by other coverages

V. Hydrology Objectives

A. Stream Typing

B. Stream Location

VI. Transportation Objectives

A. Proximity to/from streams (with Fish module)

B. Number of stream crossings (with Fish module)

C. Create 2 transportation layers

1. Zoom in on Washougal watershed (4 townships instead of 6)

2. Include a map that has all major access roads to planning area

For Surface Erosion module:

D. Traffic Frequency

E. Surface and Material

F. Road age (greater than 2 years or less than 2 years old?)

G. Road Width

H. Cut/Fill coverage

Output Modules

I. Mass Wasting Objectives

A. Where is land going to fail?

B. Sediment delivery

C. Failure due to roads

II. Surface Erosion Data Needs

A. Soil- Parent Material

B. LULC- currently assuming that the entire area is forested

C. Hydrology

1. Stream Location

2. Stream Type

3. Annual Precipitation

D. Transportation

1. Cut/Fill

2. Surface and Material

3. Traffic Frequency

4. Road Width

E. Ortho

1. Best way to estimate soil erosion?

2. General land description (i.e. any visible landslide areas?)

F. Outputs- Maps about sediment delivery

III. Hydrology

A. Data Needs

1. Peak Flow

2. Precipitation (from Jun)

3. DEM

B. Outputs- Rain on Snow

1. How does this affect hillslope saturation?

2. How does this affect potential landslides?

IV. Channels Objectives

A. Determine channel sensitivity

V. Riparian

A. Data Needs

1. Use LULC for stream shading

2. Use Soil Erosion for hazard areas that may need expanded riparian management zones

B. Output- A map of stream types 1-3

VI. Fish

A. Data Needs

1. Channel sensitivity

B. Objectives

1. Identify fish bearing streams (usually less than 4% gradient)

2. Road proximity (with Transportation module)

3. Stream Crossings (with Transportation module)

4. Affects of soil erosion during spawning season

5. Identify areas of ideal spawning/habitat

a. Identify shade areas

b. Identify large pools

Webpage created and maintained by Kai M. Brown with assistance from Jason Bradbury

Last updated on March 11, 1998