Last
week I had a couple of opportunities to try out Google's bicycling directions to travel to places I had never gone before. My experience with the directions was mostly positive, guiding me along routes that for the most part worked well. The problem of poor trail signage (not Google's fault), however, could have caused a cyclist to become temporarily lost. Here's the story.
I wanted to travel to a friend's house who lives just off Braddock Road in Springfield about one mile west of the Beltway. I live in Arlington not far from Seven Corners. I had never been to my friend's house before, so I asked Google to give me cycling directions there. What I look for in the directions is how it overcomes the major obstacles, in this case, Route 50 and the Beltway were two major roads I had to cross. Google did not have me cross Route 50 at the new pedestrian overpass at Seven Corners, which I think is a better option than what it showed me. It did, however, have me cross the beltway at the pedestrian overpass that is north of Braddock Road about 1/2 mile, which is definitely the best option. All in all, the directions were not bad. A less experienced cyclist might have found some of the roads--particularly Braddock Road--a bit daunting to ride on. However, the directions worked for getting me there.
My second trip was to travel from this same friend's house in Springfield to the Whole Foods in Vienna. Unlike the first trip above, in which I was familiar with the first part of the route (and could adjust based on my knowledge), in this case I was completely dependent on the Google directions. I had never ridden in this area before.
In this case, the directions proved to be excellent, with one exception. The implementation of the directions presented some problems, but the actual route worked almost perfectly--taking me along mostly back streets and some trail connectors right to my destination.
The major obstacles in this case were Route 50 and I-66. The crossing at Route 50 actually turned out to be better than expected, because there was a trail connector that Google Maps was unaware of that I noticed when I reached the intersection of Pickett Road and Arlington Blvd. I-66 was crossed on Vaden Drive, a back street that crosses the Interstate with no interchange.
The biggest problem presented by Google biking directions is that trail signage is typically so poor--or not designed the way street signage is--so it presents challenges for giving and following directions. At every single intersection of two streets, there is a street sign. It was simple to follow the directions: Turn right at XXYZ St. or left at ABBC St. At each of these points, I was virtually 100% confident that I was following the directions as indicated. However, each time I had to travel on a trail, I lost confidence, because the trails did not have signs like the streets. On this trip, even the trails with signs had different names than what Google indicated them as. The most disconcerting part was when I was traveling along a trail and would encounter an intersection or fork in the trail. Google does its best, but without any signage, it just states "Turn left toward Vaden Dr." or the like. If the cyclists doesn't know where the named street is, then there is no way of knowing what those directions mean. Thankfully it was a sunny day, so I could at least tell what direction I was going and could correlate that with the line on my map.
Google biking directions is a good tool for cyclists. If jurisdictions would now please put up signage that will help cyclists navigate those directions, it would make the tool work much better.
=======================
Steve Offutt is a cyclist and can tell direction by the position of the sun.