You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is by design but perhaps the design is wrong :)
When a user has edited many nodes on ways that get pulled in because they are part of a relation that intersects the defined area, those nodes are all counted towards their score.
One example I encountered was user Keith appeared as a top mapper in the Perth area, but upon closer inspection they had mainly edited lots of coastline in southern / western Australia and not all that much in the defined Perth bounding box.
The text was updated successfully, but these errors were encountered:
This is by design but perhaps the design is wrong :)
When a user has edited many nodes on ways that get pulled in because they are part of a relation that intersects the defined area, those nodes are all counted towards their score.
One example I encountered was user Keith appeared as a top mapper in the Perth area, but upon closer inspection they had mainly edited lots of coastline in southern / western Australia and not all that much in the defined Perth bounding box.
The text was updated successfully, but these errors were encountered: