-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Use disused:shop instead of shop=vacant #2707
Comments
I agree According to taginfo: 20K features tagged So it's clear both are popular options so I don't see any issues with SC changing given these healthy stats of current usage. |
Additionally, the information what kind of shop it was doesn't get lost in the object's history but is still visible in the disused state. That might not be helpful for automatic data consumers but for a human contributor. So: Am in agreement for K |
I also would say that But note that SC cannot retag old value of shop, as user has no opportunity to confirm/reject that shop type remain match current Though I would not say that BTW, I tried to find where it is applied to confirm that SC actually uses |
I noticed it in one of my own changesets, created with StreetComplete 30.1 about a month ago. Here is another example from a different user: https://www.openstreetmap.org/changeset/99967499 |
StreetComplete/app/src/main/java/de/westnordost/streetcomplete/quests/shop_type/ShopGoneDialog.kt Lines 69 to 71 in a8973ae
|
Sorry, I did not understand this sentence. More information: On the points made:
|
While
I think it already does that. StreetComplete already asks if
Sure. |
No idea why it exists. Maybe for something like |
? See https://taginfo.openstreetmap.org/tags/shop=no#wiki that links to https://wiki.openstreetmap.org/wiki/Tag%3Ashop%3Dno (it is primarily used on
There could be following sequence of events
|
You are correct, I failed to find this entry. However this wiki page states "Tag |
@matkoniecz Hm well, ok I think this is a rather minor problem though. |
Well, |
While my original argument was, that I wanted to keep the original What if we changed shop=vacant to disused:shop=yes? That value is used 4 times as often as the next value clothes and is also the first thing mentioned on the wiki page as the alternative? |
Streetcomplete doesn't usually "upgrade" tags as long as they are not deprecated.
…On April 1, 2021 8:43:05 AM GMT+02:00, Kai Michael Poppe ***@***.***> wrote:
While my original argument was, that I wanted to keep the original
`shop=*` and just make it `disused:` I can somewhat follow @matkoniecz
in that the state might not be correct in OSM anyway, so just disusing
it wouldn't change much about that being incorrect in the first place.
What if we changed shop=vacant to disused:shop=yes? That value is used
4 times as often as the next value clothes and is also the first thing
mentioned on the wiki page as the alternative?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#2707 (comment)
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
I think the difference between the two options is small and often irrelevant: maybe a vacant shop is more likely to be re-purposed again as a shop (it may have a "for rent" sign on it), while a disused shop is more likely to be on its way to become an abandoned shop? What is more important is that SC can handle new purposes of a vacant shop, which may be another shop, but also a craft, an amenity (bakery, restaurant), an office, a dentist, etc. |
I use both tags shop=vacant and diused:shop=yes as meaning the exact same thing. The shop is empty currently but just needs a new tenant and fit out. |
Yes, but
I guess that it means that if someone cares about it they can write a PR, I am doing it right now :) |
If a shop is closed StreetComplete removes all tags and adds
shop=vacant
. This tag has become rather controversial, though. This place is no longer a shop, so it shouldn't get tagged as a shop. Also, every data consumer needs to add a special handling forshop=vacant
, i.e. for excluding it when rendering shops. Therefore it would be better to use the lifecycle prefix instead, i.e.disused:shop=<former shop value>
.The text was updated successfully, but these errors were encountered: