My WebLink
|
Help
|
About
|
Sign Out
Home
2012-02-01_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2012
>
2012-02-01_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/5/2012 3:35:42 PM
Creation date
6/5/2012 3:35:39 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
2/1/2012
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Regular Planning Commission Meeting <br />Minutes – Wednesday, February 1, 2012 <br />Page 6 <br />Steve Gjerdingen, 2211 N Albert Street, Apt. #102 <br />249 <br />For full disclosure purposes, Mr. Gjerdingen serves as a member of the City’s Public <br />250 <br />Works, Environment and Transportation Citizen Advisory Commission. <br />251 <br />Speaking as a resident, Mr. Gjerdingen noted design standards for Mixed Use Zoning <br />252 <br />Districts for placement of buildings on corner lots and their alignment to the property line; <br />253 <br />and questioned how this development appeared to deviate from that standard, as well as <br />254 <br />questioning what the actual front of the building was. Mr. Gjerdingen also questioned how <br />255 <br />this project would enhance or promote the primary statement of purpose to increase <br />256 <br />pedestrian and multi-modal travel opportunities rather than relying on vehicular <br />257 <br />transportation. Mr. Gjerdingen concurred with the comments of Mr. Grefenberg that <br />258 <br />action on this proposal be deferred until all questions had been answered. <br />259 <br />Chair Boerigter interrupted public comment to reiterate that the purpose of tonight’s <br />260 <br />meeting was not to react to a specific Site Plan, only to consider the Preliminary Plat and <br />261 <br />disposal of city-owned land. Chair Boerigter advised that, if the development itself was <br />262 <br />eventually approved, it would be required to meet all conditions of the City’s Zoning <br />263 <br />Code. <br />264 <br />At the request of Chair Boerigter, Mr. Lloyd responded to some of the items raised during <br />265 <br />public comment to-date. Mr. Lloyd concurred with Chair Boerigter that the location of <br />266 <br />access doors, frontage of the structure, and all other zoning requirements of the City <br />267 <br />would have to be met in order for the City to issue building permits; with no development <br />268 <br />allowed short of meeting those codes or application for a variance to deviate from any of <br />269 <br />them. Mr. Lloyd advised that the building front would be determined by whatever street <br />270 <br />address it was given by the City, once design of structures had been completed; and he <br />271 <br />anticipated that the primary street seeing the most traffic would indicate Mount Ridge <br />272 <br />Road as the front, on the northwest corner of the site, or possibly Twin Lakes Parkway <br />273 <br />itself. <br />274 <br />Whatever the final designation was, Mr. Lloyd noted that the Twin Lakes Regulating Plan <br />275 <br />had been adopted late last year, and since codification of City Code only happened semi- <br />276 <br />annually, after which the website was updated, he suggested that the documents on the <br />277 <br />City’s website pertaining to Community Mixed Use may not reflect that most recent <br />278 <br />adoption of the Twin Lakes Regulating Plan and its requirements that replaced previous <br />279 <br />code. Mr. Lloyd suggested that residents, when searching the website for the most up-to- <br />280 <br />date zoning requirements, rely on HTML texts rather the PDF version, since the revised <br />281 <br />text and the Overlay District may not yet be on the website in their entirety. <br />282 <br />Member Strohmeier referenced the Statement of Purpose in Section 1005.07 of Zoning <br />283 <br />Code, Community Mixed Use District, for complimentary uses organized in cohesive <br />284 <br />uses, and connecting to trails, etc. to create pedestrian-oriented development. Member <br />285 <br />Strohmeier questioned how this Wal-Mart proposal was pedestrian-centered, since he <br />286 <br />saw it as more vehicle-centered; and asked for staff’s response. <br />287 <br />Mr. Lloyd advised that staff did not address that specifically for this Preliminary Plat, as <br />288 <br />Wal-Mart would become part of a larger redevelopment area of mixed uses, including <br />289 <br />offices, stand-along businesses, residences, and other allowed uses under the <br />290 <br />Regulating Plan, and pedestrian corridors would most likely be along the perimeters and <br />291 <br />would be cohesive for the overall redevelopment area. Mr. Lloyd opined that Wal-Mart, as <br />292 <br />the first and as an individual project would not achieve that pedestrian-friendly goal all at <br />293 <br />once or in a vacuum, but would be plugged into the pieces under that overarching <br />294 <br />Regulating Plan. <br />295 <br />Mr. Paschke added that we (Roseville) an auto-oriented community like most all uses, <br />296 <br />but advised that the whole purpose of Mixed Use and Twin Lakes Regulating Plan was to <br />297 <br />promote other modes of transportation in the future. Mr. Paschke noted that sidewalks <br />298 <br />and trails were already in place throughout the Twin Lakes Redevelopment Area as part <br />299 <br />of the public infrastructure investment built to-date. Mr. Paschke advised that, within the <br />300 <br />Site Plan and as part of the Regulating Plan, the developer would be required to perform <br />301 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.