My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PL MINUTES 11301987
StAnthony
>
Parks & Planning Commission
>
Planning Commission Minutes
>
1987
>
PL MINUTES 11301987
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/30/2015 5:50:01 PM
Creation date
12/30/2015 5:49:58 PM
Metadata
Fields
SP Box #
21
SP Folder Name
PL MINUTES AND AGENDAS 1987
SP Name
PL MINUTES 11301987
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
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
• 1 Mr. Childs recalled specifically suggesting to the applicant that <br /> 2 because the City in the past had granted a variance for a second sign <br /> 3 for a corner business, he might want to split the copy he was propos- <br /> 4 ing for the front sign into two separate signs with a 3 X 20 foot ( 60 <br /> 5 square feet) "Mickey D' s" sign to be - put up on the front of the <br /> 6 building and a 2 X 20 foot ( 40 square feet) "Family Restaurant" sign <br /> 7 could be placed on the east side since both signs would meet the <br /> 8 total 100 square feet of signage the ordinance allowed a building <br /> 9 within a 50 foot frontage. <br /> 10 The Manager reported he had noticed the front sign was already up when <br /> 11 he returned from his Washington D.C. trip and when he looked for the <br /> 12 permit in the files found. a drawing for a front sign which was <br /> 13 designated as having 82 square feet and on which Mr. Hamer had written <br /> 14 "sign per sketch, 82 square feet, one sign on front of building" <br /> 15 before signing. <br /> 16 Mr. Childs indicated he was not aware of any municipal ordinance in <br /> 17 any city which allowed signage to be calculated the way E.S.I. had <br /> 18 calculated the dimensions of this sign ad said he thought most sign <br /> 19 people knew that was not the way to calculate signage. He also <br /> 20 recalled that Mr. Farrell and the sign company representative had <br /> 21 been specifically advised that the City ordinance did not allow <br /> 22 signage to be calculated that way during the hearing. <br /> 23 Gow Testifies Not Unusual for City Ordinances to Allow Signage to Be <br /> 04, Calculated The Way He Does It <br /> 25 Tom Gow, who had signed the October letter to Mr. Hamer specifying <br /> 26 what signage was being requested for the restaurant, said it - had been <br /> 27 he and not his brother, Tim Gow, who had appeared with Mr. Farrell <br /> 28 November 17th, who had worked with Mr. Farrell on his sign package. <br /> 29 He also said it had been he who had met with Mr. Hamer early in <br /> 30 October and it was during that meeting that "calculations for the <br /> 31 front sign were made for each word specifically and how the sign <br /> 32 would be laid out was clarified for Mr. Hamer" , leading to the <br /> 33 Building Inspector approving the permit for the sign November 18th. <br /> 34 He explained that this type of business sign consists of internally <br /> 35 neon lighted columns, known as "channel lettering" , and, in fact, each <br /> 36 letter is .,a fixture which can be considered to be a sign in some <br /> 37 cases. He recognized `; that- this differed from the City Ordinance as <br /> 38 stated by the City .Manager, -but wanted , it understood that the original <br /> 39 calculations were made "under the supervision of Mr. Hamer" . <br /> 40 Mr. Farrell said before, he had signed a check for $5 ,000 for that one <br /> 41 sign he had personally gotten verbal assurance from Mr. Hamer that it <br /> 42 was O.K. Mr. Gow added that the Building Inspector had also told them <br /> 43 the new copy on the roof sign and the reader board on the east <br /> 44 required variances for which they had applied and paid the required <br /> 45 fees. <br /> • <br />
The URL can be used to link to this page
Your browser does not support the video tag.