My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2013_0211
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2013
>
CC_Minutes_2013_0211
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/5/2013 9:52:01 AM
Creation date
3/5/2013 9:48:41 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
2/11/2013
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
33
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 City Council Meeting <br /> Monday, February 11, 2013 <br /> Page 23 <br /> Discussion included current code lack of recognition of some repair service busi- <br /> nesses and the need to address them. <br /> Councilmember Laliberte expressed her appreciation to staff for this helpful in- <br /> formation; with staff advising that the City Council could remain updated through <br /> following the Planning Commission's Public Hearing processes. <br /> Page 2, line 58 <br /> Councilmember Etten noted his discussions with businesses (e.g. Rice Street cor- <br /> ridor) who feel they are unable to advertise without being penalized, when busi- <br /> nesses across the street may do so. Councilmember Etten noted that their percep- <br /> tion is that this is unreasonable, and suggested revising sign regulations for tem- <br /> porary signs, such as buying an annual license packet that would allow a certain <br /> number of days allowed, and their notification by e-mail to the City Inspector of <br /> those dates for check-off to ensure their compliance, while not being onerous for <br /> small businesses. <br /> As the "Sign Czar," Mr. Paschke advised that each municipality had different <br /> zoning and sign requirements; and historically, Roseville has stated their prefer- <br /> ence to be a leader rather than a follower of its neighboring communities, and <br /> therefore, has had a tendency to have minimal signs allowed and a more restric- <br /> tive code. However, in the updated zoning code, Mr. Paschke noted that the pro- <br /> cess now allows for more flexibility for businesses and various options available <br /> to them. Mr. Paschke advised that he continually fielded concerns about limited <br /> times for signs, type or style of signs, some conducive to reuse while others are <br /> not. Also in his role as "Sign Inspector," Mr. Paschke advised that he also was <br /> charged with monitoring and enforcement of signs, with little time to do so. Mr. <br /> Paschke opined that the sign codes now in place are moving in the right direction <br /> to provide people with an understanding of what is or is not allowed, and had <br /> been based on listening to those concerns previously expressed; and now opening <br /> up more opportunities to them. <br /> At the request of Councilmember Etten regarding how to communicate those re- <br /> visions to businesses, Mr. Paschke advised that those vendors creating signs for <br /> businesses are fully aware of current code, and needed to relay that information to <br /> their clients. In his continuous discussions with businesses about signage, Mr. <br /> Paschke noted he pursues that educational outreach; and suggested another option <br /> may be to provide a letter to each business. <br /> Councilmember Etten spoke in support of that more proactive communication, <br /> since they probably didn't search city codes consistently; and with the extra flexi- <br /> bility provided with revised codes, this needed to be communicated to business <br /> owners. Councilmember Etten advised that he had also addressed the HRA about <br /> how to communicate with businesses long-term and allow them to be part of the <br /> process and allow them to pursue their opportunities. <br />
The URL can be used to link to this page
Your browser does not support the video tag.