Laserfiche WebLink
3.0 Traffic Forecasts <br />To effectively address the traffic questions presented at the beginning of this report, traffic forecasts <br />were completed for 2011. It is standard practice to analyze traffic conditions for the year after full <br />completion of the proposed development. Specifically, AM and PM peak hour traffic volumes were <br />developed for the three subject intersections, as well as for the proposed access points to CSAH 14 and <br />Pine Street. Analysis of each location includes the following three scenarios: <br />• 2006 Existing <br />• 2011 No -Build <br />• 2011 Build <br />The following methodology was used to develop traffic volumes for the above three scenarios: <br />• 2006 Existing. Peak hour traffic volumes for this scenario were established based on AM <br />and PM peak period traffic counts completed at the three subject intersections on a <br />typical weekday. <br />• 2011 No- Build. To account for natural background traffic growth, existing volumes at <br />the subject intersections were increased at a rate of 5.0 percent per year. This growth <br />factor was established based on review of historic traffic volume maps and information <br />published in the TH 242 /CSAH 14 Access Management Study (May 1999). Traffic <br />volumes generated by other area developments that include a trips through the subject <br />intersections are expected to be accounted for in this conservative growth rate. <br />• 2011 Build. Volumes due to the proposed Nature's Refuge residential development were <br />added to the 2011 No -Build volumes to establish 2011 Build volumes. <br />The approach and the various steps involved in establishing development volumes are described <br />next: <br />• Trip Generation. Trip generation estimates for the 278 single - family detached houses <br />were developed based on data presented in the Institute of Transportation Engineers Trip <br />Generation, Seventh Edition. Trip generation estimates for the Nature's Refuge <br />development are shown in the Table 1. <br />