3 ms·
The answer is crowd sourcing. Everything one person creates or modifies needs to be voted on by multiple people. After x votes and y percent in favour of the ch
by tpetry 6y ago
The answer is crowd sourcing. Everything one person creates or modifies needs to be voted on by multiple people. After x votes and y percent in favour of the change it‘s visible to everyone. The x and y numbers could change depending on the user‘s reputation etc.
Think of it like the stack overflow „tasks“ you are asked to do all the time: review this question, do this, do that ...
- rathel 6y agoBecause of the OSM data model, changes can't be really held in "unaccepted" state. One would run into editing conflicts[1]. On Wikipedia withholding edits until review works in some language versions [2], but because Wikipedia pages are "atoms" that stand on their own, they have it easier. [1] https://learnosm.org/en/josm/josm-conflict-resolution/ https://learnosm.org/en/josm/josm-conflict-resolution/ [2] https://en.wikipedia.org/wiki/Wikipedia:Flagged_revisions/Sighted_versions https://en.wikipedia.org/wiki/Wikipedia:Flagged_revisions/Si...
- matkoniecz 6y agoThis would not work, in nearly all cases there is not enough of mappers to handle this. And anyway real problem is a stale data - especially shops. Data that was wrong from start is rare, OSM has nearly no vandalism. Making easier to verify data is much better idea (one of nicely working things is a StreetComplete Android app - about 20% of shops where I am asked to add opening hours are gone, so I open a note, take a photo and later me or some other mapper removes no longer existing shops)