I ran into a routing problem today, we switched to sending lat/lng (which we get using themapquest service) to get directions.
A customer called with a route that was popping up a mapquest 602 error, can't compute route or can't calculate route.
So it takes a while but I narrow it down to having doreversegeocode set to false. We don't really need it, we have the address, and we have the lat/lng, so why geocode or reversegeocode?
But now I find that in some cases, for some reason mapquest can't find an address based on a geocode, even though the geocode for the address came from mapquest. Any ideas why this would be the case?
The fix was simple once I found out the reason for the fail, but it requires recalling the directions with doreservegeocoding set to true, so it's a double whammy for an app that is trying to be frugal. (an extra call PLUS reversegeocoding)
You can see for yourself in POSTMAN
see the difference in results if you change doReverseGeocode to true.
So my question is just what is causing it to fail? mapquest has the address, mapquest has the lat/lng, what is the scenario where it can't match them without a reversegeocode?