My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2018_0723
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2018
>
CC_Minutes_2018_0723
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/15/2018 2:06:00 PM
Creation date
8/15/2018 2:05:57 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
7/23/2018
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
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,July 23, 2018 <br /> Page 3 <br /> an open house and having notification of residents within 500 feet, to provide a <br /> better opportunity for public input. <br /> Councilmember Willmus commented that what is being referred to is the applica- <br /> tion at County Road D in Fairview. That is where the Council is in alignment <br /> with the text amendments. Specific to the site or proposal, there are some issues. <br /> That is why the Council took the action it did. There is a need to further define <br /> these things, but also with regard to certain areas in the community, there may be <br /> some challenges. The Council would like to see those items. <br /> Vice Chair Bull stated there was a very general text amendment that applied <br /> across the board, and a very specific project, and they were dealt together. It was <br /> confusing as to which ones were being considered when. <br /> Councilmember Etten also asked planning staff to look at this issue. He noted <br /> that one of the challenges with the proposal for County Road D in Fairview was <br /> there were may undefined pieces like setbacks and parking requirements. The <br /> Council can learn from this to determine a better process. <br /> Member Daire commented that the separation of the project proposal from the <br /> text amendment is a wise course of action. It makes sense to refuse to allow the <br /> project proposal to go through until the text amendment has been dealt with in <br /> terms of ramifications City-wide, in order to develop as the parameters like park- <br /> ing, etc., rather than let the project define the text amendment. <br /> Mayor Roe commented sometimes it is not just changing whether something is <br /> permitted or not permitted. There are other factors and decisions that flow from <br /> that, like setbacks. Also, with that application, if it went through as permitted, it <br /> would not come back to the Council or the PC. Giving notice ahead of a project <br /> can inform everyone in the process that, depending on how the text amendment <br /> goes, will affect the steps of the specific project. He agreed that separating it does <br /> take some of the pressure off the process. <br /> Member Daire stated this has happened at least 3 times while he has been on the <br /> PC. <br /> Councilmember Willmus concurred with Member Daire that there have been a <br /> few occurrences with the simultaneous action. He has spoken about this, and the <br /> Council does not want to see the situation re-occur. But the City cannot prevent <br /> someone from applying, and the point is to put some things in place that will act <br /> as a trigger. It is great for the PC to sit down to ask some of these questions, and <br /> that is helpful for Councilmembers when it moves to the Council level. <br /> Member Gitzen stated that anything that can be done to educate the public will be <br /> very helpful. <br />
The URL can be used to link to this page
Your browser does not support the video tag.