My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CCP 11-14-2001
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2000-2009
>
2001
>
CCP 11-14-2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2007 1:16:50 PM
Creation date
11/13/2006 2:37:42 PM
Metadata
Fields
Template:
General (2)
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
140
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
<br />t <br /> <br />,(~ <br /> <br />" <br /> <br />10 December 2001 <br /> <br />. <br /> <br />To Whom It May Concern: <br /> <br />We are the current owners of2014, 2020 and 2030 Glen Paul Ave. We have the <br />following concerns about the proposed building plans for the adjacent, vacant lot on <br />County Road D and Cleveland Ave: <br /> <br />I. The set-back variance requested for the building and parking lot that will decrease <br />our privacy and could affect property value; <br />2. The privacy that will be lost due to the building's having an upper level; <br />3. The water that will now be draining between the two properties due to the large <br />parking lot and building. There will be a lot of water draining into the ditch. If it <br />is clogged from piled snow or debris, it could flood the surrounding houses or <br />property. This area has flooded in the past. <br />4. What impact will the pollution from the leaking gas have on us? <br />5. Whal impact will the parking lot lighting have on us? <br /> <br />. <br /> <br />Privacy is currently provided by a six foot privacy fence on top of the retaining waIL <br />There is also an existing three foot chain link fence on the property line which does not <br />provide privacy from the vacant lot. During the planning commission meeting held on <br />December 5, Mark McGuire talked about the need to maintain the privacy offered by the <br />fence. There was confusion about which fence Mark was referring to. Mark was <br />referring to the six foot privacy fence set back ten feet from the property line on top of <br />the retaining waiL Maintaining this privacy is necessary because there is a two foot <br />(larger on some properties) difference in elevation between our property and the vacant <br />lot Putting a six foot fence on the property line will not maintain the current privacy <br />provided by the existing, set back privacy fence on top of the retaining wall. Ifa six foot <br />fence is put on the property line, we will have plain view of the parking lot at all times. <br />Weare very concerned that the city is considering waiving the set back requirements for <br />the parking lot Furthermore I have learned from the commission meeting that the <br />building being considered will have an upper floor. When we purchased our house we <br />considered the privacy we would lose when the lot was developed. I decided it would be <br />very difficult to put a two story building on the lot due to the size of the lot <br /> <br />We have come up with solutions that would be satisfactory to us. They are as follows: <br /> <br />. <br /> <br />1. Reduce building to one level and meet set back requirements for building and <br />parking lot; <br />2. Build an eight-foot or higher privacy fence on the property line; <br />3. Leave the current privacy fence that is set back ten feet from the property line that <br />sits on top of the retaining wall; <br />4. Provide an eight to ten foot hedge on top of the retaining wall that would provide <br />year -round privacy and put a six foot fence on the property line. This option <br />would require planting some type of pine or cedar tree that would not lose its <br />leaves in the winter; <br />5. Require snow to be removed off-site; <br />6. Assure that the snow will not be piled in a way that interferes with drainage; <br />
The URL can be used to link to this page
Your browser does not support the video tag.