My WebLink
|
Help
|
About
|
Sign Out
Home
2014_1110_CCpacket
Roseville
>
City Council
>
City Council Meeting Packets
>
2014
>
2014_1110_CCpacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/11/2014 3:23:00 PM
Creation date
11/6/2014 3:53:50 PM
Metadata
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
246
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
Attachment A <br />EMO8,2014, <br />XTRACT OF THE INUTES OF THE CTOBER <br />RPC <br />OSEVILLE LANNING OMMISSION <br />b.Project File 0017-Amendment 21 <br />Request by the Community Development Department to amend certain <br />requirements contained in Roseville Zoning Code, Section 1011.11.E.2.c.I <br />(Open Parking Area) pertaining to parking lot lighting <br />Chair Gisselquist opened the Public Hearing at 6:46 p.m., and reviewed the protocol for <br />Public Hearings and subsequent process. <br />City Planner Thomas Paschke reviewed the focus of this consideration of text <br />amendments to parking lot lighting that came up recently during staff analysis of an <br />industrial use project. Mr. Paschke advised that staff also compared various codes from <br />other communities for flexibility and consistency purposes, as detailed in the staff report. <br />Mr. Paschke advised that this potential text amendment had been identified as staff <br />reviewed current code language related to parking requirements for an industrial use <br />area with only truck traffic and limited pedestrian traffic near a loading dock. Mr. <br />Paschke noted that, since there was currently an across the board standard, it became <br />evident that text amendments would be amenable to provide more flexibility and ranges <br />for various uses as each case was reviewed on a case by case basis with safety in mind. <br />Discussion <br />Prompted by Member Daire, discussion included foot candle definitions and standards; <br />standards established so very little light left the site (e.g. no more than 0.50 foot candle <br />at property line) as detailed in lines 51-52 of the staff report; changes only for open <br />parking lots, with no changes proposed for parking structures through this text <br />amendment; lighting to address pedestrian versus vehicular use areas and how to ensure <br />the utmost safety with multiple use parking lots or where pedestrians may be; and staff <br />review of each project via their site plan and lighting plan and standards where <br />pedestrians may be walking as well as along the periphery, that each area be lit <br />accordingly for safety. <br />Further discussion included minimum foot candles for parking structures versus other <br />parking situations; and depending on how a specific site functioned related to safety and <br />pedestrian traffic. <br />Member Murphy noted the text in the staff report (City Code Section 1019.11.E – Parking <br />Lot Lighting – lines 11 – 31) stated specific numbers and “average minimums” versus the <br />“range” addressed in lines Section 1019.11.I - Lighting – lines 32-37 of the staff report. <br />Member Daire opined that reading that interpretation of that particular requirement <br />could range from 0.40 to 0.90 for a range of vehicular uses. <br />Chair Gisselquist suggested that the initial text was perhaps intended to be broader <br />versus the specifics called out later in the current text. <br />Mr. Paschke responded that he was not sure why one place had a range versus a number <br />for minimum lighting levels. <br />Chair Gisselquist closed the Public Hearing at 7:00 p.m., no one spoke for or against. <br />Member Boguszewski opined that, if the overall goal of this requested text amendment <br />was to bring disparate guidelines into compliance, and the first original range was <br />acceptable when current code was written, he was amenable to replacing the language as <br />
The URL can be used to link to this page
Your browser does not support the video tag.