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 5 <br />original Plan previously presented to the Commission had more lineal frontage <br />206 <br />requirement and more variables about how much of the building would sit on those <br />207 <br />frontages. Now, Mr. Lamb noted, attempts were being made to be more overt and <br />208 <br />encourage buildings to build on the applicable “build-to” area for the best result, while <br />209 <br />recognizing the need for some flexibility. <br />210 <br />Member Wozniak sought clarification that the flexible frontage as proposed included <br />211 <br />elements to reinforce the desire for creation of pedestrian-friendly avenues and <br />212 <br />environments by offering vertical screening for parking lots if they were up to the 5’ <br />213 <br />setback. Member Wozniak opined that, in effect, this allowed flexibility but did not <br />214 <br />abandon the desirable attributes of urban design for Complete Streets and connectivity. <br />215 <br />Mr. Paschke concurred with Member Wozniak’s opinion for urban frontage to be flexibility <br />216 <br />as well as mechanics built into it to hide or screen parking. Mr. Paschke noted that this <br />217 <br />allowed the vision for Twin Lakes, while also allowing buildings in some areas to move <br />218 <br />forward, but needing to comply with screening and landscaping and regulations on how <br />219 <br />to meet those requirements if you chose to move the building forward. Mr. Paschke <br />220 <br />confirmed that it allowed for better flexibility but still addressed aesthetic appeal through <br />221 <br />urban design principles. <br />222 <br />Mr. Lamb noted, in particular, the attempt was to remain focused on where the private <br />223 <br />parcel and the public realm intersected, and what that actual condition might be as <br />224 <br />opposed to letting any solution occur, but to provide a uniform standard for that <br />225 <br />intersection and relationship to define the physical edge. <br />226 <br />Member Wozniak questioned if the recommended 36” screen was sufficient for parking. <br />227 <br />Mr. Lamb advised that the recommendation was for 36” to 40”; and Mr. Paschke advised <br />228 <br />that the current recommendation was for 36” minimum, but that the height requirement <br />229 <br />recommendation could be revised. <br />230 <br />Member Wozniak addressed the trend for vehicle height designs that were not getting <br />231 <br />smaller on average. <br />232 <br />Mr. Paschke questioned if the proposed minimum height requirement would screen the <br />233 <br />full vehicle, but it would block it to a certain extent, and could require a masonry wall in <br />234 <br />some situations. Mr. Paschke noted that the Plan narrative information spoke to that <br />235 <br />possibility; however, he didn’t think a wall was advisable everywhere, and was unsure <br />236 <br />where they would look good or be most applicable without taking away from desirable <br />237 <br />frontage amenities. Mr. Paschke advised that discussions internally were still occurring <br />238 <br />and being considered; whether a wall or vertical screen with options were best, or <br />239 <br />whether to work with a developer for mixed landscaping or fencing. <br />240 <br />Member Strohmeier sought additional information on the process to-date for public <br />241 <br />awareness of the proposed Regulating Map and Plan; and if and how mailed notices <br />242 <br />were provided beyond published notice. Member Strohmeier advised that he was most <br />243 <br />concerned with those residential properties in the immediate area adjacent to Twin <br />244 <br />Lakes; noting the fragile nature and past controversies. <br />245 <br />Mr. Paschke advised that staff provided 730 mailed notices for the open house, via a <br />246 <br />letter inviting property owners to the open house held on May 25, 2011, and mentioning <br />247 <br />tonight’s Public Hearing. However, Mr. Paschke advised that duplicate notices had not <br />248 <br />been sent, but that the Public Hearing had been noticed in accordance with State Statute <br />249 <br />and the standard City Council Policy and process for land use notifications; and was also <br />250 <br />available to the public on the City’s website. <br />251 <br />Member Strohmeier asked if there had been any additional public outreach on the actual <br />252 <br />Regulating Map and Plan sent out at the same time as the packet was received by <br />253 <br />Commissioners. <br />254 <br />Mr. Paschke responded negatively, noting that it was not typically part of the process; <br />255 <br />however, he noted the multitude of ways for the public to contact staff and the mass e- <br />256 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.