Missing segments

[phantomblack]

I was scrolling my route this morning to get it in the cache. I found lots of areas along the route with missing map data. It doesn't appear segment related I am actually seeing squares with no map or nav data just clear squares. They appear at max zoom and two clicks out, at three clicks out the road data fills in, at 5 clicks out the navigation line fills in.

[OhioStMusicMan]

Last night, after never seeing this issue, it happened numerous times and each time more seemed to be missing. I know I was not the only one in the area to have it happen to as I've seen several URs throughout northern Ohio describing the same problem.

[stevecody]

This problem has returned. It did not occur yesterday but has reoccurred today at the same locations as before. :/

[stevecody]

My problem appears to be resolved in v3.5.1. Initially, after installing the update, I still experienced the missing segments but after killing and restarting the app, the missing segment problem has not reoccurred.

[stevecody]

Interestingly, though, it's not entire editor segments. One location where I left a UR pin the segment is 15,707 meters long (almost 10 miles, a ridiculously long segment that kills any usable traffic congestion reporting, but that's an argument I gave up on). But the short missing pieces of road were in the middle of this long segment.

Wow, that is good information. I really thought it was due to a segment getting marked as bad or something. I was actually considering deleting one offending segment and recreating it to see if it fixed itself. Now I won't bother.

[jwkilgore]

I updated to 3.5 and drove from Tennessee to Ohio on Saturday, then drove back last night. Both times it's exactly like the OP said. Missing map segments in the client at some zoom levels, and continually having it beep and re-calculate the map near those segments.

Interestingly, though, it's not entire editor segments. One location where I left a UR pin the segment is 15,707 meters long (almost 10 miles, a ridiculously long segment that kills any usable traffic congestion reporting, but that's an argument I gave up on). But the short missing pieces of road were in the middle of this long segment.

I was running Waze on an Android (3.5.0.3) and two other people in the same vehicle were running iPhones (3.5), all were having the same problem.

[stevecody]

I have a device that I haven't updated to 3.5 yet. I'll test it out in a few days when I have a chance to drive this route again.

We've had a recent update to the NA tiles and the problem persists. Time for a post to support.

[phantomblack]

After a 750 mile round trip this week. I can say this is a real problem and it is messing up navigation. I left lots of UR's and all the roads look good in the editor. The route was working great but this trip Waze was continually re-calculating or telling me to head to the nearest road. Sometimes there would be no road on the client other times I was shown on the road but Waze was still telling me to head to the nearest road, very strange. Several times Waze tried to direct me off the interstate to avoid a missing segment.

Things were working great but I updated just prior to this trip so I would put my money on app issue. Maybe time for a full uninstall and fresh load.

[AlanOfTheBerg]

I've been seeing this a lot lately too. I have nearly a dozen screenshots waiting for another map update cycle to see if they clear out automatically. We have seen this happen before and Waze has always had an explanation/excuse.

Whether this is a Map issue, or an app issue, isn't clear.

[jasonh300]

Jhfrontz, if that happens again, send your logs In along with a note to support. Be sure you're set to Debug mode.


Via my iPhone 3GS.