-
Notifications
You must be signed in to change notification settings - Fork 822
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
stop rendering shop=yes [ready for review] #3718
Conversation
Note that all and each shop value except blacklisted Dropping rendering of |
I think with #2415 taken as given this change makes sense but i would be in favor of revisiting the decision of #2415 to render a catchall for shops. We currently have 105k different values for shop=* but only ~850 with more than ten uses - which means that there are nearly as many special choice values for shop=* out there as there are cases of shop=yes and many of them are just typos or pointless synonyms for existing established values. I am kind of inclined to suggest rendering neither shop=yes nor any special choice values - but that would require creating and maintaining a fairly long whitelist of values. While this could be scripted based on taginfo data this is still a maintenance problem. |
Note that script already existed - see https://github.com/gravitystorm/openstreetmap-carto/blob/c17cc64cbf37b96710439b1ca6c64ca73e514883/scripts/shop_values.rb (at that time it whitelisted everything above 100 usages except some explicitly blacklisted entries). I would also support revisiting this decision (AKA reverting #2415) in addition to stopping rendering |
My idea was more of a combined rule - including values that are not on blacklist and either
But the question is not really how the rules should look like exactly but if we want to have a dynamic list of values that needs to be updated on a regular basis. I see this also in relation to #3635 - if a generic shop dot ceases to indicate any shop value and starts indicating a meaningful shop value that would probably somewhat reduce the incentive to add special individual symbols for all kind of shops to separate them from all the meaningless dots. |
Not something that should be blindly used. I created many tag pages on wiki to document specific tag as a horrible mistake. But a good candidate for reviewing page for potential inclusion. |
Though note that potential catch-all removal is a separate project and it is unnecessary to discuss it here. |
I don't believe such list makes sense if there is no person dedicated to "gardening" this particular problem (not a big task, but needed to be done in a regular fashion for a long time). We had a short list of shops once, when there was much more activity in this project, and even then it was abandoned and I'm afraid we would get back to this fiction. At this moment I support removing |
Yes, certainly dropping BTW, I looked at old script that resulted in some updates (of script, OSM Wiki and mailing list). If someone is interested in shop values it is a good idea to look at them. |
Note since #2415 the same logic as used for shop=* was also added for office=*. While it is certainly not necessary to look at all of this (catch-alls and yes-values, shop and office) at once it could help deliberating on these things and trying to find consensus together. |
I opened #3718 (certainly not ready, but posted as PR as I made some updates to an old script). |
Another similar tag to look at is |
fixes gravitystorm#3697 Originally only shop with their own icons were rendered. Later popular shop values were also rendered - as dots without icons. This was deliberate decision to not render tags with mistakes like shop=supermarkte Since gravitystorm#2415 all shop values except 'no', 'vacant', 'closed', 'disused', 'empty' are rendered. Given that any, even never used shop value is rendered and `shop=yes` is unreasonably popular it is desirable to encourage more specific shop tagging. Dropping `shop=yes` may encourage using some new shop values and in some cases people will mistakenly create new tags duplicating existing ones, but standard shop types are still encouraged by using icons. shop tag currently has long tail of unusual shop types (with most tagged correctly - for example `shop=maps`, some shop like this really exist), so data consumers need anyway some strategy for handling rare shop types. `shop=yes` is currenly reported as a tagging mistake by decent validators (for example JOSM and Osmose). Note that this is not deprecation of a tag but stopping to render a deprecated tag. This tag was never considered as a sufficient for tagging shop type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine.
fixes #3697
Originally only shop with their own icons were rendered.
Later popular shop values were also rendered - as dots without icons. This was deliberate decision to not render cases like shop=supermarkte
Since #2415 all shop values except 'no', 'vacant', 'closed', 'disused', 'empty' are rendered.
Given that any, even never used shop value is rendered and
shop=yes
is unreasonably popular it is desirable to encourage more specific shop tagging.Dropping
shop=yes
may encourage using some new shop values and in some cases people will mistakenly create new tags duplicating existing ones,but standard shop types are still encouraged by using icons.
shop tag currently has long tail of unusual shop types (with most tagged correctly - for example
shop=maps
, some shop like this really exist),so data consumers need anyway some strategy for handling rare shop types.
shop=yes
is currenly reported as a tagging mistake by decent validators (for example JOSM and Osmose).Note that this is not deprecation of a tag but stopping to render a deprecated tag.
This tag was never considered as a sufficient for tagging shop type
Test rendering with links to the example places:
https://www.openstreetmap.org/way/237537359 and other now fixed objects, found using http://overpass-turbo.eu/s/H0Q
Before (this place has both node and area with
shop=yes
)After