My WebLink
|
Help
|
About
|
Sign Out
Home
2016-11-02_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-11-02_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/5/2017 10:10:30 AM
Creation date
1/5/2017 10:10:24 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Agenda/Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
With concurrence by Mr. Paschke, Member Kimble noted this would leave maximum <br />152 <br />height restrictions in HDR-2 Districts open ended. <br />153 <br />Member Bull noted that he found it conspicuous that there were no recommended <br />154 <br />changes to corner lot setbacks in HDR-2 Districts, and asked why the inconsistency <br />155 <br />(page 3). <br />156 <br />Mr. Paschke responded that while this hadn’t been a concern with the City Council, staff <br />157 <br />found no need or desire to change that setback, as city design standards addressed <br />158 <br />building placement at intersections as needed. Mr. Paschke noted other complications <br />159 <br />may be found if that setback was changes or a need for modifying design standards <br />160 <br />accordingly, especially related to sight lines and safety issues at corners. Mr. Paschke <br />161 <br />noted the City Council was more concerned with rear and side yard setbacks adjacent to <br />162 <br />single-family residential uses versus corner situations on public streets or across the <br />163 <br />street. <br />164 <br />Specific to city code definition for building height, Member Bill asked if there was a <br />165 <br />consistent measurement. <br />166 <br />Mr. Paschke responded that it was typically defined as midpoint to the roof truss, and for <br />167 <br />flat roofs at the top of the parapet or mechanical equipment (e.g. elevatored buildings). <br />168 <br />Mr. Paschke stated he didn’t know if that definition was exact, but was used as a <br />169 <br />standard review tool. <br />170 <br />At the request of Member Murphy, Mr. Paschke confirmed that an elevator cupola <br />171 <br />counted for the height unless excepted (e.g. eaves, bow windows) as it was part of the <br />172 <br />building and could prove substantial in some cases. <br />173 <br />Even though addressed in City Council meeting minutes provided in the staff report, <br />174 <br />Member Cunningham asked for the main reason the City Council wanted to shy away <br />175 <br />from the Planned Unit Development (PUD) process, whether it was to achieve the 10% <br />176 <br />calculation or if it was to address something unique that stood out for a specific project. <br />177 <br />Mr. Paschke clarified that an applicant such as the Good Samaritan development could <br />178 <br />not be required to go through the PUD process specific to modifications to the current <br />179 <br />PUD process and the 10% rule. In order for a project to precipitate this, Mr. Paschke <br />180 <br />advised it would need to be modified up to 30%, which had been the main discussion <br />181 <br />point for the City Council related to that project; it may have been supported for that <br />182 <br />project, but perhaps not in other areas of the community. Mr. Paschke noted the concern <br />183 <br />was with unintended consequences in the broader context. <br />184 <br />At the request of Member Cunningham, Mr. Paschke reviewed the seven deviations <br />185 <br />allowed under the PUD criteria, with height being one of those potential deviations. If all <br />186 <br />other criteria were met for a PUD, Mr. Paschke noted those overarching goals needed to <br />187 <br />be met, allowing the city to support a PUD beyond its standard city code requirements. <br />188 <br />However, in the case of the Good Samaritan project, Mr. Paschke advised that it was <br />189 <br />difficult for staff to support the PUD for that project based on the original merits as <br />190 <br />presented. <br />191 <br />Member Cunningham stated her appreciation for staff’s clarification; seeking additional <br />192 <br />clarification if other unique projects came forward that didn’t fit in the PUD category that <br />193 <br />may also require additional review. <br />194 <br />Mr. Paschke responded that he couldn’t really address that until seeing how a particular <br />195 <br />project stacked up with city goals and whether or not the project was in line with those <br />196 <br />goals. Mr. Paschke reiterated that the purpose of the PUD was not to seek dispensation <br />197 <br />for a project under the PUD, but to recognize a project may be so unique the city wants to <br />198 <br />negotiate some give and take for a superior project on a given site, not simply a <br />199 <br />developer seeking variances plus a PUD for that particular lot. <br />200 <br />Specific to the Good Samaritan project, Ms. Collins noted it was important to note the <br />201 <br />discussion surrounding that proposal included their struggle to meet the PUD on the 2- <br />202 <br />acre minimum site and not meeting that height requirement. Also, Ms. Collins noted the <br />203 <br />PUD process often proved lengthy and costly as well as labor intensive, and unless it <br />204 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.