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.
This is already working, though not properly and all devices. We are working on improving waze behavior in areas where the connectivity is not good, however, you will still have to start a new waze session with a connection .
The problem there is Waze doesn't immediately reconnect. After a relatively short amount of time it won't reconnect at all, which I still can't believe has not been fixed. It retries periodically for maybe a bit over half an hour, and not long after that it just gives up. Or if it isn't explicitly giving up then there is a bug that prevents it from reconnecting. Quite annoying to lose that much data.
At a much more basic level, Waze users construct the best map of actual cell phone network coverage than anything the cell phone service providers have. So, it was seem reasonable to map coverage based on where the app loses connection and when it returns. This could be used to preload for the "dark" areas, just warn the driver that they are about to lose connection (useful when determining if a voice call is going to drop), and it might be nice in the case of route planning to pick the route with the best network connectivity.
Greg Sully commented
Hi, I appreciate there are / were similar suggestions to this, but Waze already has the architecture in the user interface to include the extra information.
I am not really a coder, but I can work out how to archive this in an interface through a paper designed structure.
At present, when you are out of range of a connection to the Waze servers via a mobile connection or wifi. When you click the report button in the user interface screen (bottom of screen in the right hand corner on my devices). The button in the form of an object, follows a set of rules to log that you clicked the button to report n issue where I presume, the time and location where the button was pushed was logged, so when at a later occasion a similar event logged by annother Waze'er, is backed up by the event you tagged but were unable to log further details due to a network connection failure.
So when it ones to implementing this change, at a very basic level (it's probably not as simple as I am suggesting), in addition to simply logging the time and location, gps if available and other navigation details. A aditional excicutionable action can be included, where aditional information can be included in the data update.
My fear however is a concern over the quantity of data that is being shared may be a underlying issue rather than the simply re-working the current system.
August 1st, 2015 and i don't see it working. This is related to another voted improvement or two. Here is another way of doing so.
Whether the user pre-planned the trip or NOT. Sometimes we get to a destination that has no data connection and from that point want to navigate to another location. Having a chosen geological area saved to cache/storage space, can save a user much fear or not having the map data when they need it.
1) As do the competitors using the open maps, the user has to choice of what geographical area to download to their device assuming they have space.
2) When there is no connection to the live data source, the map can have a darker (maybe black or greyish) background to indicate there is no signal at the moment and the current data in waze might be stale (or inaccurate) but still the user can get where they need to go without needing a data connection since their chosen geo area should be saved in the device storage.
Waze could use some kind of asynchronous control (like JMS) and retry to send notifications until a max period is reached... For example: in case of accident report, then Waze can retry for at most 30 minutes; in case of animals on road, maybe 5 minutes should be ok; and so on. It's really frustrating when I try to report something and receive a feedback like "Ooops, try again in a few minutes". By the way, messages like that don't even make sense, since I don't intend to go back and try again. =/
I'm going to comment just to make this suggestion more visible to Waze creators.
Really, this is the most important improvement you guys have to make. I drive very frequently to a city 300km far away, and the major part of the way I have no data signal. Many times I tried to send warnings and I couldn't. Neither see others warnings.
It seems to me that is easy to improve it. Just save the info on the cache and upload when find any data signal within, let's say, one hour. Then the ones who have not reached the "blind" area yet will receive the warning and it will be saved on the offline navigation for that route. When they reach the warning place, they could say if it is still there or already gone and again, this info will be uploaded when they get data signal.
Something like this.
Please, it will make more sense to a lot of people like me to use Waze on every travel.
Also, the waving movement to activate the voice control does not work when the iphone is on landscape mode. It is very helpful when I use with my motorcycle.
A ideia é antiga, desde 2010, e até hoje não tivemos nenhum parecer, o Waze ainda não salva em cache os dados para envio futuro com base no tempo de duração de cada alerta, a ultima resposta foi em setembro de 1010 pelo Krankyd, ninguem vai fazer nada quanto a isto?
I'm fully agree with earlier comments - this is most wanted feature for active wazers!
How it looks fro my point of view:
1. There definitely shouldn't be such a problem like "no GPS - no report" (mentioned before but anyway); when no GPS but cellular data is available (mostly applicable to tunnels or similar locations) - Waze must be able to approximate position based on this data.
2. In case if 3G/EDGE/LTE or data channel is not available - system should collect everything until communication will be restored. Besides, in some countries mobile operators are switching cellular to voice for 100% in very load environment (traffic jams, underground etc).
3. At least traffic jams details (of course in case of GPS data availability - tunnels are different story) info must be offline collectible (road statistics is too critical to be dependent from this).
4. Let's say upload all the data ASAP or within 24 hrs to Waze servers.
5. Surely "Alerts" menu must be available even in case of cellular data absence but GPS availability (currently iOS version shows warning in such situation and you're unable to continue).
Hope to see this opportunity in future releases (added 3 votes).
Furthermore - I'm ready and happy to participate to beta testing (fortunately have such an experience).
Devices: iPhone 5s & iPad mini 1st gen.
Yoshi, I'm going to paste your comment into a bug report in the beta project. That's something that definitely would be better if you were able to do. I don't see why it couldn't just use your last position as the spot to flag.
Yoshi Josh Portuondo-Dember commented
During Mondays tornado storm in Boston, traffic was at a complete standstill for the ENTIRE airport tunnel- this 2.5 mile stretch was posted as NO traffic delays- because there is no GPS reception in the tunnel - there is cell service though- but Waze does not allow traffic updates to be posted while there is no GPS service :(
Seriously, this is a much wanted feature. I have been using Waze very excitedly knowing that I can earn miles and contribute to the community with my reports, however there is no way to earn miles or report when offline.
There needs to be a feature where user can use Waze and submit reports when offline, then as the user gets online, all that data is uploaded to Waze and user gets miles recorded in their accounts accordingly.
There can be a timeout set, say for example: all reports related data must be synced with Waze servers in a maximum of 24 to 48 hours
Still not working for me (2014) for reports/closures... there's a cell dead spot near me with a common speed trap and at least twice the road has been closed due to a wreck or downed power line and I've never been able to report anything. I'm not in a third world country either, I'm about 25 miles from Washington, D.C. Not sure if it's getting my drives or not but I will check next time I drive that road.
Reporting in areas with intermittent internet access is not working with an iPhone 5S in 2014, even when the session started online. I regularly drive a 20 mile mountain pass where internet access is only available about 50% throughout, and is generally spotty with max 3G (no LTE). Although the map is working in the pass and navigation doesn't hiccup at all, reporting issues is difficult to impossible and will not allow a new report to be created without internet. Since the reporting feature records your position when you initiate the report, and since the navigation continues to work along with visible map position, I would think that caching a report would be possible, pushing it to the network when it's available.
Olivier Delemar commented
I just started using Waze yesterday, and it was the very first drawback I noticed. No data connection, no report. I consider it as THE problem with Waze.
And today I see that this issue is unsolved since 2010! Bye bye Waze. I may be back in 3 years.
This problem are more critical in the developing nation where network connection are still a major problem in the rural or interior area.
Shane Sparky commented
This would be so helpful!!! I hate it when I go to the USA and come back to a wifi area and can't record my routes I drove. I could upload my data via wifi at a McDonald's or something if need be :)
I was driving on an area without network signal. I was unable to report more than 15 speed cameras, 3 accidents, several roadblocks, hazards and so on. It's a terrible failure, it would help lots of people driving around...there were some cities with signal, there it would be possible to upload all those reports. We need an offline data system. It's unbelievable, there are a lot of blind hazards not reported because of this waze failure. Best regards, Daniel Mello
Paulo Lessa commented
Another problem are the segments that one or both of the ends are in area with no signal! They don´t have how to colect velocity to have the average to calculate the best route! This happens even in city areas with bad signal! Or under tunels. Waze could have a small cache and upload the data imediately when have the connection back!
Paulo Lessa commented
I drive a lot on contryside in Brasil, and lot of roads don´t have any cellphone signal, not only 3g, but ANY. So, another day I saw an accident and couldn´t report for the cars coming, if I could, when I god the signal 2 miles after, waze could update the ones that had the route set to that area.
Same thing happens with radars, that I could not put on the road since I can´t enter them on software.
This is crucial for whom drives a lot on roads inside the country!
Thanks a lot,
luis moll commented
please the police to know the waze and put a control in areas with limited cell in road the chile