This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Using context for detecting harmful features #112
Comments
@amishas157 It's really a good idea! Context is very important. |
Breaking out overlapping features into a separate ticket: #129 |
A new city or a town created within the radius of the city could be problematic. Ideally, A suburb was wrongly tagged as a town which the same user corrected after 5 days. Yay!!! 🎉 The context here could be that a new city cannot exist very close to an exiting city, town, etc. Would be good learning to brainstorm what other features cannot exist close by on the map. cc: @chtnha |
Related issues (WIP)
Closing this issue for now. Let's reopen when it's required. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@bkowshik brought an interesting idea of context based detection for flagging harmful features.
Following are notes from the discussion we had on this idea :
So far we haven't worked on any feature detector where we use context while doing any detection.
Context can have different meaning here. It can refer to surrounding area where a feature is created or it can also refer to the time when a feature is created. Following are few examples to understand the idea of context better:
☝️ can help in following ways:
@geohacker @batpad @planemad Would be great to hear your thoughts on above and how can we leverage context more to find harmful features.
The text was updated successfully, but these errors were encountered: