Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Friday, January 14, 2011

Boulder B-Cycle and Google

B-Cycle announced today that Google donated $25,000 to the soon-to-be-launched Boulder bike share.

click through

The donation will cover roughly half the cost of one docking station, according to a story in the Denver Post.

The cost to install a station is about $45,000 to $65,000, depending on the size of the site and how much work needs to be done, he said.

One thing that stood out to me in this story is that the annual membership in Boulder will be $50, as opposed to the $65 annual Denver membership.

Cost of living difference? Except, it's more expensive to live in Boulder. What gives?

Wednesday, March 10, 2010

Alleyway

Upon a closer look, and actually riding the route, The Google did in fact suggest that I ride through the alley for four blocks.



The street view of the alley shows what I saw first-hand this morning: it's a wide, clean alley. Nice enough as alleys go.

But bikes don't go in alleys. They go on roads.

I submitted a problem report under the "Directions suggest a route that is difficult or restricted" category, because there wasn't an explicit "Directions suggest a route that is unsafe" category.


Bicycles should not be directed through alleys. It is safer for the cyclist, fir [sic] pedestrians on the sidewalks, and for motorists on the streets if the cyclist behaves as much like a car as possible. They should stay on the streets, proper.

You wouldn't randomly or spontaneously drive your car through the alley for several blocks. It wouldn't be safe!

And if you wouldn't drive that way in your car, you shouldn't drive that way on your bike.

Bike directions on Google maps


With the advent of the iPhone, it is possible to wake up only to find oneself adrift in the tubes before getting out of bed. And so I woke up this morning to find one email from the bike league, and a plethora of twooshes, all excitedly and twitchily informing me that Google Maps has added a bicycling option to its directions-finder.

I shuffled from the bed to the office, fired up the laptop, and had a gander for myself. I asked for The Google to plot my commute and to optimize the route for a bicyclist, and it proceeded to do its damnedest.

Critique of its optimized route


+1 for existing. For showing up. For bike directions even being an option. Thank you The Google for offering this service so that the people doing their living might realize the possibility of doing it by bike, alleviating wear on the roads and instead putting a healthy amount of it on their bodies.

+1 right off the bat for designated bike routes and trails being visible (highlighted in green) and for using them where possible.

-1 for making heavy use of traffic-heavy Downing Street! Granted, there are a number of blocks on which I'll ride Downing, but it's primarily not very ... Whoa, hold on a tic. What's this? The route here suddenly jumps between northbound Downing and southbound Corona. As though indicating there's a bike path in the median?

No, as though directing bike traffic through the alley! What kind of shenanigans is this? This shall not go uninvestigated!

+1 for inciting investigatory adventurism, with the possibility of later docking points for directing bike traffic off of roads and into alleys.

-1 for utilizing a bike route two blocks west of beautiful Cheesman Park instead of routing through the park. Optimizing directions for a cyclist should account for scenery-beauty. When will the Google learn to appreciate beauty?

-1 for routing the ride down 1st Ave, in front of the Denver Country Club, which is a dangerous sidewalk in winter because they don't shovel their walk. On the other hand, this option is fine in warmer weather, and whether or not to take it is a personal preference, but this is my list, so I'm docking a point.

+1 for making good use of the Cherry Creek Trail. The Google has accounted well for scenery-beauty!

Tallying up the score, it appears we are left with a total of one Arbitrary Unit of Judginess.

I am happy to have the "bike it" option on Google maps. It pleases me. Using it will be quicker than looking at driving directions and then overlaying my own map of bike routes. But it's definitely in Beta, and I'll be handling its suggestions in the meanwhile as though they are likely to be buggy. Because they are.

Friday, October 16, 2009

Google Trike

This morning, the google maps team invited us in this blog post to begin nominating off-street locations to be mapped out by the google trike.

You have till October 28th to submit a location at google.com/trike.

My first submission was not bicycle or Colorado related. I nominated the Ocean Beach Pier, up and down which I used to walk almost every day when I lived in San Diego.

Sunday, October 11, 2009

bike google



Bike Pittsburgh spots the google trike and comments on plans to start mapping bike trails.

When I'm planning out a ride, I usually compare "Avoid Highways" driving directions to walking directions, and then overlay trailsdenver's trails map and my routes map.

Two suggested routes through two different maps, and then I'm able to plan out a third route through the city's bike infrastructure.

Sometimes, it is time consuming. Other times I throw caution to the wind and set out knowing only that I need to go generally southeast.

But I gotta admit, one-click bike routing will be handy.