The Metropolitan Council held a public hearing tonight on their draft Transportation Policy Plan. If you care about transit or transportation issues in the region, you should comment (you can do so through October 1). Here are four comments I have on the plan:
Our urban areas are significantly underserved by this plan. Even under the “increased revenue scenario”, we will spend $5 on transit to serve suburban commuters for every $1 we spend on transit improvements to places where transit makes economic sense (see here for my attempt at a geographic breakdown of projects). The Met Council, in the Thrive 2040 plan, has said they want to match transit service to the number of riders and intensity of land use. This plan does not do that.
The plan currently prioritizes projects like Gateway BRT (9,000 riders at $50,000 per rider) over projects like Hennepin Ave BRT (23,000 riders at $896 per rider). This is an example of how our urban areas (that are expected to grow significantly) are underrepresented in this plan.
It’s definitely not all bad. The Met Council for the first time has identified regional priorities for a bicycle network, which will give communities the ability to apply for funds to upgrade their local network if it matches the regional plan. Many of the transit projects identified are much needed improvements (Hennepin, Chicago, West Broadway), but are simply not adequately prioritized.
I’ll start by saying I have strong feelings about Southwest LRT. So do some people on this very blog. You probably do too. However, I won’t be contributing further to the gallons of spilled real and virtual ink or weeks of public testimony. I’d like to talk about how we can set the stage for some other projects that could be really beneficial for transit-dependent and transit-interested communities. Nothing in this post should be interpreted as diminishing the importance of that LRT project, the upcoming decisions that will determine it’s fate/depth of its tunnel, or the correctness of any particular opinion about it. But I have this urge to start some positive conversations about other projects that need some support. Weird, right?
Autonomous vehicles may bring a myriad of benefits, but I anticipate that one of the largest may be the actual reduction in the total size of the vehicle fleet. Eventually autonomous vehicles will allow “whistlecar” service, and whether fully autonomous or not would, this service is likely to fundamentally change the ownership model of automobiles. Like present-day car-sharing services or taxis, a whistlecar subscription would mean one car could serve the needs of many people, instead of remaining parked most of the day waiting for its one owner to return. Once you’re done with a car, it can drive off and serve someone else in the vicinity, drive to a charging station (if it’s electric), drive to a garage for service, or perhaps even deliver packages. When you can subscribe to an on-demand travel service available 24-7 (and eventually cheaper than owning a car), many people will choose not to own.
For the last two years, I’ve mapped the flows of the Nice Ride bikes. I’ve always been slightly dissatisfied with the results, since bikes were obviously shown taking routes that any sane Nice Rider would never take (Hennepin Avenue between Lake and the bottleneck, for example). Try as I might, I could never get ArcGIS to prioritize trails, lanes and bike boulevards sufficiently.
Enter the good people at Cyclopath. Cyclopath is something like a bike route wiki, in that it is constantly updating it’s database of bike routes using ratings from users. So every street in their database has a rating from bad to awesome (actually 0 to 4). And this database includes the whole metro and beyond. Best of all, they were willing to share it!
The latest version of ArcGIS has a new “restriction preference” setting, meaning there are six levels of preference for a link from “Highly Avoid” to “Highly Prefer”. So I combined cyclopath’s street ratings with these preference settings and got a new and better route analyzer. Here are the results:
As a reminder, here is what the old version looked like:
A few changes of note:
Hennepin is obviously not so popular anymore, save in downtown where there are more Nice Ride Stations.
The Cedar Lake Trail got a little more popular, perhaps 500 trips in some locations, since it was a Highly Preferred route.
West River Parkway south of the Washington Avenue bridge got a lot less popular (although crossings at Franklin stayed nearly the same).
There is generally just a lot less jigging and jogging on small streets as trips tend to condense onto major routes (see the major difference on Summit Avenue in Saint Paul).
Here is a version with a base street map for orientation:
Today I got an email about an upcoming public meeting for the project, and I noticed the project webpage includes a Traffic Operation Analysis with some traffic projections through 2035. Hennepin County is projecting a 0.5% annual growth in traffic volumes between 2011 and 2035.
Hennepin County provided traffic volume forecasting information for the Washington
Avenue study area. Several considerations included in the traffic forecasts are:
Minneapolis overall expects to add 36,000 residents and 30,000 employees over
the next 20 years.
Closure of Washington Avenue through the U of M, east of the Mississippi River.
Construction of the new 4th Street S on-ramp connection to northbound 35W.
Reconfiguration of the interchange at Washington Avenue SE/Cedar Avenue.
Construction of the Central Corridor LRT line.
The impact of continued development in the downtown area including
townhomes/condos, office space and retail businesses.
Given the above considerations and through a review of past studies completed within the project area, Hennepin County recommends that the traffic forecasts be based on applying a 0.5 percent per year growth rate (13 percent increase by 2035) to the existing traffic volumes, then adjusting Washington Avenue, 3rd Street S and 4th Street S traffic volumes to account for circulation changes with the future 4th Street S on-ramp connection to northbound 35W.
I don’t feel qualified to speak about hyper-local traffic patterns based on certain street closures and circulation patterns. That’s traffic engineer stuff. But here are a few things (and charts) to consider:
According to Mark Filipi, who works on regional traffic modeling for the Metropolitan Council, the regional traffic model (based on old comp plan data) projects 0.3% annual growth in total Minneapolis VMT through 2025. This is lower than 0.5%.
Total Minneapolis VMT has basically been falling since 2002, with non-interstate VMT fluctuating around flat growth (all VMT figures from MNDOT).
Minnesota total VMT per capita has been falling steadily since 2004 at over half a percent each year, and total VMT has been falling since 2007.
According to the Minneapolis Traffic Count Management System, two of the three traffic count locations on Washington Avenue in the study area show a drop in traffic from their peaks in the late 90’s/early 00’s. The third shows flat volumes.
Does all this mean that 0.5% annual growth rate on Washington Avenue is incorrect? I’m not sure. Minneapolis does plan to grow a lot of downtown jobs and housing. On the other hand, per capita VMT trends have been falling not just in Minnesota, but across the country and world. In addition, Minneapolis policy makers have stated their goals to shiftmodes. It’s troublesome to me that in the “considerations” that Hennepin County used in their traffic forecasts, they didn’t include plans for that mode shift the same way they include plans for development.
Given the severe lack of detail on how the 0.5% growth figure was developed, I don’t think the community should accept any design predicated on that figure without some additional explanation, especially if the capacity needed to accomodate that growth is given as a reason to reject elements that will make this street a livable, vibrant and valuable place, namely, pedestrian and bicycle infrastructure.
Presented here without scale or legend, are the Nice Ride flows from 2012. As with the mapping I did for 2011, individual road segments are thickened to represent the volume of Nice Ride traffic that traveled over them during the year. Bike trails and lanes were favored by the routing software, but since it looked for direct routes, some paths may be under or over represented compared with real-life Nice Rider travel (Cedar Lake Trail versus Hennepin Avenue, for example).
St. Paul is much more vibrant in 2012, with the Lake Street bridge seeing a high volume of Nice Riders crossing to our twin city. Top traffic segments included the Hennepin-Lyndale Bottleneck south of Loring Park, south of the Stone Arch Bridge, West River Parkway, and the Hiawatha trail east of the Metrodome.
Once again, kudos to Nice Ride for releasing all this awesome data.
In Minnesota, we build roads really well. If you look at the metro area, we’ve created a system where despite wide differences in job and housing density, commute times are virtually the same whether you live in Dahlgren Township or Loring Park in downtown Minneapolis. We also have a semi-famous regional government that makes connection to the same wastewater system easy, no matter where you are in a 7-county region that includes both farms and skyscrapers. All these things (and more) are made possible by shared resources, often collected from one area or community type, and sent to another with a different character. Somehow we’ve determined that this is a good thing (for ease of access, equity, environmental protection, political will, etc) As I listened to Chuck I thought, “you’d really have to remake how local governments interact if you wanted to promote (or even test) the idea that our “most productive places” should be differentiated from our least productive.
I won’t attempt to figure out how this can be done. But I think it’s valuable to think about all these “transfer payments”. There are more than most people ever think about. So, here goes:
At streets.mn, Andrew Owen has a fascinating look at the work he has done with David Levinson on measuring accessibility in the Minneapolis-St. Paul metro area. I’ll let Andrew define accessibility:
Accessibility measures the ease of reaching valued destinations.
Think about the last trip you made. You were in place A, you wanted to be in place B, and you got there by paying some sort of cost. There are several components at work here.
First, lets look at your reason for wanted to be in place B. That’s the whole reason the trip took place! You didn’t just want to move around for a bit, and then come back to A. (People do that sometimes, but we don’t consider it travel — we call it things like recreation, exercise, or NASCAR.) No, you had a reason for traveling to place B. That reason, from a transportation economics perspective, is the value that place B holds for you.
Now that we’ve established that place B has some value to you, it would be great if you could get there whenever you want, for free. But you can’t. Even if you frugally decide to walk from A to B instead of drive, fly, take the bus, or ride a horse, you cannot escape spending a precious resource: your time. The total amount of resources you spend in getting to B, whether they are time, money, oats (for your horse), or some combination, is thecost you pay to reach place B. To generalize just a little bit more, we can say that when the cost of getting to B is low, then B is easy to reach.
That, in a nutshell, is accessibility. It combines the value that we get from travel with the cost of making the trip. I love accessibility because it neatly encapsulates what I consider to be the fundamental purpose of transportation systems: providing ways for people to get to places they want to reach, at costs they are willing to pay.
Andrew then goes on to discuss the results of a project they completed for MN-DOT on measuring “cumulative opportunities accessibility”, or how many things can be reached within a given cost (time) threshold by car and transit. You should read the whole post to see Andrew’s many interesting conclusions.
After reading it, a few things jumped out at me:
Owning a car gives you an overwhelming advantage in accessing jobs in this metro. In a huge swath of the metro, making up all but the most outlying areas, you can access at least 100,000 jobs in 20 minutes by car. A very large area, incorporating both core cities and most first-ring suburbs, can access over 500,000 jobs and up to 2.2 million. By contrast, transit accessibility to jobs maxes out at 100k – 250k jobs, and this is if you live very near downtown Minneapolis. If you live in parts of North and South Minneapolis and use transit, you have the same access to jobs in 20 minutes as someone with a car living in southern Dakota County (like in a corn field). Or, based on the map shown below, from parts of Minneapolis, you can only reach 10-20% of the number of jobs reachable by car.
Is our transportation/land use system is failing those that can least afford a car? I’d say that judgment wouldn’t be a stretch looking at these maps. It will be interesting to see what MNDOT does with this information.
There will be a temptation to interpret this metric as only about transportation. It’s actually about destination density AND transportation system performance. I posted this idea in the comments and Andrew had a good response:
That’s a great point, and I didn’t talk much about the land use side of things in this post.
I feel like the popular conception often sees land use as more static than transportation; it is the background canvas upon which the dynamic lines of transportation are drawn. Discussion of expensive, exciting transportation systems tends to magnify this effect.
But in reality land use is far more dynamic! Transportation systems change in big fits and starts, but land use is constantly evolving in countless small ways. Even if we completely halted new investments in transportation, we could still make huge changes in accessibility through the policies we choose to guide land use development.
MNDOT mostly builds roads, so I assume they’ll use this report to think about where and how they should build more roads. But if your goal is increasing accessibility, is it cheaper to lay blacktop or increase jobs/housing density? What are the environmental implications of choosing each of those options? Why do we have one half of the equation that’s totally socialized (road & transit building) and one that is totally privatized (with obvious regulation – land use controls/building construction)?
What if instead of a Department of Transportation we had a Department of Accessibility and it’s mission was to improve accessibility while meeting environmental standards, building resilient systems, and being economically viable? I bet it would look at lot different than our current DOTs (hint: it would do a lot more with land use).