Mapquest vs. Google Maps

Have been finding lately that Mapquest is more accurate than Google Maps in small towns. Comparisons show erroneous feature collection like roads drawn where there clearly aren’t any on the satellite image, bizarre routing and mislabeled streets.  Granted, this part of Ohio is full of little towns with only one or no streets on StreetView, but it doesn’t explain how Mapquest gets it right.

Google lacks in the local search department, too. When you know my zip code, why give me search results in Chicago Park Ridge, IL first and my location sixth never?

Next time, I’ll take screenshots to show you what I’m talking about. Screenshot:

Google knows my zipcode. So, why hits in Park Ridge, IL?

3 comments on “Mapquest vs. Google Maps

  1. Hi Maitri,

    I’ve been a fan of the blog for about 1-1/2 years now. I live near Chicago, but have close ties to NO, and work in the mapping biz so I can relate well to many things you write about. Keep up the good work.

    The answer to your question may be fairly straightforward. Mapquest uses NAVTEQ map data. Google uses Tele Atlas data, although they are now creating their own data. I work for NAVTEQ so I may be guilty of drinking the kool-aid, but NAVTEQ believes their commitment to driving the roads to keep the map database up to date make our data stand out above the others.

    Greg

  2. Thanks, Greg! Yes, I’m aware that Mapquest uses NAVTEQ, but thought TeleAtlas more up to date than that. Perhaps a more comprehensive StreetView program in small towns can correct Google’s errors.

  3. Pingback: VatulBlog: Splitting Up With Google Maps

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>