Laserfiche WebLink
399 <br />Chair Vanderwall concurred that a better explanation and definition would be <br />400 <br />helpful; with Mr. Leaf concurring, and suggesting that some graphics may also <br />401 <br />help in that explanation. <br />402 <br />403 <br />With Mr. Leaf explaining the calculations in determining those freeboard <br />404 <br />elevations, Member DeBenedet opined that he wasn't confident that they were all <br />405 <br />that conservative. While there was always the potential that a rainstorm would <br />406 <br />exceed those estimates, Member DeBenedet opined that once the new storm <br />407 <br />design numbers were released next spring that would become even more evident. <br />408 <br />409 <br />Ms. Bloom advised that this challenge had been a discussion internally, regardless <br />410 <br />of changing a table to comply with new rules; and current infrastructure designed <br />411 <br />around previous designs storm numbers and concepts. Ms. Bloom opined that the <br />412 <br />challenge was the ripple affect; creating the need for an updated plan. Ms. Bloom <br />413 <br />advised that enforcing freeboard calculations with existing numbers created no <br />414 <br />compliance issues; however, with the new numbers, it created a lot of issues in the <br />415 <br />community; and would need considerable review. <br />416 <br />IVOL <br />417 <br />At the request of Chair Vanderwall regarding creat g liability issues for the City, <br />418 <br />Ms. Bloom noted this was why staff was currently hesitant to address-the issue at <br />419 <br />this time, since there were bigger policy issues one those numbers were <br />420 <br />published. <br />421 <br />422 <br />Member Stenlund noted the "grandfather clause" and differing rules based on <br />423 <br />which plan was in effect at a given time; and making sure future plans are well <br />424 <br />aware of the a dated data. <br />425 <br />Page 10 of 15 <br />