[magduf]

Here's my suggestion for Google Maps: how about handling toll roads better? It's all-or-nothing. Why not put a little gray box saying "20 minutes shorter, $1.50", or "1 minute shorter, $29.50"? If you turn on toll roads, it'll happily always route you on a toll road or toll lane, even if it isn't any faster. And here in DC, toll roads can easily cost you $30-50 per trip.

Maps already gives you route options to choose from, both when you first start, and during your drive; why can't they do this with toll roads? Are they secretly working with EZ-Pass?

[vmarsy]

That's actually one of the suggestions I left them on the product.

I've the choice between toll-lanes or not on my way home, I'd love to know how much faster it'd take if I get on the toll lane...

But in that particular case, I'm not sure how that information is gathered in the first place, it might be hard for them to figure out which cars are on the toll-lane, and which cars are not since both the express lane and regular lane are next to each other.

[magduf]

Surely a simple filter algorithm could figure out the toll-lane thing: if you have a bunch of cars reporting speeds on what seems to be the same road, but you know that there's toll lanes there, and the speeds reported fall into two extremely different ranges (one crawling, one highway speed), then it seems safe to assume that the slow vehicles are on the regular road and the fast ones are in the toll lane.

Plus, while they aren't perfectly accurate, toll lanes are usually far enough away from the regular lanes that modern GPS devices in those lanes should be able to generally show themselves biased in that direction (relative to the devices stuck in bumper-to-bumper traffic).