Google Maps for Bicycling
Today Google Maps introduced a cycling choice for routing in 150 cities in the US. R-Town is one of them.
Playing around with it this morning, it frequently picks different routes than I typically use. It seems to favor side streets and turns more frequently, where I generally prefer a more direct route. However, it also favors bike paths over streets.
It generally provides a couple of alternates too, in addition to its preferred route.
Last week I tried it for the middle part of my Tuesday three-legged commute from Presbytery (1190 Winton Rd S) to the Arnett Branch Library. Choosing the walking route, it took me over Pinnacle Hill, through the Ellwanger and Barry neighborhood and across the Ford St bridge.
Today, the same route is listed as an alternate route, with its primary choice being a bit longer but infinitely more pleasant using the Erie Canalway and the Rochester Riverway/Genesee Valley Greenway. Neat.
For my main home to library route, it chooses an entirely reasonable route, similar to my chosen route. Where I prefer the Meigs St bridge over 490, it prefers the Averill Ave bridge. Both are better choices than Goodman or Alexander streets.
It makes an interesting choice in lining up for the Ford St bridge over the river. It takes you south to Sanford St, then right on Mt. Hope to line you up for a left to the bridge. For many riders, this is a more prudent choice that I hadn’t considered. I’ve been taking Gregory St to Mt. Hope where I have to wait to make a left on Mt. Hope through heavy traffic.
I’ll have to consider this choice, but with my own variation. Instead of my current Meigs to Cayuga to Gregory, perhaps Meigs to Caroline to Sanford.
It’s not without its quirks, though. Across the bridge, strangely it routes to Bartlett St, then has you turn a block north to Whittlesey, then back south at Epworth right past Bartlett again. I’ll ride that today, but I suspect it’s to cut out the light at Bartlett and Jefferson Ave. Maybe it knows something else I don’t, or maybe it’s just some weirdness.
The estimated ride times seem consistent with my experience. My long-term average speed is in the upper 15s, so your times may vary.
There’s an article about it on Wired, which seems more like a press release, and a slightly more in-depth article about it on BikeHugger, and of course, on the official Google blog.
