Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, January 6, 2016 <br />Page 12 <br />Mr. Stenson noted that his home and property abuts the east side of this subject <br />560 <br />property, and he had two issues. Related to the zoning change itself, Mr. Stenson stated <br />561 <br />his gut reaction was “no,” preferring the existing forest he currently viewed from his back <br />562 <br />yard. However, Mr. Stenson noted his understanding of real estate, since he worked in <br />563 <br />that field, and recognized that change wasn’t always bad and this project would improve <br />564 <br />the tax base of the City of Roseville. <br />565 <br />Mr. Stenson opined that the developer seemed to have things together, but asked that <br />566 <br />they reconsider their plans to shift the footprint toward Cleveland rather than his house, <br />567 <br />even though he was aware the requested action before the commission was only related <br />568 <br />to zoning. However, with the potential that a concerned developer could sell the city on <br />569 <br />this project, a future project may actually turn out to be for a six-story condominium with <br />570 <br />underground parking, and expressed his concern that the city may lose control of the <br />571 <br />situation if approving this zoning request, especially with no further public vetting of the <br />572 <br />final project specific to lighting and/or landscaping. Since his hot tub was located on that <br />573 <br />side of his property, Mr. Stenson stated that was of concern to him, and asked the <br />574 <br />commission to make those impacts to adjacent properties part of their decision-making. <br />575 <br />Chair Boguszewski asked staff to address any development and how it related to city <br />576 <br />standards for light and sound mitigation, and what was allowable with this permitted use if <br />577 <br />the request for comprehensive plan amendment and rezoning was approved, and what <br />578 <br />may trigger a variance or other situation the public would get the opportunity to weigh in <br />579 <br />on. In general, Chair Boguszewski asked what regulations and safeguards were in place <br />580 <br />and considered adequate to address neighborhood concerns. <br />581 <br />Mr. Paschke addressed current zoning and comprehensive plan guidance at LDR, <br />582 <br />allowing someone to come in and develop under those standards today without any <br />583 <br />public comment whatsoever, and no control for the public to voice their concerns. Mr. <br />584 <br />Paschke reminded the commission and public that this request was not seeking special <br />585 <br />approval of the project, but staff’s analysis reviewed those things on a regular basis as <br />586 <br />they related to city code and design standards, and administratively determined what <br />587 <br />needed to be mitigated. For instance, when single-family residential properties (LDR) are <br />588 <br />adjacent to MDR, there are fewer screening or setback requirements or control <br />589 <br />mechanisms to control placement of buildings , but it was staff’s role to understand and <br />590 <br />address those controls provided in city code no matter what development or <br />591 <br />redevelopment was occurring. Once a land use designation was approved, Mr. Paschke <br />592 <br />advised that the project had to meet those requirements, but clarified that something <br />593 <br />coming in at a higher density than allowed under current designations (e.g. size and <br />594 <br />height) could not happen under existing codes and design requirements and played a <br />595 <br />huge role in how things are laid out on a site based on those requirements and specific to <br />596 <br />each development and its zoning designation. Unless a development or project requires <br />597 <br />a Variance or Conditional Use, Mr. Paschke noted most were handled administratively by <br />598 <br />staff, with this proposed project no different than any other permitted use and the controls <br />599 <br />and protections embedded in city code required to be followed. <br />600 <br />P. Carrington Ashton, 2200 Midland Grove Road <br />601 <br />Mr. Ashton stated that he had some concerns, having lived in this immediate area for 43 <br />602 <br />years and initially surrounded by trees until the owner of buildings to the east had <br />603 <br />removed trees and gardens and built the condominiums, apartments and single-family <br />604 <br />homes. Mr. Ashton questioned who owned the road and grove of trees, noting more <br />605 <br />recent removal of Willow trees and later Russian Olive trees. Mr. Ashton addressed this <br />606 <br />latest threat of removing more trees and only having a fence, with rezoning on the other <br />607 <br />side of that fence. Mr. Ashton admitted he was confused with some of the issues being <br />608 <br />discussed, but questioned if the proposed rezoning was the same as that of Midland <br />609 <br />Grove Condominiums, to which Mr. Paschke responded affirmatively. <br />610 <br />If zoned the same, Mr. Ashton questioned how a facility could move to a 54-bed home <br />611 <br />adjacent to private owners at Midland Grove Condominiums. Mr. Paschke clarified that <br />612 <br />the condominiums were guided HDR because that designation fit their number of units, <br />613 <br /> <br />