Back Continue

HCMAG Home
Overview
Introduction
Getting Started
Problem 1
Problem 2
Problem 3
Problem 4
Problem 5
Problem 6
Problem Index
Datasets
Search

Sub-problem 6c - Page 3 of 4

ID# C106C03

Sub-problem 6c: Planning Analysis at Sweet Avenue

For this example, the Northbound left turn is protected, the eastbound left turn is not opposed, and the other two left turns do not exist.

The analysis results are presented in Exhibit 1-53. Note that the minimum cycle length of 60 seconds will accommodate the projected 20-year traffic volumes with no apparent operational problems.

Exhibit 1-53. Quick Estimation Summary: U.S. 95 at Sweet Avenue

Direction East-West North-South
Phase 1 2 3 1 2 3
Movements EBWBTH     NBTHLT NBSBTH  
Critical Volume 416     160 500  
Computed cycle length in the specified range of 60-120 sec 60
Total entering vehicles 1,076
Critical v/c ratio based on the selected cycle length 0.79
Status: "Under Capacity"

Notice also that, even though this is a T-intersection with no westbound approach, the phasing designation for east west traffic is EBWBTH, indicating the presence of westbound vehicles. This is an important principle that describes the way that traffic movements are represented in the Quick Estimation model. The principle is that, for the Quick Estimation method, all movements must exist in the model. Those that don’t exist on the street are simply assigned zero volume and capacity. This is an important distinction between the Quick Estimation method and more detailed traffic models.

As indicated above, the HCM quick estimation method distinguishes between protected and protected-plus-permitted left-turn treatments. It is important to note, however, that the mathematical treatment of the permitted phase differs from the full operational procedure. The full operational procedure computes a capacity for vehicles turning left on the permitted phase, based on advance knowledge of the signal timing plan. The Quick Estimation procedure does not require this information, and cannot, therefore, perform the computations at the same level of detail. This is an essential feature of the tradeoff between the reduced data requirement for planning level applications and the amount of detail that can be expected in the results.

[ Back ] [ Continue ] with Sub-Problem 6c