My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Reso25 16276
RedwoodCity
>
City Clerk
>
Resolutions
>
City Council
>
2020-2029
>
2025
>
Reso25 16276
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 11:56:46 AM
Creation date
1/28/2025 11:56:39 AM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Resolution
Meeting Type
Joint
Agency Type
City Council
Date
1/27/2025
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
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
Managing Tomorrow’s Resources Today <br />MEMORANDUM <br />Page 8 of 11 <br /> RWC_Memo_19Dec2024 <br />The City’s design standard or Traffic Index (TI) for each category of streets could not be provided. <br />Lacking specific design standards for the City, we utilized the most common design standards in <br />modern pavement design guidelines from other similar local agencies, however we note that older <br />streets in the City's road network were likely not built to this standard. We want to point out that our <br />assumption here is conservative, not aggressive. Streets built to a lower standard can withstand less <br />vehicle traffic loading. Assuming a lower standard of design would mean a larger percentage of the <br />overall loading placed on the streets would be attributable to Recology’s collection vehicles. <br />Therefore, Recology would be responsible for a greater share of the street impact costs incurred by <br />the City. <br />The assumption of common design standards resulted in an estimated residential street TI of 5.0 or <br />7,161 ESALs. Collector streets were estimated to have a TI of 7.0 or 121,021 ESALs. Arterial streets <br />were estimated to have a TI of 9.0 or 1,000,000 ESALs. <br />HF&H collected from Recology vehicle weights and profiles for the various vehicles being studied in <br />this analysis. Each vehicle type was modeled based on weight, vehicle specifications, axle profile, and <br />average payload. This modeling produced an average ESAL for each pass of each vehicle type, which <br />was then used to assess the direct impact of each vehicle trip by each vehicle type. <br />The City provided its Pavement Technical Assistance Program FY 2021-22 Final Report. The Report <br />specified five funding scenarios to address the City’s plans for preventative maintenance of its roads. <br />Two scenarios of spending were analyzed: one scenario covered the anticipated annual expenditure <br />of $4.0 million per year, commensurate with the City’s typical paving maintenance budget, and the <br />second scenario analyzed the targeted annual level of necessary funding, $9.6 million per year, to <br />upgrade all City streets to a condition where only future preventative maintenance would be required. <br />The annual budgets were allocated among residential, collector, and arterial streets in proportion to <br />the percentage of lane miles for each of those street classifications. Refer to Figure 6 for the allocation <br />by street classification. The residential, collector, and arterial street portions of the Average Annual <br />Expenditures were allocated among the various vehicle types in proportion to the calculated impact <br />of each vehicle type, as determined above. <br />Figure 6. City Lane Mileage by Street Classification <br />Road Centerline % of <br />Type Miles Total <br />Current Funding <br />Residential 177 50.8% <br />Collector 56 16.0% <br />Arterial 116 33.2% <br />Total 349 100.0% <br />Target Funding <br />Residential 177 50.8% <br />Collector 56 16.0% <br />Arterial 116 33.2% <br />Total 349 100.0% <br />ATTY/RESO.0003/CC RESO 2025 SOLID WASTE COLLECTION RATES & ADOPTING FRANCHISE FEE STUDY - EXHIBIT B <br />REV: 01-14-25 MI Page 8 of 11
The URL can be used to link to this page
Your browser does not support the video tag.