For simply browsing a map, there's very little difference between the two (Indeed, it seems they both get their data from NAVTEQ). But when using them for trip planning, there is a huge difference: MapQuest actually knows what the hell they're doing. Here's part of an itinerary I was working on when traveling from Seattle to Baker City, OR:
MapQuest:
- Merge onto I-90 E via the exit on the LEFT toward BELLEVUE / SPOKANE.
- Merge onto I-82 E via EXIT 110 toward YAKIMA (Crossing into OREGON).
- Merge onto I-84 E via the exit on the LEFT toward PENDLETON.
Google Maps:
- Take the I-90 E ramp to Bellevue/Spokane
- Take exit 137 to Wanapum Dam/Richland
- Bear right at WA-26
- Bear right and head toward WA-243
- Continue on WA-243
- Bear right at WA-24
- Continue on WA-240
- Turn right at WA-240 E
- Take the I-182 W ramp to Yakima (I-82)/Pendleton
- Take the I-82 E ramp to Umatilla/Pendleton
- Take the I-84 E ramp to Pendleton
Now, I have no idea which one of these routes is faster, but even assuming that Google's way is the quicker of the two, that advantage goes completely out the window if I get lost. I don't even have to write down MapQuest's directions, I can remember those in my head. Since the point of giving directions is arguably to get me to my destination, Mapquest wins hands down.
This isn't the first time Google Maps has steered me wrong, either. (Hah, steered me wrong... get it? Hah... Ok, I'll quit) In Peoria, it tried to direct me down a road that no longer existed. In Seattle, it told me to exit on a later exit to get downtown, disagreeing with Kan Kan's directions. (MapQuest gave me Kan's version)
So my advice to the serious trip planner is to stick with MapQuest. You should, of course, take this with a grain of salt. Erickson has told me MapQuest has tried to steer him the wrong way down a one-way street before, so it's apparently not infallible.
Re: Mapping Engines: A Real World Comparison
reply