My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03-15-2000
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Minutes
>
2000-2009
>
2000
>
03-15-2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/28/2018 8:28:26 AM
Creation date
8/28/2018 8:28:16 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
Mounds View Planning Commission March 15, 2000 <br />Regular Meeting Page 7 <br /> <br /> <br />Commissioner Johnson indicated that if Sysco’s trucks were parked against the second <br />monopole, this would prevent a complete wrap-around design, and all they could do is put some <br />type of brick in front of the sign. Commissioner Laube stated they could camouflage the pole by <br />utilizing an imitation brick wrap-around material. <br /> <br />Commissioner Hegland stated he was convinced that Sysco was willing to make the signs as <br />aesthetically pleasing as possible, and had no concerns in this regard. He indicated there were <br />concerns with regard to the property line issue, however, he believed the application for the <br />variance should be Sysco’s responsibility. <br /> <br />Chairperson Peterson stated it was the general consensus of the Commission that the signs be <br />aesthetically complementary, and that staff should work with the applicant to accomplish <br />something to this effect. He stated he did not believe it was fair that Sysco must bear the burden <br />of applying for the variance, however, there was an apparent hardship in terms of both <br />applications. <br /> <br />Commissioner Berke stated he believed that the application for the variance should be the City’s <br />responsibility, however, he would be agreeable to granting a variance to Sysco, if their <br />application is approved at this time, to ensure that this would be done. He explained that if one <br />of the applicants was required to lose a sign, it should be the City. <br /> <br />Commissioner Miller pointed out that the City’s 1,000-foot spacing requirement exceeds the <br />500-foot State requirement, which would also be a consideration in terms of granting the <br />variance. <br /> <br />Mr. Coyle stated they were not opposed to being required to apply for the variance, however, <br />they would prefer not to be left hanging, and required to undergo a second application process, <br />after having already been before the Commission twice on an indirect basis, in terms of the <br />City’s application. He suggested the Planning Commission provide a recommendation to the <br />City Council that the variance be approved; in conjunction with the approval of the interim use <br />permit. He indicated they would prefer not to have to go back through the process again, when <br />the variance could be achieved on the City’s property. He explained that Sysco was able to <br />satisfy their application on their own property; however, the adjacent City property was creating <br />the issue. <br /> <br />Chairperson Peterson inquired if the variance request was anticipated to come back before the <br />Planning Commission for consideration, or if this would be resolved at the City Council level. <br /> <br />Planning Associate Ericson advised that according to the City Code, the Planning Commission is <br />required to review the variance request, and public hearing notification must be published and <br />provided to residents within 350 feet of the proposed site. He stated staff appreciates the <br />applicant’s suggestion, however, they must comply with the public hearing and public noticing <br />requirements of the variance request. <br />
The URL can be used to link to this page
Your browser does not support the video tag.