Archive | August, 2012

email of the month: grids on the brain

An intriguing email from Kenny Easwaran:

I was very struck by this post in which you try to generalize the geometric issues to show that some of these features of transit are really universal.  [JW: I also wrote this on the underlying power of grids in public transit.]

At the time, I was thinking of the various transportation systems we know of that aren’t designed by humans.  The main examples I could think of were things within the human body, and I noticed that things like the circulatory systems of animals and plants, and the digestive system of animals, seem to follow somewhat different trajectories from grids.  In particular, they either have a branching tree structure, or something more like an extended linear structure.  

Of course, in these cases, it may have more to do with the drive system – the circulatory system is driven by a single central pump, and I don’t know if it has any sort of intelligent routing, which may make a grid system hard to operate.  It also seems to primarily ferry resources from two centers (the lungs and digestive tract) to all the rest of the body, so a tree structure may be the most efficient way to do this (like an old hub and spoke rail network centered on downtown).  

At any rate, the reason I’m writing this e-mail now is that I just saw an article suggesting that the human body *does* actually use a grid system!

Monkey-connectome-640x442From the article:

It’s rather weird: If you’ve ever seen a computer ribbon cable — a flat, 2D ribbon of wires stuck together, such as an IDE hard drive cable — the brain is basically just a huge collection of these ribbons, traveling parallel or perpendicular to each other. There are almost zero diagonals, nor single neurons that stray from the neuronal highways. The human brain is just one big grid of neurons — a lot like the streets of Manhattan, minus Broadway, and then projected into three dimensions.

Kenny goes on:

It seems plausible that the information transport network of the brain is a better comparison for human transportation needs than the resource transport network of the bloodstream … !

Looking at the diagram in that article a little more closely, it seems that there’s a two dimensional grid structure, even though the brain is three dimensional.  There appear to be axes going from front toback, and other axes going radially from the “suburbs” through the central axis through to the “suburbs” on the other side, but no grid elements going around the periphery from left to right.  I guess there’s an interesting sense in which a three dimensional transport structure can be gridlike in two dimensions but not the third?

At any rate, I’d be very interested to hear your thoughts on any of these analogies!  (It might also be interesting to look at structures in ant colonies and prairie dog towns, to see how they approximate thevarious geometries of transportation that you think might be worth looking at, though they are probably more analogous to purely pedestrian cities, rather than ones with long transport tubes.)

I’d be interested in hearing everyone’s thoughts on this!  (Apologies for the new comment monitoring; it’s purely to combat spam!)

Image from the article.

greater seattle: loving the new sub-network maps

Now this is a clear map!  It's by the Seattle area agency King County Metro.  First the legend:

KC metro legend.png
RapidRIde is King County Metro's new rapid bus product, with widely spaced stops, high frequency, special stations, but usually no exclusive lane.  Note how cleanly this legend distinguishes services that are useful for different purposes.  Note too that it omits peak-only commuter express services, because if they were present they would be lots of confusing overlapping lines that would make the basic network impossible to see.

So here's a piece the map.  Click to enlarge, but more important, go here (that's an order) to see the whole thing.

KC metro eastside map

The distinctions on this map are entirely about what matters to the customer, especially the person who wants to see the all-day transit network that is ready to liberate your life, not just your commute.  Red means fast and frequent.  Blue means frequent.  Green means all day but not frequent.  And if you want to see peak commuter express services, which would obliterate the legibility of this map if they were included, see another map or individual timetable.  

To be fair, many good maps do show peak only services and visually de-emphasise them as faint dashed lines.  That works too, but the key design principle is this:  The network of any particular layer in the hierarchy of service should be clear without being obscured by lower levels of service.  This map does that perfectly:  You can see just the red Rapid Ride line, or you can focus easily on red plus blue to see the frequent network, or you can notice the paler green and see the all-day network.  All in one map.

To get to this kind of customer-centered clarity, note what they had to omit:  Two transit agencies' services are presented here with no differentiation at all.  Bus routes numbered in the 500s belong to Sound Transit while the others belong to King County Metro.  Most multi-agency regions would focus on highlighting this distinction first, on the assumption that the customer's loyalty to a transit company is much more important than their desire to get where they're going.  The distinction should arguably be at least a footnote if you don't have integrated fares between the companies, as it could imply fare penalties and different fare media.

Some multi-agency maps do show all operators, but still visually distinguish them, as the Los Angeles Metro map does, for example.  But if you want a really simple map, reduce the transit company's identity to a footnote, or something that can be inferred from a route number*, or don't even show it at all.  Instead, show the customer what matters to them: frequency, speed, and duration of service.

*Can you spot the one place on the LAMetro map where they do that?  The answer is in "Joseph E"'s comment below.