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 10 <br />that a PUD process could have helped in the examples shown by staff; and while the <br />446 <br />PUD was stripped away with the best of intentions, it was now being missed, while it <br />447 <br />could also prove dangerous to reinstate as well. <br />448 <br />Member Boguszewski stated that he preferred to presume the validity of the electorate <br />449 <br />process, and in as much as the City Council represents the views of its citizenry at that <br />450 <br />particular point in time, he found that reverting back to a PUD process, under this newer <br />451 <br />City Council and their values and wished expressed, could prove easier than going <br />452 <br />against a rigid set of codes. Member Boguszewski opined that he found it as beneficial, <br />453 <br />and his sense of history in this situation was not whether it was or wasn’t a PUD <br />454 <br />applicable process, but just a dissatisfaction with the process itself, with an unfair or <br />455 <br />unequal application of the PUD process or tool. If the Commission supported bringing the <br />456 <br />PUD tool back, which he interpreted was the consensus, and then Member Boguszewski <br />457 <br />suggested a more rigorous review and as suggested by Member Cunningham, ensures a <br />458 <br />due process is provided. <br />459 <br />As it relates to reimplementation of a PUD process this time around, Mr. Paschke stated <br />460 <br />the need to use it as a tool in unique situations or certain circumstances, but not a tool to <br />461 <br />be used all the time. Mr. Paschke noted that this was a situation the City fell into in the <br />462 <br />past due to its outdated Comprehensive Plan and Zoning Ordinance and problems <br />463 <br />meeting goals and objectives. Mr. Paschke noted that this created a situation where <br />464 <br />complaints were heard that the City was issuing too many PUD’s in an attempt to deviate <br />465 <br />from code, when they felt projects should be meeting code or seeking a formal variance. <br />466 <br />Mr. Paschke advised that the attempt now was to balance the current zoning code with <br />467 <br />PUD issuance for unique situations or development on land with unique circumstances <br />468 <br />where the PUD made the most sense versus five choices where the PUD was only one <br />469 <br />of those choices. Mr. Paschke clarified that it was staff’s goal to develop the PUD <br />470 <br />process in a whole different sense than how it was previously designed. <br />471 <br />Specific to the site plan review mentioned by Member Cunningham, Mr. Paschke sought <br />472 <br />clarification as to what instances she would prefer that or if the intent was for all <br />473 <br />scenarios of development. Mr. Paschke noted that there were permitted uses where no <br />474 <br />process was involved beyond staff review; and sought preferences for applying such a <br />475 <br />process to all or only certain situations for formal review and approval tied to the site <br />476 <br />plan. As an example, Mr. Paschke advised that the site plan couldn’t be tied to rezoning, <br />477 <br />but formal discussions could be held at the staff level as a project moved forward with <br />478 <br />code created to address such situations. <br />479 <br />Member Cunningham responded that, from her perception, she didn’t want the goal of a <br />480 <br />PUD to micro-manage every project coming forward, opining that this was not the best <br />481 <br />public policy. However, in certain situations that staff may identify as leading to greater <br />482 <br />problems or issues, or if a lot of neighborhood concern was being heard about a specific <br />483 <br />redevelopment, Member Cunningham said that she would then like to see City officials <br />484 <br />look at the PUD tool at their discretion to ease some of those citizen concerns if that was <br />485 <br />an appropriate use. <br />486 <br />Mr. Bilotta suggested that staff return with a menu of possible scenarios and let the <br />487 <br />Planning Commission pick and choose their preferences to inform the discussion going <br />488 <br />forward. Mr. Bilotta noted that there is the potential for abuse, which could be <br />489 <br />incorporated into the structure of City Code, as some were addressed in the example <br />490 <br />ordinances from other communities. One of those examples, the City of St. Louis Park, <br />491 <br />provided that the City obtained something of value if they varied a standard; but under <br />492 <br />some older and sloppier codes, they may allow the PUD to change anything, and those <br />493 <br />created other issues. Mr. Bilotta opined that the PUD process could eliminate some of the <br />494 <br />pressure on the Variance Board in requiring findings for that process. <br />495 <br />Member Murphy questioned what was being considered as the triggering mechanism for <br />496 <br />the PUD route as opposed to another tool. <br />497 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.