Today we’ve added biking directions and extensive bike trail data to Google Maps for the U.S. My team has been keeping close tabs on all the public support for biking directions that’s been steadily coming in, but we knew that when we added the feature, we wanted to do it right: we wanted to include as much bike trail data as possible, provide efficient routes, allow riders to customize their trip, make use of bike lanes, calculate rider-friendly routes that avoid big hills and customize the look of the map for cycling to encourage folks to hop on their bikes. So that’s exactly what we’ve done.

Here’s a quick little screenshot (or, go try them out now):

And here’s a quick video of how to use the bike directions:

Thanks to the Google Maps team that put together, what at first glance, appears to me to be an exceptional tool. The quick and accurate routing, the multiple route options, the drag-and-drop routing ability, and the bike route layer are all brilliant.

Thanks to all of you 51,330 (and growing) petition-signers who took the time to lend your support to the cause. I believe we helped make a difference.

Thanks to long-time editor of this site, Brandon Warga, for preventing many of my mistakes from going out the door — too bad we didn’t have him before we wrote up the petition!

Thanks to Pierre for providing the French translation of the petition.

Thank to Bibi for providing the Italian translation of the petition.

Thanks to RideTheCity.com for proving that bike directions could be done, and done very well. I can’t tell you how many comments and emails I received saying: a) why are you doing this? b) why aren’t you doing this yourself? c) this can’t be done, d) this should not be done, e) etc. It was so common we decided to add it to the FAQ — with a bit of a defiant tone. RideTheCity were not necessarily the first web application in the world to provide bike directions, but when I first saw RideTheCity, I was very impressed — and it made myself and others hopeful that Google would eventually follow suit.

Thanks to the many people over the past couple of years who said, “Keep it up!” — your support was often the only thing keeping us hopeful and energized. In comments, in person, through email — y’all rock!

Thanks to the myriad people, places, and policies who had some role in pushing for this feature — too many to list, of course, but off the top of my head:

• BikePortland.org — for making it obvious how a website could help build community and inspire us to action
• City of Palo Alto — for allowing me to be introduced to ‘everyday cycling’ by way of bike lanes and physically-separated bike paths
• Austin — for being an insanely cool place, with insanely cool people, and a crazy-fun place to get around on bike (and an awful elevated highway that cut downtown in half and convinced me that bikes were the best way forward )
• Austin Bike People — for being insanely cool people who were enthusiastic supporters of the petition and really helped kickstart its take-off
• Wheatsville Coop and Black Star Coop — who inspired by being living examples of ‘working together to achieve common goals’
• Other Mapping Efforts — for pushing us all to continue to think bigger in terms of what could be possible for an online mapping tool
• John Pucher — for an incredible presentation at Simon Fraser University that first alerted us to the existence of sophisticated bicycle mapping tools like BBBike, for inspiring us with examples and data, for imploring us to use all the tools at our disposal to turn public opinion in our favor, and for speaking out in favor of social justice and, in particular, women’s rights and the importance of appropriate bicycle infrastructure.

My deep apologies if I missed anyone!

This site will stick around and we may even continue to post occasionally.

Looking forward to tons more people being exposed to biking as a practical and fun way to get around town!

Internet search giant Google has asked the city of Mountain View to allow homes and storefronts to be built near its headquarters.

At a City Council and Planning Commission meeting Tuesday night, officials considered a letter from Google. The letter said the company wants plans for a stretch of Shoreline Blvd near its headquarters to include more housing.

Every day, fleets of buses coming from all over the Bay Area take Google’s employees to their offices. Google said in its letter that building more homes nearby would be more sustainable.

In the video, notice all the cars. Notice how wide the roads are, with the unbuffered, unprotected, non-grade-separated, split-by-gutters bike lanes. Notice how loud the cars are — even blocking out much of the audio in the video clip. As beautiful as the Mountain View area is, including and especially the Googleplex area, it seems shocking that anyone would allow cars to so completely overwhelm a place of such natural beauty. It’s really a crime.

Google has talked a lot about renewable energy and all sorts of very high-tech ways for us to live better and greener, and they’ve done quite a bit — relatively speaking, with bikes — but they’ve not done enough. Google can save and profit from becoming more bike-friendly. People, including potential genius future employees and their families, love bike-friendly.

At some point, we need to convince someone high up at the company that bikes are a serious, if old-fashioned, technology. Bike technology can solve many of Google’s growing pains.

Bikes can also make a place a great place to be — a great place to work, play, live. I just returned to San Francisco after a quick weekend in Fullerton/Los Angeles — a very car-dominated place, relatively speaking (and I’m still completely enamored with LA culture and LA people). On my Monday morning bicycle ride into work in SF, I just thought, “Wow — so civilized.” Or, more accurately, “Wow — so much less uncivilized.”

All the talk of ’sustainability’ really misses that important aspect of bike culture vs. car culture — quality of life. In the video, a person walking their dog near the Googleplex says, “…I wouldn’t want to live here.” Ouch.

Providing enough space for cars and anything else is becoming increasingly difficult. You can have cars, or you can have housing, but you can’t have both. It’s the old Jane Jacobs advice — you are going to have attrition of the Googleplex by cars, or attrition of cars by the Googleplex — one side is going to be dominant, and it’s a policy decision that we make consciously every time we add roads and lanes without accommodating pedestrians and cyclists. Thus far, cars have won out, but we’re not doomed to repeating the mistakes that got us here. Get rid of that first ginormous car parking lot and build the first mixed use building. Provide some real bicycle infrastructure. Watch community opposition disappear. If you promise to make Mountain View better, you’ll find that people actually want to help you implement your plans — but if you promise to deliver them more cars/traffic/air and noise pollution/danger/brutishness, they’ll fight you all the way to City Hall.

A little over a year ago, our now-retired sister blog published a post titled, ‘To Save Money, Google Can Do More with Bikes, Land Use‘. We left a few quick recommendations:

1. Hire a bicycle program coordinator for the Googleplex campus. Their job is to motivate your employees, to help make and keep them happy and healthy, to save you money, and make Google the bike-friendliest company on earth. Any program should be open, as much as is possible, to contractors (note added: that is, ‘contract workers’).
2. Call up the SFBC and the SVBC and tell them that ‘Google wants in’ – tell them ‘we want to lend our institutional support’ to making the Bay Area the #1 most bikable region on earth.
3. Start thinking more creatively about land use, and how you can work with the Mountain View City Council and other local and regional governments to make the Googleplex more like a traditional transit-oriented development – maybe it can become a bicycle-oriented development. Mixed-use. Housing. Shopping. Retail. Whatever. No more parking lots.

And don’t call the position ‘bicycle coordinator’ — give the person some real power to make Google some money — ‘Bicycle Program Manager’, etc.

The (highway) 101 is a human-maiming and killing scar that runs between SF and San Jose — and it cuts off the Googleplex from the rest of civilization, including the commuter train, Caltrain, busy commercial/retail corridors (e.g. El Camino Real) and shopping centers, etc. The 101 is certainly a crime against humanity and one that should be scaled down from car-only use to provide a bicycle highway and transit corridor, and ideally, phase out car use on it altogether. There is always talk of building special walk/bike bridges over the 101 at various points — little gerbil runs — to allow people to walk and bike to that place where only cars go — but I’d prefer we demand to be treated like humans, and get full access to existing roadways — just reappropriate some space for pedestrians and bikers. I recently accepted a job offer in SF because the other option would be to Caltrain down from SF to Redwood City (awesome-ish), but then make a 3-mile ride from the Caltrain station through this brutish, car-centric landscape, including a ride across that loveliest of all highways, the 101 — not my cup of tea. Google can help make the Googeplex accessible to people on foot and bike — it’s not rocket science, we have the technology to make Google better, faster, stronger. It’s called the bicycle, and sufficient bicycle and pedestrian infrastructure — and it’s already working wonders around the US and around the world.

[via sf curbed]

…TechCrunch has the letters from/to Google/City of Mountain View. Many folks have been pointing out for years that existing zoning laws are not ideal — that is, many/most of the places we most enjoy because they allow us to walk instead of drive, would be illegal to build today because of auto-centric zoning laws. The Googleplex area is so car-dominated, in part, because it is set up by law to prevent any sort of ‘mixed use’ development (e.g. business, housing, retail, shopping, etc.) — it is ’single use’ (e.g. business, office parks, etc.). SmartCode is just one way of allowing towns to grow smarter without having to reinvent the wheel — think of it as a design pattern for zoning laws (@see video of Andres Duany of DPZ). It should be noted that the auto-centricity of the Googleplex is completely predictable — it was designed, by law, to be car-dominated. The City of Mountain View should look to change existing zoning laws to allow mixed-use development (i.e. to allow the Googleplex to become less car-dominated, and therefore, a decent place/area to live) — but the City should not do so without guarantees of bicycle infrastructure, and a plan to connect the Googleplex to the rest of Mountain View — i.e. Castro Street/downtown Mountain View — and to connect it for pedestrians, bicyclists, transit, etc. Right now the only realistic connection between the Googleplex and Caltrain/downtown MV/VTA light rail/Castro/El Camino Real is by car — that ain’t gonna fly. The 101 presents a huge problem.

If you speak ‘nerd’, or know someone who does, then the rest of this could apply to you. There are some high-level FAQs about data formats, and a link to a form to fill-out if you have some data and you want to partner with Google to get your data integrated into Google Maps. The data we most care about here, of course, is bike-related data — bike lanes, routes, paths, etc.

Who has bike data? Well, cities and bicycle coalitions, probably — and/or the folks who hold the copyrights on maps/data, if they are copyrighted. [Of course you know how we feel about this type of data -- it should be free free free.]

If you are a planner/GIS-type person in the Bicycle division of the San Francisco Municipal Transportation Agency, then maybe you can help Google get us some bike directions — just fill out the form and see what happens. Could the good folks of our local bike coalition (the folks who put out the bike map) possibly work with Google to get this done? Got me — there’s one way to find out. [SFBC is up to 11,000+ members, now.]

Whatever city or town you live in, do your best to convince someone — I’d start with your local walk/bike/transit advocacy organization, if you have one — to contact the city/town/municipal government and ask them to follow up on this.

What does bike data look like? A lot of it is over my head, but we can look at Google’s “Complete Map Content Specifications“. There are lots of details, of course, but the human-understandable parts are very cool. If you’ve wondered what the GTFS format for bikes was going to be, we may have our first draft.

Can the data format handle wide curbs vs. bike lanes vs. one-ways vs. two-ways vs. high-speed arterials vs. bike boulevards vs. contraflow lanes vs. buffered bike lanes? I’m not sure, but it looks like it’s pretty flexible and can handle most if not all of the crazy configurations and complexities that occur in road networks.

New roads and bicycle and pedestrian paths

Google is presently accepted two specific types of network data: new roads, and bicycle and pedestrian paths.

• Use a segment-based representation: a segment is part of a road between two intersections. We can not accept roads that have multiple intersections hanging off of them.
• The street format is similar in many ways to the address format, with the exception of the different street number format.
• All address ranges should be specified relative to the the geometry (that is, the right side is to the right of the path from the start of the segment to the end of the segment).

The following fields are useful for roads and bike and pedestrian paths. Fields marked as “optional for BP” are not necessary for bike and pedestrian paths:

Field	Description	Example values
ID	A unique and stable identifier for the road segment	Any alphanumeric string (e.g. “14232514″)
AR_RT_FR (optional for BP)	Starting address on right hand side, relative to geometry	42
AR_RT_TO (optional for BP)	Ending address on right hand side, relative to geometry	58
AR_LT_FR (optional for BP)	Starting address on left hand side, relative to geometry	41
AR_LT_TO (optional for BP)	Ending address on left hand side, relative to geometry	57
ST_NAME	Street Name and Type (the words Street, Avenue, etc., can be abbreviated)	Powell St
ST_NM_A1 (optional)	Alternative Name 1	U.S. 101
ST_NM_A2 (optional)	Alternative Name 2
NEIGHBH (optional)	Neighborhood Name	Union Square
CITY	City Name	San Francisco
STATE	State (Two Letter Abbreviation)	CA
ZIP (optional for BP)	5-digit zip code	94108
CNT_NAME (optional)	County Name	San Francisco
CNT_FIPS (optional)	County code (see here and here.)	06075
ONEWAY (optional for BP)	One-wayness – relative to the direction of geometry	“None”, “To-From”, and “From-To”
PRIORITY (optional for BP)	We would consider the following levels: interstate, federal/state highway, expressway, minor arterial, local, not intended for public traffic.	minor arterial
LANES (optional)	Number of lanes	2
SURFACE (optional)	Road Surface	Paved or Unpaved
SPEED_LM (optional)	Speed limit in MPH	55
AVG_SP (optional)	Average Speed	25
CAR (optional)	Cars are allowed on this segment?	Allowed, Small vehicles only (mopeds etc), None, Disallowed
PEDEST (optional)	Whether the segment allows bikes, and if so, what type it is	One of: Trail, Walkway, Mall, Sidewalk, Wide Shoulder, None, Disallowed
BIKE (optional)	Whether the segment allows bikes, and if so, what type it is	One of: Trail, Bike Lane, Wide Shoulder, Recommended, None, Disallowed
SEPARATED (optional)	Whether the road is separated by a barrier in the middle	Y/N
TURN_R (optional)	Turn Restrictions (or see below for exact format)	Freeform text
ELEVATION (optional)	If the road is elevated, or a bridge or a tunnel	One of: bridge, tunnel, overpass, underpass

We are happy to accept turn restrictions as freeform text to make it easier for people to submit data as turn restriction formats can be very complicated. We can accept turn restrictions in any format. However, to assist, here is a model format that would typically be delivered as a CSV file or a DBF file:

Field	Description	Example
FROM_ID	The ID (see the id column above of a road segment) of the segment where the turn restriction starts	14232514
FROM_END	The end of the segment the turn restriction applies to relative to its geometry.	Either “FROM” or “TO”
TO_ID	The ID (see the id column of a road segment) of the segment where the turn restriction ends	14232599
TO_END	The end of the segment the turn restriction applies to relative to its geometry	Either “FROM” or “TO”
MODE	The mode of transportation the limitation applies to.	Either “ALL”, “PEDESTRIAN”, “CAR”, “TRUCK”, “BUS” or “NON-HOV”
START_TM	The start time of the turn restriction, in 24 hour notation. Leave this and END_TM blank for permanent restriction	06:00
END_TM	The end time of the turn restriction, in 24 hour notation. Leave this and START_TM blank for permanent restriction	10:00
TYPE	Type of turn restriction	Either “NO LEFT TURN”, “NO RIGHT TURN” or “NO U-TURN”

Special thanks to The Tri-State Transportation Campaign (TSTC) (wiki), who just blogged about our petition (thanks, y’all!), and in doing so, they implored us to assist Google if our help was requested. The TSTC is sort of a group of transportation/environmental/sustainability superheroes and their respective organizations from the New York, New Jersey, and Connecticut areas (the ‘Tri-State Area’). They work on all the sorts of things we care about, and it seems like lots of important people have worked with them or for them at one point or another. [Janette Sadik-Khan was on their Board of Directors.] It was their blog post that made me re-examine Google’s Data Format/Submission site.

We hit that number about a week or so ago, thanks to ‘Jessica’ — the 50,000^th signature.

Shortly after we hit the big 50k mark, Google made a small announcement on their LatLong blog:

The best part about this new dataset is that we’ve been able to add a lot of new, detailed information to Google Maps – information that helps people better explore and get around the real world. For example, college students will be pleased to see maps of many campuses; and cyclists will now find many more trails and paths to explore. Soon we even plan on providing you with biking directions to take advantage of this new data. Of course, in the true Google spirit of “launch and iterate,” we plan to work with more data sources to add new features in the map.

Now we’re all curious to see the first cut. If there is a city or organization working with Google to provide them actual bike-specific street data (say, on the relative ‘bikiness’ of certain streets, Class I/II/III, contra-flow routes, etc.), I haven’t heard about it yet — but that’s not saying much, as I’m usually the last to know.

Ride the City, who originally provided mapping directions in New York City, followed by Chicago, now provide bike directions for Austin — that bike-crazy town smack dab in the middle of Texas:

Even if you haven’t been there, you might have heard that Austin is great for bicycling. According to the bike gurus, the League of American Bicyclists, Austin is the only city in the whole state of Texas worthy enough to receive a ranking in their Bicycle Friendly Community program. (The City comes in as the 15th best U.S. city for bicycling, and for that it gets a silver badge.)

Well, we’re hopeful that bike riding in the Lone Star state is going to get even better today as we launch Ride the City – Austin: www.ridethecity.com/austin. Put your hands together!

We’d like to thank all those who helped during the tweaking and clean up of the data to improve the routes. We especially thank Nathan Wilkes and Jason Fialkoff, both of Austin’s Bicycle Program, and bike advocate Tom Wald. These guys gave excellent feedback and helped to comb through the routes to make sure the most common local routes are accurate. Thanks guys. (Some day we’ll show you one of Nate’s hand-drawn maps, really cool.)

We hope that Ride the City – Austin will make bike riding a little bit easier in another great American biking town. So pass it on and, remember, if you test a route and find a glitch or a better way please come back to rate it/give comments on the “Feedback” tab so we can continue to improve the site.

Notice they’ve made the switch from Google Maps tiles to OpenStreetMap tiles. Because the OpenStreetMap tiles have fewer of the yellows and other bright colors of Google Maps, your bike route is easier to see — at least it seems that way to me. So, that’s a big plus.

Props to everyone who got it going.

Austin is a great town, and it just got a bit greater. 

Give it a whirl!

Read more about it, here.

Or, just go check it out for yourself at http://goroo.com/.

Hopefully we’ll be getting some awesome ’street views’ of walk and bike paths. After that, we’ll need the bike directions to go with them.

Google UK is doing some of the same, but their press release seems to suggest the project is not so much about shooting non-street paths, but popular tourist destinations. We’ll see.

And the CBC got some of our tech/research heroes on camera:

[Download full video here (.wmv).]

The most interesting part of the planner to me was the survey results showing that cyclists’ primary concern in selecting a route was to find one with low air pollution. It’s possible I read/viewed that incorrectly, but if true, that would seem to be an important factor in cycle route planning that I never even once considered as being important to us cyclists.

As best I can tell, Vancouver seems to be the Portland of Canada — fairly progressive biking policies, relatively speaking. Maybe that’s why Vancouver was just ranked 4th best city in the world for livability.

For more info on how the route planner fits into the overall research program, and links to all sorts of other interesting data/analysis, check here.

To navigate there from Google Maps, click the Help link in the top-right, then ‘Send Feedback’ on the right.

The ideal would be to vote for (’Suggest’) just the ‘biking directions’ feature — that would probably help make it stand out a bit better — but feel free to vote for other features you really really really want, too. 

If you’re feeling particularly frisky, you can head over to the Google Maps Help Group and ‘Post a question’ to the ‘Features Requests / Suggestions‘ Google Maps Group. Any details you add about why you want this feature and how you would use it are a great way to show support for this feature — it really helps the engineers and product managers at Google know what you want. So, you’re answering the question, “If Google Maps adds bicycle directions today, how will I use them tomorrow to get where I need to go? How will they help make me safer, my life better, etc.?”

I know I’ve posted in those groups before, but I’m going to try to get back in again with a good example. For whatever reason, I can’t seem to get a good mental map of San Francisco in my head, so I’m constantly heading to the San Francisco Bike Map hanging on my wall to figure out how to get somewhere. It usually includes leaning over furniture and zooming my face into the wall, trying to get a close-up of street names and things like that.

Thanks for the heads up, Donny!

It’s incredible, really. Monthly ciclovias. Just like that.

And in Miami, of all places — so car-choked as to look almost helpless against the onslaught of motor traffic. And they’re doing it – taking back the city.

Miami is sun-drenched, has good population density, and is currently the 43rd-ranked city in population size in the U.S. Miami has the potential to become a great bicycle town.