Archive | June, 2014

A Primer on Trip Generation

As a key factor in determining rates for Portland’s proposed street utility fee, the Institute of Transportation Engineers’ (ITE, henceforth) Trip Generation Manual has gotten a lot of love lately among local transportation wonks. It is worthwhile, then, to take a quick trip through the weeds of the manual to better understand where the opportunities and complications lie when it comes to using this data as the backbone of our fee structure.

First, a bit of context. The art/science/guesswork of predicting the trip generation of various land uses is the first of four steps undertaken in transportation forecasting. Along with the ensuing three steps—determining where, generally, the trips will originate and end; choosing which mode they will utilize; and identifying the time, route choice, and other properties of the individual trips—the goal is to understand the future needs of the transportation system based on current land use and development patterns. Because most jurisdictions have a concurrency requirement—a stipulation that roads and intersections must have adequate capacity to accommodate new demand concurrent with a proposed development—trip generation is of particular interest to folks in my line of work so that we might identify what developers must do to meet this requirement, blissfully ignoring any notion of induced demand.

To this end, ITE has been aggregating and disseminating trip generation data since the first edition of the manual was published in 1976 (the current edition is the ninth). The context manifests in the data in myriad ways. For any of the 172 land uses listed in the manual, the robustness of the dataset is likely a function of both how often that particular land use arises, and how much NIMBY-ism it’s likely to inspire. The well-known suburban bent of the data owes to the fact that most development over the last 40 years has occurred in the suburbs or exurbs, so this is where the vast majority of studies have been conducted.

The trips described by the manual are one-way trips, so what one might colloquially describe as “a trip to the grocery store” is actually two trips: the trip from home to the store, and the return trip home. This is important for analysis purposes—the “trip to the grocery store” will indeed traverse an intersection along the way twice—but results in quantities that are twice as high as what one might intuit. This means that in a closed system each trip is double counted, as both the home and the grocery store would be credited with generating both an inbound and an outbound trip in this example.

The manual provides two general mechanisms for determining the trip generation of a given land use. The first is a mathematical function derived through what’s called regression analysis, which attempts to fit the cleanest possible curve to a set of disparate data points. The second is the trip rate, often expressed as a number of trips per thousand square feet. But it’s important to recognize that square footage is often not the best (or even a viable) independent variable for predicting trip generation. For example, student enrollment is a much better predictor of trip generation for schools, employee count is a better predictor for offices, and the number of ‘fueling positions’ is a better predictor for gas stations.

Interestingly, there’s another predictor for trips generated by a gas station that works better than floor area: the amount of traffic using the street that it’s located upon. That’s because gas stations generate a large number of pass-by trips, which are trips that are ultimately headed to another destination (this destination is credited with generating the primary trip) but stop at a business located directly along the way. A similar type of trip—a diverted trip—is also a trip ultimately headed elsewhere, but in this case the pit stop entails a small amount of out-of-direction travel. There are also internal capture trips, which describe trips that take place entirely on roads and facilities located within a mixed use development. Note the suburban bias there; in the city, this would likely take the form of a person parking once and visiting several locations on foot, using the public streets.

And here we have arrived at the biggest failing of the Trip Generation Manual with regard to our purposes: The manual implicitly considers only vehicular trips. Assuming that only a nominal number of trips are non-automotive might work for the ‘burbs, but this often causes the stated trip rates to be wildly inaccurate in the city. Recent work by Professor Kelly Clifton’s research group at Portland State University confirms what we might have suspected: The more “urbany” a built environment, the more inaccurate the assumption that all trips are automotive is likely to be.

Thus, there is a need to distinguish between the vehicular trips quantified by the ITE manual and what are generally called person trips, which include all trips regardless of mode. Fortunately, as Clifton verifies, the latter seems to be relatively consistent regardless of the built environment. So perhaps by considering only vehicular trips, but doing so primarily in auto-centric locations, the manual has inadvertently provided a good proxy for estimating the differences in person trips generated from one land use to the next. There are exceptions, of course—the manual will understate the person trips generated by a school compared to other land uses, for example, due to the prevalence of buses in travel to and from schools. But it seems that basing a potential street fee on person trip rates inferred from Trip Generation Manual data is defensible and keeps with the spirit of the residential fee in being mode-independent. Basing the fee on vehicular trips, by contrast, would be far more complicated to implement and would leave unsolved many of the issues with the gas tax that Chris Smith wrote about last week.

The manual offers a lot of utility with regard to predicting trip generation, but really it’s just one piece of a puzzle that fits together differently from one land use to the next, and one business to the next. To accurately model the trip generation of a particular business requires a heck of a lot more than the published trip rate, which does not consider countless predictors and is often derived from a small sample size. While using these rates as the basis of the street fee would hardly be the first or most egregious misuse of the data, it seems inevitable that it will result in some businesses substantially overpaying and others substantially underpaying. As luck would have it, that seems to fit with the spirit of this fee quite well.

Streetcar Loop Milestone

It might be masked a bit by Rose Festival, but Portland Streetcar hit an important milestone today!

The “CL” line (the “loop” to the east side) is now running at the same headways as the “NS” line on the west side (about 4 minute shorter headways at peak service).

The important benefit of matching the headways is that in the shared route portion of both lines (10th and 11th from Market to Lovejoy), we can interleave the vehicles evenly, resulting in effectively doubled frequency for customers on that part of the system (7 minutes at peak).

In a little over a year when we “close the loop”, this double-frequency zone will extend all the way from South Waterfront to the Pearl.

It just keeps getting better! BTW – for the skeptics, ridership on the CL line has approximately doubled since it opened, and overall system ridership is very close the 16,000 riders/day on weekdays.