-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option 'has been removed' #1097
Comments
In that case, you ought to leave a note. It is not possible to delete elements with StreetComplete.
…On June 7, 2018 2:20:08 PM GMT+02:00, Pander ***@***.***> wrote:
As, in the Netherlands, post boxes (to send mail) are disappearing
everywhere. When a quest asks for collection times, an option 'has been
removed' is a viable one.
Perhaps a query per county could indicate which kind of SC supported
objects are disappearing with a certain high rate in order to add that
'has been removed' option is a practical addition to a query in that
country or region.
Phone boots and post offices have disappeared all together here, but
that might be an ongoing process in another country, so will more of
certain objects that get outdated.
|
What speaks against creating a note for that purpose? IMO notes should be used in those cases because if it gets removed automatically by StreetComplete in the background and nobody notices it (maybe in a region where not so many mappers are active) there is a chance that somebody just didn't found it and removes it without any noise... |
Notes are also hard to query as different language and wordings are used when some object has been removed. |
Maybe 'needs review' should be added. |
Needs review is for a different purpose.
Review ≠ Resurvey
…On June 7, 2018 2:46:41 PM GMT+02:00, Pander ***@***.***> wrote:
Maybe 'needs review' should be added.
|
Does tag 'needs resurvey' exist? |
It would be very useful to have option like this that would leave a prewritten note. At this moment I need to spam "this object is gone" constantly. It is also not obvious for new users that one should leave note in that case. StreetComplete removing objects is not feasible (I written a longer explanation why in one of duplicates of this issue - not in #459) edit: it was in #1046 (comment) |
So when the note popup is shown just suggest some common text? That sounds good, IMHO. Users can add it with a few clicks, can adjust it/add more information and send the result. |
I thought about silently leaving note, like maps.me is doing but it may be better. |
Is maps.me leaving a note containing a preformatted message? If we used the same, it will be picked up by the same filters (if there are any). Also, leaving a preformatted message in English, makes using a query to collect them all easy. |
Yes, it includes some info allowing to identify object and optional part from user. |
I am not convinced that marking things as deleted (via a note) should be implemented as a "Other answer..." option. "Forcing" the user to leave a note in that case gives him the chance to explain what perhaps in it's stead is there now plus add a photo. A Maps.Me-like staple "has been deleted" note is not that helpful because at least in the case of Maps.Me, it usually requires a resurvey by some other user to acknowledge this. |
So it depends on what has gone. If a business has gone away, the building indeed stays and might have another business using it. Something like a post box, recycle bin or phone booth that has been removed, doesn't leave something else in place. Uploading a 3 MB picture of what isn't there seems a bit too much, IMHO. Especially when such objects are being removed 'en masse'. Perhaps a mixed note could be used. Starting with something which is to to be queried and optionally a custom message after it. What do you think of that? |
Sure, for these, to remove it directly may make sense, but this a little specific to warrant the effort and bug-potential in implementing that the app gains the ability to actually remove elements. |
It turn out that many users were especially confused about questions referring to not existing objects and were unaware that th proper solution is to create note (though many of them figured this out) this change will guide them toward note feature as applicable in case of nonexisting objects fixes streetcomplete#1673 fixes streetcomplete#1097 using a different method
It turns out that many users were especially confused about questions referring to nonexisting objects and were unaware that the proper solution is to create a note (though many of them figured this out) this change will guide them toward note feature as applicable in case of nonexisting objects main negative is increased complexity, more work for translators but as this confusing is quite widespread (mentioned both in talks with more experienced mappers and revealed in testing) it seems to be a worth doing fixes streetcomplete#1673 fixes streetcomplete#1097 using a different method
It turns out that many users were especially confused about questions referring to nonexisting objects and were unaware that the proper solution is to create a note (though many of them figured this out) this change will guide them toward note feature as applicable in case of nonexisting objects main negative is increased complexity and more work for translators but as this confusion is quite widespread (mentioned both in talks with more experienced mappers and revealed in testing with newbies) it seems to be a worth doing fixes streetcomplete#1673 fixes streetcomplete#1097 using a different method
As, in the Netherlands, post boxes (to send mail) are disappearing everywhere. When a quest asks for collection times, an option 'has been removed' is a viable one.
Perhaps a query per county could indicate which kind of SC supported objects are disappearing with a certain high rate in order to add that 'has been removed' option is a practical addition to a query in that country or region.
Phone boots and post offices have disappeared all together here, but that might be an ongoing process in another country, so will more of certain objects that get outdated.
The text was updated successfully, but these errors were encountered: