Waze forum

Drove close to 500km yesterday, over 6 hours period, on the Pacific Highway from Sydney to the mid-north coast. Had Waze running the entire time, with permanent data connection and permanent good GPS reception. What a disappointment it was to discover that only the first 140 km or so are showing in my dashboard the next day. The remaining 350km, all of them were new roads paved, do not show at all. These roads show up on my iPhone but not in cartouche!

I don't know if this is a server problem or a client problem. All I know is that it's a common problem with Waze and plenty of posts in these forums show this.

I was very excited to be one of the "pioneers" in Australia and to contribute to this community effort. I was very disappointed and discouraged after "losing" 350km (I have another 1500km trip ahead).

If this project is to take off in a serious way it needs serious improvements. The fact that map editing is as finikie at best of times is one thing (and I'm sure that it will improve). But when the roads we pave do not show up at all then we have to ask ourselves: "whats the point???"

Y.

Fej, I noticed sometimes the GPS points do pop up, but it doesn't create the roads (nor a route in the archive). To me this seems like a server side problem then?
Also, the last couple of weeks it became worse (I think). After the server split, I did not encounter any of this, and now it's getting worse every day (might be coincidence).

Hope this info might help you, and it's so good to hear you are looking into this problem.

Is it possible that part of your trip happened after the cut-off point for the 'nightly' process run? That starts at 1pm PST/9pm GMT. While possible, it also may not be the case. I lost a huge portion of a 300km trip the other day. I've since had other trips show up in my archive, and it wasn't anywhere near this cut-off point in the day for me, so I know that I've lost that portion of my trip for whatever reason. Strange, because I haven't lost a trip in a pretty long time. Been fairly stable recently, and this was why I had decided to undertake longer trips again. And then one of my longest in a little while gets a huge chunk of it lost. It's pretty annoying for me, because in some cases, such as this one, it was a trip I made for no other reason than to Waze it because I was bored. If I had been out there for some other reason, and Wazed it as a bonus, it would not have been a big deal. Sucks when it's a Waze-only trip and it gets hooped.

Ah, but Fej, I got up to the ski resort, closed Waze, went inside the resort for a few minutes, came back out to my car and started it up, started up Waze again, and headed back down the mountain. *That* trip is missing from beginning to end.

Indeed disappointing and I am extremely sorry for this mishap. We are working to correct this ASAP.
We have got the report earlier from Shorty-CM and are we think we understand the problem relating to new roads recording being miscommunicated from the client, so I hope we have a correction for iPhone ready next week for beta testing (which will of course be at a later stage submitted to the store).
For time being, what might be advisable (as a temporary work around) is to close and reactivate waze every 100 KMs (an hour) or so to reduce (and hopefully eliminate) this phenomenon.

Is it possible that part of your trip happened after the cut-off point for the 'nightly' process run?

my trip started after the cut-off time. indeed the first part of the trip showed up in the archive the next day, but the remaining 350km did not and still don't.
I downloaded the KML files to compare - there are 4 of them. 2 of them show the first part of my trip. one shows 0km and Google Earth displays a point over the Indian Ocean (roughly 7000-8000km from where I am). the last one shows Road Miles in the archive but displays no road segment on the map.