My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03-01-2000
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Minutes
>
2000-2009
>
2000
>
03-01-2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/28/2018 8:28:00 AM
Creation date
8/28/2018 8:27:50 AM
Metadata
Fields
Template:
MV Minutes
GOVBOARD
Planning Commission
DOCTYPE
minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
23
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).
Show annotations
View images
View plain text
<br />Mounds View Planning Commission March 1, 2000 <br />Regular Meeting Page 9 <br /> <br /> <br /> <br />Commissioner Johnson pointed out that if the spacing requirement was decreased to 500 feet, the <br />sign could be shifted 50 feet or more in either direction. Mr. Coyle indicated they would be <br />willing to consider this, and would do their best to cooperate with the City. <br /> <br />Commissioner Laube inquired if the construction materials for a monopole structure could be <br />more consistent with the materials used on the golf course. Mr. Coyle indicated they would <br />discuss this matter with City staff. He pointed out that at this time, he could not commit to this, <br />because it would depend upon the location of the signs. <br /> <br />Commissioner Hegland advised that the Commission should address the sign location relative to <br />the adjacent property lines. He indicated that as a Commission, it was their responsibility to <br />recommend changes to the Code to address problems therein, and this was a problem. He stated <br />they should have a 250 foot limit between the property line and any sign that is installed, so that <br />any adjacent property is provided the same rights as their neighbor. He explained that this would <br />comply with the 500-foot MnDOT spacing requirement, and would not change the present <br />proposal with the exception of the first sign on the golf course, and possibly the adjacent sign on <br />the Sysco property. He pointed out that if Sysco only has 1,400 feet of frontage, they would <br />have to decrease the sign spacing distance to 900 feet, however, that would appear to be a <br />solution, and all of the criteria would fit for the eight signs. He proposed the Planning <br />Commission consider examining the Code to amend it accordingly. <br /> <br />Chairperson Peterson noted that the site map clearly indicates the location of the proposed signs, <br />however, there are two additional signs involved, which are for the golf course, itself. He <br />advised that if there were a 250-foot property line distance spacing requirement, the locations of <br />these signs would become a problem. He explained that as the Code is written, these proposals <br />fit, with the exception of one sign that could be resolved with a variance. He explained that <br />amending the Code would involve delaying this matter, and he was not certain that creating a <br />property line distinction would be particularly helpful. <br /> <br />Commissioner Johnson stated he had considered this as well, and did not believe this constituted <br />a change in the Code, because there was very little possibility that additional billboards would be <br />proposed, except possibly to the north of the City’s first sign, on the border of Mounds View and <br />Blaine. <br /> <br />Commissioner Stevenson indicated the permits would only be specific to this area, therefore, he <br />did not perceive a problem in this regard. He stated that in terms of the 250-foot property line <br />separation, the intent of the original spacing requirement was to address residential properties, <br />and this requirement should remain in place, to insure that the signs do not infringe upon <br />residential property owners. He pointed out that this was a specific case, and they should not <br />interfere with the City Code, they must simply decide whether or not to allow this specific use. <br />
The URL can be used to link to this page
Your browser does not support the video tag.