Save and later upload client data for areas with limited cell and/or Wi-Fi only users.
The amount of data saved currently is insufficient to allow mapping of vast rural areas. Saving this data when storage is available and later uploading will speed the completion of your goals.
We are aware the status of “In the works” could be misleading. This is an old suggestion and this status is old as well. For now this is not a priority yet so we are changing the status to avoid confusion. We will discuss that internally again and hope to bring better priority ASAP.
This function is working perfectly in 2.2 for me.
All the offline routes (doesn't matter if I start with network connection) were uploaded.
A related issue is when Waze is used during a phone conversation on networks list Verizon's which do not allow data during a call.
Alexander Lifanov commented
Is it possible to show the fullness of send buffer somehow? I've lost several tracks by closing Waze before it has sent the full track. Or, i'd like to have a button "Push the buffer to server NOW!!".
Why do you have to start a session with a connection? And is that going to be fixed? The activity described in my earlier comment should realistically be possible.
I wish more apps would allow some kind of "store now, upload later" functions like that. Paying for internet on a cell phone is still too overpriced in my opinion, even more when I am on prepaid! Im glad that you seem to support it to a point but the more you can add or improve upon it, the better! :-)
Hakan Tandogan commented
I know, I had the very same setup in the last two weeks.
On vacation in Tunesia, no mobile Internet access, but I just wanted to collect tracks for later analysis in waze...
And yes, I am serious too :-)
I should be able to fire up Waze in the middle of the desert with no cell towers or wifi for thousands of miles and record roads. Never having any type of connection for weeks on end. Recording thousands of sessions, and thousands of roads. And come back to civilization, fire up waze on the wifi, and watch as it uploads 3 GB of data.
Yes, I'm serious.
Thank you, it seemed it started working for me last week when I turned on data compression. My longest track is now over 40 miles using iPod touch w/ TomTom gps.
pre-load your surroundings map works great, but recording new roads for later uploading is a must if you want to map areas with poor coverage or where data plans are often limited.
Paulo Abreu commented
Storing all updates and synchronizing later at a Wi-Fi connection would be a marvelous feature! Data traffic is very expensive in Brazil!
Occasionally I drive abroad and would be glad to provide my tracks to those area managers. Unfortunately data roaming charge is way too much to keep phone online. Would be good to download maps offline but even without that I would like to give my contribution to Waze.
please make this happen.
The rural areas that have patchy phone coverage urgently need mapping and new road recording just doesn't happen when there is no network available.
Make those buffers BIG! From what I can see, storing a driven route (1 sample per second) takes less then 30-40KB per hour driving - so there could be stored 20 hours of driving in a MB. I have 1000's of MB free for Waze! To show a small Waze-Icon on the map it would be sufficient to send 1 (one) sample every few minutes.
Also, a complete map costs between 0.1KB (in the desert) and maybe 30KB (in a city) per square kilometer, so there could be 30 to 1000 square kilometers in a MB. Again, I have 1000's of MB available for that.
Trafficinformation is very dense - a set of 20 events may take only a few KB. If I am driving in a foreign country, with dataroaming on, I could get maybe 500 trafficevents in 1 MB for €2. I guess that generating a message on the client does cost a comparable volume. There is an option to block trafficinformation - but from a costperspective that does not make much sense.
All that Waze has to do is:
1. Make those recording- and mapbuffers BIGGER. At best make their limits set by the user.
2. For each set of data - recording, position, mapdata, trafficevents - make it possible to block transmission when not in WiFi. That way users can choose for mapdata and recordingdata could be swapped/updated at home, positioninfo (1 per 5 minutes) trafficinfo on the way. That is how I would use it, probably.
I agree - I live and travel in many rural areas where phone coverage can be poor. Please allow me to select the largest cache I will accept and then cache all data normally uploaded so that it can be uploaded later when coverage is available. Automatic upload via UMTS would be fine for me, or option batch upload would allow me to benefit from WiFi at home.