My WebLink
|
Help
|
About
|
Sign Out
Home
2011-06-15_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2011
>
2011-06-15_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/20/2011 2:29:14 PM
Creation date
12/20/2011 2:29:12 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
6/15/2011
Commission/Committee - Meeting Type
Special
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
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
Special Planning Commission Meeting <br />Minutes – Wednesday, June 15, 2011 <br />Page 11 <br />Member Wozniak opined that, from the City’s perspective, he would be hesitant to bend <br />514 <br />too much on greenway frontages and to not be too flexible, given that those areas are <br />515 <br />essentially priority spaces for this development in terms of access to the park and <br />516 <br />possible access to regional trails, at least a portion of the Iona segment. Member <br />517 <br />Wozniak further opined that he was not so certain about the smaller segment east of <br />518 <br />Mount Ridge Road on County Road C-2; and questioned staff and Mr. Lamb on whether <br />519 <br />there were opportunities that could be considered as some type of trade off on parcels to <br />520 <br />incorporate more flexible design standards (e.g. stretch of greenway frontage that the <br />521 <br />developer be allowed to build parking on in exchange for extending urban frontage on a <br />522 <br />corner segment no currently shown as urban frontage, but still desirable as an <br />523 <br />intersection feature; or no screening for parking if not necessary due to adjacent open <br />524 <br />space in exchange for something else, such as increased urban frontage). Member <br />525 <br />Wozniak suggested that such compromises may be to everyone’s advantage to initiate <br />526 <br />standards for the area that would encourage development, without abandoning ideas for <br />527 <br />open space, park access, multi-modal transit options, and other goals and visions from <br />528 <br />the Imagine Roseville 2025 community visioning process and 2030 Comprehensive Plan <br />529 <br />guidelines. Member Wozniak opined that those goals and visions needed to be retained. <br />530 <br />Mr. Paschke assured Commissioners that staff was attempting to retain those goals and <br />531 <br />visions. <br />532 <br />Vice Chair Gisselquist spoke in support of the attempt to implement more flexible <br />533 <br />frontage to address business owner concerns; however, he opined that that he didn’t <br />534 <br />want the document to be a “work in progress,” but wanted the Regulating Map in place to <br />535 <br />guide development as envisioned but also to be realistic. <br />536 <br />Vice Chair Gisselquist asked that, if the Public Hearing was continued to July, staff and <br />537 <br />Mr. Lamb return with a final plan for the Commission to vote up or down for <br />538 <br />recommendation to the City Council. Understanding that the vision and reality were a fine <br />539 <br />balancing act, Vice Chair Gisselquist noted Mr. Rancone’s and other developers’ <br />540 <br />concerns for flexibility and zoning for the market versus zoning for the vision, while <br />541 <br />recognizing pending environmental cleanup costs. Vice Chair Gisselquist noted his desire <br />542 <br />to encourage development, not discourage it, but was unclear on how much the <br />543 <br />Commission’s decision-making would impact development; but expressed his concern <br />544 <br />that the new design standards and zoning code doesn’t end up looking a lot like the old <br />545 <br />zoning code. <br />546 <br />Mr. Paschke opined that he didn’t share those concerns that it might, but did note that the <br />547 <br />old code and process was no different with its restrictions in what could be developed in <br />548 <br />Twin Lakes by requiring urban design principles be met or achieved. Mr. Paschke <br />549 <br />assured the Commission, and the public, that staff was very aware not to restrict <br />550 <br />development with too many regulations; however, he opined that no matter what the <br />551 <br />regulations are, development is difficult and cities created zoning regulations for a <br />552 <br />reason, whether for now or in the future. Mr. Paschke opined that the City and its staff <br />553 <br />owed it to its citizens to provide guiding documents for that development, or to re-think <br />554 <br />the vision. Mr. Paschke further opined that, if this is not the correct plan to meet the City’s <br />555 <br />vision, then it needed to be rethought. However, Mr. Paschke noted that this proposed <br />556 <br />Regulating Map and Plan is a direct result of the Imagine Roseville 2025 community <br />557 <br />visioning process and the updated 2030 Comprehensive Plan that put those urban <br />558 <br />design principals in place. <br />559 <br />Vice Chair Gisselquist questioned how set the guiding principles were for frontages. <br />560 <br />Mr. Paschke advised that, from that standpoint, there were no internal property lines; but <br />561 <br />big parcels with build-to lines or setback lines and additional requirements for that given <br />562 <br />area. If someone bought all the property in the Twin Lakes Redevelopment Area, Mr. <br />563 <br />Paschke opined that they would need to remove the existing public road, having received <br />564 <br />City support to do so, of course. Mr. Paschke noted there would also be a requirement for <br />565 <br />additional environmental review against the AUAR, impacts on roadways, and other <br />566 <br />items to consider. Mr. Paschke advised that, just because a developer wanted to do so, <br />567 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.