Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
If anything, the user should be able to decide what to hide.
I, for example, like to add trees to OSM, among other things.
Also, you want to have the possibility of updating the survey date of elements, including trees, swimming pools and highway crossings. Hiding those elements would result in users not checking and thus not updating the survey date. This may result in stale data.
All in all, filtering options would be a nice addition. But the filter definitely needs to be customizable by the user, in my opinion.
Obviously the filter list should be customizable per user. (We all have different point of interest ;) )
I think blocking the creation of filtered elements can prevent some double creation.
For example, if I hide the swimming pool, but at some point want to add one (while forgetting, that it's in the filtering list), it will create a double.
Creating filters can be very dangerous and can lead to the creation of duplicates.
Sometime, one element can be tagged with differentes keys. If you hide "office=travel_agent",
I will try to implement this quickly, but use with caution