My WebLink
|
Help
|
About
|
Sign Out
Home
2015-09-02_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2015
>
2015-09-02_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/16/2015 11:32:10 AM
Creation date
10/16/2015 11:32:06 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.
/
30
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, September 2, 2015 <br />Page 11 <br />be found from dropping elevations and hard cover from new residences and their <br />507 <br />driveways. <br />508 <br />Mr. Culver responded that the majority appeared to be set up to flow adequately <br />509 <br />depending on the location of future downspout locations, anticipating that one proposed <br />510 <br />lot may prove problematic flowing east as it currently does. <br />511 <br />Commissioner Discussion and Position Statements <br />512 <br />For the benefit of newer Commissioners, Chair Boguszewski noted his vote to <br />513 <br />recommend approval the last time a similar proposal came before the Planning <br />514 <br />Commission and restated his rationale for that support. Basically, even though there was <br />515 <br />a lot going on with this subdivision, Chair Boguszewski expressed his faith in the City <br />516 <br />Engineer’s assessment that the stormwater management would be no worse with the <br />517 <br />proposal than if nothing was done. Chair Boguszewski opined that the tree situation was <br />518 <br />what it was. From his personal perspective, Chair Boguszewski opined that it didn’t come <br />519 <br />down to petitions or neighbors, but what a private property owner could do with his own <br />520 <br />property and how that affected the immediate neighborhood. Given that perspective, <br />521 <br />Chair Boguszewski noted that a lot of the concerns crossed that line, and since beauty <br />522 <br />was in the eye of the beholder, there were good and bad perspectives to be considered. <br />523 <br />Based on his own role as a Planning Commissioner, Chair Boguszewski stated that he <br />524 <br />weighted his decision-making more heavily on the technical side, using the existing tree <br />525 <br />ordinance as an example and steps taken by the developer to meet it whether it seemed <br />526 <br />stark or not, he could not say “no” because he didn’t particularly want this developer to <br />527 <br />move or remove trees, didn’t seem appropriate. Chair Boguszewski stated that he could <br />528 <br />not stop a project because he didn’t like a particular action, even though if he was a <br />529 <br />neighbor he might wish to prevent the development from happening or even sign a <br />530 <br />petition. However, as a Planning Commissioner, Chair Boguszewski stated that he felt <br />531 <br />the issues had been addressed, especially so in this latest plan in response to the City <br />532 <br />Council’s direction; and therefore advised that he would vote to recommend approval of <br />533 <br />this Preliminary Plat as he had done with the previous plat, having provided his rationale <br />534 <br />upfront as to why he supported the subdivision. <br />535 <br />Member Stellmach expressed his appreciation of the comments and concerns brought <br />536 <br />forward in writing and in person by neighbors, and stated that he shared some of those <br />537 <br />concerns especially regarding tree preservation, since he preferred to remove none of <br />538 <br />them. However, from the perspective of the Planning Commission, Member Stellmach <br />539 <br />stated that his decision needed to be based on whether or not this proposed Preliminary <br />540 <br />Plat complied with City Code, and finding that it did, offered his support in recommending <br />541 <br />its approval. <br />542 <br />Member Murphy thanked the neighbors for sharing their comments with the Commission. <br />543 <br />As he and Member Bull reviewed the maps for this subdivision, Mr. Murphy noted lot <br />544 <br />sizes on County Road B, Acorn Road and Marion Road were all relatively smaller than <br />545 <br />these proposed lots, with getting larger moving north as noted by Mr. Mueller regarding <br />546 <br />previous subdivisions of neighboring properties. Mr. Mueller concurred with Chair <br />547 <br />Boguszewski that a revised tree preservation ordinance was not yet available, <br />548 <br />necessitating the need to seek compliance with the existing ordinance. While being <br />549 <br />sympathetic to the concerns expressed by neighbors, Member Murphy advised that he <br />550 <br />could not find a sufficient reason to vote against this proposal. <br />551 <br />As a new member of the Commission, Member Bull advised that he had reviewed the <br />552 <br />technical part as addressed in the City’s Comprehensive Plan and revised Zoning Code <br />553 <br />regarding lot sizes and design specifications, as well as reading the respective purpose <br />554 <br />statements of those documents to protect citizens and allow their safe enjoyment of their <br />555 <br />homes, the character of neighborhoods, and other factors outlined by and for Roseville <br />556 <br />citizens, all an important part of the picture. Member Bull also expressed appreciation for <br />557 <br />the written and verbal input provide by neighbors. Member Bull admitted he could not call <br />558 <br />the proposed tree plan a preservation plan, but considered it more of a removal plan, <br />559 <br />which would certainly affect the neighborhood with that removal and replacement with <br />560 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.