My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
05-16-11-WS
ArdenHills
>
Administration
>
City Council
>
City Council Minutes
>
2010-2019
>
2011
>
05-16-11-WS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/16/2011 10:25:48 AM
Creation date
6/16/2011 8:22:57 AM
Metadata
Fields
Template:
General
Document
City Council Worksession Minutes
General - Type
City Council Worksession Minutes
Category
City Council Worksession Minutes
Date
5/16/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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
ARDEN HILLS CITY COUNCIL WORK SESSION — MAY 16, 2011 12 <br />Ms. Beekman stated she doesn't see an impediment in our ordinance for accessory structures on <br />through lots. She explained our ordinance allows the Staff to determine which is the front yard <br />and which is the rear yard. She added that we may want to move that language into the section of <br />the code currently under review so that it's clear rather than just being included in the definition <br />section. <br />The consensus of the Council was to direct Staff to proceed with the amendment as proposed. <br />3.E Notification Requirements <br />City Planner Beekman explained that in the last six months, the City has reviewed a number of <br />planning cases that drew the attention of residents. The question of who is notified when a public <br />hearing is to be held was raised by Councilmembers and residents as well as neighboring <br />communities. She explained that state statute requires notification of all property owners within a <br />minimum of 350 feet of a subject property for all public hearings. She then reviewed the <br />notification policy for some of the surrounding communities. She explained that Staff is looking <br />for direction from the Council to establish a City policy that would identify appropriate <br />notification distances. She further explained that for projects Staff anticipates will be <br />controversial, the notification area is extended. She referred to the recent Fox Ridge project when <br />Staff extended the notification to 1,000 feet and beyond. She also explained that if the Council <br />decides to extend the notification area that will result in increased costs which means we may <br />r <br />want to consider raising our fees. <br />Couneilmember Holmes commented that for some applications, such as a variance. she didn't <br />feel going beyond the 350 feet would be warranted, but on larger projects the extended <br />notification would be appropriate. <br />Ms. Beekman explained that there are no requirements for notification of variance applications <br />but the current practice is to notify residents within 350 feet. <br />Couneilmember Holden questioned how often Staff goes beyond the 350 feet notification and <br />indicated that she would like to see the extended notification done on a case -by -case basis. <br />Ms. Beekman responded that anything within the B2 district, she usually does send notification to <br />property owners within 500 feet. For the Arden Plaza petition, because of the interest in that <br />project, the notification was sent to properties within 1,000 feet. <br />Couneilmember Holmes stated she believes the notification should be 1 ,000 feet for projects <br />such as Fox Ridge or Presbyterian Homes. She recalled that at one time the Council had made an <br />informal recommendation for 1.000 foot notification which was followed for a while then <br />stopped. <br />City Administrator Klaers expressed concern that increasing the notification area may <br />necessitate holding hearings at a location other than City Hall because Council Chambers cannot <br />accommodate that many people. <br />
The URL can be used to link to this page
Your browser does not support the video tag.