My WebLink
|
Help
|
About
|
Sign Out
Home
2014_08_06_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2014
>
2014_08_06_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:43:18 AM
Creation date
10/21/2014 11:43:16 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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, August 6, 2014 <br />Page 9 <br />Mr. Bilotta advised that staff was attempting to initiate discussions on non-time-sensitive <br />393 <br />issues when the City Council requests such an analysis from staff, by seeking Planning <br />394 <br />Commission feedback before staff attempts to craft text. Mr. Bilotta advised that the City’s <br />395 <br />current Planning Intern, Cadence Peterson, outlined some basic ways PUD’s are done; <br />396 <br />and noted that staff had also provided historical information. While PUD’s provide <br />397 <br />additional opportunities for design oversight in circumstances where an applicant is <br />398 <br />seeking regulatory flexibility, in instances where no request is made for that flexibility, a <br />399 <br />different approval process could be provided. Mr. Bilotta also noted the current site plan <br />400 <br />review used in Roseville as part of the PUD discussion, since it is not in Roseville <br />401 <br />ordinance, but compares to PUD approval using similar design oversight purposes. Mr. <br />402 <br />Bilotta noted that staff outlined a range of what could and could not be done to regulate <br />403 <br />that control; and advised that once staff develops text, the Planning Commission would <br />404 <br />be given another chance to review the proposed language; but at this time was seeking <br />405 <br />feedback in developing that text. <br />406 <br />Member Cunningham stated that she felt strongly in maintaining the site plan review <br />407 <br />process or as part of the PUD process. Member Cunningham noted that the Commission <br />408 <br />had dealt with those issues in the past when they had no ability to make smaller changes <br />409 <br />or suggestions; and expressed her interest in the Commission having more authority <br />410 <br />where applicable for cases needing neighborhood concerns addressed. <br />411 <br />Member Murphy asked staff if they had any recent examples of where a PUD would have <br />412 <br />resulted in a better outcome had the tool been available. <br />413 <br />Mr. Bilotta responded that some outcomes may not necessarily have been better, but <br />414 <br />using the County Road B project as an example, he noted that the project had not been <br />415 <br />approved by the City Council due to their concern about LDR-2 zoning potentially <br />416 <br />allowing for townhome development, and having a lack of control in regulating that <br />417 <br />possibility. With a PUD in place for that project, Mr. Bilotta stated that the project or the <br />418 <br />developer voluntarily could have locked such a possibility out of that area, to ensure <br />419 <br />single-family was the only potential for that area. Mr. Bilotta noted that single-family <br />420 <br />residential uses were not as large of a concern as other potential uses. <br />421 <br />Another example provided by Mr. Paschke was for the Dale Street Redevelopment <br />422 <br />Project, a mixed residential project, which he noted could have been accomplished <br />423 <br />through application of a PUD versus the need to amend code. Mr. Paschke opined that <br />424 <br />PUD’s come in handy in redevelopment projects, including the Twin Lakes <br />425 <br />Redevelopment Area as a potential candidate given issues related to buffering, setbacks, <br />426 <br />bad soils, and building placement; or to achieve the City’s goals and desires while <br />427 <br />allowing a viable project for the developer. <br />428 <br />Mr. Bilotta noted another example would be in redevelopment areas with smaller lots, <br />429 <br />where all of the backyards would not be big enough to address open space and/or <br />430 <br />environmental resources (e.g. wetland), but a communal area could be preserved to <br />431 <br />accomplish such a goal under a PUD. <br />432 <br />Approaching this from a greater distance, Member Murphy questioned why the PUD tool <br />433 <br />was originally removed from the tool box, and whether that didn’t serve to injure the City <br />434 <br />and no longer allow for repeatable results through the same process by vote versus strict <br />435 <br />meeting of the zoning code. Member Murphy referenced a recent Minneapolis Star <br />436 <br />Tribune newspaper article about Minnetonka land use for a public facility and political <br />437 <br />issues related to land uses and the process. Member Murphy opined that there was <br />438 <br />something to be said for a defined set of obvious standards in code versus negotiation <br />439 <br />under a PUD process. Member Murphy opined that it seemed like the PUD route opened <br />440 <br />up the process to political influence and the potential for different City Councils and <br />441 <br />individual Councilors making those land use decisions. <br />442 <br />While agreeing that may be part of the history, and although it may not be political, Chair <br />443 <br />Gisselquist opined that if the zoning code was done correctly, it should be perfectly clear <br />444 <br />and without any ambiguities. However, based on reality, Chair Gisselquist further opined <br />445 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.