Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, September 7, 2011 <br />Page 8 <br />various models developed, based on PM Peak Trips from various developments, <br />345 <br />determining how network trips were determined and how traffic was distributed through <br />346 <br />the development and immediate area surrounding it. <br />347 <br />Member Boguszewski noted that these models and use of the word “probably” were <br />348 <br />based on the Institute of Traffic Engineers using historical data with some science <br />349 <br />involved in those calculations. <br />350 <br />City Engineer Bloom confirmed that the models were indeed based on standard traffic <br />351 <br />modeling and assumptions, with trips per square foot, and determining other uses and <br />352 <br />how and where traffic was being generated and distributed throughout the area, as well <br />353 <br />as determining how many different improvements a particular development touches. <br />354 <br />Line 114, Timing <br />355 <br />Member Boguszewski questioned how the effective date of this ordinance and the <br />356 <br />seventeen (17) identified improvements would remain relevant six (6) years from now if <br />357 <br />the numbers generating the predicted trips changed substantially and how the table of <br />358 <br />network trips would be adapted over time as changes occur. <br />359 <br />City Engineer Bloom advised that, at this time seventeen (17) improvements were <br />360 <br />identified, and there were no others anticipated. Ms. Bloom noted that Iona had been <br />361 <br />added as part of the Metropolitan Transit Park and Ride development; however, she <br />362 <br />advised that an annual review was done to ensure the model remained relevant. <br />363 <br />Member Boguszewski opined that this language enabled developers, but did not hold <br />364 <br />them accountable for old or outdated studies. <br />365 <br />City Engineer Bloom advised that the models in the allocation study were based on the <br />366 <br />AUAR, and additional changes were not anticipated, as the uses weren’t changing. Ms. <br />367 <br />Bloom noted that, as individual development proposals came forward, a hard and <br />368 <br />thorough examination of all uses and their compatibility was done as part of the AUAR <br />369 <br />review; with any related mitigation efforts for the AUAR identified at that time. Ms. Bloom <br />370 <br />noted that, from a staff perspective and with a total of $24 million in improvements, <br />371 <br />enforcement was a necessity and part of staff’s charge from previous City Council <br />372 <br />directive and formal action. <br />373 <br />Member Boguszewski advised that his concerns were not with methodology or <br />374 <br />application, just with fixed outcomes versus reality. <br />375 <br />City Engineer Bloom responded that roadways within the Twin Lakes Redevelopment <br />376 <br />District and intersections as identified all impacted the overall area. <br />377 <br />Section E – Chart <br />378 <br />Chair Boerigter sought clarification on the static numbers based on previous uses, and <br />379 <br />how their basis from historical numbers could be proved correct, rather than forcing an <br />380 <br />appeal process to prove them incorrect. <br />381 <br />City Engineer Bloom advised that existing uses were evaluated; along with PM Peak <br />382 <br />Hour trips based on ITE standards, and determined to be fair after significant discussion <br />383 <br />and as those uses were abandoned on some of the sites. Ms. Bloom advised that the <br />384 <br />proposed ordinance had been developed taking that into consideration and she didn’t <br />385 <br />anticipate those base numbers changing. Ms. Bloom noted that, once the ordinance was <br />386 <br />in place, revisions could be made through a Public Hearing process only. <br />387 <br />Chair Boerigter questioned how new developments assumed above the anticipated uses <br />388 <br />would participate in the overall cost, or if it was a static number versus a future number. <br />389 <br />City Engineer Bloom responded that it was the nature of the AUAR that residential <br />390 <br />development in some areas would generate less traffic than some commercial uses; and <br />391 <br />if future development didn’t exceed the base line numbers, a developer may not have any <br />392 <br />costs in the allocation. <br />393 <br />Member Wozniak questioned why there was no “#11” on the table. <br />394 <br /> <br />