route calculation on device instead of server
When navigating over longer routes, it takes quite some time before the route is calculated and sometimes a server timeout is the result.
can the option be added to opt for local route calculation? This would significantly reduce server load. The option to cancel an ongoing calculation is also nice with this, as well as the choice for local or server calculation.
why does this calculation happen server wise? is this to reduce the mobile data used on the client as not all traffic info is on the client, but is on the server?
-
Anonymous
commented
I don’t understand why I get the router server timeout message but my husband’s phone doesn’t get it. We are side by side in the car. Both using iPhone 8.
-
Dynomight
commented
It’s 2018, this issue should be able to be resolved. You can’t tell me the Waze servers can’t accomplish this, even with all the data it brings in...the server should be able to break into shorter segments as meeded
-
PhoenixofMT Wazer
commented
Not so much to reduce mobile data (though a lot would be required) as to offload the computation required to find the route. Pathfinding is a very computationally intense process but Waze adds even more data (time of day, day of week, time of year) to the computations than just "shortest path". If your phone had to crunch the route across town your patience would probably time out, never mind a very long route that the server has trouble with.