Search
Close this search box.

non-motorized

Important Information

This article summarizes an inspiring talk given by our traffic engineer, Ariana Jeske, PE, at the 2013 Institute of Transportation Engineers conference.

Preventative traffic engineering refers to an approach to traffic engineering and planning that prevents, rather than reacts to, dangerous situations and accidents.  The key is keeping walkability in mind. The term “walkability” has surfaced recently due to increased concern over accessibility, and because walkability can increase public health, decrease vehicle traffic, and drive economic development.

Traffic engineers use complex models to justify the traffic infrastructure that guides our behavior. The “stereotypical” traffic engineer tends to focus on:

  • Antiquated suburban development patterns (built for cars, not pedestrians)
  • Inflexible road design standards
  • An unchanging, unadaptable system

As the model of mobility changes, traffic engineers can lead the way to a safer world, rather than being “in the way.”

“It didn’t meet the warrants.”

Warrant, to a traffic engineer, means justification. To justify a traffic signal installation, a traffic engineer completes a signal warrant study using a set of guidelines outlined in the Michigan Manual of Uniform Traffic Control Devices (MMUTCD)–the manual that forms the legal basis for all the State’s signs, traffic signals, and pavement markings. Conventional warrants tend to treat pedestrians as vehicles. Rarely can traffic signals be justified solely for facilitating pedestrian movements, since signal warrants are not based on the intersection’s performance, but on detailed research from the 1970s.

So what about new projects and approaches? When a non-motorized path needs to cross a busy four-lane road, how will we know how many pedestrians will be crossing it? Pedestrian forecasting is not as developed as vehicular traffic forecasting.  Often, a wait-and-see approach is taken to see if a problem develops. Isn’t there a better way?

Don’t respond, prevent.

Traffic engineers need to enter pedestrians into the equation. Pedestrians need 39% more time to cross a two-lane road than a car does, and pedestrians are ten times more likely to be fatally injured in an intersection crash than a vehicle driver.

Preventative traffic engineering, then, is the meaningful evaluation of a multi-modal mobility network to identify areas of increased risk and mitigating those risks. Traffic engineers need to recognize that pedestrians are legitimate users of public mobility systems – whether or not we design for them – and have an inherent vulnerability.

How to lead the way

  • Every detail matters: Consider curb radii, pedestrian data, road width, signage, cycle lengths, parking zones, pavement markings, lighting, and bicycle facilities.
  • Standards can be flexible: Use context-sensitive design. Make standards fit your projects, not the other way around.
  • Use multiple sources: Use all the books on your shelf, and even look internationally for case studies and examples.
  • Use your engineering judgment: Safety isn’t rocket science. Trust your instincts and prove them right.
  • Be proactive and holistic: Projects should not just be a road widening, or a pavement reconstruction, or any one single facet.  Evaluate safety problems, find the data out there, and integrate walkability and pedestrian safety into the planning of your transportation projects. Especially when you have funding. (In fact, adding a walkability component can sometimes get you more funding.)

Case study

It seems likely that putting a non-motorized trail crossing at a busy four-lane roadway might result in some safety issues. Here is a case study that took a more proactive approach to ensure safety.

Grand Valley Rail Trail: a major community project for Ionia and Saranac, the GVRT is an AASHTO-compliant non-motorized trail that repurposes an abandoned rail bed, including seven trestles over various water bodies.

The trail also crosses M-66 (Dexter Street) in Ionia, which averages about 15,499 vehicles per day.  To determine if the estimated 100,000 yearly users of the trail would have enough time to cross the street, we conducted a pedestrian gap study, which determined how long of a window (16 seconds) a pedestrian would need to cross the street. From traffic data we found that there weren’t enough time gaps during the day for the expected volume of pedestrians to cross M-66 safely.  The study helped secure funding  for a pedestrian bridge across M-66/Dexter Street, which will be built next summer.

Several years ago, I met Fred Meijer at a meeting. Mr. Meijer was well known for his philanthropy, especially in the development of bicycle paths across West Michigan. When he found out that I design these paths, he baitingly asked me, “Why do we need an engineer to design bike paths?” I gave him all of the standard engineer answers about drainage, road right-of-ways, easements, retaining walls, and good construction oversight. He smiled at my answer, having known it ahead of time. But the question stuck with me. Why should someone invest in good engineering design and oversight on a bike path? They’re simple, right?

I will answer the question with an example.

Sometime back a Township client asked this same question, and, despite my good “engineer” answer, decided that rather than accepting my proposal they would just have a local developer build the trail. It seemed like a good idea to them at the time. They saw the initial cost savings of removing the engineering independent design and construction observation from the project budget.

Fast forward five years. the same Township called me to design an extension to their developer-built trail. They also requested that I take a look at the existing trail section, admitting that it needed significant maintenance, and that they wanted my advice on how to fix it. The photos below show what went wrong with the original trail.

  trailcracks1 trailcracks2 trailcracks The old trail is peppered with cracks. Why? Here are my thoughts:

  • Design for each trail is site-specific. There is no “typical cross section” that can be constructed everywhere. Each section of trail has its own unique design and construction challenges that must be carefully reviewed to ensure that the trail lasts as long as possible.
  • Construction oversight is critical. Contractors and developers construct. Engineers design and work to make sure the design is implemented in the field. Some of the most common problems are smooth curve radii, improper slopes, poorly compacted gravel, incorrect asphalt thickness and temperature, and drainage.
  • Asphalt pavement relies heavily on a good base to perform properly. Good pavement design considers the asphalt mix, the gravel quality, gradation and thickness, and the level of compaction beneath it.
  • Drainage is critical–for both surface water crossing the trail and sub-base drainage under the asphalt. If these issues are not properly addressed, the surface will not last.
  • The pavement for this trail was constructed in one layer. This may have seemed like an easy way to cut cost from the project, but we learned long ago that it takes two asphalt layers to build a lasting, low-maintenance trail. Two layers of asphalt provide a significantly smoother and stronger trail with minimal increase in cost.
  • Weeds and roots are growing through the asphalt. Often in situations like this, it helps to place a Bio-Barrier type product below the trail surface to prevent vegetation growth.

  Below is a photo of the new trail section for which Prein&Newhof provided design and construction observation services. It should last for many years before needing anything beyond normal maintenance. paved trail

Over the past few decades and several hundred miles, Prein&Newhof has learned much about good trail design. Good engineering makes a real, tangible and positive difference in the outcome of a trail. It is well worth investing a little more to make sure your community’s trail is done right. The next time someone asks about the value of an engineered design, I’ll have more to say!