My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01/06/2026 Meeting Minutes
Document-Host
>
City North Olmsted
>
Minutes
>
2026
>
01/06/2026 Meeting Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2026 11:30:11 AM
Creation date
1/21/2026 11:25:56 AM
Metadata
Fields
Template:
North Olmsted Legislation
Legislation Date
1/6/2026
Year
2026
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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
2 <br />TO: NORTH OLMSTED CITY OFFICIALS, <br />After the initial presentations by City Officials and the developer, we studied the 2025 <br />Comprehensive Plan. We found overwhelming specific documentation that the development is <br />not compatible with the Plan. Once we became familiar with the 2025 Plan, it was stunning <br />how weak the belief in compatibility is. A few general portions of the Plan were used to justify <br />adherence to the proposed project. We previously submitted these findings in a printed report. <br />In the meeting on October 22', the City again presented their justifications. The Butternut <br />Ridge Apartments were used as an example of how the proposal fit into the neighborhood. This <br />is ludicrous. The apartments are not part of the Historic District, they don't exit/enter on <br />Butternut and were forced on us in place of Kmart! <br />Another stunning statement was that the City owns the lot on the south side of Butternut and <br />have no plans to develop that property. This is not comforting to the long term residents of the <br />street familiar with it's history. That is not a statement that will stand the test of time. There <br />have already been attempts to develop the south side. If a developer is able to intrude on the <br />north side, why would there be any concern about future impacts on the south? <br />The second main document used to justify the plan is the Butternut Ridge Historic District <br />Design Guidelines. The first section on the overhead display used by the City is section 9 New <br />Construction. This clearly states "The design GOAL of new free standing buildings, as with <br />additions to historic buildings, is VISUAL COMPATIBILITY with the site, SETTING and <br />CHARACTER of surrounding HISTORIC buildings through the use of modern materials by <br />taking cues from surrounding buildings". By this very statement of goals, the current proposal <br />is non conforming. How are modern attached structures within the District compatible with the <br />surrounding character? It is in fact the exact opposite. Another portion in section 9 states in <br />part, new buildings should remain sensitive to the surrounding character. Again, the current <br />proposal is far from sensitive to the areas character. <br />Section 9.1 was then used to show compliance. The very first sentence should stop the <br />development efforts. It states "the goal of new construction is visual compatibility". I cannot <br />think of anything less compatible than putting these attached structures on Butternut. The <br />section then states in part "Site design for new construction should take into consideration the <br />alignment, orientation, spacing, massing, scale, and proportion relative to the framework of <br />SURROUNDING BUIULDINGS". This proposal again just does not fit. <br />Section 9.2 was then posted. All of the wording in this New Construction: Visual Compatibility <br />section is contrary to the proposed development. In fact this section is better suited to argue <br />against the project. <br />Section 10, Site Design was then used. Again this states in part any site design should fit within <br />the framework of surrounding buildings. This also is better evidence against the proposed <br />development. <br />
The URL can be used to link to this page
Your browser does not support the video tag.