If the first two TPW summaries I posted here at streets.mn seemed a bit arcane (outfall structures?  asphalt contracts?), this one should have at least one meaty topic.  In fact, one topic is so meaty that I’m going to upend two millennia of mathematics to begin with #9, then briefly summarize the rest afterwards.  Stay tuned.

9. Bottineau Transitway Draft Environmental Impact Statement (DEIS) Scoping Comments and Memorandum of Understanding  In between the time when unscrupulous investors drove the Twin City Rapid Transit Co into the ground and the construction of the Hiawatha Light Rail line, there was virtually no government spending on capital improvements for all-day transit.  Perhaps then we can be excused for feeling a bit overwhelmed by the recent flowering of construction.  After 50 years of lean, two light rail lines per decade feels like 10 years of fat.

Though 3rd on deck, Bottineau Transitway is charging forward, and the City of Minneapolis is currently considering deciding on a Locally Preferred Alternative for the southernmost segment of the line.  For this TPW meeting, Staff forwarded a recommendation that the City endorse the D1 alignment – the one that would run through Wirth Park to Olson Hwy.  While that endorsement has been postponed, the County is looking to have this more or less decided by this May.

While the City hasn’t formally asked for an opinion from citizens, that timeline means that those of us with strong opinions need to get our email fingers ready.  For those of you who haven’t yet formulated an opinion about Bottineau (maybe because you feel like you just finished formulating an opinion about Southwest), here is a quick history and overview of the issues.

Like most local transitways, Bottineau has had a long and tortured history, but is generally agreed to consist of some kind of at least medium-capacity transit line extending northwest from Downtown Minneapolis, probably along County Road 81 (aka Bottineau Blvd) for much of its length.  Most recently, a three-year alternatives analysis process whittled an overwhelming array of alternatives down to three Most Promising Alternatives (i.e. those that scored best):

•  A light-rail line that would run between Maple Grove and Downtown Minneapolis via an existing rail right-of-way on the eastern edge of Wirth Park & Olson Hwy (known as LRT A-D1)
• A light-rail line that would run between Maple Grove and Downtown Minneapolis via West Broadway, Penn, and Olson (known as LRT A-D2)
• And a light-rail line that would run between Brooklyn Park and Downtown Minneapolis via Wirth-Olson (known as LRT B-D1)

In response to stakeholder input, BRT versions of the Wirth-Olson routes were also forwarded as finalists (known as BRT A-D1 or BRT B-D1), and possibly in deference to symmetry a fourth route alternative was also forwarded, that would travel via Penn-Olson but with a northern terminus in Brooklyn Park (known as BRT or LRT B-D2).   So at this point under consideration are the alternatives depicted below:

Last alternatives standing, Bottineau

I’m going to be candid:  The AA study found Segment A to be unambiguously best for the northern third of the line.  The only reason segment B was included is that scoring favored any D1 alternative, since all other alternatives were penalized for the sin of running through a city (and thereby impacting traffic, parking, and property).  The tough choice is on the Minneapolis side, where each alternative offers a devil’s bargain:

• The Wirth-Olson alternative is the type that models really well because it skips over the type of neighborhood that is dense enough to actually contain transit users, which allows it to offer a fast ride for commuters that board in the suburbs.  However, this type of line often performs much more poorly than the models predict, because theoretical commuters don’t always actually board; see Dallas.
• The Penn-Olson alternative serves around 10,000 more people, but because it would run more slowly through urban neighborhoods, it was projected to attract around a thousand fewer weekday riders in 2030.  However, since Penn-Olson would run through areas that contain around 17,000 more current riders of transit (engineers call them transit dependent), my guess is that the 1,000 fewer theoretical riders would be made up for by actual riders (these numbers all come from the AA study).  So what’s the problem?  The Penn-Olson alternative would require the taking of dozens of properties along Penn between West Broadway and Olson, which would widen that section of Penn to 90-100 feet, at least halve the number of pedestrian crossings, and, as Mpls Public Works staff notes in their comments, leave parcels along Penn “substantially smaller, and it is not known whether they could be redeveloped.”  Even with LRT, could the neighborhood recover?

No one knows.  Hennepin County engineer Joe Gladke told the TPW committee that he has been unable to identify a light rail line in the USA that runs in an alignment analogous to Penn-Olson.  City staff does not seem eager to blaze this particular trail, hence their recommendation to endorse D1.

As such, the conversation has largely turned to D1, and much of Gladke’s presentation was about whether to place a station at Golden Valley Road or Plymouth Avenue on the Wirth-Olson alignment.  Basically, the trade-off there is that Plymouth has more people living nearby, but Golden Valley connects to more feeder buses.  In the process, the map shown at right was produced, showing the population that lives within a half-mile of the station as measured by the routes that are actually possible, rather than as the crow flies.  This would please Jarrett Walker, but doesn’t seem to have made a huge difference in this particular location.  Perhaps that is because both locations are at extremely low densities, a fact that seems to have been lost on City staff, who recommend looking into stopping at both.

Making decisions on this scale is never easy, but Bottineau seems to be even harder than most.  That’s why it’s doubly important to look into this stuff and make your voice heard.  The Councilmembers who have the last call are smart people, but it’s not like they’re transportation experts – unlike you, dear readers of streets.mn.

And now, on to the rest:

These and a few more streets are getting smoother

1-3.  Near North Area (South Portion) and Grant Area Street Resurfacing Project  A whole bunch of streets in the Near North area – specifically between Olson and Plymouth, Penn and Emerson – are getting resurfaced this year.

4.  RFP for Mattress Collection and Recycling  Hennepin County will no longer be handling Minneapolis’ old mattresses, so the City is looking for someone to take them.  CM Colvin-Roy notes that “Minneapolis is the last city in Henn Cty to be told it needs to organize its own mattress collection.”

5.  Water Treatment and Distribution Services Lime Slaker Replacement Project  It turns out that lime slakers are not involved in any way in mixing margaritas.  Instead they are used in softening water for public consumption, specifically, “to convert the dry pebble lime into a milk of lime slurry that is fed into incoming river water to begin the treatment process.”  And you thought this stuff was boring.

6.  Special Assessment Deferment Application  State law allows municipalities to “defer the payment of special assessments for… a person 65 years of age or older or retired by virtue of a permanent and total disability for whom it would be a hardship to make the payments.”  Which is nice, but maybe also an argument against our whole home ownership-based housing policy.

7.  Minneapolis Bicycle Advisory Committee  Marin Byrne is joining the BAC, and I’m sure is an excellent candidate due to sharing a last name with bike advocate and Talking Head David Byrne.

8. & 10. Traffic Management Center Upgrade and Traffic Signal Controller & Cabinet Replacement Project & Hiawatha Corridor Signal System Improvement Project  Yes, Virginia, stoplights really do have computers, they’re called controllers and they can be used to make annoying delays at stoplights go away.  But, just like the duopoly of operating systems in personal computing leads to nothing but consumer suffering, the 8-10 contractors that control the national controller market lead to exorbitant pricing – these two projects have a combined budget of  $10.8m for a grand total of 29 controllers (to be fair, both projects contain a lot of other stuff, including 141 traffic signal cabinets, a number of detectors, and miscellaneous engineering).  But don’t worry, the Feds are paying for 80% of item #8, the fruit of a CMAQ grant applied for in ’05 and ’07.  At least we got it before Boehner took it away…