Erroneous realtime seconds value

7 posts / 0 new
Log in or register to post comments
Last post
Mon, 11/06/2017 - 13:14
#1
ama
Erroneous realtime seconds value

Made a directions request to mapquest and received 10,000,000 secs for realtime while time is 4170

http://www.mapquestapi.com/directions/v2/route?key=xxx&outFormat=json&am...

  • "realTime":10000000,
  • "boundingBox":{},
  • "distance":71.708,
  • "time":4170

That doesn't seem accurate...What's happening here?

Top
Tue, 11/07/2017 - 05:27
MQBrianCoakley
If any road along the route
If any road along the route path is currently closed, the time will be greater than 10000000 (an absurdly long time for a route).
Top
Tue, 11/07/2017 - 06:32
(Reply to #2)
ama
Thanks Brian,

Thanks Brian,
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?

Top
Wed, 11/08/2017 - 09:18
(Reply to #3)
ama
Some other questions Brian,

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
 

Top
Thu, 11/09/2017 - 08:55
(Reply to #4)
MQBrianCoakley
No, there are no other
No, there are no other indicators of a closed road other than the unrealistic value. I will forward the null value suggestion on to the route team.   The route algorithm does try to create alternate routes around closed or roads with current heavy traffic. Some routes have to go too far out of the way to be completed and return the mentioned value.   This is not a recent addition to the directions api. The documentation has included this description as long as the apis went to their current RESTful format if I recall correctly.
Top
Fri, 11/10/2017 - 06:29
(Reply to #5)
ama
Thank you, I see it in the

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

Top
Thu, 02/22/2018 - 09:03
Jaminb2030
I am also having this issue,

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.

Top