Changes

From Wazeopedia

Map protection

2,815 bytes added, 1 year ago
Manual locks: Rewrite "local concerns" item to be simpler and more general.
==Traffic locks==
Traffic locks (aka - road ranks or segment locks) are the first line of defense when protecting the Waze map from damaging edits.
 
{{TrafficLocksDisabled}}
===How it works===
====Automatic lock rank====
This is the default calculation. In each country, Waze automatically manually changes some of the parameters according to:<br />
- Community size<br />
- Management methods<br />
99.5% - 100% - Rank 5+<br />
The calculation process occurs about once/month in an effort to keep all locks up to date.
 
==Manual locks==
 
Many regions have established minimum manual locks depending on road type or Place status. Please check your [[Mapping resources|state's Wazeopedia page]] for details.
 
Editors with sufficient rank may choose to lock objects higher than regional standards require, based on tradeoffs of ''exposure, risk, value, stability, obscurity,'' and ''local concerns''. These tradeoffs are detailed below.
 
*''Exposure'' reflects the number of ranking editors likely to have editing access to the location. It is highest at large international airports and popular international destinations.
 
*''Risk'' is the likelihood that an intentional construction (or omission) may be mistaken for an oversight. Risk is greatest for complex constructions that involve subtle knowledge or difficult tradeoffs, or that appear to depart from common practice. Risk also accompanies constructions that may appear incorrect due to obsolete street-view data, inaccurate GPS Points, or out-of-date or misregistered aerial imagery. Sometimes even an ordinary red turn restriction may be at risk due to careless use of basemap editing tools. Risk may be reduced with the use of a [[Map comment|Map Comment]], but this is no guarantee of protection; some editors may not have their Map Comment layer enabled, and others relying on automated tools may not be looking. ''(Note: Places are subject to an additional kind of risk from intentional or unintentional "trojan horse" place-update requests whose thoughtless acceptance could lead to Place corruption or deletion.)''
 
*''Value'' is highest for popular and infrastructure-critical roads and destinations.
 
*''Stability'' reflects the expected necessity of future editing. A less-stable location, such as one subject to frequent closures, may benefit if it is locked low enough that local regular editors can be responsive.
 
*''Obscurity'' means how long a counterproductive change to the location might endure before someone notices and fixes it.
 
*''Local concerns'' involve particular map objects known to local editors to require additional protection.
 
Balancing these tradeoffs may lead to manual locks that at first glance seem surprising. For example, the main street of a large but essentially rural town with few visits by editors may be locked at 5, while the main street of a major city subject to frequent closures due to parades and other events may be locked at 4.
 
When departing from regional locking standards, it is always useful to include a [[Map comment|Map Comment]] describing why the departure was necessary. Meanwhile, Map Comment or not, higher-ranking editors encountering a highly-locked construction should always attempt to understand it, perhaps contacting the apparent author, before using their rank to change it or lower its locks.
==Throttling==
==Regression Checker==
Regression checkers is a tool currently in the WME beta, which further assists in protecting the quality of the map. Regression checker warns editors of edits which might harm the map and/or cause map issues. This tool does not work in conjunction with the throttling system, but is an additional layer of protection to overall map quality.
===How it works===
====What the user sees====
After each save, the user will see one of three save results:
Save succesful successful - everything is cool.
Warning - Potential issue. A list of the issues appears and their locations. The user needs to review the issues and decide if they’d like to move ahead with the edits.
Error - Serious potential issue. A list of the issues appears and their locations. The user needs to review the issues and fix them. Only then will they be able to save again.
1,173
edits