U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000


Skip to content
Facebook iconYouTube iconTwitter iconFlickr iconLinkedInInstagram

Federal Highway Administration Research and Technology
Coordinating, Developing, and Delivering Highway Transportation Innovations

 
REPORT
This report is an archived publication and may contain dated technical, contact, and link information
Back to Publication List        
Publication Number:  FHWA-HRT-14-069    Date:  October 2014
Publication Number: FHWA-HRT-14-069
Date: October 2014

 

Collecting and Analyzing Stakeholder Feedback for Signing At Complex Interchanges

CHAPTER 3. RESULTS

This section describes the results of the stakeholder activities, and it is divided into three parts. The first part addresses stakeholder experiences with complex interchanges. This includes common characteristics of complex interchanges, which leads to a high-level definition of what stakeholders think constitutes a complex interchange. Also covered in this part is how often stakeholders work on complex interchange projects and the specific human factors challenges that stakeholders encounter at complex interchanges. The second part of the Results section addresses issues that stakeholders consider when they are designing for drivers. Specifically, what assumptions they make about drivers, how they identify problems at complex interchanges, and what design resources or guidance documents that they use regularly. The last part of the Results section summarizes the key research needs related to complex interchanges that were identified by stakeholders in the interviews and survey. This section concludes with a final prioritized list of research needs that was obtained in the survey.

Although the information in this section comes from the interview and follow-up survey, the organization of the sub-sections does not strictly follow the order of the interview questions (see appendix C). The reason for this is that many of the same ideas were reported in different questions, so we extracted the common themes across sections and used them to organize the report sections. Note also that for most questions there is no information provided about how frequently topics were mentioned across stakeholders. Although some topics were mentioned repeatedly, our focus in this report is to capture breadth of topics discussed, since the number of stakeholders interviewed is too small to support quantitative analyses.

One caveat that is important to convey at the outset of the Results section is that the findings presented in this report are based on stakeholder comments only, and not separate analyses or existing research. At multiple points in the discussion of the results, the comments about State-level practices sometimes differ from the current MUTCD recommendations or common practices. This likely reflects several factors, including shortcomings in the awareness/communication of recent guidance and supporting research, the casual nature of the interviews and the fact that stakeholders were not asked to prepare in advance, and that some stakeholders held administrative positions removed from the engineers doing the day-to-day implementation. Nevertheless, the project objective is to present stakeholder views on complex interchange topics, so the findings reported describe their knowledge, opinions, and experiences. Contradictions with the MUTCD or other guidance materials are left as-is. Thus, the findings should not be interpreted as suggesting that the MUTCD or common design practices are flawed or lacking.

STAKEHOLDER EXPERIENCES WITH COMPLEX INTERCHANGES

This section focused on discussing general characteristics of complex interchanges, the pervasiveness of these interchanges, and stakeholders' perspective on complex interchanges as an issue. Questions 6 through 9 of the interview asked stakeholders for this information.

Characteristics of Complex Interchanges

This section of the interview focused on obtaining information about stakeholders' previous experiences in which they were involved in identifying, resolving, or attempting to resolve issues with complex interchanges. Specifically, stakeholders were asked to identify and discuss an example of an interchange that they previously had to deal with that had specific problems involving human factors issues (question 6). Follow-up questions addressed how they determined what the problems were, and various aspects of their efforts to address those problems.

Stakeholders did not have a common definition of what a complex interchange was, and it was more common for them to base their assessment of whether an interchange was complex on specific elements that caused problems for drivers. A list of the characteristics associated with the examples of complex interchanges discussed by the stakeholders is provided in table 3. Additional discussion about these specific driver problems is provided later in this Results section. A trend that emerges from the characteristics listed in table 3 is that complex interchanges often involve multiple routes that converge or diverge within a short distance, resulting in geometric or signing elements that ultimately cause higher workload for drivers in addition to a scenario that departs from drivers' mental models and other expectations.

Table 3 . Characteristics of complex interchanges from the stakeholder examples.

Characteristics of Complex Interchanges

Mentions
by Stakeholders

System interchanges

6

Multiple/successive option lanes, splits, or exits

5

Short weaving sections

4

Collector-distributor roadways

4

On-ramps and off-ramps for high-occupancy vehicles (HOVs) and managing/signing access

3

Providing a lot of information to drivers

1

Unfamiliar sign/marking elements

1

Lack of lane balance leading to forced merges

1

Unexpected maneuvers/violations of driver expectations

1

Horizontal/vertical alignment of interchange

1

How Often Stakeholders Work on Complex Interchange Projects

Based on their definition of complex interchanges, stakeholders were also asked how often they work on projects related to complex interchanges and how many complex interchanges there are under their jurisdiction. There was a wide range of responses to both of these questions and stakeholders generally found them difficult to answer because they often lacked a clear definition of what interchanges qualify as complex interchanges.

Figure 3 shows how frequently stakeholders were involved in projects that addressed complex interchanges. Note that text descriptors accompany the numeric ranges for each category. This is because not all answers to this question could be unambiguously linked to a specific numeric estimate, and some participants did not have a precise answer. Nevertheless, the overall trend is still informative. Based on the responses to this question, approximately two-thirds of stakeholders work on projects related to complex interchanges at least once a year.

This histogram shows the number of projects related to complex interchanges per year. The x-axis is the frequency (in years), and the y-axis is the number of responses. The histogram shows that 3 respondents dealt with these projects very frequently (12+ projects/year), 4 respondents dealt with these projects frequently (3-11/year), 3 respondents dealt with these projects occasionally (1-2/year), 2 respondents dealt with these projects rarely (every 1-2 years), 2 respondents dealt with these projects very rarely (every 3-5 years), and 1 respondent never dealt with these projects.
Figure 3 . Histogram. Frequency of projects related to complex interchanges per year.

Figure 4 shows the number of complex interchanges in the stakeholders' areas (the same caveat about the numeric range described for figure 3 also applies to this figure). The wide range of responses is most likely due to the fact that some stakeholders interviewed work at the State level and were replying with the number of complex interchanges in the whole State compared to other stakeholders who work at a district level, and were replying with the number of complex interchanges in their district. Most stakeholders said there were several or many complex interchanges in their area.

This chart shows the number of complex interchanges in stakeholders' areas. The x-axis is labeled as the number of interchanges, and the y-axis is labeled as the number of responses. The chart shows that 1 respondent had few (1-5) complex interchanges in their area, 2 respondents had some (6-10) complex interchanges in their area, 4 respondents had several (11¬-24) complex interchanges in their area, and 4 respondents had many (25-50) complex interchanges in their area.
Figure 4 . Chart. Number of complex interchanges in stakeholders' areas.

Specific Human Factors Challenges that Stakeholders Encounter at Complex Interchanges

Overall, stakeholders identified a range of human factors challenges that they encounter at complex interchanges. Most of these involved design and implementation issues, but some involved the planning and construction phases. Stakeholders were also asked to discuss previous instances where they had to improve or address a problem at a complex interchange. In the past-project examples, some stakeholders were also able to describe solutions that they developed for specific problems. A list of the most commonly mentioned issues is provided below. The first four topics were cited most frequently, and they are discussed in more detail below the list. Some topic discussions also include information about solutions or alternatives that were implemented, as follows:

Close Spacing of Interchanges, Routes, or Access Points:

Concerns related to closely spaced interchanges, routes, or access points were a common problem that stakeholders discussed. These roadway sections were associated with a variety of challenges for drivers (e.g., hurried maneuvers, information overload, etc.), and engineers (e.g., providing sufficient sight distance for signing, deciding what information to provide, etc.). The fundamental problem is that drivers have to make more decisions in a shorter amount of time under these conditions. Moreover, this is compounded by the fact that engineers are also often more constrained in the amount of information that they can present in that limited space. These circumstances lead to a variety of specific challenges, which are described as follows:

Signing Lane Movements

Problems related to signing permissible lane movements were discussed by several stakeholders, particularly in the context of making decisions about sign design during upgrades to existing interchange signing. In general, stakeholders are looking for effective approaches, but they must also deal with key constraints, such as exit density and implementation costs. Changing a sign design to include the MUTCD up-arrows is perceived as making it easier for drivers to understand the driving movements, but implementation can be prohibitive because of the arrow size requirements and high cost of providing the requisite support structure. Specific problems encountered by stakeholders include the following:

Stakeholders also discussed specific problems related to providing navigation information for single lanes that serve multiple destinations (e.g., option lanes, exits that split), and for unusual interchange configurations that are not expected by drivers. These include the following:

Guide Sign Destination Information

Stakeholders identified problems with the selection of which major destination information to include on signs. This issue can lead to guide signs that are inconsistent with driver navigation expectations, or that are more difficult to comprehend because of the additional information elements. Some of the specific problems that stakeholders reported on this issue include the following:

Driver Task Overload

Stakeholders reported issues with driver task overload. Driver task overload can be the result of short weaving distances, many lane changes, or the lack of advance guide signs. This overload can cause drivers to miss a sign due to its location or to not understand which way to go in order to get to their destination. Some of the specific examples stakeholders provided about this issue include the following:

DESIGNING FOR DRIVERS

Stakeholders were asked how they design for drivers and how they incorporate driver needs into their design processes. This included discussion about the design resources that are commonly used and stakeholders' approaches to solving design problems that are not covered in those design resources.

Assumptions that Stakeholders Make about Drivers

In this section of the interview, we asked whether stakeholders make any assumptions about what drivers need or what drivers know when they are designing a new or retrofit interchange (question 10).

Driver Characteristics

Assumptions that stakeholders reported they made about driver characteristics were as follows:

Driver Abilities

Assumptions that stakeholders reported they made about driver abilities were as follows:

Driver Needs

Assumptions that stakeholders reported they made about driver needs were as follows:

How Stakeholders Identify Problems at Complex Interchanges

As a follow-up to the discussion of issues at interchanges, we asked how stakeholders identify problems involving driver information needs or driver issues at interchanges or other roadway sections (question 11). There are three main categories of ways in which State transportation department representatives identify drivers' issues: crash histories or reports, complaints from the driving public, and observations from trained professionals (e.g., highway patrol, field personnel). These are described in more detail below.

Crash Histories or Reports

Nine stakeholders reported using crash histories, crash trends, or individual crash reports (including the type of crash, location in reference to decision points, verbal information provided to the Highway Patrol) to determine sites where drivers are having issues. One State creates a list called the "Suggested List of Surveillance Study Sites" or the "SLOSS" list every year. This list includes all of the sites where the crash rate is higher than what would normally be expected for that type of roadway. The sites that are high on this list are the first to get fixed. Additionally, if there is an ongoing project, they will check to see if any of the project sites are included on the SLOSS list. If so, they will do a little investigation to see if the crash cause can be easily fixed during the ongoing project.

Complaints from the Driving Public

The most common way that State transportation departments know where there is a problem is when the driving public sends a complaint using email, phone calls, or letters. States generally take complaints very seriously and a State or district representative is certain to follow up with each person. One State described a complaint tracking system that ensures that each complaint is addressed. Another State described how they call each person who complains to find out exactly what that person is talking about. Additionally, they will look on Google Mapsâ„¢ to find the problem, direction of the approach, etc. This information gets passed down to the individual districts, whose personnel will visit the site to make sure that all of the appropriate signing is present and visible.

Observations from Trained Professionals

There are multiple types of trained professionals who make and report traffic observations, including the following:

Design Resources that Stakeholders Use

There are many design fundamentals for signing and markings that are used by stakeholders (question 12). The resources that were mentioned are as follows:

To follow up, we asked how transportation department personnel design signing or markings for unique interchanges where there may not be any guidance in the MUTCD or other sources (question 13). The following approaches were mentioned, often in combination with one another:

One stakeholder added that they would let their FHWA contacts know that guidance is missing and needs to be created for this design situation, to ensure consistency between States.

RESEARCH NEEDS FOR COMPLEX INTERCHANGES

At the end of the interviews (question 14), we asked stakeholders specifically if they had any ideas about research needs that would help them resolve interchange design issues. Below is a description of the most commonly mentioned research needs that were discussed during that portion of the interview. The research needs mentioned by stakeholders fit into several themes, including: signing, roadway geometry, and general design challenges. The "corresponding research summary" sections within each description more succinctly summarize what a research project in that area might examine. These research summary sections are also the exact text that the stakeholders used to assign priority ratings during the follow-up survey.

Signing

Guide sign spacing requirements. The research basis for the 800-ft required spacing between guide signs in interchanges is unknown to some stakeholders. That standard is difficult to maintain for closely spaced exit ramps or interchanges, particularly in urban areas. Additionally, there is a limit in the MUTCD for the amount of information that can be placed on each guide sign. This limit can feel like it compounds the challenge, since engineers are limited on the number of signs per mile and the amount of information that can be presented on each of those signs. This is the topic of a current research study being conducted by FHWA.

Corresponding research summary. This research would examine whether the 800-ft guide sign spacing requirement is necessary in urban environments, where interchanges are closely spaced and there are many destinations to list. More specifically, if the 800-ft distance is not met, what are the impacts on drivers in terms of information acquisition success, sign reading time, and traffic flow? Since this research is already being performed, this topic is not a priority for new research; however, it is important to follow-up and convey the findings to stakeholders.

Information limit per guide sign. There was an opinion expressed by multiple stakeholders that the MUTCD's limit on the amount of information that can be put on a single guide sign is unrealistic. In some situations, there is a minimum amount of information that needs to be presented to guide drivers to make the appropriate movements, to ensure safe operation of the roadway, and to direct traffic. One stakeholder acknowledged that while it can be a lot of information on a single display, from a driver's perspective they do not have to read and digest all of that information; they focus on what they are looking for. Also, if that information limit was strictly followed, some sign information would be left out and people would complain. In previous focus groups addressing complex interchanges, some drivers agreed that they could scan the signs and ignore irrelevant information; however, many others noted that including too much information on a single sign structure causes problems.(2)

Another State had a local university perform some research that examined the maximum number of items of information that could be presented on a guide sign. Guidance was given for situations where there were one, two, or three signs on a single support structure.

Corresponding research summary. This research would examine the limit on units of information for guide signs, particularly in urban areas where there are many destinations to sign for and limited space to hang signs. What are the human factors impacts of including additional guidance information on guide signs in dense areas? Although there is a lot of existing research on this topic in both driving and comparable domains, some stakeholders find the current limit to be unreasonably low. They would like either a clear justification for the limit, or some sort of analysis of the trade-offs of providing more information beyond that limit.

Sign placement in interchanges. One stakeholder mentioned a case regarding an issue with sign placement. He noted that drivers were missing a critical guide sign because it was placed in a location where they were merging from an on-ramp onto the mainline. His solution utilized pavement markings in that location to denote the lane for the primary destination, which was an airport. However, if the situation could be avoided altogether, that would be better. Something like merging onto the highway and then immediately merging or negotiating a merge-weave should be avoided, but sometimes it is challenging to avoid this situation altogether.

It would also be useful to compare exit approaches at interchanges with and without some of the design features like pavement markings, option lane signing, etc., particularly in situations where drivers need to view all of the signs to reach their destination. This stakeholder believes that it would be helpful to have supplemental pavement markings in those areas; however, this would be a good area to study.

Corresponding research summary. This research would gather and present the human factors considerations for implementing pavement markings containing guidance information within complex interchanges. It would examine the driver interpretation of pavement markings and the best placement choices for those markings within different interchange scenarios.

APL sign requirements. At multiple times during different sections of the interview, stakeholders discussed the MUTCD requirement to use APL signing. The new requirement for APL signing is extremely difficult to accommodate because the arrows themselves can be 6 ft high. This sign height requires that a large and costly support structure be installed to mount the signs. This is sometimes cost-prohibitive for States. They are attempting to follow the MUTCD guidance, but often the cost of the sign support limits their ability to do so.

Figure 5 shows an alternate design where the destination names were placed beside the arrows instead of above the arrows, reducing the required sign height.

This photo shows vehicles on a highway. The highway has one direction sign where the destination name is placed above the arrow, and two direction signs where the destination names are placed beside the arrows.
Original image: ©2013 Google®
Figure 5 . Photo. Example of alternate APL destination name layout.(4)

Another solution proposed was truncating the upward-pointing arrows, as shown in figure 6.

This photo shows vehicles on a highway. The highway has four direction signs. One sign has no direction arrow, but the other three signs do have direction arrows. On the signs that have upward-facing arrows, the length of the arrows is truncated, reducing the height of the sign.
Source: Missouri Department of Transportation
Figure 6. Photo. Truncated up-arrows on APL guide sign.

It would be helpful for States to have an alternate design option for APL signs, in order to have shorter signs that still provide adequate guidance to drivers. A published laboratory study compares driver comprehension of various signing options, including what is currently recommended by the MUTCD.(3)

Corresponding research summary. This research would examine alternate methods for signing APL configurations that would reduce overall sign size requirements, while still communicating the necessary information to drivers. This research would examine sign height reductions and also sign width reductions, such as whether it is beneficial to sign all of the through lanes for the width of the roadway, or whether that space on the sign support could be used to provide other guidance information for upcoming decision points.

Roadway Geometry

Option lanes or shared lanes. In general, it is easier to communicate that a lane serves a single destination rather than multiple destinations. There is a wide range of sign designs, and in particular arrow types, that are used for signing option lanes (e.g., one arrow, two arrows, up-arrows, down-arrows, slanted arrows). Stakeholders expressed some uncertainty regarding what is the best signing method and if the current MUTCD language reflects the results of research and current studies of driver perception. Engineers want to know how drivers understand the signs and what they can do to help drivers understand that the lane is an option lane. Although there is existing research on this topic, and stakeholders are generally aware of the current guidance and research findings, they did not seem confident in applying this knowledge. The benefits of undertaking the effort to comply with the current guidance are unknown.

Additionally, sometimes lanes are used as option lanes in order to satisfy AASHTO's recommendations for lane balance. Although that may help to balance the traffic flow, the signing becomes more complicated as a result. The stakeholder who discussed this issue noted that he thought that the lane balance guidance from AASHTO should be applied on a case-by-case basis.

Note that the option lanes or shared lanes research need does not have a corresponding research summary section because it was not included in the follow-up survey.

Two-lane flyover ramps. When constructing two-lane flyover ramps, some States are encountering problems with horizontal and vertical alignment. With the concrete barriers that are on the ramp, the construction does not meet the AASHTO horizontal sight distance requirement. As the drivers go around the curve, they cannot see far enough ahead due to the height of the barrier. In order to meet the criteria, the barriers need to be very tall and that is not cost effective or feasible. The solution that has been used, for example for a left-turning curve, is to move the right shoulder to the left side to improve sight lines as drivers are going around the curve. This is a design exception, but it could benefit from more research to see if it is acceptable.

Corresponding research summary. This research would examine vertical and horizontal sight distance requirements for two-lane flyover ramps. Specifically, what are cost-effective and physically feasible ways to meet these requirements, or can these requirements be reasonably violated in some scenarios?

General Design Challenges

Algorithm for justifying the cost of roadway construction projects to drivers. One stakeholder described in detail the calculations that are often undertaken to justify the cost of roadway improvement projects to the general public. In order to justify the cost, they perform calculations to figure out the savings afforded by the completion of the project. Savings based on crash reductions are easier to calculate than savings based on delay reductions, because the data on the cost of fatalities and injuries is widely published. To calculate the savings based on the delay reduction, values for things like the value of gasoline saved, driver time saved, and emission reductions are necessary. Placing a numeric value on driver time and vehicle emissions is difficult, since there is no standard source for these values.

Corresponding research summary. This research would create an algorithm that could be used to justify the cost of roadway construction projects to the public. The algorithm would include standard metrics to quantify and calculate the project's benefits, such as driver time saved, pollution reductions, etc. This research would relate to the MAP-21 Act, with an emphasis on performance-based decisions and management.

Develop additional design examples. One stakeholder noted that he would like to have additional examples available to him regarding how to design or fix a particular interchange scenario. He suggested that a batch of Subject Matter Experts evaluate challenged interchanges around the country to determine how they were designed, how they could have been designed, and how they could be improved. If those proven or suggested design solutions could be made sufficiently generic, then engineers in other States could apply them to their interchanges.

If this research resulted in a reference document, then instead of only having a small number of examples in the MUTCD, engineers would be able to see a much larger number of examples, one of which may be a better match to the situation that they are facing. If the examples were all vetted by a panel, then State engineers wouldn't need to submit an example to FHWA and wait for a response. These examples could include signing, marking, and geometric solutions, or a subset thereof.

It would also be preferable if this document also contained more written descriptions of the decision criteria. For example, if a decision had to be made between two sign types, which one should be chosen, and why? The current MUTCD often gives multiple options that are satisfactory, without guidance about which option to select. It would be beneficial to have additional guidance explaining why a particular sign type is preferred.

Another stakeholder described a similar need for additional research that would help them know what the outcome would be for designs that do not conform to the MUTCD. For example, some interchanges cannot be designed or altered to look like an MUTCD solution. If that is the case, how will that interchange function? Engineering confidence could be improved in terms of what the outcome would be for a non-standard interchange design.

Corresponding research summary. This research project would find examples of uncommon complex interchange design challenges across the country. Solutions to signing, marking, and geometric problems would be developed by a panel of experts, and the corresponding example solutions shared in a compendium with the engineering community. An additional tool for explaining the solutions could be simulations or visualizations of their design and function.

ADDITIONAL RESEARCH TOPICS

A follow-up survey was conducted to help prioritize a subset of the key research ideas identified in the interviews. The main component of the follow-up activity asked the participants to assign the priority of conducting research on each of 12 research ideas (survey questions 5-16). They were also provided with space to give comments on each research topic. Note that the order of the research topics was randomized between participants to ensure that the presentation order did not affect the results. The list of research needs in the previous section provided the basis for many of the topics that were included in the survey. The others were based on the results of other portions of the interview and are as follows:

PRIORITIZING RESEARCH NEEDS

Table 4 shows the results of the rating of research ideas performed in the follow-up survey. The research topic rows are sorted by ascending rank. As mentioned previously, in order to account for the differing number of participants per region, an average was calculated for each region before averaging by topic across all of the regions. This was done to give all regions equal weighting, regardless of the number of participants from that region. The "Average" column in table 4 was calculated in this way. The "1 or 2 Rank" column shows the absolute number of times that an individual participant rated this research topic as "high priority" or "medium-high priority." The "State Rank" column reflects the order of research topics, as determined by the average rating across States.

Table 4 . State/region rating results for complex interchange research ideas.

Research Topic

State Rank

Average*

1 or 2 Rank

APL sign requirements

1

2.18

39

Guide sign spacing requirements

2

2.18

35

Information limit per guide sign

3

2.32

35

Pavement markings

4

2.44

33

Develop additional design examples

5

2.50

28

Signing for exit-lane splits

6

2.60

26

Diverging diamond interchanges

7

2.69

30

Signing for collector-distributor roadways

8

2.78

23

Organization and number of route shields

9

3.31

15

Algorithm for justifying the cost of roadway construction projects to drivers

10

3.34

18

Control cities on guide signs

11

3.54

13

Two-lane flyover ramps

12

3.75

12

*Rating values used in the calculations correspond to the ratings from "High priority" (1) to "Low priority" (5).

 

Federal Highway Administration | 1200 New Jersey Avenue, SE | Washington, DC 20590 | 202-366-4000
Turner-Fairbank Highway Research Center | 6300 Georgetown Pike | McLean, VA | 22101