My WebLink
|
Help
|
About
|
Sign Out
Home
2016-03-02_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-03-02_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2016 4:29:30 PM
Creation date
4/8/2016 4:29:16 PM
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.
/
96
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 CommissionMeeting <br />Minutes –Wednesday, January 6, 2016 <br />Page 4 <br />Chair Boguszewski noted that the subject parcel appears to be currently zoned low <br />150 <br />intensity, and when the original comprehensiveplan and zoning designation were <br />151 <br />created, he presumed concerns about buffering could and should have been raised, and <br />152 <br />questioned whether or not that lack of buffering was an error carrying forward to this <br />153 <br />situation. Under that presumption, Chair Boguszewski questioned if actions such as this <br />154 <br />request would correct those adjacencies across the city, changing underlying zoning and <br />155 <br />comprehensive plan designations versus individual Conditional Use permits, and <br />156 <br />changing the actual capability of what that land could hold. <br />157 <br />Chair Boguszewski sought confirmation from staff that, if the designation and subsequent <br />158 <br />zoning is changed and this particular proposed development doesn’t work out, the land <br />159 <br />use designation and zoning remains changed; and other developers maypresent other <br />160 <br />proposals that may not be as palatable as this particular proposal. <br />161 <br />Mr. Lloyd advised that similar questions had been fielded from the public by staff; <br />162 <br />basically if this development proposal doesn’t work out after rezoning is approved, doe <br />163 <br />the city have a mechanism to initiate rezoning to move it back to today’s designation and <br />164 <br />zoning for LDR (single-family use) independent of another developer or a property owner. <br />165 <br />Mr. Lloyd advised that guidance of the comprehensive plan and instances of multi-family <br />166 <br />zoning adjacent to single-family uses, review of the existing the comprehensive plan map <br />167 <br />and renewed community goals often served in large measure to compare what is now on <br />168 <br />the ground, and what may or may not prove the best future use for every single property <br />169 <br />in the city. However, Mr. Lloyd noted that, for the foreseeable future, he didn’t anticipate <br />170 <br />any real wholesale, citywide change over the life span of this current comprehensive <br />171 <br />plan. <br />172 <br />In staff’s analysis of this property’s planning commission history, as noted in a condensed <br />173 <br />version included in the staff report and from the time previous projects were first <br />174 <br />approved, and development occurred on the parcels north of this site (Midland Grove <br />175 <br />Condominiums), the entire parcel had been under oneowner, with that first proposal <br />176 <br />including some multi-family units, with townhome buildings on the outer edges to serve <br />177 <br />as a transition from HDR, multi-family structures, to single-family (LDR). Mr. Lloyd <br />178 <br />observed that not many adjacent parcels are to theeast and south, and at one time the <br />179 <br />Planning Commission had made an observation that, if the northern parcel was <br />180 <br />subdivided, an MDR townhome developments around the perimeter would serve as a <br />181 <br />good buffer. Mr. Lloyd opined that this choice at the time of that initial approval had <br />182 <br />served to shape the current comprehensive plan map and could have provided for more <br />183 <br />intentional changes going into that initial planning effort. <br />184 <br />Mr. Paschke noted that, when the last comprehensive plan update had been reviewed in <br />185 <br />2008, a thorough review of the map and a determination of specific areas of parcels <br />186 <br />needing to be addressed had been discussed collectively as to whether or not they were <br />187 <br />guided correctly or needed changing. However, Mr. Paschke advised that the general <br />188 <br />discussions didn’t necessarily delve into specific sites, other than three major discussions <br />189 <br />highlighted: Twin lakes, Har Mar Mall, and Target #1 sites, to address current and <br />190 <br />appropriate future designations. Mr. Paschke admitted that many other sites could have <br />191 <br />been considered as well during that review (e.g. Old Highway 8), but hadn’t been <br />192 <br />addressed and therefore were coming to the Commission’s attention independently of <br />193 <br />that or future general updates. <br />194 <br />Chair Boguszewski reviewed the mechanics of potentialdecisions before the <br />195 <br />Commission tonight: vote to table after the public hearing pending further analysis; or <br />196 <br />recommend approval of the comprehensive plan and zoning designation change as <br />197 <br />requested, requiring a super majority vote. Chair Boguszewski notedthat the second <br />198 <br />option would go before the City Council for their review of the Commission’s <br />199 <br />recommendation and the record of their deliberation, with the City Council still casting <br />200 <br />their own independent vote, also required for super majority approval by that body. <br />201 <br />However the Commission decided to proceed tonight –approval or denial –Chair <br />202 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.