PM sent. Will give the editor two days to respond before requesting they be blocked.

No response to my PM yet either. Their editing rights have been revoked and they have been asked to contact me or @CivicDuty29.

Response received: "I was just copying the google maps. Since google did buy Waze."

There has been no contact from the editor from my response to their "because google" answer. Their forum account now shows "Anonymous" in the PM, so I believe they have requested removal.

We will have to clean up the mess ourselves.

nhanway wrote:

daknife wrote:I think you miss-understand what locking a dead end road does. It doesn't prevent Waze from sending you on a U-turn. Locking doesn't affect any actual routing events or actions. It only limits editors.

You have to qw the end node to get it to not give u-turn instructions.

Copied this from the editing restrictions wiki page:

"The Waze server can alter road directionality, shape, and turn restrictions based on tracking real-world driving, via GPS inputs. It only does this on unlocked segments and junctions (that is, those locked at rank 1)."

Waze server automatically changes turn restrictions if a couple of wazer's turn thru the restricted turn. So locking does keep editors from editing but it also keep Waze's servers from editing...

1. 'qw' an end node? You just need to set the u-turn to hard restricted. 'q' does this from the parent node automatically with JNF installed. No 'w' about it.

2. "Locking" is all of the time now. That paragraph really refers to the old locking system where a segment could be locked or not (boolean). Before you locked them at rank 2, they were already locked at rank 1. Now, a segment is considered "locked" if an editor edits it in any manner.

That paragraph needs some work to be updated to today's editor environment.

Kent, the info is good, but I wonder how much "history" we should be putting into operational-style instructions and guidelines. If we still want it, perhaps the "now" comes first and history after?

But honestly, what purpose does the historical info serve in assisting editors right away? I understand that it could be interesting, but I don't see it as something which should be included in current operational guidelines. Think about a service desk that you call in for help with your computer. It would not be helpful to them to have pages of previous information about other operating systems or apps which are no longer in use, or the history of Microsoft outlook, just to get to the part about Outlook 2013 and a problem they are having with that one. Only if the historical information is actually relevant to today, should it be included. I see it as only a potential source of confusion.

I just PMed the Regional Coordinator for Washington...

I'm cleaning up some of the "chicken pox" now...

Can someone check street naming on these segments? https://www.waze.com/editor/?lon=-122.1 ... 8,54568939

I think we need the history mentioned in there somewhere - there are other places the info is located, so when someone finds the old info, we can point to the current info and say "that info is old, see it says so here"...