New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Admin Order 58-01-11-F
COE
>
PW
>
Admin
>
Execs
>
Admin Orders
>
Admin Order 58-01-11-F
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/25/2008 3:35:36 PM
Creation date
8/14/2008 10:07:16 AM
Metadata
Fields
Template:
PW_Exec
PW_Division_Exec
Administration
PWA_Project_Area
Admin Orders
PW_Subject
SDC Methodology
Document_Date
6/29/2001
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
73
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
Anoth r basic assumption of the transportation SDC is that the rates assigned to each use <br /> classifi ation include all related functions for that type of development. Where the <br /> develo ment includes mixed land uses which are independent activities, as distinguished <br /> from a ciliary or supporting uses, a composite development charge will be calculated for each <br /> <br /> I, use. <br /> <br /> I!, 1.3 rterial and Collector Street Cost Analysis <br /> <br /> ~i <br /> The c st figure for street construction is a key factor in the equation by which the <br /> transp rtation portion of systems development charge is calculated. This discussion outlines <br /> the m thodology and assumptions- used to calculate a unit cost used in the systems <br /> develo ment charge equation. <br /> The c st of a lane mile of arterial or collector street is derived from several components: <br /> • t e basic construction cost of a linear section street <br /> • t e cost of intersections <br /> • t e cost of bridges or other structures <br /> • t e cost of traffic signals, and <br /> • t e cost of street lights <br /> Figure 2 illustrates the method for calculating the arterial and collector street components of <br /> the tra sportation SDC. <br /> 1 3.1 Linear Section Construction Costs <br /> he two typical sections developed for this analysis are based upon standard <br /> e gineering practices, City policy, and policies included in the most recent Council- <br /> a opted, long-range transportation plan for the Eugene-Springfield area. <br /> e supporting data and detailed analysis for typical arterial and collector sections used <br /> i this methodology can be found in Table 3 of this Appendix. The supporting data <br /> i cludes estimated construction costs per lineal foot and linear mile for typical arterial <br /> a d collectors including engineering and administrative costs, the average number of <br /> I nes per mile of arterial and collector section, and the average assessable and non- <br /> a sessable cost per linear foot, per linear mile, and per lane mile. <br /> 1 3.2 Intersection Construction Costs <br /> e importance of intersections as a component in the arterial and collector street cost <br /> c Iculation comes from costs which are higher than a linear section of street and from <br /> t e City's long standing policy not to assess costs for intersections to adjacent property. <br /> he cost calculations for typical street intersections were based on the lineal foot unit <br /> f r different street widths and typical right-of-way widths for local and collector/arterial <br /> s reets. Based on the average number of intersections per mile, the intersection cost <br /> p r lane mile ofarterial/collector streets including administration and engineering costs <br /> c n be estimated. <br /> ote that the average number of intersections does not include the downtown grid. It <br /> as judged unlikely that the dense grid system of streets in downtown Eugene would <br /> b repeated elsewhere and thus avoids the potential for overestimating the number of <br /> i tersections per mile. <br /> City of Eu ene SDC Methodology Transportation, Page B- 3 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.