My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Historic Preservation Commission Agenda and Packet 2018 02 12
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
HISTORIC PRESERVATION COMMISSION
>
2005-2019 Historic Preservation Commission Agendas and Packets
>
2018 Historic Preservation Commission Agendas and Packets
>
Historic Preservation Commission Agenda and Packet 2018 02 12
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2021 3:08:20 PM
Creation date
2/15/2018 10:50:39 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
HPCPKT 2018 02 12
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
45
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
Planning Commission <br />Meeting Minutes <br />December 14, 2017 <br />Page 3 of 10 <br />Ritchie replied that the previous grant request of about $13,000 would not be deducted, as the <br />new proposal was for the applicant to start construction of a new sign from scratch. <br />Fahey stated that the $34,133 as a total cost, it was not the amount they would be spending in <br />excess of redoing the existing sign. <br />Chuck Thomas asked if the $2,850 to package and remove the sign was the cost to the City of <br />removing and packaging the sign. <br />Ritchie confirmed that the $2,580 was a package and removal cost from the same contractor <br />who proposed the $34,133 amount. <br />Haley invited the owner to speak. <br />Mark Oberholzer, 224 Hoover Avenue in Louisville offered to answer questions from the <br />Commission. <br />Fahey asked if Oberholzer planned to make a similar sign with the allocation funds. <br />Oberholzer responded that they were planning to use a similar design to what had been <br />presented to the Commission in October. <br />Ritchie added that the PUD amendment heading to Planning Commission proposed to regulate <br />the neon tubing, colors, fonts, and size of the new sign. They were also considering putting a <br />historic plaque near the new sign. They are not regulating the face of the sign to avoid having <br />new owners come to Commission every time they want to change the branding on the sign. <br />Oberholzer stated that he wanted to preserve the history of the sign. He and the other owners <br />wanted the new sign to look like the old one in look and feel. They planned to keep the same <br />colors and the same basic shape while changing the branding to "The Corner," which was the <br />new name of the building. <br />Haley stated that it was in the owners' interest to keep the sign as a semi -replica, as they were <br />applying for a variance to allow the new sign. <br />Haley invited public comments. <br />Joan Riggins, 912 Lincoln Avenue in Louisville, stated that the sign was very special and if they <br />tried to reface it there would be gouges that would effectively change the sign entirely. She <br />requested a new but similar sign from the beginning rather than re -facing the old sign. She <br />preferred to have the old sign at a place where people could come visit it. <br />Haley closed public comment and turned to commission discussion. <br />Chuck Thomas asked if the Commission needed to amend the previous ruling or if it required a <br />new ruling. <br />Ritchie stated that the applicant withdrew the previous application and submitted a new one, so <br />the ruling would need to be new as well. <br />Cyndi Thomas stated that she was in favor of the new course of action and was a better option <br />than redoing the sign. She added that there did not seem to be issues with landmarking a sign <br />that was not attached to a building. She was concerned about the pricing for acquisition. <br />
The URL can be used to link to this page
Your browser does not support the video tag.