Kent Hohlfeld//October 24, 2017//

Drivers in cities who encounter a new sign prohibiting a left turn or a roundabout or a motor vehicle diverter might be able to blame navigation apps for that obstacle.
While apps like Waze and Google can save drivers time and aggravation, they can also cause headaches for the people in charge of designing cities’ transportation infrastructure.
“Essentially you have different goals,” said Eric Shimizu, principal engineer and regional director for smart cities and connected vehicles at DKS Associates. App developers “are into computer analyses and how to help people with flexibility and making choices. We have to worry about designing safe transport.”
Engineers responsible for ensuring safe and efficient travel on city streets are adopting a variety of strategies to accomplish their goals. They can’t tell apps where to direct drivers, but they can influence traffic enough to make their desired outcomes favorable to the apps.
When an app tells a driver to travel on a residential street, it is simply relying on an algorithm that determines the most efficient route. A traffic engineer has to also take into account the likelihood, especially on smaller streets, that a cut-through driver will exceed the posted speed limit and consequently increase the chances of a fatal accident.
The chances of a pedestrian fatality in a collision with a vehicle nearly double as the vehicle’s speed increases above 25 mph, according to study results from the AAA Foundation for Traffic Safety.
“Typically, when we look at projects, the big arterials are where we want the traffic to go,” said Hermanus Steyn, senior principal engineer at Kittelson & Associates. “What is happening is (the apps) look at the whole network. We want people to travel Barbur (Boulevard). With the apps, they are trying to find the quickest routes between points A and B. The big models we use don’t include the smaller routes.”
The end result is that apps often send large numbers of motor vehicles to streets that weren’t designed to handle such volume.
Engineers are beginning to take this into account. During a recent traffic mitigation project in Clyde Hill, Washington, Shimizu said, consideration of how apps would react to changes in the streetscape became a major part of the project.
DKS’ studies found that nearly half of drivers in the Seattle suburb used navigational apps. Due to congestion on State Route 520, apps sent a lot of drivers to smaller neighborhood streets. This was despite the presence of an available arterial, Bellevue Way.
“Bellevue Way was underutilized for how big the road is,” Shimizu said. “It could handle the increased capacity, but the apps were telling drivers that the cut through is saving time.”
Engineers’ solution hinged on increasing the drive time along cut-through routes during rush hour. Their traffic studies revealed that when drive times through the most popular cut-through routes increased by two to three minutes, the apps would send drivers back to the arterial roads that were designed to handle the volume.
“We calculated times over the course of nine months,” Shimizu said. “When we were doing this study, (drivers) would save three minutes, which is significant on a short trip of about 20 to 25 minutes. The apps are pretty good in saving time.”
Engineers adopted a multiphase strategy to influence behaviors of both navigational apps and drivers. First, they made a major effort to inform regular drivers of the speed limits on the smaller roads.
“They started slowing down,” Shimizu said. “We had a good timing benefit. The apps take the actual driver information it is collecting. It knows what velocity drivers are traveling at. That information and that calculation formulates the path routing.”
The next step included a combination of strategies. They added no-left-turn signs on numerous streets to force drivers to travel past signals and then come back to make a right-hand turn. They also added permanent roundabouts on numerous east-west streets to slow drivers even more.
Lastly, they tweaked traffic lights that grant access to State Route 520.
“They adjusted the meter rate just slightly, which added the minute and pushed us over the two- to three-minute goal,” Shimizu said.
Engineers largely got what they wanted. As traffic slowed on the smaller surface streets, the apps began routing drivers back onto the larger roads.
“All the sudden we saw a big shift to go to Bellevue Way,” Shimizu said. “It has lanes and plenty of space. We saw with the apps that eight to nine out of 10 drivers avoided the cut through.”
Traffic engineers in Portland are using similar techniques, although few go to the extent that designers did in the Seattle-metro area.
“Portland is one of the test cities to reduce speeds to 20 mph from 25 mph,” Steyn said. “Basically the idea is to target speed if you can’t control the algorithm.”
The new speeds will roll out next year, Portland Bureau of Transportation Public Information Officer Dylan Rivera said. PBOT officials hope the traffic apps will consider a 20 mph street less attractive.
“We think Waze would consider those residential streets with a 20 mph speed limit as less favorable alternatives to busy streets that are marked 30 mph, for example,” he said. “Today they might see a residential street with a 25 mph speed limit as a viable alternative to a busy street.”

Planners also must deal with unintended consequences. An effort to limit cars on one street to promote bicycle and pedestrian use can send a stream of vehicles down another parallel street that can’t handle the volume.
When city planners aimed to increase bicyclists’ use of Southeast Ankeny Street, they faced a big challenge: it runs parallel to Southeast Burnside Street. When Burnside is crowded during rush hour, drivers flood onto Ankeny. Although no study was performed to identify how many drivers were rerouted there by apps, engineers knew they had to direct them elsewhere.
“Our policy is Ankeny is a greenway and to prioritize it for bike use,” Rivera said. “We have put in diverters that force traffic off Ankeny.”
The diverters (physical, man-made barriers) allowed bicyclists to roll though, but not drivers. Early studies showed a 20 percent reduction in the traffic on Southeast Ankeny; it wasn’t 100 percent because some apps won’t show diverters and direct drivers onto streets blocked to vehicular traffic in reality, but appear clear in cyberspace.
Another issue is that drivers often trust their technology more than their own eyes. When the no-left-turn signs were posted in Clyde Hill, drivers frequently would turn left anyway because their apps said they could.
“The cops would sit there and were pointing at them to don’t (turn),” Shimizu said. “The driver would look at the app and make the turn anyway.”
While navigation apps can hurt an engineer’s best-laid traffic plans, they can also provide useful information.
“Overall, they have been more a benefit than detriment,” Shimizu said. “Google alone has helped do field reconnaissance. Initially, you get a feel of what is out there. We love the added information.”
Meanwhile, PBOT officials are engaged in ongoing conversations with Waze developers.
“We are trying to figure out how to get their app to show school zones,” Rivera said.