7 posts / 0 new
Mon, 11/06/2017 - 13:14#1
Erroneous realtime seconds value
Made a directions request to mapquest and received 10,000,000 secs for realtime while time is 4170
That doesn't seem accurate...What's happening here?
Are there any other indications that a road is closed in a direction request without checking to see if realtime is a constant of 10000000?
Some other questions Brian,
Why is 10,000,000 chosen as an arbitrary value for a routh path that is closed? Why not return a null value?
Does MapQuest normally attempt to find an alt route automatically in cases of road closure?
Is this a recent change? I don't recall we have had this problem before in all of last year and it scares me to think that values requested from the api cannot be trusted to be accurate or self-describing
Thank you, I see it in the documentation now. I guess we have never had a situation where the road closure was so severe that MapQuest was unable to create alt routes
I am also having this issue, ill have to see if i can play with the alt route apis to geta proper real time calulation.