Laserfiche WebLink
Purgatory Creek Watershed Storm Drain Study <br />hyetograph. <br />b. Identify input hydrograph(s) (Purgatory, Purgatory Trib No. 3, etc.) as needed. <br />c. Identify two (2) historical floods for calibration/validation. <br />2.3 Initial Test Run and Troubleshooting <br />a. Select time step and other initiation parameters. <br />b. Run storm events and debug. <br />c. Run historical floods and validate model with high water marks and/or staff reports. <br />d. Make adjustments to the model (n values, rainfall losses, etc.). <br />e. Select reporting depth (e. g. flow depths >0.3 feet) and meet with City to review draft <br />maps/results. <br />3. Inundation Mapping— Once the model is up and running and the initial results have been reviewed <br />with the City staff, LAN will develop an inundation map of the study area. <br />4. Post Processing: Characterization and Identification of Problem Areas — Once the inundation <br />mapping is completed, LAN will characterize the flooding issues for the area and the problem areas <br />as defined by the following: <br />a. Characterize source(s) of flooding (e. g. local, inlet control, pipe control, tail water or <br />watershed overflow). <br />b. Identify locations where flow leaves right of way (ROW). <br />c. Estimated the number of flood structures (based on assumed finished floor elevations). <br />Prepare Flood Assessment Report — LAN will document the methods of the analysis, summarize the <br />results and prepare a draft of the Phase II scope of services. LAN will also make presentation to <br />staff and/or city council as requested. <br />