Change “delete” option #1650

New issue

Open

opened 2021-12-02 16:07:51 +00:00 by meinrad-0 · 1 comment

meinrad-0 commented

2021-12-02 16:07:51 +00:00

(Migrated from github.com)

It would be great if the option to delete a POI ("Place does not exist") actually would delete it in OSM.
There would be 3 main issues:

When to allow a user to delete something (anti-vandalism)
Which traps are there & how to avoid
How to add warnings from OSM notes by other apps

From the Telegram chat the following points were raised:

A minimum number of edits. A minimum time the account should exist. Check if the user was blocked recently. Delete option only enabled when you are close to a POI.Or a combination of the above
See how StreetComplete deals with this. An amenity that is also a node should be blanked, objects that are part of relations should not be offered for direct deleting.
OM, maps.me and other apps (?) add notes in OSM for POI deleted by users. It would be very helpful if those notes can be shown as warnings in OM like "This place probably does not exist". It also helps to clean OSM as the POI could directly be deleted.

It would be great if the option to delete a POI ("Place does not exist") actually would delete it in OSM. There would be 3 main issues: 1. When to allow a user to delete something (anti-vandalism) 2. Which traps are there & how to avoid 3. How to add warnings from OSM notes by other apps From the Telegram chat the following points were raised: 1. A minimum number of edits. A minimum time the account should exist. Check if the user was blocked recently. Delete option only enabled when you are close to a POI.Or a combination of the above 2. See how StreetComplete deals with this. An amenity that is also a node should be blanked, objects that are part of relations should not be offered for direct deleting. 3. OM, maps.me and other apps (?) add notes in OSM for POI deleted by users. It would be very helpful if those notes can be shown as warnings in OM like "This place probably does not exist". It also helps to clean OSM as the POI could directly be deleted.

👍 1

matkoniecz commented

2021-12-03 18:05:57 +00:00

(Migrated from github.com)

An amenity that is also a node should be blanked, objects that are part of relations should not be offered for direct deleting.

special cases are at least:

objects that are within lines (amenity=atm that is also node of a building - in such case it should be blanked but node preserved)

objects that are parts of relations - in SC not offered for direct deletion as exact action depends on situation, sometimes nodes should be blanked from tags and kept, sometimes they should be deleted and removed from relation and so on. What worse future new types of relation may change preferred action

See https://github.com/streetcomplete/StreetComplete/pull/2335 where StreetComplete implemented this (and some related functionality - detecting objects that are likely to not exist anymore)

> An amenity that is also a node should be blanked, objects that are part of relations should not be offered for direct deleting. special cases are at least: objects that are within lines (`amenity=atm` that is also node of a building - in such case it should be blanked but node preserved) objects that are parts of relations - in SC not offered for direct deletion as exact action depends on situation, sometimes nodes should be blanked from tags and kept, sometimes they should be deleted and removed from relation and so on. What worse future new types of relation may change preferred action See https://github.com/streetcomplete/StreetComplete/pull/2335 where StreetComplete implemented this (and some related functionality - detecting objects that are likely to not exist anymore)

This repo is archived. You cannot comment on issues.