Home/ Questions/Q 513211
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T07:23:57+00:00

So I’ve been looking into the different mapping API’s out there, and I’ve narrowed

  • 0

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?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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 😉

    • 0