From Wazeopedia

Map protection

3,996 bytes added, 1 year ago
Manual locks: Rewrite "local concerns" item to be simpler and more general.
==How does Waze protect the map from potential damage?==
The Waze Map is updated by a large community of editors around the world with varying levels of experience. As such, there are a few systems in place to protect and uphold the quality of the Waze map from both intentional and unintentional harm.
===Throttling=Traffic locks==The throttling system is a mechanism that detects anomalies in number Traffic locks (aka - road ranks or segment locks) are the first line of edits per time frame and prevents cheaters / scripters to gain points for massive edits. While many scripts are used for positive additions to defense when protecting the Waze map, some scripts cause specific harm with the goal of accumulating points quickly. Scripts used for massive from damaging edits are allowed, but may not always result in the rewarding of points.
=====Why was the throttling system put in place?=====Massive edits / scripts are "borderline" mapping methods. On one hand, they are not necessarily cheating and may have significant contribution to the map, especially in uncharted countries. This is why they are allowed. On the other hand, editors often use them to cheat. {{TrafficLocksDisabled}}
In both cases, editors using them can easily accumulate a HUGE amount of edits & points VERY QUICKLY. If ===How it was only a matter of points works===Every road segment has two lock values in the WME:<br />- the issue wouldn't be of concern. The bigger problem is that it allows users to reach higher editing levels quickly and easily. This is the main issue that the throttling system is meant to fix.Automatic lock rank<br />- Manual rank (aka User lock rank)
====Rank rules====1. The complexity of this situation led to a solution that will not prevent editors from using scripts that may user lock cannot be legitimateset higher than the user's own level.<br /> 2. The goal is rather to avoid 10k edits made in User cannot change a onelock-click-script level that is set to count higher than their own.<br />3. Last edit date does not influence the same way as 10k edits made in two weeks of hard work without scriptsalgorithm.<br />
====Automatic lock rank====This is the default calculation. In each country, Waze manually changes some of the parameters according to:<br />- Community size<br />- Management methods<br />- Activity<br />- Map maturity<br />- Population<br />- Road network characteristic<br />- Road Weight (see below)<br /><br />A road’s weight reflects how busy that segment is and how long it's been on our map. Waze then divides all the segments in the country to half percentiles, removing some very highly weighted segments (because they significantly shift the results). Traffic locks are applied for countries where it's relevant and required. Waze works with the local editing community to understand the correct traffic lock parameters. After a period of beta-testing, the parameters are made live in the WME. ====Manual rank====Use manual lock if the automatic road rank seems insufficient. ====Example parameters (varies by country)====Lowest 97.5% of the segments in the country - are available for everyone to edit (= no automatic lock)<br />98% - 98.5% - Rank 2+<br />98.5% - 99% - Rank 3+<br />99% - 99.5% - Rank 4+<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. ==How Throttling == The throttling system worksis a mechanism that detects anomalies in number of edits per time frame and prevents to accumulate edits and gain points for massive edits. While many scripts are used for positive additions to the map, some scripts cause specific harm with the goal of accumulating points quickly. Scripts used for massive edits are allowed, but may not always result in the rewarding of points.  The system was put in place to prevent cheaters from unfairly racking up points with massive edits. Waze is aware of the value that some scripts have to the map, but also recognize that some scripts are used simply to gain points. The throttling system is in place to allow massive edits, but deter cheating.  ===How it works===
Waze has many thresholds for different types of massive editing activity. Once a limit is reached, the next round of edits results in no additional points. The transaction is followed by a time frame during which edits remain uncredited.
=====Types of editing thresholds=====
Different thresholds exist for each object type (segments, MP, UR, places etc). Some are calculated per minute, some per hour and some per day. The exact numbers are internal and may change occasionally as needed (new scripts, etc).
Please note that the thresholds are high. It is unlikely to reach them when editing manually without using scripts.
=====What is seen when will I see if I’ve reached the limit is reached=?====
Nothing. This is a backend process and invisible in the UI. Edits will go through, everything will look the same, but points will not be granted.
=====Will this block me as an editor?=====
Currently, Waze won't auto-block/lock users due to massive edits. This may change in the future.
 =====If points count is affected by Reset after throttling, when will the system reset?=====
Currently, it takes a few hours to reset your ability to acquire points after edits have triggered the throttling system. The exact timeframe is internal and may change occasionally.
=====Throttling vs. Cheating =====Waze defines cheating as the performing of pointless edits for to the purpose of moving up unfairly in the ranks. Massive edits map that do not add value to the mapunfairly move up in rank. Throttling is one of the current methods we use to identify these types of edits, when done on a massive editsscale. Not all massive edits equals equal cheating , and not all throttling is as a result of cheating behavior. The system currently does not differentiate between “good” and “bad” massive editing behavior. Contributing to the map with the use of scripts and massive editing is allowed, however, may trigger the throttling system.
===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.
=====Purpose==How it works===Regression checker warns editors Every save is analysed against a list of edits which might harm the map possible issues, recent drives in an area, and/current road structure. Waze estimates how correct or cause map issuesrisky an edit is and gives it a risk score.
=====How it works=====Every save is analysed against a list of possible issues, recent drives in an area, and current road structure. Waze estimates how correct or risky an edit is and gives it a risk score. For example - a Ex: A very large change in a busy highway which cannot work with current driving patterns is expected to have a very high risk score, while a small change in a side street which seems to comply with current driving patterns will have a low risk score.
=====What the user sees=====
After each save, the user will see one of three save results:
* '''Save 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. =====Effect of ranks=====
There are different warning and error thresholds for each rank.
Higher ranking users are more likely to get 'successful' where a lower ranking user might only get a warning, and to get a warning where a lower ranking user might get an error.