My initial email:
Alan wrote:Why is routing on the client restricted to about 200 miles, but routing on the Live Map is not? I can make very long routes on Live Map and it works great, but similar routing on the client does not work. They should use the same routing servers, so performance in figuring out the route cannot be the problem. So, why the restriction on the client and when will it be removed?
Alpha wrote:Thank you for your e-mail
We didn't find any problem with routes bigger than 200 miles,
can you please send us the origin and destination point of the route?
(I am wrong about the wiki containing information about the 200-mile route limit in the following.)
Alan wrote:That is not correct. It is all over the forums and I believe in the wiki that the client cannot route farther than 200 miles. When attempted, it returns " Oops. Routing server internal error." it works in live map but not client. At least, iPhone client.
I just tried to route from Sherwood, OR to Hood River,OR and it works fine, but I get the error trying to route to Pendleton, OR.
Alpha wrote:We don't have restrictions on routes over 200 miles, sometimes we have problems with the calculation of long-range routes and the system loses the connection with the server in the middle of the calculation.
it is part of the system limitation but we are working on improving the mechanism for calculating the long-term track routes.
If the problem repeats itself try to reroute again.
Given this, I don't really know if they understand what we are seeing in the client. As I've posted before, Live Map calculates long-distance routes well and quickly.
In the end, Waze says they don't explicitly restrict 200+ mile routes, but there is some other restriction in the system which essentially makes it look this way.