MapQuest API: Any reason to use it over Google Maps?

Question

So I've been looking into the different mapping API's out there, and I've narrowed it down to Google Maps API and MapQuest's API. I'm leaning towards the MapQuest API for:

1. Unlimited queries
2. Support for draggable routes. Google's API allows multiple way points, which is not the same thing.

The draggable routes is a pretty important feature for what I'm working on, but am I missing any big reasons to avoid MapQuest's API? Some caveat in the EULA perhaps? The draggable route support sucks in practice?

Answer 1

Are you sure Google Maps doesn't support draggable routes? There are plenty of times I've accidentally dragged a planned route when using the website, throwing everything off. Not sure about the API though.

As accuracy goes I've noticed that for directions here in North Carolina, MapQuest is slightly more accurate. Google doesn't always map addresses to the right position. MapQuest and Google use different data providers in some places. Google uses a variety of data, and in some places the providers will be the same (NAVTEQ and Tele Atlas).

Otherwise it is largely user preference: I rarely do see sites though that don't use Google Maps. Microsoft seems to force their projects to use Bing for some reason ;)

Answer 2

It's kind of a late answer, but I ended up using the Mapquest API because they work better as small maps, and don't look quite as cluttered, especially after I extracted the zoom control from the map and implemented it via jQuery UI Slider.

I thought it was rather intuitive and easy to use. If I'm just looking up directions somewhere, I still always opt for Google Maps. If I need to build an API map, especially to fit smaller dimensions, MapQuest seems to do the trick.