Laserfiche WebLink
Special Planning Commission Meeting <br />Minutes – Wednesday, June 15, 2011 <br />Page 7 <br />corridor lay in final form, and whether it needed to be 60’ wide, as currently prescribed. <br />309 <br />Mr. Paschke noted that this would be doubling over the existing Metropolitan Council’s <br />310 <br />sewer easement of that width. Mr. Paschke advised that parking could go over the <br />311 <br />easement, but not a structure; and staff had been questioned if that didn’t take away uses <br />312 <br />for that area, and whether there could be more flexibility with the build-to lines as the <br />313 <br />building fronted that easement. Mr. Paschke opined that consideration could certainly be <br />314 <br />given for the approach to be softened to fit more of a variety of uses. Mr. Paschke <br />315 <br />advised that, with this corridor mandated over that existing easement, it created an <br />316 <br />undevelopable, landlocked parcel, and should be addressed. If the corridor remained as <br />317 <br />is, Mr. Paschke noted that it took that portion of the parcel out of the equation, and <br />318 <br />needed further thought for additional flexibility. <br />319 <br />Member Wozniak noted that the landlocked parcel did not have freeway frontage <br />320 <br />designation. <br />321 <br />Mr. Paschke concurred, however, noted that it was narrow, with no parking; and <br />322 <br />warranted further consideration. <br />323 <br />Associate Planner Bryan Lloyd noted site entrances with build-to areas at the corner and <br />324 <br />the corridor off Iona that limited access to the site, with access indicated between Twin <br />325 <br />Lakes Parkway and Iona east of the build-to line where the roundabout was located going <br />326 <br />east along Twin Lakes Parkway. Mr. Lloyd opined that the question was whether further <br />327 <br />consideration could be given, while remaining sensitive to what was already there; again <br />328 <br />adhering to a Plan predicated to the City’s vision, but recognizing market realities; and <br />329 <br />that may indicate access connecting to Iona. <br />330 <br />Member Boguszewski questioned how that parcel-specific flexibility would be <br />331 <br />documented. <br />332 <br />Mr. Paschke advised that it would not be listed as specific exceptions, but addressed <br />333 <br />through flexibility within the public connection circle (e.g. to the park) addressed in the <br />334 <br />350-400’ radius. <br />335 <br />Mr. Lamb concurred, noting the public dedicated corridor connecting to the park. <br />336 <br />Member Boguszewski recognized that the Regulating Map was a different approach than <br />337 <br />zoning, and was a work in progress at this point. However, he questioned if the concept <br />338 <br />was that the Regulating Map would be eternally work in progress; and questioned if that <br />339 <br />was the concept, how would any action taken by the Commission at tonight’s meeting to <br />340 <br />recommend approval make any difference or fit into the overall process that would allow <br />341 <br />for ongoing additional adjustments; or whether approval needed to be conditioned on <br />342 <br />future amendment(s). <br />343 <br />Mr. Paschke advised that, since tonight’s meeting was not being televised or recorded for <br />344 <br />delayed viewing, he would suggest that the Public Hearing be continued to the <br />345 <br />Commission’s July 6, 2011 meeting, to allow recording for public documentation. Given <br />346 <br />the fact that staff was still referring to the Regulating Map and Plan as a “working <br />347 <br />document.” Given that staff had indicated to the Commission those ongoing discussions <br />348 <br />and considerations based on public and property owner comment, some yet to be <br />349 <br />articulated to the point they would be beneficial for the Commission or public to consider <br />350 <br />at this point, he reiterated that staff would recommendation continuation of tonight’s <br />351 <br />Hearing to allow for a more formal recommendation to be formulated. <br />352 <br />Related to whether this document would be in flux all the time, Mr. Paschke advised that <br />353 <br />it would not be in flux once approved; however, he did note that if a project came forward <br />354 <br />in the future, no matter whether a residential or commercial use, and if modifications to <br />355 <br />the Map and Plan were indicated, there would be an option to amend the Plan and Map <br />356 <br />similar to amendments to other City Code and Ordinances. <br />357 <br />Member Boguszewski recognized the timing constraints in getting this Plan and Map <br />358 <br />approved; however, he requested that, if the Hearing was to be continued, those <br />359 <br /> <br />