Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OsmAnd live: rework rank computation #135

Open
bagage opened this issue Oct 23, 2018 · 2 comments
Open

OsmAnd live: rework rank computation #135

bagage opened this issue Oct 23, 2018 · 2 comments

Comments

@bagage
Copy link
Contributor

bagage commented Oct 23, 2018

I'm not sure it's the proper place to address that issue, but I believe that the current rank formula for recipients reward (eg., the more changesets, the better rank) chould be improved:

When you look up first contributors on https://osmand.net/osm_live (sorted by OSM changes), the first ones are simply doing one changeset per node modified (adding tree one by one…).
In the mean time, someone that is importing 100K objects at once (buildings for instance) will do a single changeset. You don't want to have 100K changesets.

In my opinion, these extremes changeset (1K changesets of one node and 10K nodes modified at once) should be both valuated equally. But I believe it should also be equivalent to medium changesets (for instance 10 changesets of 10 modified objects). Maybe these "top contributors" will optimize their rank based on the new formula, but at least it would not encourage people to do lots of small changesets.

@vshcherb
Copy link
Member

As of today we are counting only changesets. Also we are not trying to range users by top 10 or top 100, we are trying to find the 7 mostly ranked group. So if the user wants to be in top 1 group, he doesn't need to make 100K changesets he just need to have 192 (as of October).

Probably we will just our calculation based on number of edited objects in the new year.

@bagage
Copy link
Contributor Author

bagage commented Oct 31, 2018

As of today we are counting only changesets.

I agree with everything you said. It was the point I was trying to address. I do not know which type of users you want to reward the most, but I believe micro mapping trees one per changeset is not the most valuable thing OSMAnd Live buyers want?

number of edited objects in the new year.

As I tried to point out, I think it will lead to many massive bad quality (automatic) imports which is not desirable neither, for OSM's sake. I think best ranked contributors should be the ones who do a valuable job for buyers (eg. useful and properly done mapping).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants