Mapquest.com vs API Distance Variations

4 posts / 0 new

Tue, 11/07/2017 - 12:26

tbarne1

Hello,

I am using the Mapquest API to report the shortest distance between two locations. This distance is used in our mileage reimbursement calculation. However, I have noticed that Mapquest.com reports a different mileage than the API. From: 3800 Anglin Dr, Fort Worth, TX 76119-2182 To: 800 Mercedes St, Benbrook, TX 76126-2527. Mapquest reports: 16.9 miles and the API reports 13.88 miles. What accounts for this difference?

https://www.mapquestapi.com/directions/v2/route?key=KEY&from=3800+Anglin...

Thank you,

Thu, 11/09/2017 - 08:58

MQBrianCoakley

MapQuest.com uses the fastest

MapQuest.com uses the fastest route by default rather than the shortest. Any route can change over time given current traffic conditions too.

Tue, 11/14/2017 - 09:04

(Reply to #2)

tbarne1

Thank you. Is there a way to

Thank you. Is there a way to have Mapquest.com display the shortest route instead of the fastest? Our users confirm the mileage caculations provided by the API with Mapquest.com and more often than not there are discrepancies. None of the routes returned by Mapquest.com equal the mileage reported by the API.

Tue, 11/14/2017 - 11:51

(Reply to #3)

MQBrianCoakley

While MapQuest.com isn't

While MapQuest.com isn't intended to be a verification tool, you may be able to use https://www.mapquest.com/routeplanner. Keep in mind that MapQuest.com will always consider traffic too. So route times and distances can, and will, vary at times. This is not unexpected.