Google Biking
Mar. 10th, 2010 11:10 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Google Maps gets biking directions: http://googleblog.blogspot.com/2010/03/biking-directions-added-to-google-maps.html
Dark green routes are dedicated bike trails and sidepaths; light green are bike lanes, and dashed green lines are "recommended" roads for biking.
I haven't explored it much yet to see what I think of the actual routes it suggests. It seems to recommend bike paths and lanes strongly over other roads, which is fine, but of course it can't really take things like road surface quality into account.
Dark green routes are dedicated bike trails and sidepaths; light green are bike lanes, and dashed green lines are "recommended" roads for biking.
I haven't explored it much yet to see what I think of the actual routes it suggests. It seems to recommend bike paths and lanes strongly over other roads, which is fine, but of course it can't really take things like road surface quality into account.
no subject
Date: 2010-03-10 04:20 pm (UTC)I see this and I think "why the heck not??". It would require some level of crowd sourcing, but that'd be a useful thing to suggest to the team. If I work there I may try and do that :-}.
Your point about the recommendations is interesting, though; I've had multiple modes in my own biking life of whether I preferred direct path with traffic, or mellow bikepath without. That might be an area for personal preference learning. Hmmm.
(Can you tell I'm considering working at Google? It gives a much more personal investment in these kind of issues :-})
no subject
Date: 2010-03-10 04:30 pm (UTC)The route it recommends between East Arlington and my office favors the Minuteman bikeway extension all the way through Davis Square. That's a fine way to go if your goal is to minimize road travel, but I prefer taking Mass Ave. to Beacon St. and cutting a half-mile off the route. That's hard to account for, given the range of individual tastes.
no subject
Date: 2010-03-10 04:47 pm (UTC)no subject
Date: 2010-03-10 04:59 pm (UTC)I think the hard part would be collecting data on issues like road surface quality and lane width. Those aren't quantities with a known canonical source, but can affect the bikeability of a route a lot.
no subject
Date: 2010-03-10 06:14 pm (UTC)no subject
Date: 2010-03-10 06:45 pm (UTC)Unfortunately for me, it can't actually create bike routes where there really aren't any. The shortest path to the close Mexican place for me is on a busy and fast road through the middle of a freeway cloverleaf. Google, can you fix that?
More seriously, to the local coffeeshop it recommends taking the bigger surface street instead of the small winding streets. Hills may play a role in that too. For my comfort factor, I take the side streets with the hills every single time.
no subject
Date: 2010-03-10 07:03 pm (UTC)Getting quality data about roads is a big problem. There is no systematic data source for pavement quality, and even the information about where hills are is full of noise.
no subject
Date: 2010-03-10 07:15 pm (UTC)Pavement quality is going to be a rough one in general, since it's going to vary over time. Columbus is spending a *lot* on pothole repair right now.
and even the information about where hills are is full of noise.
*sings* The hills are alive, with the sound ... oh, nevermind.
no subject
Date: 2010-03-11 03:22 pm (UTC)no subject
Date: 2010-03-11 08:01 pm (UTC)