Learning?

[jasonh300]

It can't be live. No map updates have gone live since december 11. This problem didn't start until the 26th.


Sent from my iPhone using Tapatalk

[CBenson]

I don't really think there is any discrepancy between the statements that "no previous edits are lost" and "the screwed up map is 'live.'" I too have seen sync problems with the live map on my client. However, In my case the screwed live map is for streets that haven't been edited (to my knowledge) in months. I expect the live map to return with these streets and once the new tiles are generated that the map will reflect the map edits that have been saved. (Athough, I'm not betting my house on this expectation.)

[jasonh300]

I retract my earlier statement. The client maps have indeed been updated.

I'm not seeing any problems with it. I'm seeing a change I made on 12/18, although that's one of the few areas that is still out of sync in the editors.

[gettingthere]

Waze had stated that the last tile update process (apx. 1 week ago) didn't complete. So likely they aborted it since it was causing problems and some of those problems are 'live' in the Application.

As I understand it, the date on LiveMap is when the last tile building process completed. But since we know another tile update process was attempted and problems have been spotted, we can assume that some tiles have been updated since Dec 11.

Hopefully they can get the process to complete this weekend to fix up this mess.

[yrrabsille]

A LOT of editing has been lost

[dmcconachie]

A LOT of editing has been lost

Just because you're not seeing things as you expect doesn't mean anything has been lost. We've had issues like this before on both servers and rarely has anything actually been lost. Once support have confirmed a solution/timescale you can begin to assess the impact. There's no point speculating before!

[CBenson]

A LOT of editing has been lost

You might want to post over here.

[yrrabsille]

So to update everyone on this topic, It's now been well over a year of driving with Waze back and forth to work. Several months ago it FINALLY caught on that my way was the best and fastest way to work. But as far as going home, it still doesn't have a clue. The routing algorithms for this app are utterly obsessed with getting me to the highway first, and then getting me home, even though that's the longest way I know. When I initially fire up Waze leaving work, it tells me that it'll take as much as 50 minutes. Little by little as I ignore it's instruction and go my own way, it whittles away at the ETA, fully acknowledging that my way is shorter. Yet it will do it again tomorrow. It only takes me 38 minutes to get home MY way, but day after day it ignores that route. It doesn't even come up as one of the options for alternate routes. I've gone through all my settings over and over again. What gives?

[bgodette]

What gives?

Help us help you. There's zero chance of anything substantially improving without know what the route is as there's only so much the automated (learning) systems can do.

Rereading this whole thread, not once did you mention, or give livemap links or editor links, general start and stop points, or the expected route and/or ideal route. No one here is psychic and we cannot read your mind.

[yrrabsille]

Jesse Doe Rd. Rollinsford, NH
TO
School St. Sanbornville, NH

Preferred route:
left on Church St.
L on Main
L on High
L onto Rte 236
Follow into Berwick, ME and once I cross Rte. 9 it finally catches on to "my" way (because of various one ways and turn restrictions, I wiggle through town, which waze gets right, and come out the other side going NW on Rochester Rd.)
From there it does well