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 .
really is not yet functional, there is something that the community can do to facilitate the completion of the request. send logs or examples of routes to study?
Lysdexia Eht commented
If this is meant to be working, it didn't on a recent drive. I routed and panned the route prior to losing reception, however around 2 hours later towards the end, tiles had failed to load with the final 30 minutes or so a patchwork of missing tiles. This was an approximately 40km mountainous road.
Alex Bonyhai commented
The feature is availabile now. Please close the request!
Dante Barba commented
This is fundamental. Some country roads don't have coverage, and I can't edit the road on WME afterwards.
Agree with everyone else. I used to be a big Waze advocate but lacking this feature is a fundamental flaw for a tragic app. And so begins the downfall of the great Waze...
AC Smith commented
Waze has lost a hell of a lot of credibility in Santa Cruz County this winter. Too many problem areas are out of cell range, and it's impossible to input updates until you're back on line. At which point Waze will auto pop your advisory in the wrong location.
Miki Kadubec commented
I live in the mountains and I only get connectivity in spurts while driving. And it happens a LOT that I don't have sufficient signal to report major road issues like downed trees, mudslides, and accidents - especially this winter! This is something that really really really needs to be addressed.
This has been insane lately attempting to drive alternate routes besides CA-17 after the major rains in the south bay area. There are road closures everywhere, and in most of these backroads, people including me, can't report closures because it's difficult to get a network connection. One major alternate route had lots of cars going through it, yet, no one was able to report the closure due to network conditions. I've been told in the past that Waze doesn't want to support uncommon commuters, but seriously, even highway 17 itself loses connection during some parts.
No Kranky it is not working. When You see there is data, you signal, but sometimes after 20 sec, it doesn't work and Waze say: try later... lol , later I will be 1 or 5 km more far. Waze must stock the signal and send it when data is ok. loading must not be in the center of the map/ screen, very bad idea from the beginning.
They should really allocate what can't be a very large amount of time to get this working properly. It should be able to cache data until the phone runs out of storage space and should be able to then upload everything that is cached when either signal returns or you return to wifi.
Huge issue for me. should be a standard feature. wonder how many reports go unreported!
Since poor net coverage with a very limited access happens everywhere, so we should be able to store the data within the app and upload once the access to net is granted.
This is great. I have this problem many many time
Mac Newbold commented
This is huge for me. I live near a lot of mountains, and cell coverage is often spotty, but when I have no cell coverage, I can't gain any editing area to be able to go home and update the map problems in the area where I just traveled.
It's ridiculous because the amount of data we're talking about is very small. There's no reason this data couldn't be cached on any phone while waiting for a signal again, no matter how long it takes to get a signal again.
Elanor Riley commented
As a map editor, it's extremely frustrating to drive to an area that needs work, only to get back home and realize you received no credit for going out there because the cell signal sucks. We NEED to be able to edit this data, regardless of if we have network signal out there or not. Cache our GPS data or something.
Very frustrating when you drive 6 hours through Norway to find out none of the reports went through nor can i edit the route. The phone was offline (roaming) with the preloaded route from when I left the hotel.
I imagined the data would be uploaded when entering Sweden and acquiring my mobile network back but nop.
Unfortunately this is not a problem only in "extensive rural areas" ...
It happens in urban areas very often.
in a route of 245 km, I get no internet hyper link for 30 ~ 40 kilometers and then it reconnects not more.
even it is 180 km with good quality 4G signal.
Only resolves to close the app and reopen it
The most amazing is the DEVs ignore our requests for help.
How long these claims are already here?
Since it can not solve the problem, at least give us a button "reconnect now" could solve the problem without closing the app and lose all trip data
We can organize a march of users if it who are waiting to give us attention
I have Waze on a WiFi enabled tablet. I have been able to use it when driving away from my house - and therefore losing the WiFi connection. So long as I go the way that Waze recommends, it works. However, if I choose not to use the suggested junction to the motorway - deviating from the Waze route - Waze then tries to find out where I am using the internet. That is a bit tough unless I drive back through my front room. Typically, I know the way to the local motorway network - it it the far end of the journey where I need navigation. Waze needs to be able to determine where I am on the route, even if I have deviated - whether that is by choice or by circumstances.
I notice that this has been an active suggestion for 5½ years, and 5 years since staff replied to it (and ignored it ever-since.) In that time, there are hundreds (if not thousands by now) of apps that are able to lose data connectivity, continue to function and store data and run with what it has locally, and then resume data send/receive when connectivity (either mobile or wi-fi) is restored without missing a beat of functionality. There is no need to end a session and create a new one once data is restored (making the user pay attention to connectivity state - which is dangerous for a driving app) and lose data from the previous session and/or start everything from scratch. Continuing to hide behind such an excuse - especially with the resources of google at their backs - is only a sign of poor programming skills and/or a lack of pride in product.