My WebLink
|
Help
|
About
|
Sign Out
Home
2011_11_02_VB_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Variance Board
>
Minutes
>
2011
>
2011_11_02_VB_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:52:16 AM
Creation date
10/21/2014 11:52:15 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Variance Board
Commission/Committee - Document Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
3
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
Variance Board Meeting <br />Minutes – Wednesday, November 02, 2011 <br />Page 2 <br />Further discussion included the percentage of impervious surface included with this plan; with <br />48 <br />Member Strohmeier opining that there appeared to be a lot being condensed on this parcel; and <br />49 <br />staff defining that, in an HDR-2 Zoning District, requirements were that impervious surfaces not <br />50 <br />exceed 85% for the entire development, with governing authority for the site’s storm water <br />51 <br />management plan reviewed, approved and monitored under requirements of and by the City’s <br />52 <br />Engineering Department and the Rice Creek Watershed District, and as reviewed by those <br />53 <br />jurisdictions under previous plan approval. <br />54 <br />Applicant Representative Mark Nelson, United Properties <br />55 <br />Mr. Nelson concurred, noting that the development’s storm water management plan was <br />56 <br />processed through watershed approvals under a global review of the site. From a practical <br />57 <br />business perspective on the site, and the need for guest parking near the front door, Mr. Nelson <br />58 <br />advised that this was driving the variance request; and reiterated that the development continued <br />59 <br />to meet all runoff requirements of the City of Roseville’s Engineering Department and the Rice <br />60 <br />Creek Watershed District. <br />61 <br />At the request of Member Strohmeier, Mr. Nelson advised that the assisted living building would <br />62 <br />not be physically connected with the other buildings on the site; with staff reviewing the various <br />63 <br />phases of the development. <br />64 <br />At the request of Member Strohmeier questioning how the graphics outlined in Attachment D <br />65 <br />would negatively impact the development without the additional stalls; Mr. Nelson advised that <br />66 <br />the total number of stalls and their location not by the front door was the detriment. Mr. Nelson <br />67 <br />advised that the development was planned with underground garage space for approximately half <br />68 <br />of the total square footage to accommodate residents and employees; however, vendors and <br />69 <br />visitors needed to be accommodated on site. Due to the nature of Cleveland Avenue, Mr. Nelson <br />70 <br />noted that there was little overflow parking available; in addition to a portion of the parcel taken up <br />71 <br />by the road constructed by the developer for the City and access to the park. Mr. Nelson advised <br />72 <br />that he didn’t’ see parking on the site a day-to-day problem; however, from an operational <br />73 <br />perspective he did anticipate the need for those additional stalls for holidays and/or special <br />74 <br />events at the assisted living facility. <br />75 <br />Chair Gisselquist closed the Public Hearing at approximately 5:58 p.m., with no one appearing for <br />76 <br />or against. <br />77 <br />Commission Deliberation <br />78 <br />Chair Gisselquist spoke in support of the variance; while recognizing that the variance request <br />79 <br />was not consistent with the City’s recently-adopted Comprehensive Plan and attempted move to <br />80 <br />modern urbanism, and suggested that there may be other alternatives available on the site. <br />81 <br />Member Boguszewski spoke in support of variance, noting that from an operational flow in the <br />82 <br />health care industry it was better to have visitor parking by the door. Member Boguszewski noted <br />83 <br />that there was not an adjacent residential area that would be impacted from additional noise or <br />84 <br />light. <br />85 <br />Member Strohmeier reiterated his initial concerns that this was a very large use of a limited site; <br />86 <br />and noted the usual hardships requiring a variance did not apply in this case, since there were <br />87 <br />other alternatives available to the developer, and this was basically being requested for <br />88 <br />convenience. Member Strohmeier expressed his concern in setting such a precedent. <br />89 <br />City Planner Paschke questioned where Member Strohmeier would put the parking, since it <br />90 <br />needed to be on-site; and there was no other place to put it without entirely redesigning the site. <br />91 <br />Mr. Paschke opined that this was the rationale in the state statute being revised to allow this type <br />92 <br />of variance. Mr. Paschke noted that this development had been in the design stages since 2006 <br />93 <br />or before, and previously approved under a Planned Unit Development (PUD) designation, with <br />94 <br />the developer having made a huge investment to-date in that design, initially completed before <br />95 <br />the City adopted its revised zoning code. Mr. Paschke opined that, to not grant this variance <br />96 <br />request would create a huge functional challenge for the site; with only ADA-compliant parking in <br />97 <br />front, but no visitor parking. Mr. Paschke advised that the variance would allow something that <br />98 <br />the City had changed on the developer during the process through creation of the City’s new <br />99 <br />ordinance to apply in all cases, but allowing dispensation of that requirement in this case. <br />100 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.