Geocoding Etc.

Thursday, March 09, 2006

Google Maps vs. Yahoo Maps vs. MapQuest - API's

Since Google Maps launched their API allowing developers to use their mapping service to draw their own data, Yahoo has tried to play catchup with their own API. Well now with MapQuest's announcement of their new API, it's now a three way. Which one to choose?

Google Maps API

Pros:
  • Fluid interface, brilliant looking map marker flyouts
  • International
  • Built in Aerial Photos
  • Largest developer base, as a result...
  • Lots of hacks and how-to's available

Cons:

  • No built-in geocoding service
  • No built-in routing capability

Yahoo Maps API

Pros:

  • Built-in and external geocoding capability
  • Very flexible and open API's
  • Rate limiting by IP instead of appID
  • Built-in GeoRSS support
  • Flash version available

Cons:

  • U.S. and Canada only
  • Flyouts not quite as spiffy as Google
  • No aerial photo option
MapQuest API

Pros:

  • Built-in routing (driving directions) capability
  • Built-in geocoding capability

Cons:

  • No smooth AJAX client (yet)
  • Rate limiting by appID + web site URL (instead of end-user IP)
  • No photos option

Yahoo and MapQuest seem to be eager to please their developers, probably with good reason. They have a lot of catching up to do with Google. I give Yahoo a lot of credit for being first to release a AJAX map client with built-in geocoding functionality. That's one clear area where they are ahead of Google.

Time will tell how sustainable each companies model is and how much change will be necessary. Remember too that they aren't just always going to give this away for free, even if there will be no charge in the future, there are bound to be ADs.

posted by pkh at 6:41 PM

13 Comments:

  • You could probably add Public ArcWeb Services to your list for those who want to see it compared, but I believe the Geocoding service can only be used 1,000 times per day, but you cannot batch geocode at all.

    By Blogger James Fee, at 7:40 PM  

  • I don't know about the mapQuest API, but having developed in both GMaps, and YMaps, GMaps is far superior. I wanted to like the Yahoo maps, butust check out the Yahoo Example Page . The zoom is broken!!! As it is for all Yahoo Ajax maps. That.s bad. The event system (YEvent) in yahoo maps is also buggy. GMaps just work.

    By Blogger brent, at 9:37 AM  

  • brent -
    There is a workaround for the zoom problem (not sure why its not in the main code yet), but in general I agree with you that the Google Maps API is much slicker for mapping than Yahoo's.

    I am guessing that Google Maps was probably in development for a year or more before they actually launched, while Yahoo had much less time to play catch-up.

    Still Yahoo has a wonderful feature with their geocoding capabilities, lets just hope they don't cripple it into oblivion.

    -Phillip

    By Blogger pkh, at 5:53 PM  

  • yes, i know, because i wrote the general workaround: here

    the general code has not changed for months. i totally agree, yahoo, could be better than GMaps for style and api extras, but if the zoom dont work...

    By Blogger brent, at 7:42 AM  

  • brent -
    Ha! that's funny I didn't put 2 and 2 together with that one. I didn't pay much attention when I saw that fix, but I did implement it!

    I always assumed it came from Yahoo.

    I agree, its really odd that they have left the zoom broken for months now. Surely it can't be that hard to fix...

    By Blogger pkh, at 10:42 AM  

  • Hi,
    Does anyone know where I can find MapQuest open API code that works with xhtml1.0 strict DOCTYPE ??

    Thanks,
    Al Toman

    By Blogger vladimir allen, at 5:12 AM  

  • Looks like Google has updated the api to support Geocode lookups and Directions/Routes.

    By Blogger harking, at 8:29 AM  

  • I am confused as to which API is most suitable for a business that wants a map with points plotted, and is a subscriber only service (pay to see proprietary data on Google/Yahoo/Mapquest map api)?

    Does this require enterprise license?

    By Anonymous Anonymous, at 12:55 AM  

  • For me deal maker was driving directions. Only Mapquest had them at the time I designed my module, so I did not have any other choice but to go with them :)

    By Anonymous Map Quest, at 8:14 AM  

  • I am looking to batch geo-code a total of 6-7 million records, do any of these services allow you to batch geo-code maybe 100,000 records at a time?

    By Blogger Tomk, at 2:55 PM  

  • I can't believe google doesn't provide geocoding & routing in their API. First they switched to a non-free API for their search engine, now this. I'm not liking it one bit.

    By Anonymous Anonymous, at 2:54 PM  

  • I used to use the Mapquest API, but recently I have switched over to the Google Maps API, it seems more reliable.

    By Anonymous Mapquest, at 10:56 AM  

  • I certainly have preferred the look and UI of Google Maps but I'm done with them now. I had a business appointment out of town and Google's map and directions both took me to a mis-named street in a neighboring town half an hour past where I needed to go. I typed in Hunter St. Peterborough, Ont. and when I got there, I was on Fraser St. in Lakefield. So instead of being relaxed and on time, I was an hour late and frazzled. When I got home, I checked Mapquest and it had the correct map and directions. So now I'm just going to use Mapquest (until they screw up).

    By Anonymous Anonymous, at 1:53 PM  

Post a Comment

Links to this post:

Create a Link

<< Home