My WebLink
|
Help
|
About
|
Sign Out
Home
2016-05-04_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-05-04_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/19/2016 4:26:49 PM
Creation date
5/19/2016 4:26:39 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.
/
65
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, April 6, 2016 <br />Page 5 <br />Discussion ensued briefly regarding the process in pursuing the previous motion, <br />194 <br />amending it further or the maker and seconder of the motion withdrawing it and new <br />195 <br />motions and/or amendments considered by the body. <br />196 <br />At the request of Chair Boguszewski, Ms. Collins clarified staff’s perspective based on <br />197 <br />the discovery between Commission meetings; and specifically staff’s review for <br />198 <br />positioning the fence installation along the northern lot line.Ms. Collins advised that <br />199 <br />staff’s due diligence included an extensive review of documents on file and past records. <br />200 <br />After staff’s analysis, Ms. Collins stated that staff was not in a position to comfortably <br />201 <br />recommend that a fence be installed along the northern lot line due to the issues <br />202 <br />addressed by Senior Planner Lloyd.Ms. Collins advised that staff’s recommendation <br />203 <br />would be to address the original intent and concern with original conditions for approval <br />204 <br />were for the purpose of screening parking areas, as it would do so for any limited <br />205 <br />production/processing use, with those options provided in the March 2, 2016 staff report. <br />206 <br />However, Ms. Collins stated that staff was uncomfortable with Option B for fence <br />207 <br />installation on the lot line, following their further due diligence, based on some challenges <br />208 <br />with the potential easement for the underground cable line and overhead power lines. <br />209 <br />Therefore, given that situation, Ms. Collins advised that staff could not recommend that <br />210 <br />property line as the ideal location to install the fence.Ms. Collins further referenced city <br />211 <br />code that didn’t always specify the exact fence location or setback due to site-specific <br />212 <br />challenges, allowing for discretion and some maneuverability for the applicant.Ms. <br />213 <br />Collins noted that staff’s basic concern had been and continued to be the fence’s <br />214 <br />screening of the Vogel Mechanical parking lot for the benefit of adjacent residential <br />215 <br />properties. <br />216 <br />At the request of Chair Boguszewski, Ms. Collins confirmed that staff supported and <br />217 <br />recommended Option Crather than Option B as detailed in the March 2, 2016 staff report <br />218 <br />and described as follows: <br />219 <br />Option 1.C Standard Buffer Screening <br />220 <br />a.A solid opaque cedar fence approximately 6.5’ in height shall be installed north of the <br />221 <br />existing eastern parking lot to screen the lot, including delivery and dock doors and the <br />222 <br />refuse/recycling areas. <br />223 <br />b.Additional landscaping shall be installed in and around the berm adjacent to the front <br />224 <br />employee and customer parking lot to more fully screen headlights from view of the <br />225 <br />adjacent residentially zoned properties. <br />226 <br />Member Cunningham referenced the comments of Interim Community Development <br />227 <br />Director Collins when stated staff’s stance, and stating that staff could not affirm the <br />228 <br />fence along the property line due to concerns with a “potential” easement.Member <br />229 <br />Cunningham sought clarification, stating that she had never heard it referred to as a <br />230 <br />“potential easement, but had understood an easement was in place. <br />231 <br />Ms. Collins advised that staff and the commission had been recipients of a “draft <br />232 <br />encroachment agreement,” apparently provided by CenturyLink to Vogel Mechanical, <br />233 <br />creating the supposition that there was an easement in place.However, with staff still <br />234 <br />unable to uncover that document nor could anyone provide such an easement agreement <br />235 <br />to staff, Ms. Collins advised that the easement agreement remained hypothetical, causing <br />236 <br />staff to hesitate in making a decision based on supposition.Therefore, Ms. Collins noted <br />237 <br />that the city was unable to affirm whether or not a fence can or cannot be installed on the <br />238 <br />property line on that easement without first having staff and the city’s legal counsel <br />239 <br />review the document. <br />240 <br />As with other permitted uses, Ms. Collins noted that the city could therefore only state <br />241 <br />some variability based on the certain risk a property owner assumes in placing a fence.If <br />242 <br />there are no easement issues and no potential issues with CenturyLink’s underground <br />243 <br />cable, Ms. Collins opined that it seemed the fence option now supported by staff (Option <br />244 <br />1.C) would provide those variables.Ms.Collins reiterated that the intent was to satisfy <br />245 <br />screening for adjacent residential properties by screening overhead and vehicle lights for <br />246 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.