Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />. <br /> <br />Attachment B: Planning Commission Meetinl! Excer{lt <br /> <br />12. Consideration should be made for improvements to the Hwy 96/10 and 96/1-35W intersections <br />as per the traffic study; <br />13. Reconstruction of the intersection of Gateway Boulevard and Round Lake Road should be <br />considered to accommodate development; and <br />14. The applicant must obtain all necessary reviews and permits from Rice Creek Watershed <br />District. <br /> <br />Chuck Habiger, HKS Associates, stated applicant's tower was no longer in compliance with State <br />guidelines and that was the reason they were requesting this proposal. Mr. Habiger summarized <br />applicant's proposal and presented site plans for the area. <br /> <br />Mr. Habiger clarified that all of the panels on the building would be glass with the pre-finished <br />aluminum being around the giass. <br /> <br />William Smith, Transportation Planner with Biko Associates, summarized the traffic study and the <br />development of Chesapeake Companies. He indicated two traffic studies had been prepared on <br />the site, one before the Chesapeake office development was developed and the other one <br />prepared in 2000. The results from the first study indicated the intersection could accept an <br />additional 1 , 1 00 cars during peak hours. He stated while the intersection could handle the <br />additional cars, there was concern regarding the ramp terminals on and off of 135W. He indicated <br />traffic signals would probably fix any problems with those ramp terminals. However, any <br />improvements with the ramps would probably not be made until 2003. <br /> <br />Commissioner Pakulski inquired about the lane width. Mr. Smith replied the lane width was chosen <br />for traffic calming purposes and there would be no parking allowed on the street. <br /> <br />Tom Stella, United Properties, summarized the market conditions for office space versus <br />office/warehouse space. <br /> <br />Mr. Habiger addressed the concerns regarding the tower including safety issues raised by staff. <br />Mr. Habiger stated applicant had a contractual obligation for the tower for the next 17 years and it <br />wouid be a financial hardship for applicant to take the tower down and redevelop the site. Mr. <br />Habiger restated that the current design of the tower did not meet the Code requirements. <br /> <br />Dan Vaughn, Arden Towers, stated the existing tower had been there for 20 years and the tower <br />they were talking about replacing it with would be a tower almost identical in appearance to the one <br />that was there now. The new tower would have solid steel legs, instead of tubular steel legs, which <br />would make it a stronger tower and therefore, it would hoid more antennas. He indicated the tower <br />served a large part of the community and it was a very important structure in the communication <br />industry in the City. He stated it would be very difficult to take it down and find a replacement. <br /> <br />Commissioner Zimmerman asked what dictated the height of the tower. Mr. Vaughn stated 700 <br />feet was what the tower was now, and that was what the new tower would be. There was a <br />misprint in the application. <br /> <br />Commissioner Zimmerman asked if Mr. Vaughn had prepared a cost analysis as to building versus <br />not building the new tower. Mr. Vaughn replied he would have to buyout his contractual <br />obligations, and while he had not specifically looked at the financial end of this, he believed the <br />tower was an asset to the City. <br /> <br />Commissioner Galatowitsch asked if Mr. Vaughn was under a contractual obligation to provide a <br />safe tower. Mr. Vaughn replied that was correct. <br /> <br />Commissioner Galatowitsch stated by adding buildings to the property, the tower would be an <br />accessory use and the Code only allowed for a 75-foot tower under an accessory use. Mr. Vaughn <br />replied it was always intended there Would eventually be buildings on the property. However, the <br />PUD did not reflect this. <br />