Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

Aid new mappers in inactive mapper areas #148

Open
bkowshik opened this issue Apr 11, 2017 · 3 comments
Open

Aid new mappers in inactive mapper areas #148

bkowshik opened this issue Apr 11, 2017 · 3 comments

Comments

@bkowshik
Copy link
Contributor

With osm-compare, we have traditionally tagged changesets that are suspescious and/or potentially harmful. But, the osm-compare and osmcha 🤝 has a whole world of possibilities to explore. This I think is one such interesting idea.

With our recent context based validation work, we have touched areas where we use the existing features on the map to validate a new incoming feature. We could potentially use a similar context about the number of active mappers in the region to aid new mappers editing in non-active mapper zones.

Workflow

  • For features from new mappers on OpenStreetMap
  • Check, if edits are in an inactive mapper area. An inactive mapper area could potentially be derieved from:
    • Number of days any feature in the area has been touched in the last X days.
    • Number of unique mappers who have touched features in the area in the last X days.
  • For all new mapper edits in inactive mapper areas, label those changesets in osmcha as New mapper in inactive mapper area
  • The osmcha community then can filter out these changesets, 👀 them and aid new mappers when necessary with tips, etc.
  • With this, the hope is to aid new mappers on OpenStreetMap (yes, in a small way) to become long-term contributors to this amazing project. 🤗

cc: @planemad @batpad

@willemarcel
Copy link
Collaborator

@bkowshik It's a very good idea. One question: how would you determine the mapper area? Would it be the area of the changeset?

@bkowshik
Copy link
Contributor Author

Thank you @willemarcel

Area of the changeset

The area of the changeset could be really covering a large area in some cases even though the features themselves are just a few. For the changeset below, there is one feature in Thailand and another in Italy. So, area of the changeset would not be very useful.

changeset-bbox

Area around the feature

How I am thinking about this is as follows:

  • Given that a new user creates edits a feature on an island in Thailand.
  • Get the appropriate pre-calculated tiles over the region that contain active mapper counts.
  • If number of active mappers in the region, based on the number of mappers and number of mapping days is less
  • Label the changeset on osmcha as New mapper in inactive mapper area

@willemarcel
Copy link
Collaborator

@bkowshik for very small changesets it wouldn't work to use its area as well, for example a changeset that just edited a couple of closer POIs or buildings.

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

No branches or pull requests

2 participants