My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11/9/2023 Minutes
Document-Host
>
City North Olmsted
>
Boards and Commissions
>
2023
>
Planning and Design Commission
>
11/9/2023 Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/10/2024 9:45:52 AM
Creation date
4/10/2024 9:45:31 AM
Metadata
Fields
Template:
N Olmsted Boards & Commissions
Year
2023
Board Name
Planning & Design Commission
Document Name
Minutes
Date
11/9/2023
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
3
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
funding opportunities in the current infrastructure -focused climate. <br />The consultants were asked if the city's master plan from 2015 was considered in the initial <br />analysis. The team reviewed various plans. including previous TLCI and corridor plans in the <br />area. to identify alignments as a starting point for the current work. There was an inquiry about <br />the time frames outlined in the plan -immediate. near-term. intermediate. and long-term. The <br />explanation was that immediate improvements could start now and extend up to two or three <br />years. while the near-term spans up to five years. Intermediate timelines look beyond five years <br />but within a decade. recognizing the complexity of certain projects. and emphasizing that some <br />might not be high priority. Continuing the conversation. the consultant explained the concept of a <br />trailhead at the Columbia Road intersection. liking it to Metro Parks and proposing a bus rapid <br />transit line connecting residents to recreational assets. The discussion also touched on the <br />challenges of working with public utilities to bury lines. considering safety concerns. Regardin�u, <br />the brickscape program, the existing conditions were acknowled��ed. and recommendations were <br />made based on different focus areas along the corridor. with considerations for green edges and <br />density development zones. In the conversation. there was discussion about the challenges of <br />dealin�� with utility poles. including issues related to ownership. legal rights. and utility <br />easements. The conversation also touched on the success rate of removing inactive or non- <br />operable poles. emphasizing the difficulty of achieving success along a lengthy corrido. The <br />consideration of targeting specific areas or blocks with political will to pressure utilities was <br />discussed and the focus on utility pole compliance with desmon standards. especially regarding <br />safety concerns was highlighted. The potential for collaboration with utility companies to <br />address safety issues and the involvement of the law director in notifying them on non- <br />compliance was suguested. The conversation included a question about the total cost of the plan. <br />and the response emphasized that the undertaking is substantial. The 10 -year vision involves <br />phased implantation. with a current project from Stearns to Canterbury funded by ODOT. Desh-111 <br />guidelines from the plan will be incorporated into the project. The strategy includes leveraging <br />funds from ODOT. creating an incentive district with local funds. and utilizing grant writers to <br />execute the plan in phases. Board members and staff all agreed to revisit the study during the <br />meetin(, in January to cast their recommendation. This was to allow for time to fully review the <br />document in its entirety with the knowledge form the presentation that was given at the current <br />meeting. <br />ADJOURNMENT <br />Mr. David moved to excuse Mr. Patton: seconded by Mr. Leon. all in favor none opposed. <br />With no further business before the board. the meeting adjourned at 8:32 p.m. <br />
The URL can be used to link to this page
Your browser does not support the video tag.