Laserfiche WebLink
<br />6.1.6 Traffic Data <br /> <br />Traffic data should include the following: <br /> <br />Design or projected ADT <br />Initial ADT <br />Traffic mix <br />Vehicle running cost, $/vehicle mile <br />Average occupancy rate, passengers/vehicle <br />Value of time, $/hr. <br />Length of normal route and detour routes <br />Average speed on each route <br />Fatality rate on each route, people per hundred <br />million vehicle miles <br />Injury ratio, injurieS/fatality <br />Property damage ratio, accidents/fatality <br />Unit cost of injuries, $/injury <br />Unit cost of property damage, $/accident <br /> <br />Detour routes must be identified along with the expected overtopping frequency. <br />In other words detour routes may change as the flood frequencies vary. Also, <br />the crossing being designed may be planned as a detour for other crossings <br />and the ADT may be a function of flood frequency. <br /> <br />6.1.7 Embankment and Pavement Repair Costs <br /> <br />Although many highway agencies keep elaborate maintenance records, these records <br />are not likely to be of much value in estimating repair costs. Repair costs must <br />be estimated in much the same manner as construction costs. The repair operations <br />must be conceptualized and related to standard construction operations when <br />estimating costs. <br /> <br />To estimate repair time and cost, data should include the following: <br /> <br />Total volume of embankment, CY <br />Total area of pavement, SY <br />Rate of embankment repair, CY/day <br />Rate of pavement repair, SY/day <br />Unit cost of embankment repair $/CY <br />Unit cost of pavement repair $/SY <br />(assume density of asphalt pavement = 100 lb/SY/in.) <br />Adjustment cost for rapid repair <br />Mobilization cost, $ <br /> <br />6.1.8 Summary of Data Requirements <br /> <br />Table 6.1 is a summary of the data requirements and includes an indication of <br />units, possible sources and where the data are used in the analysis. <br /> <br />22 <br /> <br />e <br /> <br />. <br /> <br />, <br /> <br />e <br /> <br />e <br />