User rank 1 will be able to change a max of 30 street names within per day
Updating primary/alternative street name is both counted. Changing both is counted as 2.
User Rank 2 will be able to delete a max of 10 segments within per day
Deleting your own segments is not limited, but still counted toward the total limit of 10. For example, the user deletes 5 segments other owns, now deletes 5 segments he owns. He can continue deleting his segments but not others.
Other changes
Lock rank to Lock level
Stated what the objects are that can be locked (road segments, junction boxes, enforcement cameras, map comments, or places (PP, AP, or RPP)
Stated that more experienced editor can unlock and provide guidance to the new editor (trying to show we will work with people to help make the map correct)
Added some of the common segment edit types (house numbers and speed limits)
Added example of overlock when road configuration changes but the aerial/street view (and maybe GPS traces) don’t show the change. To prevent inadvertent unfixing of the map.
Clarified about editing with RTCs on a segment, that RTC has to be removed prior to lowering. Also that edits that change road segment id can prevent restoring the RTC when done.
Removed guidance that an AM can update RLC or SC w/in their AM even if adjusted/locked by a higher ranking editor
New sections
Road segment attribute lock, routing preference, headlights required Need R4+
New city name lock - need to be R4+ Note also added in about the CM+ ability to do new city name replace all of the current city name ability thoughts on posting this?
Added section on editor rank lock for 1 and 2
Would also like to incorporate the changes discussed for the rank table from this wazeopedia forum, ex Headlights required. There wasn’t any dissent from Jan 2018.
In the Road closure / real time closure lock section:
Question: Would an editor even be able to remove an RTC on a segment locked above them? I don’t think so. I would remove “The editor should be sure the segment is not also locked above their rank before starting this procedure.” since it implies they can. I would instead clarify that an editor of rank high enough to edit the segment needs to copy down the relevant closure information, remove the closure, and downlock the segment for a lower ranked editor, then reverse all that (uplock, return the closure).
Typo in that same paragraph: “If the segment’s lock is above the editor’s rand and…” - change rand to rank
The headlights required and other new restrictions also need to be added to the table at the bottom and to the Rank template.
This statement needs to be removed from the section on camera lock:
That’s pretty dated. As for removing and re-adding closures, I like the technique of copying the closure over to a nearby dead-end PLR or whatever, removing RTC on the segment of interest, making edits, copying RTC back and then removing on the PLR. If you’re quick enough, it won’t even affect routing. Maybe that shouldn’t be in the wiki though since it is easy to mess up.
That is what I am trying to remove that statement about. I just have “When an editor approves a tracked enforcement camera (speed or red light), the camera is locked at that editor’s rank. An editor with a lower rank may not change / delete the camera; the camera cannot have the lock level lowered.”
Understand on the RTC, I often do that too, but do not think it should be in the wiki since it is an editing shortcut/hack.
Derp, should have read your whole draft. Sorry! As for the draft, the new sections after enforcement camera lock should be promoted. As it is, they appear as sub-section under the camera section, which is surely not what you intended. In the new section headings, is it redundant to use both “rank” and “level”?
Ok I have clarified that the new sections are to be part of the Automatic segment lock section. Was originally trying to keep is short and just what changed. Let me know if the new display is clearer.
I don’t believe it is redundant. Rank refers to editor’s hierarchy; Lock refers to the level of the road segment, place, camera etc. Yes many users use rank and lock interchangeably, but they refer to two different things. An editors rank determines the maximum lock level he or she can handle. But a Rank 6 Champ can lock a road segment to any lock level from 1-6. I used the terminology Editor rank level locks since those locks are determined by the editor’s rank. To me it is precise and correct. If people have better terminology great, more than willing to consider improvements for clarity to all.
Yes, rank and lock are different and must be used properly according to our US terminology, but rank and level are interchangeable. Why not say “Editor rank lock” and remove the “level”? This is the commonly used term in my experience: Snapshot mode is rank-locked to R4+, RTC is rank-locked to R3+, JB is rank-locked to R5+, etc.