My WebLink
|
Help
|
About
|
Sign Out
Home
2016-11-02_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2016
>
2016-11-02_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/5/2017 10:22:11 AM
Creation date
1/5/2017 10:22:09 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
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.
/
20
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 Commission Meeting <br />Draft Minutes – Wednesday, November 2, 2016 <br />Page 3 <br /> <br />preference that all parking and storage issues be addressed as conditions for a <br />97 <br />specific property, opining the issue would come up frequently for properties <br />98 <br />having more than one public street surrounding their parcel. Alternatively, if not <br />99 <br />acceptable to the city, Ms. Steingraeber asked that at a minimum, “primary” be <br />100 <br />inserted before “public street;” with the rationale being that not only one street <br />101 <br />could impact a parcel in most instances. Specific to the setback requirements, <br />102 <br />Ms. Steingraeber noted a 5’ versus 10’ setback requirement would be consistent <br />103 <br />with the remainder of city code, opining that made sense, while respecting the <br />104 <br />city’s position on that issue. However, overall, Ms. Steingraeber asked that the <br />105 <br />city consider where storage was most appropriate on any given lot and specific to <br />106 <br />a Conditional Use, unless agreeing to insert “primary” before “public street.” <br />107 <br />In being sensitive to this request applying to all properties in Roseville designated <br />108 <br />Industrial Use, Member Murphy clarified that Ms. Steingraeber, on behalf of her <br />109 <br />client, was suggesting a Conditional Use application that would be filed with the <br />110 <br />property in perpetuity. Member Murphy asked Ms. Steingraeber’s thoughts on <br />111 <br />using the Variance option for particular applications needing stricter standards <br />112 <br />than allowed by city code. Member Murphy opined the Variance Board was <br />113 <br />receptive to unique situations for use of properties, and further opined that he <br />114 <br />found that a more flexible approach to take; and asked if Ms. Steingraeber and <br />115 <br />her client had considered that versus a permanent condition in a Conditional Use <br />116 <br />application. <br />117 <br />Ms. Steingraeber stated they had considered that, and were amenable to <br />118 <br />discussing a Variance as a possibility. However, when considering the amount of <br />119 <br />work required for a Variance versus a specific condition applied to a Conditional <br />120 <br />Use for an applicant, while similar in this client’s case, Ms. Steingraeber <br />121 <br />expressed hope that if their client submitted a Conditional Use application, the city <br />122 <br />would provide a list of conditions that the applicant could comply with versus the <br />123 <br />lengthier period for submission and review of a Variance application. <br />124 <br />From his recall of previous discussions, Member Murphy noted that <br />125 <br />commissioners were concerned with a condition being filed in perpetuity with a <br />126 <br />properly; noting that a Variance would be similar and only reconsidered if an <br />127 <br />appeal was filed and contested before the City Council. Therefore, Member <br />128 <br />Murphy opined that a Variance seemed a timelier and straightforward approach <br />129 <br />with the requester listing the exact things found burdensome and seeking relief <br />130 <br />from them through a Variance. <br />131 <br />Ms. Steingraeber stated her client would be willing to consider a Variance <br />132 <br />process; however, asked that even with such a procedure, they would find it <br />133 <br />helpful if “primary” was inserted in the language under discussion tonight. Ms. <br />134 <br />Steingraeber opined this would give developers/owners assurances that they can <br />135 <br />anticipate their intended use of the property versus a Variance application <br />136 <br />process, often adding considerable time to the development timeline. <br />137 <br />Member Daire asked Ms. Steingraeber their rationale in requesting a 5’ versus 10’ <br />138 <br />setback in light of Fire Marshal recommendations. Member Daire asked if a 5’ <br />139 <br />versus 10’ setback would further reduce drive space and maneuverability for <br />140 <br />semi-trucks and trailers on the site. <br />141 <br />Ms. Steingraeber responded that in this particular section of city code (1006.5), <br />142 <br />there were already setback requirements of 5’; and asked that consistency be <br />143 <br />followed with other portions of code, even though they recognized staff’s <br />144 <br />recommendations to keep the setback at 10’. <br />145 <br />146 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.