My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2016_0725
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2016
>
CC_Minutes_2016_0725
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/26/2016 2:31:57 PM
Creation date
8/17/2016 1:47:26 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
7/25/2016
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
38
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 City Council Meeting <br />Monday, July 25, 2016 <br />Page 12 <br />Interim Community Development Director Kari Collins noted the purpose of to- <br />night's discussion was to gather the objectives and outcomes the City Council <br />would like to see for HDR proposals (e.g. senior housing classifications as lower <br />impacts); and whether they thought the Conditional Use (CU) process addressed <br />any and all uses, if done on a case by case review. As mentioned by Mr. Paschke, <br />Ms. Collins noted the proposed PUD text amendment pending Planning Commis- <br />sion review and recommendation and City Council approval that would include <br />density language and increase it to 30%. However, Ms. Collins noted this also <br />involved the acreage component that also may need amending, but advised staff <br />was seeking which option the City Council found more to accomplish the desired <br />outcomes it was seeking (from 24 to 36 units as outlined in the proposed draft at <br />50% versus 30%). Assuming the CU allow up to 50%, Ms. Collins noted it could <br />also be a percentage not necessarily that high, but subject to discussion by the <br />City Council to address mitigation and cost versus benefit analyses. <br />Mr. Paschke agreed, noting that a subsequent traffic study and case by case re- <br />view during the CU process may determine that an increase up to 36 units may <br />not work, while something in between may be more preferable and thus recom- <br />mended rather than the maximum number of units per acre. <br />At the request of Councilmember Willmus, Mr. Paschke confirmed the maximum <br />building height would remain the same. <br />Specific to the Good Samaritan proposal and rezoning request that brought this <br />discussion forward, Councilmember Willmus advised his concern was whether or <br />not that was the highest and best use for those parcels. Councilmember Willmus <br />stated he still struggled with that, and therefare wasn't sure if staff's recommen- <br />dation to move from 24 to 36 units per acre sufficed, without also addressing a <br />maximum building height and design considerations. For reference, Coun- <br />cilmember Willmus stated he wasn't interested in seeing a duplication of the situ- <br />ation at 6800 Xerxes Avenue in Edina, MN; with single-family residential use on <br />one side of the street and 65' to 70' buildings directly across the street. Coun- <br />cilmember Willmus noted the impacts for solar access for those single-family <br />properties; stating the real issue for him was the overall height and proximity of <br />this type of use to surrounding single-family residential and what those existing <br />neighborhoods would be faced with. Councilmember Willmus questioned if in- <br />creasing units per acre addressed either of those variables. <br />Mayor Roe noted, with confirmation from Mr. Paschke, the 30' setback form the <br />side property line that would remain in effect. At the request of Mayor Roe, Mr. <br />Paschke confirmed that there were no HDR-2 zoned parcels yet built upon, but <br />several zoned accordingly. Therefore, Mayor Roe noted any development would <br />need to request rezoning from the city to add height over the 65' in the HDR-1 <br />zone. <br />
The URL can be used to link to this page
Your browser does not support the video tag.