GPS layer not updating evidence

[Dave2084]

The A46 junctions with the A6097 and A52 opened to traffic along a new route on 25 November, three weeks later there are still no tracks. The road has been on the live map for about 10 days.

https://world.waze.com/cartouche/?zoom=5&lat=52.96814&lon=-0.96176&layers=BTFFTTTTTTTTTFTTTTT

The new road is a major highway labelled A46 (N) and A46 (S), whereas the old route (which has GPS traces) is now a street and is named Fosse Way (which is an old Roman road if you are interested!)

The few traces that are there were there before the road opened as one of the construction crew seems to be a Wazer (handy for placing the road path before it opens!)

There's still no new traces here even in the new editor.

[douglasr007]

I've noticed the GPS layer updated with the new map editor. The question is to what date.

[CBenson]

Another question would be - when will it be updated again?

[gettingthere]

These questions were already answered to some extent:

* GPS point on the US/Canada server are from mid-December
* Waze is working on a process to keep them updated. ETA unknown, but I suspect it shouldn't be too long.

[gettingthere]

Here is what was posted by Sagi on January 10th when inquiring about the the GPS points layer of the Beta Waze Map Editor:

"The new GPS layer is still experimental and currently does not update at all. When its fully functional it will update about once every few days (current plan is 2-3 days). It will still not show the first and last 500m of your gps points for privacy, and its possible that holds for the case your were viewing."

Since the editor is now released it should be safe to assume that the GPS layer is no longer experimental and is now fully functional.

[petervdveen]

Another question I have is, will it show my own gps traces without the first and last 500m removed, like cartouche used to do?

[foxitrot]

Still reading the same questions about all possible dates, here to what date the GPS traces were updated...

When will Waze Support finally build a true automated Status page (that might contain (a link to) the current occasional blog), which would display:

• up to which date the GPS traces are recent (possibly differentiated between editors, as we can read that their layers are independent),
• up to which date the different maps (client map, LiveMap, routing servers' map, whichever else...) are recent,
• up to which date the different maps will be created, when the currently running process will finish (with an ETA, if at all possible),
• up to which date the different parts of Dashboard items were accumulated into the points (until it will start happening continuously),
• (up to which date the users' routes were merged, if the merger process will ever cease to merge them on-the-fly,)
• any other relevant dates, which the users need and are constantly asking for...
  

and update this info whenever a particular process is being started and finished?

Such page would save sooooooo many questions, answers, confusion and forum posts, that I believe it would be worth investing a few manhours (or at most mandays?) into it.

(Or should such dates be considered being some secret, to be revealed just upon request? I do not think so. Even the HQ could see at a glance, what is the current state and which part of the chain should be addressed with a priority.)

[CBenson]

Since the editor is now released it should be safe to assume that the GPS layer is no longer experimental and is now fully functional.

[gettingthere]

Another question I have is, will it show my own gps traces without the first and last 500m removed, like cartouche used to do?

This is not currently an option in the new Waze Map Editor. Why do you need it? If you want to see your GPS traces you can look at your drives in the new editor.

[RallyChris]

And the status page should not be based on when the job last ran, but how old the queue of data is.

It does us no good, to have a status that says the GPS layer is up to date today, if it relies on data from the route processing layer, and that layer is a week behind. (not saying that is the current case... just an example)