Laserfiche WebLink
Mounds View City Council June 12, 2006 <br />Regular Meeting Page 17 <br /> <br /> 1 <br />Brian Amundsen, 3048 Wooddale Drive, stated he is here because he believes there are two areas 2 <br />of concern. He said that 1104.01, Subdivision 5, which still refers to a terrace or “similar 3 <br />structure” and can cause confusion. He questions what is considered an encroachment and the 4 <br />issue of setbacks and believes that the current language does not specify whether or not retaining 5 <br />walls are allowed on the property line. He believes that it would be more clear if “retaining 6 <br />walls” were added to the 1104.01, Subdivision 5. 7 <br /> 8 <br />Mr. Amundsen stated the other piece he believes is short of information is protection if a 9 <br />retaining wall is built too high. He said at the back of a property there is a retaining wall nearly 10 <br />6-7 feet high and if a person were to step off, they could be injured. He stated he believes there 11 <br />should be some place that the City requires a protective fence. He said it would help 1104.01, 12 <br />Subdivision 5, if it was clarified and specifies setbacks. He also stated he questions the phrase 13 <br />“similar structures.” He stated that, regarding his issue, he built 2 additional feet on his fence. 14 <br /> 15 <br />Director Ericson said the Planning Commission considered a necessity for terraces in the 16 <br />definition and in the opinion of the Planning Commission that the present definition is adequate. 17 <br />He said the Council could make the determination whether or not the word “terrace” needs a 18 <br />different definition. He said the Planning Commission is comfortable with the way the word 19 <br />Terrace has been applied. He said the Planning Commission felt it was not a necessity to make a 20 <br />modification. 21 <br /> 22 <br />Director Ericson stated, regarding the retaining walls, the Planning Commission felt that in many 23 <br />cases something would be warranted, but it was not necessary to put it in as a code requirement. 24 <br />He said that it is in the City’s best interest to put in rails or warnings if the City is putting in a 25 <br />high retaining wall and that the City has done so in the past. He explained it is not something the 26 <br />Planning Commission believes citizens need to put in their own yards to protect themselves from 27 <br />falling off their own property. 28 <br /> 29 <br />Councilmember Flaherty said this does stem from the Edmonson’s property and it did come from 30 <br />the change in elevation from the Edmonson’s neighbors. He said the neighbors elevated their 31 <br />property and it is an issue of privacy and security. He asked if the Planning Commission has 32 <br />addressed this issue. 33 <br /> 34 <br />Director Ericson replied that the amendment does not address a change in elevation. He said if 35 <br />the grade change would mean changes to storm water, the City would be involved, but said that 36 <br />unless that happens, there would be no City involvement. 37 <br /> 38 <br />Councilmember Flaherty asked if there is no specific limit to the height of a retaining wall and 39 <br />asked if a car could sit up on top of a retaining wall, looking over the neighbor’s fence. He asked 40 <br />if Director Ericson could address such a scenario while making changes to the ordinance. 41 <br /> 42 <br />Director Ericson explained that when they looked at codes from other communities and did 43 <br />research, no other municipality had any restriction on retaining walls. He said there are areas in 44 <br />Northeast Minneapolis where there are 20-foot retaining walls in order to hold back soil instead 45