My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2021-01-11-minutes-public-works-study-session
>
Meetings
>
2021
>
01. January
>
2021-01-19 10:00 AM - Commissioners' Agenda
>
2021-01-11-minutes-public-works-study-session
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/14/2021 1:14:24 PM
Creation date
1/14/2021 1:11:04 PM
Metadata
Fields
Template:
Meeting
Date
1/19/2021
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Alpha Order
a
Item
Approve Minutes
Order
1
Placement
Consent Agenda
Row ID
71688
Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
74
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
4.2 HYDRAULIC ANALYSIS <br />The Cedar Gulch HEC -RAS model was configured and run for the 100 -year flows listed in Table 3. The <br />upper and lower Crystal Creek models were run for the five flow quantiles (10-, 25-, 50-, 100-, 500 -year <br />events) shown in Table 3. Flows were specified at the upstream end of each reach, confluence locations, <br />and downstream of major tributary inflows. <br />Normal depth boundary conditions were applied at the downstream end of Cedar Gulch Creek and the <br />lower Crystal Creek model reach, and at the downstream (east) boundary of the 2D area in Cie Elum. <br />Friction slopes were determined based on average channel/basin slope at each location. The upper Crystal <br />Creek steady ID model used a fixed water surface boundary condition that was based on the steady state <br />water surface elevation output from the lower Crystal Creek model. <br />Model simulations for Cedar Gulch Creek and Upper Crystal Creek were performed using the subcritical <br />t <br />flow regime option. Model simulations for the lower Crystal Creek ],* D model were performed using <br />the subcritical unsteady flow option with constant inflows (pseudy state). For model stability, flows <br />in the lower Crystal Creek model were ramped up to the V staff ipflow shown in Table 3 over <br />approximately 48 hours. <br />4.2.2 MODEL RESULTS <br />Model results for the 100 -year event on Cedar QWch Creek, fpr Crystal Creek, and Lower Crystal Creek <br />are included in Appendix A. Flood profiles forth$Z]-; 50-, 1•, and 500 -year event on Crystal Creek <br />are provided in Appendix B as 01P through 20P — mj-oed`ac�3rding to FEMA FIS profile guidelines and <br />specifications. Mapping was completed"date'l replace the effective FEMA floodplain within the <br />5 ' <br />study area. <br />4.2.3 FLOODWAY MODELING <br />The "regulatory floodwa means chAgi*1 of the creek and the adjacent land that must be reserved <br />in order to discharge* 100 -year fIciaod without increasing the water surface elevation more than a <br />designation height (typic�N'"1_foot).SE defined a floodway for the entire Crystal Creek study reach. An <br />effective floodway currently e4"r the lower 9900 feet of Crystal Creek but was defined as "coincident <br />with the 100 -year boundary" (FtMA, 1981). WSE determined an updated floodway boundary through an <br />encroachment analysis by the following steps: <br />Within the lower model: <br />Applied the effective floodway boundary to the updated model using blocked obstructions. The <br />boundary had to be adjusted in several areas where the effective floodway boundary was outside <br />the current 100 -year boundary. <br />• Ran the model to simulate the 100 -year flood, with floodway enforced. <br />Compared floodway water surface elevations to BFEs to determine if floodway rise was less than <br />1 foot at all cross sections. <br />WATERSHED P a g e 19 <br />SCIENCE 4 ENGINLERING <br />
The URL can be used to link to this page
Your browser does not support the video tag.