Case Study 1: Overview, Introduction, and Getting Started

Home > Overview

Overview

 

[ Back ] [ Continue ] with Sub-problem

 

Page Break
[../introduction/introduction.htm]

 

Page Break
[../introduction/introduction2.htm]
Page Break

Home > Getting Started > Page 1 of 5

Getting Started

Printable Version Printable Overview, Introduction, and Getting Started

As we begin this case study, we will consider several issues, including the scope of the analysis that we will undertake, the stakeholders and the issues that are important to them, the goal of the case study, the performance measures that we will use to support this decision-making process, the analyses that we will perform to generate our performance measures, the tools that we will use, the data that is required, and some of the technical issues with respect to the Highway Capacity Manual that are included in each problem. Click here to see what kinds of problems will be considered as part of this case study.

Scope of the Analysis
Our major focus is the intersection of U.S. 95 with Styner Avenue and Lauder Avenue. But we will see as our discussion proceeds that it is important to consider not just this intersection but some of the surrounding highway system as well. For now, we'll define the segment of most interest to us as the U.S. 95 corridor from State Highway 8 on the north to Palouse River Drive on the south.

We will also consider travel patterns that normally occur during a typical weekday, while the University of Idaho is in session. Traffic volumes vary throughout this typical weekday, with peak periods occurring during the morning and afternoon, with a secondary peak during the midday. There are also mini-peak periods during class change times, but these variations are not significant enough to consider for our analysis here. We'll see later in the analysis, however, that there are other time periods, such as during special university events, that traffic volumes increase significantly and have a bearing on the results that we need to consider.

While many people are concerned about the operation of the intersection today, it is also important to consider how the intersection is likely to operate in the future. The investment in signal controllers and related equipment is sizable, and its feasibility must be justified by looking at both conditions present today and those likely to exist in the future. For this reason, we will also consider future traffic volume projections for the U.S. 95 corridor.

[ Back ] [ Continue ] with Getting Started

Page Break
Home > Getting Started > Page 2 of 5

Getting Started

Stakeholders
The Idaho Transportation Department has primary authority for the operation of U.S. 95. It does all of the planning, design, and maintenance of this highway. However, it works closely with the staff from the City of Moscow so that, as much as possible, decisions regarding the state highway facilities within city limits are made jointly between the city and the state. As we develop the results from our analyses, the major audience, then, will be the engineering staffs from these two agencies. 

In addition, residents of the city will need to understand the rationale for any final decision that is made regarding the intersection and whether a signal should be installed or not. This points up an important issue in any technical analysis. While any analysis must be technically sound and based on standard methods of professional practice, it must also be presented in such a way that it is understandable by decision makers and elected officials (who often do not have technical backgrounds) as well as the general public. This is particularly important as we consider such concepts as level of service, and as we talk about sensitivity analysis and the relative certainty that we have in our final results.

Goals
The major reason for conducting the analyses that makes up this case study is to provide decision makers with sufficient information about the performance of the intersection of U.S. 95/Styner Avenue/Lauder Avenue so that they can decide whether the intersection should be signalized or whether it should remain stop-sign controlled. The Highway Capacity Manual provides estimates of delay, volume/capacity ratio, queue length, and other data that are helpful to decision-makers in making this kind of decision.

We should also point out that the Manual on Uniform Traffic Control Devices (MUTCD) is commonly used to determine if a signal is warranted and in most jurisdictions is the legal document used to determine many of the characteristics of a design. However, it is also useful to compare the forecasted operations of an intersection under different control scenarios. The Highway Capacity Manual provides the tools for such an operational analysis.

[ Back ] with Getting Started

 
Page Break

Home > Getting Started > Page 3 of 5

Getting Started

Performance Measures
The Highway Capacity Manual provides several performance measures for intersections, both signalized and unsignalized. For both of these types of intersections, the primary measure of effectiveness is control delay. Control delay is directly related to level of service, a range of levels that categorize performance from the point of view of the driver, or the user of the highway system. Level of service (along with delay) will be used here to help us determine if the intersection of U.S. 95/Styner Avenue/Lauder Avenue should be changed from stop sign control to signal control.

We will also need to consider other performance measures besides just level of service in order to fully judge the overall performance characteristics of the intersection. Depending on the type of control at the intersection, these may include the volume/capacity ratio of the critical movements at the intersection, the traffic signal cycle length, and/or queue length considerations.

Analyses
We must complete several computations in order to gather the required information on the performance of the U.S. 95/Styner-Lauder Avenue under both stop sign and signal control. For convenience, we've divided the analyses into six parts or problems. We will consider each problem separately. We will also see that each problem consists of several separate computations, using the Highway Capacity Manual or other tools, such as TRANSYT 7F or CORSIM.

In Problem 1, we will study the intersection under both stop sign and signal control under both present and future traffic conditions, for the typical weekday found in Moscow, Idaho.

In Problem 2, we will consider these same conditions, but within the context of the U.S. 95 arterial as a whole. Here, we will particularly focus on the effect that the adjacent intersections have on the U.S. 95/Styner-Lauder Avenue intersection, and how a new signal at this intersection must operate in conjunction with the adjacent signalized intersections.

In Problem 3, we will consider other time periods, including traffic volumes during special events at the University of Idaho and during different times of the year, when the mix of vehicles in the traffic stream changes.

In Problem 4, we will consider how we can forecast the performance of the U.S. 95/Styner-Lauder Avenue intersection when an actuated traffic controller is used.

In Problem 5, we will consider the operation of the highway outside the city limits, where it is operating as a two-lane highway.

In Problem 6, we will consider the less detailed planning analysis and what information it can tell us about future operations of the intersection and the corridor.

with Getting Started

Page Break
Home > Getting Started > Page 4 of 5

Getting Started

Tools
Most of the computations that we conduct in this case study will be with the Highway Capacity Manual, particularly those chapters that deal with intersection and arterial operations. This includes Chapter 15 (Urban Streets), Chapter 16 (Signalized Intersections), and Chapter 17 (Unsignalized Intersections).

For some parts of the analyses, however, and for certain traffic conditions, we will consider the use of other tools. There are a variety of software tools available that we could use, and for illustrative purposes we will demonstrate the use of only two, TRANSYT 7F and CORSIM. TRANSYT 7F is a macroscopic flow model that consider the progression of traffic platoons from one intersection to the next. CORSIM is a microscopic traffic model that considers the movement of individual vehicles along an arterial and the details of actuated traffic controller operations. Other software packages could also be applied with equal effectiveness.

Data
Three kinds of data are generally needed for traffic analysis. Demand or volume information specifies the turning movement flows (usually in vehicles per hour) at each intersection approach. Intersection geometry includes the number and configuration of lanes at an intersection and along an arterial. Control conditions include information about the traffic signal system, including signal timing and phasing data.

The data for each problem can be found at the links provided below. These links are also provided in each of the problems, as you need to access them.

U.S. 95/Styner Avenue/Lauder Avenue
U.S. 95/Styner Avenue/Lauder Avenue, during special university events
U.S. 95/Styner Avenue/Lauder Avenue, during summer periods
U.S. 95/Sweet Avenue
U.S. 95/Palouse River Drive
U.S. 95/State Highway 8

U.S. 95 arterial data

with Getting Started

Page Break

Home > Getting Started > Page 5 of 5

Getting Started

Technical Issues
The computational procedures of the Highway Capacity Manual are complex, often including a number of default values or assumptions that need to be understood (and sometimes modified) if the procedures are to be applied correctly to specific problems.

This case study presents, and hopefully clarifies, a number of technical issues that often arise in the application of chapters 15, 16, and 17 of the HCM.  A searchable index of the issues and important key words addressed in this and other case studies within the HCMAG is provided near the bottom of the table of contents located in the left margin of this page and labeled as "Search".

[ Continue ] to Problem 1