9/8/1997 - Laserfiche WebLink

Home Browse Search

M M M County obligations to fund landscaping improvements will vary depending upon roadway jurisdiction and alternative funding sources such as grants and private donations. For instance, during SR 60 Task Force workshops FDOT staff stated that, in regard to SR 60, landscaping installation could be funded by FDOT in conjunction with state road improvement projects (e.g. resurfacing, adding lanes) as long as the county agrees to maintain the landscaping. For county road projects such as the CR 512 project, all costs will be the county's obligation. In some instances highway beautification grants and enhancement fund grants could be applied for and administered by staff, although such duties would require additional staff time. Staff is also aware that private donations from citizens, civic organizations, and businesses are possible sources for specific, designated areas. For "big picture" planning purposes, the Board should assume that all maintenance costs will be borne by the county, that all county road landscaping installation costs will be borne by the county, and that state road landscaping installation costs will be borne by FDOT, where the county enters into an agreement with FDOT to maintain such landscaping. In regard to supply of landscaping material for installation and replacement, the county could consider using existing, unused county property to establish and maintain a nursery for county landscaping needs. Such material could be used exclusively or as a supplement for any given project. Such a nursery could ensure supplies of certain trees and/or plants in the great quantities that might be needed for extension projects. As of this time, staff has not researched the costs of such an operation. Currently, a limited number of Public Works personnel maintain county road rights-of-way. Special roadway landscaping will probably increase maintenance needs beyond present mowing requirements. In lieu of adding staff and performing maintenance in-house, the county could contract out special road or corridor maintenance duties to a private company. Such privatizing could be specifically costed -out on a project by project basis by accumulating private estimates or bids and could be a more efficient alternative to gearing up a new "program" with county staff. It should be noted that the City of Port Orange, which recently completed a significant landscaping project within its Dunlawton corridor, contracted -out to a private firm the performance of a corridor specific maintenance schedule. County funding of installation can be handled on a project -by -project basis under current practices if the cost of landscaping is a reasonable percentage of a road project budget. For instance, all county road projects have a "landscaping budget" for sod, and most projects, according to Public Works stag could support a special landscaping budget (landscaping above and beyond sodding) of 7°/.-10% of total project budget without additional, specially designated landscape funding. It appears that such funding could cover the costs of providing enhanced roadway landscaping similar to the previously discussed urban and rural guideline designs depicted in attachments 6 and 7. However, any additional maintenance needs that might arise -from enhanced landscaping will require specific funding. Such needs would be identified during project design and would require county (Board) action at that time to ensure adequate maintenance funding. QUESTION #3 FOR THE BOARD: CONSIDERING AESTHETIC EXPECTATIONS, ROAD AND UTILITY DESIGN CONSTRAINTS AND OPPORTUNITIES, AND INSTALLATION AND MAINTENANCE COSTS, DOES THE BOARD APPROVE THE PROPOSED URBAN AND RURAL LANDSCAPING SECTIONS AS GENERAL COUNTY GUIDELINES FOR IMPROVING DESIGNATED CORRIDORS? C. Implementation If approved, the guidelines will need to be implemented on a project by project basis. Landscaping improvements will need to be designed along with the design of the road improvements. For FDOT roadways designated by the county as special corridors (e.g. SR 0 September 8, 1997 RIM