Mooneapolis, A.D. 2030

How to cross the street in February

The council voted yesterday on the items that came out of this cycle’s committee, so it’s probably a bit late to report on what went on in the Transportation & Public Works meeting.  On top of that, the Star Tribune, in their fitful effort to cover Minneapolis, scooped me on a few items.  One was the new civil fines proposed for failing to shovel snow, which I’m excited about.  The idea that we’ll be able to walk a block without sinking to your ankles in snow is one more reason to get excited about winter.  Maybe with the proceeds of this fine the city will be able to afford to finish their plow jobs, instead of leaving icy piles of plow debris blocking every crosswalk.

Speaking of the city affording stuff, I’m obstinately writing this post about the 10/25/11 TPW committee despite having been shown up by professionals because of one item:  the Infrastructure Study presentation.  Basically, Public Works looked at four major transportation infrastructure components and compared their condition to their funding level with the goal of coming up with an eye-popping number to report as a shortfall.

It all begins with the Pavement Condition Index (PCI), or Evidence A that engineers’ confidence in the omnipotence of math is why they shouldn’t be trusted with absolute control over our public spaces.  Here is how the presentation describes it:

The Pavement Condition Index (PCI) is a numerical index between 0 and 100 that is used to indicate the condition of a roadway. It is a statistical measure and is based on a visual survey of the pavement. A numerical value between 0 and 100 defines the condition with 100 representing an excellent pavement.

A 101 point scale would be fine if they were using lasers to measure the pavement surface to discern the level of distortion.  Sending Chuck in his Trail Blazer to glance at the road on the way to McDonald’s is not going to result in a reliable measure, and even a careful visual survey will not reliably tell the difference between a PCI of 71 and a PCI of 72.

Road to Mooneapolis

But the PCI is what we have, and in Minneapolis it’s the low end of the index that is seen more and more.  In fact, the presentation contains an apocalyptic chart showing the descent of many of the cities streets into a gravelly moonscapes within 20 years.  The presentation doesn’t clearly describe, however, what we’re sacrificing back to the elements.  It mentions four networks – 206 miles of Municipal State Aid (MSA) streets, 632 miles of Residential streets, 70 miles of Local streets, and 378 miles of Alleys.  The MSA streets, mostly the heavily traveled arterials such as Hennepin or Nicollet and including many Downtown streets, are fed by the state and projected to remain in roughly the same condition.  It’s Residential streets and Alleys that are going to crumble.  Local streets tend to be a)industrial streets, b)leftover bits of MSA streets or c) the slightly more traveled Residential streets that aren’t vital enough to be MSA routes – circa 2030, they will also be a lo0se arrangement of tar chunks, duct tape and car parts, but there are only 70 miles of them.

Chart Fail

The presentation is interesting, but with one exception it doesn’t really explain how we got into this mess.  (The exception being the Pavement life cycle chart reproduced at left, which terrifyingly predicts “Total Failure” after 16 years if pavement isn’t attended to.)  The problem is less one of underfunding today and more one of overfunding several decades ago.  Around 70% of Minneapolis’ residential streets were built in a 15-year binge from 1967 to 1982.  I don’t know for sure how this indulgence was financed, but a 1966 Citizens’ League report suggests that it was paid for with bonding, which of course is ultimately paid for with property taxes.  So more or less, the city just increased its budget for the massive push to pave Residential streets, and once they were paved the total budget just shrunk, or, more likely, went to other things.

Paved with intentions to pave

So now the city would like to double Public Works’ capital budget to address this crisis of crumbling Residential streets.    Residential streets mostly don’t provide corridors for transportation, except as the very beginning and end of trips.   Instead, both in terms of use and area, their primary function is to provide parking for the residences along them.  It’s difficult to justify expending community resources on such a local benefit, and according to the Citizens’ League report, Residential streets used to be financed mostly locally – at the same time the council decided to jack up property taxes to pay for smooth parking on side streets, it reduced assessments on abutting property owners from 2/3rds to 1/4.   (The local share seems to have been reduced to about 5%, if you can trust my math and this document.)

Smooth paving on side streets, like some rural roads, is probably not necessary for our society to function.  But like subsidies for corporate relocation or sports stadiums, localities feel like they need to shell out in order to be competitive.  I’d say it’s reasonable for people to pay for their own parking spaces, but any proposal to use local money to fund local streets is sure to be met with fury, and it certainly wasn’t mentioned in the presentation.  But if we ever start having a grown-up conversation about how to adjust our life-style to our declining economic situation, I hope that free parking is on the table.

Push me to blink

A quick word about another TPW committee item:  authorization for Public Works to spend $4,000 to convert a pedestrian crossing light “from constantly blinking to user activated.”  Apparently neighbors “observed that many drivers, having become accustomed to a continuously flashing pedestrian light, no longer stop for bicyclists and pedestrians at this location.”  They noticed that drivers yield more often a nearby user-actuated crossing light (no numbers were offered in the RCA, so apparently they took neighbors at their word).  Just another example of the expense we go to in order to avoid enforcing motorists’ legal obligation to yield to pedestrians in a crosswalk.

Bonus Regulatory, Energy and Environment Committee item

Bicycle Regulations

Minneapolis will amend its traffic code to explicitly define bicycles as vehicles, and therefore include them in the definition of Traffic.  Vague statements in favor of clarity were included in the Request for Council Action rather than an explicit rationale for the revision.  My first thought was that this will now guarantee that cyclists can be charged with violations of the traffic code, although Gary Schiff says the goal is to “make it easier to issue a ticket to someone parked in a bike lane.”  I just hope it won’t settle the Great Crosswalk Debate in favor of requiring cyclists to stop and yield in a crosswalk.

Bonus Community Development Committee item

Minnesota Statewide Historical and Cultural Grants Program (a/k/a Legacy Grants Program)

Warehouse District atmosphere

Staff is recommending that the City apply for a grant from the Minnesota Historical Society to help implement the Warehouse District Heritage Street Plan, which recommends rebuilding several crumbling patchwork streets mostly in the North Loop with brick pavers in an effort to restore their appearance as existed at a certain point in history.  The summary from the Request for Council Action is worth quoting in full:

Funded with a 2010 Legacy Grant, The Warehouse District Heritage Street Plan set out a detailed street-by-street plan for preserving historic infrastructure in the Warehouse Historic District. The Plan provides a practical, forward looking, and historically-sensitive approach preserving and rehabilitating historic streets and loading docks while improving pedestrian accessibility, and enhancing stormwater run-off by increasing sustainable practices within the Warehouse Historic District. The completed document was approved by the HPC in August of 2011. The document is a detailed street-by-street plan with specific trouble-shooting for how to preserve the remaining historic materials and industrial infrastructure, while accommodating the American with Disabilities Act (ADA) requirements and addressing the need for street and sewer repairs. The plan will be used to inform the individual site decisions that property owners, design professionals, and the City will need to make when properties in the District are rehabilitated. It is also being used as the guiding document for the design and development of City capital improvement projects for the reconstruction and repair of specific streets and alleys.

Now that the plan is completed, CPED and Public Works are beginning work toward implementation with a focus on reconstruction of 6th Avenue North. One of the challenges identified in the plan is that original brick material will be deficient to reuse throughout the district due to breakage or removal from past utility cuts. In order to reconstruct 6th Avenue North with full brick replacement, Public Works will need to find similar brick from other city streets under reconstruction. This grant will be used to salvage, palletize, transfer, and store subsurface brick from other City projects where the brick is similar to that in the Warehouse District. One possible removal project will occur in 2012 with the first phase of Nicollet Avenue South reconstruction.

The Plan is worth looking through, especially Chapter 5, or the design concepts for specific streets.  In one sense this is good news, because the sooner Minneapolis has more experience with textured pavement surfaces, the more people will realize their traffic calming effect.  The bad news is, if the first removal project won’t happen till 2012, it could be awhile before these plans are realized – and the North Lo0p badly needs new infrastructure.  I’m looking out my window at a big pile of brick pavers torn up as part of the new Lunds construction at 12th and Hennepin – Public Works, would it help if I gave you the number to Zeman Construction?

Greenfields and trenches

A couple doozies in the agenda for the 9/27 Transportation & Public Works committee:

1. is the first waft of a new greenfield housing development in Bryn Mawr.  It seems that someone long ago went through a great deal of trouble to plat a few blocks south of Chestnut Ave and west of Upton, but then only built houses on maybe half the land.  Now someone else has decided that now (or relatively soon) is the time to finish building the blocks and to line them with single-family homes.  Here are the blocks in question:

This map produced by Mpls Public Works shows the parcels owned by the developer in grey

I shouldn’t sensationalize:  this project has a long way to go before any ramblers or McMansions pop up.  The developer – Frank Stucky is the name in case you know him – asked the city to “open” the unbuilt portions of Vincent and Xerxes.  I’m unclear on whether that means the developer asked the city to build the streets and attendant infrastructure for him or whether he merely asked permission from the city to build them himself.  The tone of the report implies that the city is not interested in building these streets, but would allow the developer to do so.  Most intriguingly, it requires a report on the following:

identification of all applicable permits, processes, ordinances, and standards related to Public Works and Planning & Zoning for single family home development; the estimated cost of maintaining the improved roadways and related utilities; the estimated cost to construct the roadways and related utilities; documentation that confirms that the Owner/Developer is willing to bear the costs of such improvements; the proposed prospect for developing the currently vacant lots; estimated tax revenues to be derived from the developed lots vs. vacant lots; the ability of the roads to bear emergency vehicle access; the wishes of the neighboring landowners with respect to the opening of the roads and the development of the lots [who wants to bet on what the wishes of the neighbors will be? -alex]; identification of relative hardships, if any, caused by not opening the roads vs. relative hardships, if any, caused by opening the roads.

In other words, a micro-scale version of the recent report by Edmonton (thanks Brendon) on the “extent to which new residential neighbourhoods pay for themselves.”  (note- this quote is in Canadian)

I’ve done some rough measurements of the area and length of block face of the parcels in question, and based on the minimum lot area of 6000 sq ft and minimum lot width of 50′ in an R1 district, it looks like the developer could put up no more than 12 houses.  Interestingly, the lots appear to be platted at 5400 sq ft and about 40′ wide (presumably these blocks were platted decades before the zoning code was enacted), meaning they need to be either replatted or rezoned.  If that happens and they only require the more typical lot area of 5000 sq ft and width of 40′, 16 houses could fit.  If this were a more progressive part of a more progressive city (like, say, Chaska), some 22 houses could be placed on these blocks.

We can dream

All that speculation assumes the developer would like to build more houses on the lots, instead of just using them for a few houses on large lots.  It’s hard to tell exactly at this point, but it is likely in the city’s interest that more houses be built.  Because of the required approvals, the city actually has some leverage here – let’s hope they use it.  The committee postponed action for two cycles to wait until the report was ready – at least that sounds like what CM Colvin Roy was saying.

2. is my old nemesis, the proposed 4th St S ramp to Northbound 35W (now with its own project page).  The goal is to make it easier to commute back to your hobby farm in the northern suburbs from your boring job in Downtown Minneapolis by building a new ramp to 35W from CR-122 (aka the Washington Ave Trench), a mere 700 feet south of the existing ramp to 35W from Washington Ave S (the non-trench Washington).  Here is what the new time-saving on-ramp will look like:

Blaine is now two minutes closer

Apparently the news about a little construction project called the Central Corridor hasn’t made it out to Medina, because Hennepin County’s engineers forgot to put the new on-ramp configuration on this layout.  It shouldn’t make a big difference; the new ramp to Cedar is 300 feet from the stoplight proposed as part of this project.  But if we’re reconfiguring the Washington Trench to have a stoplight spacing similar to Lake St, maybe they could have thrown in a sidewalk or two?  Or at least made the new ramp to 35W a bit more perpendicular so as to not encourage as lethal speeding.

To understand why this ramp is superfluous, it helps to consider the history of this trench.  Sometime around the middle of the last century, someone decided that it took too darn long to drive from Downtown to the U of M.  There was just too much dense neighborhood in the way.  The Washington Ave Bridge was due for a replacement anyway, so they just tore down a bunch of the dense neighborhood and built a little mini-freeway to connect to the new bridge.

So while it may look like this project concerns the intersection of three roadways, Washington Avenue and its trenched doppelganger perform essentially the same function, that is to move traffic from west to east and vice versa.  With that understanding, the 8 existing ramps forming the interchange seem sufficient, and adding one seems superfluous.

Ramp map - ramps are numbered (including the proposed ramp in red), directions represent the destinations linked by the interchange

Why get worked up about a $13m project?  For one thing, it likely won’t be long before the whole thing needs to be redone again.  Right now, thanks to Central Corridor, the interchange is a pile of dirt except for a forked viaduct carrying vehicles from nb 35W to 3rd St S and Washington Ave (marked 6 and 4 respectively on the ramp map).  This viaduct will soon turn 50 years old, but is a sibling to a nearby bridge that will not be there to celebrate.  That means that chances are the viaduct will also need to be rebuilt soon, at which point it will be much more logical to make this interchange more diamond-like.  Rather than spend $15m for another flyover ramp, at that point it will make sense to instead build one ramp from nb 35W to the Trench, where a signalized intersection could accommodate all the movements that are currently made using the viaduct, including a connection north to Washington Ave, from which vehicles could access (or re-access, as the case may be) nb 35W.  Alternately, you could fit in a 400′ diameter roundabout, as I mentioned a few months back.

Circle gets the square

I admit that my radical side, considering the extreme disparity between transportation spending on cars and all other forms of transportation, is opposed to any new auto-oriented spending.  But I do have a timid, quiet, practical side that realizes that we live in an auto-dominated society (because of that modal disparity in spending) and realizes that there are some auto-oriented projects worthy of construction.  An example is the 35W access project, which proposes to increase the usefulness of a freeway to a neighborhood that it currently cuts through.  That is to say, it adds accessibility.  The 4th St ramp to 35W does not increase accessibility.  It does not increase safety.  It is a small reduction in trip time for some commuters.  The existing exit has working imperfectly for 50 years, so why choose this particularly cash-strapped moment to move forward with this project?

Of course the TPW committee voted in the consent agenda to spend $2m in city money on this nice gift for commuters from Anoka and northern Ramsey counties.

One more item, not from the TPW committee, but rather from the Planning Commission meeting of 9/13, but I haven’t seen anyone else discuss it so I’ll mention it briefly (or as briefly as I am capable of mentioning anything).

Gary Schiff has proposed amending the zoning code to blow the top off of the CUP ceiling for multi-family developments.  As it stands, you need a CUP for any building of more than five units.  Where that rule came from, I have no idea – while fourplexes and duplexes are more common, sixplexes aren’t unheard of and I knew a guy who used to refer to his building as a nineplex.  Anyway, if this passes, no hockey player will again need a CUP for his new sixplex.

The staff report contains some nice quotes:

• The average fee for a conditional use permit is $750.00.  Between 2005 and 2010 there were 113 conditional use permit applications for multiple-family residential uses with five or more dwelling units submitted. At an average fee of $750.00 per application this amounts to $84,750 dollars that was collected.
• Between 2006 and 2010, 92 percent of all conditional use permit applications for multiple-family residential uses with five or more dwelling units that were reviewed by the City Planning Commission were approved. Of the eight percent that were denied, other applications (i.e., rezoning) were typically required that were not supportable, so therefore the conditional use permits were also denied.
• In both the City of St. Paul and the City of Bloomington, multiple-family dwellings are a permitted rather than conditional use in the zoning districts where they are allowed. In the City of Richfield, multiple-family dwellings over nine dwelling units in the MR-2 Multi-Family Residential District require a conditional use permit and multiple-family dwellings over 20 dwelling units in the MR-3 High Density Multi-Family Residential District require a conditional use permit.
• The conditional use permit application for multiple-family residential uses with five or more dwelling units often adds relatively little value to the review process.

Good news as we move into an apartment “boom.”  Don’t get too excited, though – the proposal also would “require City Planning Commission action on site plan review applications for any development of ten or more units…” with an associated application fee.

County Road Rethink

Another Transportation & Public Works Committee meeting brings another layout to critique.

Hennepin County will be reconstructing about a mile of County Road 9 (called 45th Ave N between York and Xerxes, but Lake Dr west of York) in 2013 or 2014, and apparently 100 feet of it runs through Minneapolis, so the county was kind enough to ask for the city’s thoughts on the design.

Not much will be changing in Minneapolis – the roadway will be a foot narrower, which in this segment is accomplished by taking away a foot from the 15′ of paved shoulder (currently 6′ on one side and 9′ on the other).  Oh yeah, and those useless shoulders?  They’re going to make them both 7 feet, paint an arrow on them, and a bike symbol and poof!  It’ll be a bike lane.

The Layout

Bike lanes have actually been conjured along nearly the entire segment to be reconstructed, beginning at Xerxes and ending without any logical terminus at Josephine Lane or Lake Road.  This is a fulfillment of the Hennepin County Bike Plan, which shows a bike facility along Lake Dr connecting Victory Pkwy and a yet-to-be path along Bottineau Blvd, although the plan (a product of the late 90s) actually shows the Lake Dr facility as existing (as opposed to planned).  This raises questions in my mind about whether the little bike symbols shown on the layout will suffer the same fate as crosswalk markings on Minneapolis’ bike facility layouts, doomed to never be applied to pavement.

Speaking of pedestrians, I’m not sure the new design for Lake Dr looks as nice from above two shoes as it does from behind handlebars.  The plan makes minor improvement to the sidewalks – currently on the south side the sidewalk is mostly 4′ with a boulevard that appears to be 2-4′ narrow depending on the block, and on the north side the sidewalk is 8′ with no boulevard.  The plan will widen the sidewalk on the south side to 6′ but leaves the minor aesthetic detail of how to treat the north sidewalk unaddressed.

Meanwhile, I’d like to point out the very low vehicle traffic on this road – it peters from 9,300 on the west end near Bottineau to only 7,050 near Victory.  Frankly, this road is useful for only a small number of people, since it runs through a very low-density residential area with only a smattering of retail except for on its west end.  The intersecting streets are also very local, and on the north side of the road, with the exception of France Ave, don’t run for more than a block or two.

Why, then, does Hennepin County provide a continuous center turn lane?  Is the level of turning traffic really so heavy here that they need that extra 11′ of payment along the entire road?  And even if there is a lot of cars turning left, 7,000 vehicles a day don’t make for a very long queue.  Here’s a thought – why not just provide turn lanes where they’re needed?  Probably France and Indiana could justify a turn lane, and maybe one of the streets further east could be designated as a neighborhood access street and given a turn lane.  With that extra 11′ of right-of-way, Robbinsdale would have room for a nice wide boulevard on either side, plenty of room for nice tall trees to grow some day (if Robbinsdale doesn’t like trees, they could use the space for parking their cars, although they don’t exactly seem to be hurting for parking).

Gateway to R-dale's toniest subdivision, Chowen Downs

The half-block Minneapolis segment has a (probably) more justifiable turn lane, and the sidewalks do strange things there, in keeping with the strangeness of a park that is also a road.  I know that Minnesotan traffic engineers really hate striping crosswalks, but the five streams of non-motorized traffic at the intersection of 45th & Victory really does justify some paint, I swear.  Technically that intersection is out of Minneapolis’ jurisdiction, the Robbinsdale segment is thoroughly out of Minneapolis’ jurisdiction, and the whole damn thing is way out of my jurisdiction.  Still, I wonder if there is a polite way to say to Robbinsdale or Hennepin County “you might want to think about not fucking this up”?

Who does Public Works work for?

I got my Transportation & Public Works committee agenda notice in my email today, as usual a whole four days before the meeting.  In other words, too late to change anyone’s mind.

As expected, the committee will vote on the new layout for Nicollet Ave.  This is the new new new layout, the third presented to the public.  The agenda was the first I’ve seen of it, although I checked the project page and sure enough it’s there, dated 8-16.  For the record, August 16th is at least 15 days after the decision was made to remove curb extensions from the design.

Just to recap, the city decided to remove any physical design element for pedestrians, then waited 15 days to notify the public of or even acknowledge the change, conveniently after it was too late to do anything about it.  I’m not in favor of Greek or even California-style democracy, where the general public gets to vote on every little detail.  But when a decision is made to remove a feature that changes the entire character of the street, I think it’s irresponsible to even let the public know about it.

It appears that the city has pounded another nail into the idea of complete streets, another nail into the validity of their own design guidelines, and another nail into the idea that pedestrians are anything more than a bush or bench, allowed at the side of the road to make it look pretty.

For the record, here is the layout:

Easy driving

8/9/11 Transportation & Public Works Committee

A couple interesting items from this week’s TPW committee:

1. 22nd St E (re)construction.

This is not a typical reconstruction as the street was never “built” – it is still an “oiled dirt” street (a bit of a misnomer; I believe these are original dirt streets that used to be covered with oil in the old style but now are patched with asphalt).  Also, in a fun twist on the typical street “reconstruction,” 22nd will follow a new alignment that will reconnect it to Cedar Ave, only 61 years after it was severed in the ill-advised freewayfication of the Cedar-Franklin-Hiawatha intersection.  Here is the layout:

A connection is made

The plan is a vast improvement over the existing street – the narrowed intersection with Snelling banishes the menace of speeding trucks that make the city’s industrial districts so unpleasant.  Right now 22nd St is connected to Cedar Ave with a crumbly staircase; presumably the roadway and sidewalk connections will be a much better option for the many potential users on wheels.

The Project Map included in the committee report omitted two things:  First, a left turn lane on Cedar, which Seward Neighborhood Group and Redesign want here in order to close Minnehaha Ave between Franklin and Cedar.  The city believes that there will be too much traffic in the future to close that road, however, and as far as I know they are planning to reconstruct the intersection with a very similar layout to what is there today.

Ghost ramp

Second, the map is missing a connection from the new 22nd St to the Light Rail Trail.  The existing connection runs on public right-of-way that is being used as parking for some anonymous industry, and consists of a steep curb that is softened by a wood plank.  Sometimes the excitement of the connection is enhanced by repositioning the wood plank in lots of dangerous ways.  Apparently the long-term plan is for the main neighborhood connection to the trail to be at 24th St, but it seems like now may be a good time to add a cheap asphalt ramp or something at 22nd St.

As you can see, the project map is not very detailed.  It’s possible those two omitted items are actually a part of this project.  I couldn’t find any more details on the project page, though, so we’ll have to wait and see.

2.  Lowry Bridge Bike Lanes

There’s a ton of confusion about whether or not there will be bike facilities included on the new Lowry Bridge, despite their inclusion on the Minneapolis Bike Master Plan of 2001.  Apparently 10 years wasn’t enough time for Hennepin County to find time to look at that plan, so they designed the Lowry Bridge without bike facilities (or narrowed the bridge to save money and thereby chucked the bike lanes?  Thanks guys).  Now they say they can find room for lanes or a separated trail somewhere, but the layout dated 8/30/10 included in the TPW committee agenda doesn’t show them.  Maybe the county just hasn’t gotten the new layout to the city, or maybe they didn’t find room yet, or maybe they just told bicycle advocates they’d try to find room and then went upstairs and had a smoke and somebody spoke and they went into a dream.  We’ll know in “Summer 2012″ at the latest.

A Bridge Too Many

Once again this week’s TPW committee was packed with items that fascinate me and bore my girlfriend.  I’m going to comment on a couple:

Cedar Ave S Bridge

Blobs to be?

If you want a sample of the byzantine nature of transportation funding in the state of Minnesota, check out the RCA for this project.  Hennepin County is going to widen sidewalks on the bridge that carries Cedar Ave over CR-122 (referred to as Washington Ave SE in the committee agenda; someday I’ll post my rant on Minneapolis’ street naming “system” if I can cut it down to a length that doesn’t crash WordPress), also they’re replacing some streetlights and adding some nice railings.  If I’m reading it right, the only reason the issue is coming before the council is that Hennepin County awarded the city a TOD grant for this project, even though the county will be doing the work (“The project scope has limited implications to the City” according to the RCA).  The county seems to have awarded itself a grant.  Interesting the contortions that need to be made in order to improve the pedestrian environment.

If the project looks familiar, that’s because it first came up as a sweetener for the highway expansion project that Hennepin County submitted to the TIGER program.  It’s heartening that the County took this sweetener seriously enough to pursue it even without “free” money.  The RCA doesn’t mention widening the bridge, but mentions the same sidewalk widths as the TIGER application, implying the plan hasn’t changed.  Also not mentioned is the bridgehead “flaring” depicted in the sketch above; my guess is it won’t be included – the document I took the sketch from lists the flaring as a $750k expense over and above the $1m for widened sidewalks; the RCA lists the project cost as $1m total.

Van White Boulevard

A new place to slither

Pretty much everyone who’s been on Lyndale north of the Bottleneck has wished for another way between Uptown and the Northside.  Our wish will be granted by the Fall of 2012, when a half-mile segment of Van White Boulevard is scheduled to be completed at the cost of $42m per mile.  (Drivers, of course, will still have to contend with the Bottleneck itself, but the more mobile modes will be able to walk or bike through the park and avoid the mess – hopefully long-term plans include some paths through the mansions and up Lowry Hill, but I won’t count on it).

In order to just get this damn road built, they’re probably going to phase the project:  where the long-term plan calls for two bridges over the railroad tracks, each carrying one direction of travel, instead at first only one bridge will be built carrying both directions of travel.  I can’t help but ask the question why, then, they are planning to build two bridges at all.  The Bassett Creek Valley Plan answers that question – the city is planning for a lot of redevelopment in this area (although Hennepin County may throw a monkey wrench in the works).

The plan includes a bike path on the east side in place of the sidewalk.  North of Glenwood, it is a multi-use trail, with 6′ for pedestrians in addition to 10′ of bidirectional bike path; south of Glenwood the ped space disappears.  While I’m not much of a separatist in terms of non-motorized traffic, it seems like they could have designed it to include walking space along the entire segment.  It even looks like they bought enough right-of-way for it; isn’t it just the same old story that a bridge would be designed for twice the projected amount of cars but half the projected amount of pedestrians?

 

Minneapolis Solid Waste Facts

It is a great idea (and worth the time) to skim the city council committee agendas as they’re issued.  If you do, you’ll be rewarded with gems like the powerpoint Public Works came up with for the 10/12/10 Transportation & Public Works committee meeting:

10-Solid-Waste-Recycling-PPP

Straight from the horse’s mouth…