Problem 3: Shenendehowa Campus
Problem 3 Printable Version
On the western edge of
the network is the entrance to the Shenendehowa (Shen) Campus (Intersection
A). It is a signalized, fully-actuated intersection. It has
two lanes eastbound (left-through and exclusive right), two lanes
westbound (left and through-right), two lanes northbound (left and
through-right), and one lane southbound (left-through-right).
|
Exhibit 2-26. Shenendehowa Campus AM peak hour turning movements |
Large volumes exist on the eastbound, westbound, and northbound
approaches.
Exhibit 2-26 shows typical volumes for the AM peak hour. Traffic enteLevel of Servicend
leaving the Shenendehowa campus uses the westbound left and eastbound
right. Those flows are highly peaked. The volumes to and from the north
are extremely small because a church is the only building generating
traffic on that approach. On a
typical weekday during the peak hours, there isn’t much traffic going
into or out of the church.
Analysis Plans
We’re going to use this intersection to examine three issues:
peak hour
factor, heavy vehicles, and impact dilution. We’ll examine the first two
issues in the context of the AM and PM peaks (AM Existing & PM
Existing), while we’ll use the PM With condition for the
third.
Sub-problem 3a: AM &
PM Peak Hour - Existing Conditions
Sub-problem 3b:
PM
Peak Hour - With Conditions
Discussion
Discussion:
Are there
any large school facilities in your jurisdiction? If so, how do you analyze
their performance? Do you need to consider special times of the day to
understand the facility's performance? If so, what extra data do you need to
collect? [ Back
] [ Continue
] to Sub-problem 3a |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
Peak
Hour Factor
The
peak hour factor (PHF) accounts for variations in flows that occur during
the heaviest hour of traffic. If the volume for the hour is 800 vehicles
and the heaviest volume duLevel of Serviceny one 15-minute period is 250 vehicles,
then the peak hour factor is 0.80 (800/(4*250)). When you input the hourly
volumes and the peak hour factor, you will evaluate the conditions that exist during the peak 15
minutes, the time when the facility is most heavily loaded.
We can use the highly peaked flows at
the entrance to the Shenendehowa campus to show how the peak hour factor
works and the effect it has. Using data for this intersection will show
how the typical method for applying the peak hour factor might or might not lead
to the right assessment of the performance conditions in some situations.
Discussion:
Traffic
engineers hold different perspectives on the peak hour factor. Some compute
values for each clock hour (3-4, 4-5, etc.). Some consider each sequence of
four 15-minute time periods and use the sequence with the maximum total
volume for the peak hour factor. Some predicate PHF
calculation on the sequence of 15-minute time periods that has the maximum
flow for the movement, others, the maximum total intersecting volume for
the intersection. Still others focus on demand, not volume as the basis
for computing the PHF. What do you do? What do you think should be done if
the data were available?
with
Peak Hour Factor Analysis |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
The AM peak volumes by 15-minute interval
are presented in Exhibit 2-27. The peak hour is highlighted in yellow. As can
be seen, there is high variability in most of the flows. Only the
eastbound through is relatively consistent. For example, during the peak
hour, the eastbound right ranges from 54 to 111 vehicles in a 15 minute
period. The westbound left ranges from 106 to 45 (because of the school
traffic), while the northbound right ranges from 41 to 79.
Exhibi 2-27. Shenendehowa Campus AM peak hour volumes
|
Time |
Eastbound |
Westbound |
Northbound |
Southbound |
Intersection Total |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
7:00 |
0 |
113 |
19 |
132 |
19 |
132 |
0 |
151 |
12 |
0 |
22 |
34 |
0 |
0 |
0 |
0 |
317 |
7:15 |
0 |
118 |
27 |
145 |
35 |
149 |
0 |
184 |
18 |
0 |
30 |
48 |
0 |
0 |
0 |
0 |
377 |
7:30 |
0 |
120 |
41 |
161 |
41 |
168 |
1 |
210 |
11 |
0 |
21 |
32 |
1 |
0 |
0 |
1 |
404 |
7:45 |
0 |
172 |
64 |
236 |
86 |
166 |
1 |
253 |
6 |
0 |
18 |
24 |
0 |
0 |
0 |
0 |
513 |
8:00 |
0 |
171 |
111 |
282 |
106 |
128 |
5 |
239 |
33 |
1 |
53 |
87 |
0 |
1 |
1 |
2 |
610 |
8:15 |
0 |
190 |
58 |
248 |
78 |
153 |
2 |
233 |
47 |
0 |
79 |
126 |
2 |
0 |
0 |
2 |
609 |
8:30 |
0 |
166 |
54 |
220 |
45 |
94 |
9 |
148 |
27 |
0 |
41 |
68 |
1 |
0 |
2 |
3 |
439 |
8:45 |
0 |
151 |
62 |
213 |
68 |
121 |
12 |
201 |
27 |
2 |
59 |
88 |
7 |
1 |
6 |
14 |
516 |
AM Peak |
0 |
678 |
285 |
963 |
297 |
496 |
28 |
821 |
134 |
3 |
232 |
369 |
10 |
2 |
9 |
21 |
2,174 |
PHF |
1.00 |
0.89 |
0.64 |
0.85 |
0.70 |
0.81 |
0.58 |
0.86 |
0.71 |
0.38 |
0.73 |
0.73 |
0.36 |
0.50 |
0.38 |
0.38 |
0.89 |
%HV |
0.00 |
0.03 |
0.09 |
0.05 |
0.15 |
0.06 |
0.04 |
0.09 |
0.13 |
0.00 |
0.08 |
0.09 |
0.00 |
0.00 |
0.11 |
0.05 |
0.07 |
If we do a standard peak hour analysis for the AM peak hour, we get an
overall level of service C.
Dataset 22
contains the complete input data for the AM peak hour analysis.
Exhibit 2-28 shows the delays and levels of service for each of the
movements. The largest delays
are associated with the westbound left and the conflicting eastbound
through. The westbound left
movement clearly has the worst LOS (D).
Exhibit 2-28. Shenendehowa Campus AM peak hour delays and levels of
service |
Dataset |
PHF Conditions |
HV Correction |
Performance Measure |
EB |
WB |
NB |
SB |
OA |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
22 |
Overall |
Yes |
Delay |
33.9 |
12.4 |
27.5 |
39.8 |
12.0 |
22.0 |
25.0 |
33.9 |
30.7 |
19.2 |
19.2 |
25.9 |
LOS |
C |
B |
C |
D |
B |
C |
C |
C |
C |
B |
B |
C |
v/c |
0.94 |
0.49 |
- |
0.64 |
0.50 |
- |
0.59 |
0.79 |
- |
0.09 |
- |
- |
with Peak Hour Factor Analysis |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
The
PM peak is similar. The
15-minute counts are shown in Exhibit 2-29, and the peak hour is highlighted in
yellow. Comparing the PM peak
to the AM peak in
Exhibit 2-27, we can see that the PM peak eastbound rights and the westbound
lefts are significantly less then in the AM peak. Also, the westbound
through volume is much larger. Finally,
there’s a major change in the percentage of heavy vehicles. In the AM
peak, the percentages were 15% for the westbound left and 9% for the
eastbound right. In the PM peak, they are 26% for the westbound left and
41% for the eastbound right.
Exhibit 2-29. Shenendehowa Campus PM peak hour volumes |
Time |
Eastbound |
Westbound |
Northbound |
Southbound |
Total |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
16:00 |
0 |
193 |
21 |
214 |
29 |
183 |
1 |
213 |
37 |
1 |
74 |
112 |
4 |
0 |
2 |
6 |
545 |
16:15 |
0 |
182 |
18 |
200 |
27 |
231 |
0 |
258 |
25 |
1 |
52 |
78 |
1 |
0 |
0 |
1 |
537 |
16:30 |
0 |
208 |
23 |
231 |
32 |
196 |
1 |
229 |
31 |
0 |
54 |
85 |
3 |
0 |
0 |
3 |
548 |
16:45 |
0 |
187 |
13 |
200 |
24 |
216 |
0 |
240 |
31 |
0 |
35 |
66 |
1 |
0 |
1 |
2 |
508 |
17:00 |
0 |
209 |
11 |
220 |
25 |
221 |
0 |
246 |
21 |
1 |
23 |
48 |
1 |
0 |
2 |
3 |
517 |
17:15 |
0 |
175 |
25 |
200 |
12 |
258 |
7 |
277 |
29 |
0 |
25 |
54 |
0 |
0 |
3 |
3 |
534 |
17:30 |
1 |
210 |
15 |
226 |
23 |
224 |
3 |
250 |
26 |
0 |
15 |
41 |
3 |
1 |
1 |
5 |
522 |
17:45 |
0 |
193 |
15 |
208 |
28 |
219 |
2 |
249 |
18 |
0 |
19 |
37 |
7 |
0 |
0 |
7 |
501 |
PM Peak |
|
770 |
75 |
845 |
112 |
826 |
2 |
940 |
124 |
2 |
215 |
341 |
9 |
0 |
3 |
12 |
2,138 |
PHF |
|
0.93 |
0.82 |
0.91 |
0.88 |
0.89 |
0.50 |
0.91 |
0.84 |
0.50 |
0.73 |
0.76 |
0.56 |
1.00 |
0.38 |
0.50 |
0.96 |
%HV |
|
0.02 |
0.41 |
0.06 |
0.26 |
0.03 |
0.00 |
0.05 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.05 |
Exhibit 2-30 compares the delays and levels of service for the AM and PM peaks.
Dataset
23 contains the input data for
the PM peak analysis. Overall,
the delays in the PM peak are slightly smaller than the AM peak.
Exhibit 2-30. Shenendehowa Campus AM & PM peak hour delays and levels of service |
Dataset |
PHF Conditions |
HV Correction |
Performance Measure |
Eastbound |
Westbound |
Northbound |
Southbound |
OA |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
LT |
TH |
RT |
Tot |
22
AM |
Overall |
Yes |
Delay |
33.9 |
12.4 |
27.5 |
39.8 |
12.0 |
22.0 |
25.0 |
33.9 |
30.7 |
19.2 |
19.2 |
25.9 |
LOS |
C |
B |
C |
D |
B |
C |
C |
C |
C |
B |
B |
C |
v/c |
0.94 |
0.49 |
- |
0.64 |
0.50 |
- |
0.59 |
0.79 |
- |
0.09 |
- |
- |
23
PM |
Overall |
Yes |
Delay |
27.2 |
7.9 |
25.5 |
23.9 |
14.5 |
15.6 |
18.7 |
21.6 |
20.5 |
16.2 |
16.2 |
20.3 |
LOS |
C |
A |
C |
C |
B |
B |
B |
C |
C |
B |
B |
C |
v/c |
0.92 |
0.15 |
- |
0.25 |
0.72 |
- |
0.45 |
0.62 |
- |
- |
- |
- |
The question we want to
raise is this: do either of these conditions shown in the table above occur? Are these good representations of the conditions in either peak
hour? Are they pessimistic? Optimistic? We need to look at the individual
15-minute intervals to find the answer.
We
must be careful not to oversimplify this analysis, because there isn’t any
real carryover in queues from one 15-minute interval to the next. If there
were, we would need have to do a series of cascading analyses across sequential
slices to capture the effects of queue spillover.
with
Peak Hour Factor Analysis |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
Let’s first look at the 15-minute
intervals that makeup the AM peak. The volumes were shown in
Exhibit 2-27. We
have to create four datasets and get four separate results. Then we
can compare those results with the original “peak hour” solutions we
obtained, shown in
Exhibit 2-30, to see where the differences are. We could also perform a pair of analyses in which the peak hour factors are different for every movement. That produces yet a third assessment
of the intersection’s performance.
Click here to see the input data for each of these analyses.
The delays and levels
of service that we obtain for the AM peak are shown in Exhibit 2-31.
The first line shows our original AM peak hour analysis. The next
shows the results if we use movement-specific peak hour factors, and the
last four lines show the results for each 15-minute interval during the PM
peak. (Where a movement has zero flow, no LOS has been computed.)
Exhibit 2-31. Shenendehowa Campus AM peak hour delays by 15 minute interval |
Dataset |
PHF Condition |
HV Correction |
Performance Measure |
EB |
WB |
NB |
SB |
OA |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
22 |
Base Case Overall |
Yes |
delay |
33.9 |
12.4 |
27.5 |
39.8 |
12.0 |
22.0 |
25.0 |
33.9 |
30.7 |
19.2 |
19.2 |
25.9 |
LOS |
C |
B |
C |
D |
B |
C |
C |
C |
C |
B |
B |
C |
24 |
By Movement |
Yes |
delay |
50.0 |
21.8 |
39.6 |
58.3 |
15.4 |
32.2 |
35.8 |
54.9 |
47.9 |
25.1 |
25.1 |
38.0 |
LOS |
D |
C |
D |
E |
B |
C |
D |
D |
D |
C |
C |
D |
25 |
Internal 8:00-8:15 |
Yes |
delay |
31.8 |
21.8 |
27.8 |
51.6 |
12.2 |
29.7 |
29.9 |
34.3 |
32.6 |
24.5 |
24.5 |
29.2 |
LOS |
C |
C |
C |
D |
B |
C |
C |
C |
C |
C |
C |
C |
26 |
Internal 8:15-8:30 |
Yes |
delay |
28.1 |
12.1 |
24.3 |
48.5 |
15.6 |
26.6 |
- |
33.7 |
- |
19.7 |
19.7 |
- |
LOS |
C |
B |
C |
D |
B |
C |
- |
C |
- |
B |
B |
- |
27 |
Internal 8:30-8:45 |
Yes |
delay |
20.8 |
10.8 |
18.4 |
28.4 |
11.0 |
16.3 |
19.4 |
19.7 |
19.6 |
17.1 |
17.1 |
17.8 |
LOS |
C |
B |
B |
C |
B |
B |
B |
B |
B |
B |
B |
B |
28 |
Internal 8:45-9:00 |
Yes |
delay |
34.9 |
18.0 |
18.0 |
37.6 |
12.9 |
21.3 |
26.5 |
34.0 |
31.7 |
24.9 |
24.9 |
26.7 |
LOS |
C |
B |
B |
D |
B |
C |
C |
C |
C |
C |
C |
C |
In the original
analysis, the average delay per vehicle is 25.9 seconds. When
we use movement-specific PHF values, the average delay is 38 seconds, or 47% higher. Is
this realistic? We’ll see. The average delays on
a 15-minute basis range from 17.8 to 29.2 seconds per vehicle. So the 38.0
seconds is clearly too high. The
original analysis underestimates the delays during
the peak 15 minutes where it is 13% higher.
Discussion:
Look at the datasets used for each of the 15-minute
analyses. Check the values for the analysis parameters we set, such as the
value for T, the duration of the analysis, and the peak hour factor. Think
about whether you would have chosen the same or a different set of parameter
values.
with
Peak Hour Factor Analysis |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
A detailed look at the individual 15-minute intervals from
Exhibit 2-31 is also instructive. The eastbound through-and-right
delays range from 20.8 to 34.9 seconds; the northbound approach delays
range from 19.6 to 32.6 seconds; and the westbound lefts range from 28.4
seconds all the way to 51.6 seconds per vehicle.
For the rest of the movements, the delays are more consistent.
Notice that in all of the interval cases and in the base case, each of the
delays is lower than those produced by the analysis done using PHF by
movement.
When comparing the original peak hour analyses to each of the 15-minute
interval analyses, it is obvious that the actual intersection performance
levels are not consistent with the predicted AM or PM peak hour
conditions.
In the worst 15-minute interval (8:00 to 8:15), the overall LOS is
C. For this interval, there are
significant increases from the PM peak hour results for the eastbound
right, the westbound left, and all three of the southbound movements.
Looking at the best performing 15-minute interval (8:30 to 8:45),
the overall LOS is B. For this
interval there are significant decreases (from the base case) in the
delays for the eastbound though-left, the westbound left, and all three
northbound movements.
with Sub-problem 3a |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM
peak - Existing Conditions
Exhibit 2-32 shows the results of our sensitivity analysis for the PM
Existing condition. The overall delay doesn’t change very much. It
ranges from 19.4 sec/veh up to 24.1. The delays for the individual movements
are similar except for the eastbound left-through. It varies from 20.2 to
31.1 sec/veh. That’s a 50% change.
Exhibit 2-32.
Shenendehowa Campus PHF Sensitivity Analysis for the PM peak hour |
Time Period |
PHF Condition |
Performance Measure |
EB |
WB |
NB |
SB |
OA |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
PM |
Overall |
Delay |
27.2 |
7.9 |
25.5 |
23.9 |
14.5 |
15.6 |
18.7 |
21.69 |
20.5 |
16.2 |
16.2 |
21.3 |
LOS |
C |
A |
C |
C |
B |
B |
B |
C |
C |
C |
B |
C |
PM |
By Movement |
Delay |
31.3 |
8.5 |
29.0 |
28.6 |
17.7 |
19.0 |
20.0 |
29.2 |
26.2 |
17.3 |
17.3 |
24.1 |
LOS |
C |
A |
C |
C |
B |
B |
B |
C |
C |
B |
B |
C |
PM |
Interval
16:00-16:15 |
Delay |
31.1 |
9.4 |
28.9 |
27.8 |
15.0 |
16.8 |
19.4 |
26.2 |
23.9 |
16.9 |
16.9 |
23.0 |
LOS |
C |
A |
C |
C |
B |
B |
B |
C |
C |
B |
B |
C |
PM |
Interval 16:15-16:30 |
Delay |
21.6 |
9.5 |
20.5 |
27.2 |
16.3 |
17.4 |
20.8 |
24.0 |
23.0 |
19.4 |
19.4 |
19.4 |
LOS |
C |
A |
C |
C |
B |
B |
C |
C |
C |
B |
B |
B |
PM |
Interval
16:30-16:45 |
Delay |
29.8 |
9.1 |
27.7 |
31.0 |
13.6 |
16.0 |
22.1 |
26.6 |
24.9 |
20.4 |
20.4 |
22.3 |
LOS |
C |
A |
C |
C |
B |
B |
C |
C |
C |
C |
C |
C |
PM |
Interval
16:45-17:00 |
Delay |
20.2 |
9.5 |
19.5 |
29.3 |
17.1 |
18.3 |
24.6 |
24.2 |
24.4 |
21.9 |
21.9 |
19.6 |
LOS |
C |
A |
B |
C |
B |
B |
C |
C |
C |
C |
C |
B |
Discussion:
Consider
the table shown above. These analyses show variations in results that were
obtained by making slightly different assumptions and using different inputs
for the peak hour factor.
with Sub-problem 3a |
Page Break
Sub-problem 3a: Shenendehowa Campus AM & PM peak - Existing Conditions
Heavy
Vehicles
What
would happen if the heavy vehicle percentages were ignored? Let’s
compare the results from the base case AM and PM peak
hour analyses with results if the correction factors were
left out. For complete input data for each of
these analyses click
here.
Exhibit 2-33 demonstrates
the differences in delay that will be obtained by neglecting the percent heavy
vehicle correction. In both the AM and PM conditions, the delays are smaller when the
correction factors are omitted. The differences in the AM peak are
slightly larger than they are during the PM peak. This is due to the
slightly higher volumes that occur during the AM peak.
Exhibit 2-33. Shenendehowa Campus Effects of Heavy Vehicles |
Dataset |
Time Period |
HV Correction |
EB |
WB |
NB |
SB |
OA |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
22 |
AM (base) |
Yes |
33.9 |
12.4 |
27.5 |
39.8 |
12.0 |
22.0 |
25.0 |
33.9 |
30.7 |
19.2 |
19.2 |
25.9 |
29 |
AM |
No |
29.4 |
12.0 |
24.2 |
36.7 |
11.6 |
20.7 |
22.8 |
29.3 |
26.9 |
19.2 |
19.2 |
23.3 |
23 |
PM |
Yes |
27.2 |
7.9 |
25.5 |
23.9 |
14.5 |
15.6 |
18.7 |
21.6 |
20.5 |
16.2 |
16.2 |
20.3 |
30 |
PM |
No |
22.2 |
7.6 |
20.9 |
23.0 |
13.8 |
14.9 |
19.3 |
22.5 |
21.4 |
16.7 |
16.7 |
18.3 |
Discussion:
A
sensitivity analysis was not conducted. It might be useful to see how much
the performance predictions change if the percentage of trucks grows. Then
you could understand how important it is to have an accurate estimate for the
analysis and the sensitivity to variations that occur in normal traffic.
to
Sub-problem 3b |
Page Break
Sub-problem 3b: Shenendehowa Campus PM peak - With Conditions
Traffic
Growth and Sensitivity
The PM With condition is a 2004-forecasted condition that
considers the impacts of the traffic generated by the Maxwell Drive site
development. As we move
further from the actual site development, the impact of the site-generated
traffic diminishes. We’ve
seen the impacts at Maxwell Drive and Moe Road. Let’s now look at
the impacts of this site-generated traffic at the current intersection.
The
volumes that will be used to analyze the 2004 PM With and PM
Without conditions are shown in Exhibit 2-34.
There is a small estimated growth on the eastbound
through movement, and the westbound through movement and the rest of the
movement volumes are unaffected by the site development.
For
the input
datasets
click
here.
Exhibit 2-34. Shenendehowa Campus Forecasted 2004 PM peak hour volumes |
Condition |
Eastbound |
Westbound |
Northbound |
Southbound |
Intersection Total |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
2004 PM Without |
0 |
801 |
78 |
879 |
117 |
859 |
2 |
978 |
129 |
2 |
224 |
355 |
9 |
0 |
3 |
12 |
2,224 |
2004 PM With |
0 |
869 |
78 |
947 |
117 |
927 |
2 |
1,046 |
129 |
2 |
224 |
355 |
9 |
0 |
3 |
12 |
2,360 |
2004 PM With +30% |
0 |
890 |
78 |
968 |
117 |
948 |
2 |
1,067 |
129 |
2 |
224 |
355 |
9 |
0 |
3 |
12 |
2,402 |
Exhibit 2-35 shows what we find from analyzing each of these three conditions.
Comparing the with and without conditions, the changes in overall delay are quite small.
To check the robustness of this comment (i.e., the sensitivity to
uncertainty in the site development volumes), we looked at an additional
with condition with 30% more site-generated traffic. The delays
still have not changed much. This tells us that this intersection is not
significantly affected by the site development at Maxwell Drive.
Exhibit 2-35. Shenendehowa Campus Growth and Sensitivity Analysis Results |
Dataset |
Condition |
HV Correct |
Cycle Length |
Performance Measure |
EB |
WB |
NB |
SB |
OA |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
L |
T |
R |
Tot |
31 |
PM 2004 Without |
Yes |
52.0 |
Delay |
25.9 |
7.7 |
24.3 |
25.5 |
14.1 |
15.5 |
20.0 |
24.7 |
23.0 |
17.2 |
17.2 |
20.2 |
95-Queue |
25.6 |
1.5 |
- |
3.1 |
23.0 |
- |
3.9 |
7.2 |
- |
0.3 |
- |
- |
Queue |
14.4 |
0.7 |
- |
1.5 |
12.8 |
- |
1.9 |
3.6 |
- |
0.2 |
- |
- |
32 |
PM 2004 With |
Yes |
55.0 |
Delay |
28.7 |
7.2 |
26.9 |
27.3 |
14.1 |
15.6 |
22.0 |
28.5 |
26.1 |
18.7 |
18.7 |
21.7 |
95-Queue |
29.8 |
1.5 |
- |
3.3 |
25.5 |
- |
4.2 |
7.8 |
- |
0.3 |
- |
- |
Queue |
17.2 |
0.7 |
- |
1.6 |
14.4 |
- |
2.1 |
3.9 |
- |
0.2 |
- |
- |
33 |
PM 2004 With
+30% |
Yes |
56.0 |
Delay |
29.3 |
7.1 |
27.5 |
27.8 |
14.1 |
15.6 |
22.7 |
29.8 |
27.2 |
19.2 |
19.2 |
22.2 |
95-Queue |
31.1 |
1.5 |
- |
3.4 |
26.3 |
- |
4.3 |
8.0 |
- |
0.3 |
- |
- |
Queue |
18.1 |
0.7 |
- |
1.6 |
15.0 |
- |
2.1 |
4.0 |
- |
0.2 |
- |
- |
to Discussion |
Page Break
Problem 3: Shenendehowa Campus
Discussion
So what have we learned?
We’ve seen that you have to be careful in using the peak hour factor.
It’s good to incorporate a peak hour factor, so that the conditions in
the peak 15 minutes are examined. But unless you know the flows all peak
simultaneously, it’s not good to use peak hour factor values that are
movement specific. You’re better off using the value that pertains to
the intersection as a whole during the peak hour. Even that value can lead
to delay estimates that are higher than any real values obtained
during the actual 15-minute intervals. The reason is that the
overall peak hour factor, applied to all of the flows, still assumes
implicitly that all of the movements peak simultaneously and
proportionally as well. Sometimes, as is the case here, that doesn’t
happen. If you find this is a significant issue, you might want to do
analyses for each 15-minute period individually.
We’ve also seen that
it is important to pay attention to the heavy vehicle percentages. This
may be of particular importance in a situation like this, where the Shenendehowa intersection
serves a lot of school buses. We might not initially realize the
importance of accounting for their presence in the traffic stream, but
doing so
changes the delays considerably.
Lastly, we’ve seen
that there are ways to check for impacts from site-generated traffic. We
were relatively formal about that, doing the performance assessment with
and without the site-generated traffic, looking at the resulting changes
in delay, and deciding that the impact was insignificant. Sometimes, for expedience, analysts make
a decision based on the percentage increase in intersecting traffic that
results from the site-generated traffic.
Discussion:
Do
you routinely perform sensitivity analyses on the volumes? Planners often use high, low, and base case predictions of
population and traffic growth to bracket possible future conditions. Do you
ever do operational analyses for such conditions or design for such
conditions and consider the incremental impacts?
to Problem 4 |
|