My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
4/12/1994
CBCC
>
Meetings
>
1990's
>
1994
>
4/12/1994
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2015 12:04:24 PM
Creation date
6/16/2015 1:55:31 PM
Metadata
Fields
Template:
Meetings
Meeting Type
Regular Meeting
Document Type
Minutes
Meeting Date
04/12/1994
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
123
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).
View images
View plain text
2. For Single -Family Units in 5th Edition ITE Manual: <br />a.. Average Weekday Trip Ends: 9.55/unit <br />b. P.M. Peak Hour Trip Ends: 1.01/unit <br />C. Inbound (P.M. Peak Hour): 65% <br />i. Westbound (P.M. Peak Hour): 75% <br />ii. Eastbound (P.M. Peak Hour): 25% <br />d. Outbound (P.M. Peak Hour): 35% <br />i. Westbound (P.M. Peak Hour): 25% <br />ii. Eastbound (P.M. Peak Hour): 75% <br />3. Peak Direction of C.R. 510, from 66th Avenue to C.R. 512: <br />Westbound <br />4. Formula for Determining Number of Peak Hour/Peak Season/Peak <br />Direction Trips Generated: Number of Units X P.M. Peak Hour <br />Rate X Inbound P.M. Percentage X Inbound -Westbound Percentage <br />(477 X 1.01 X .65 X .75) = 235 <br />(trip distribution based on a Modified Gravity Model) <br />5. Formula for Determining Number of Average Weekday Trips <br />Generated: Number of Units X Average Weekday Rate <br />(477 X 9.55 = 41555) <br />6. Traffic Capacity on this segment of C.R. 510, at a Level of <br />Service "D": 630 peak hour/peak season/peak direction trips <br />7. Existing Traffic volume on this segment of C.R. 510: <br />.422 peak hour/peak season/peak direction trips <br />The number of Average Weekday Trip Ends associated with the most <br />intense use of the subject property under the existing land use <br />designation is 1,518. This was determined by multiplying the 159 <br />units (most intense use) by ITE's single-family residential factor <br />of 9.55 Average Daily Trip Ends/unit. <br />The number of Average Weekday Trip Ends associated with the most <br />intense use of the subject property under the proposed land use <br />designation is 41555. This was determined by multiplying the 477 <br />units (most intense use), by ITE's single-family residential factor <br />of 9.55 Average Daily Trip Ends/unit. <br />Since the county's transportation level of service is based on peak <br />hour/peak season/peak direction characteristics, the transportation <br />concurrency analysis addresses project traffic occurring -in the <br />peak hour and affecting the peak direction of impacted roadways. <br />According to ITE, the proposed use generates more volume in the <br />p.m. peak hour than in the a.m. peak hour. Therefore, the p.m. <br />peak hour was used in the transportation concurrency analysis. The <br />peak direction during the p.m. peak hour on C.R. 510 is westbound. <br />Given those conditions, the number of peak hour/peak season/peak <br />direction trips that would be generated by the most intense use of <br />the subject property under the existing land use designation was <br />calculated to be 78. This was determined by multiplying the total <br />number of units allowed (159) under the existing land use <br />designation by ITE's factor of 1.01 p.m. peak hour trips/unit, to <br />determine the total number of trips generated. Of these trips, 65% <br />(104) will be inbound and 35% (56) will be outbound. Of the <br />inbound trips, 75% or 78 will be westbound. <br />To determine the number of peak hour/peak season/peak direction <br />trips that would be generated by the most intense use of the <br />subject property under the proposed land use designation, the total <br />number of units allowed under the proposed amendment (477) was <br />APR 12 x`04 67 <br />BOOK r 158 <br />
The URL can be used to link to this page
Your browser does not support the video tag.