Single Route Broken into Many Routes

[AlanOfTheBerg]

In theory, data compression should only minimize the data that is being sent to and/from the Waze servers. It should not impact the Way that Waze acts in regards to network disconnects.

I agree with the theory, but the result of that behavior may be that Waze waits longer between uploads of data and therefore intermittent data disconnects may have a less noticeable effect on the route integrity. That's just another theory.

[gettingthere]

In theory, data compression should only minimize the data that is being sent to and/from the Waze servers. It should not impact the Way that Waze acts in regards to network disconnects.

[jcrawford27]

I took a ride on Saturday Oct 15 and just noticed when I logged in that I have several routes on the 15th. Now I did lose service coverage during the route a few times but that shouldn't effect the GPS should it? If it does how is waze going to track the roads in areas where cell service is not yet existing?


Sat Oct 15 2011 20:23:51 2.80 miles
Sat Oct 15 2011 20:01:13 3.73 miles
Sat Oct 15 2011 19:26:56 0.66 miles
Sat Oct 15 2011 16:54:50 1.69 miles
Sat Oct 15 2011 16:04:16 15.81 miles
Sat Oct 15 2011 15:12:54 54.03 miles
Sat Oct 15 2011 10:29:53 1.14 miles
Sat Oct 15 2011 09:54:29 2.00 miles

This is my actual route on Saturday: http://g.co/maps/dvfam

[jcrawford27]

I cannot prove this but when I turned on data compression, I seemed to get much longer routes without being connected. My longest is about 60 miles. I did change several things at the same time though. I have left data compression on since then and have rarely had a route broken into pieces. I suspect they collect many entries and do the compression just before they know they will send the data out.

How do you turn on compression i would like to give it a shot.

[lchamp423]

In theory, data compression should only minimize the data that is being sent to and/from the Waze servers. It should not impact the Way that Waze acts in regards to network disconnects.

I agree with the theory, but the result of that behavior may be that Waze waits longer between uploads of data and therefore intermittent data disconnects may have a less noticeable effect on the route integrity. That's just another theory.

I just turned on data compression. I'll see if that stops my little mini-crashes.

[RickW-NC]

I cannot prove this but when I turned on data compression, I seemed to get much longer routes without being connected. My longest is about 60 miles. I did change several things at the same time though. I have left data compression on since then and have rarely had a route broken into pieces. I suspect they collect many entries and do the compression just before they know they will send the data out.

[RickW-NC]

on waze 3.0, it is Menu->My Waze->Settings->Advanced->Data Transfer.

[rotus8]

I believe this happens when there is no cell data coverage plus no maps in the client for the area. I have found that if I pre-load the maps before traversing a section without data coverage, it doesn't happen.

By pre-load, I mean I scroll the map through the approximate path I will take, waiting for the map to appear while scrolling. I do this when I have WiFi to reduce data usage and speed up the process, but it should also work as long as you have cell data coverage.

[WeeeZer14]

If you lose and regain cell service, that may count as a new session with the Waze servers so the route will appear as multiple pieces. I have seen that occur many times.

Waze is designed to work with an always on internet connection, so areas with limited/no cell service are not guaranteed to work reliably or at all. I have not had any success recording roads in areas with no service.