thoughtcrumbs

it's a neat concept, but watch out for the one-ways. (the directions from my street to cmu suggest riding the wrong way up bartlett street.)

It also tells you to go the wrong way on Darlington, which—while corresponding to the actual behavior of a number of bicyclists, including a certain CMU grad student I used to see out my kitchen window—is extremely stupid.

I'd guess it's a bug in the Pgh data rather than a fundamental design "feature", though, since it seems to get Portland's one-ways right (e.g. 1800 SW 11th Ave to 800 SW 11th Ave gives a route up 12th).

Joshua is right about the one-way issue. The Pittsburgh data seems to be in pretty bad shape. Coincidentally, someone from CMU is working on the PGH data integration.

Also, I would like to point out (sorry, just being nit-picky) that the trip planner is not built "on top of" Google Maps. The GMap is a separate component and could easily be replaced by a Yahoo Map or a MapServer interface.

Good point, all, about the one-ways. Oh, and I was being lazy when I said "built on top of." I literally meant layered but separate, but should have phrased that more carefully. Thanks.