The day I discovered Google Maps was the day I stopped using Map Quest. And the day I loaded Google Maps for Mobile on my Blackberry 8700c was the day I had found the “killer app” for my mobile device. I’ve become very reliant on both versions of Google Maps for a variety of uses — so much so that I’ve developed a false sense of confidence in Google’s ability to accurately find an address. Last night my love for Google Maps was crushed when it led me two blocks in the opposite direction of my destination.

Google Maps thinks 1990 M Street is on the corner of 24th Street

My starting location was the Embassy Suites Hotel (1250 22nd Street NW, Washington DC). My destination was the Pizza Hut on M Street (1990 M Street NW, Washington DC). After entering the starting and destination locations Google led me to believe that what I wanted was approximately 2 blocks from my starting location. Since Google knows when a road is one-way, it presented directions that followed the appropriate flow of traffic. Since I was walking, I was able to adjust the directions accordingly. Nevertheless, here are Google’s directions to 1990 M Street NW from 1250 22nd Street NW:

I was pretty certain Google was wrong because of how the streets are layed out in Washington D.C., but since it was a short walk I decided to follow Google’s directions just in case. Two blocks later there was no Pizza Hut in sight — my hunch was right and Google was wrong. I walked the opposite direction on M Street till I reached the 1900 block and saw gleaming red neon letting me know that I correctly found my destination — Pizza Hut.

The correct route to 1990 M Street from 1250 22nd Street

Here’s the correct path from my starting location to my destination. Keep in mind, Google draws a path that correctly follows the flow of traffic; however, it’s easy to see a quicker walking route that took me down 22nd street and the left on M Street passing over 21st, 20th, and then 19th street.

How can Google make such a big mistake in Washington D.C.?

If the starting and destination locations were some little known address or in small remote part of the United States, I could understand the mistake; however, the starting and destination addresses were on well known streets in one of the most widely map cities — Washington D.C. How could Google Maps make such a simple mistake? Have you found similar Google mapping errors? If so, please share your experience with in a comment.

Share, Bookmark, or Email this post

If you liked this post, subscribe to TechTraction's RSS feed or TechTraction's email feed

Filed under: Tech Commentary