Open ParzivalWolfram opened 3 weeks ago
Thanks for your interest! However, (and please don't take this personally), I don't think that it is good idea, for multiple reasons:
Firstly, shop=yes
is basically as useless as amenity=yes
. It doesn't tell you anything except that money is exchanged for something else (without any hint of what that something else might be); and as such is more likely to mislead people then help them. It might as well be a node with just fee=yes
on it.
E.g. imagine you're a data consumer trying to make use of that shop=yes
:
You need to buy milk and bread? Bad luck if that shop=yes
turns out to be shop=hardware
. Need USB cable urgently to charge your phone? Well, bad luck as that shop=yes
is shop=greengrocer
. Need to buy some wine as you're late for a dinner with your wife already? Too bad as that shop=yes
is actually shop=fabric
. Want to just buy anything as last-second gift? Too bad, that shop=yes
was actually shop=hairdresser
.
Secondly, making such an exception to not use id-tagging-schema as for all other tags, and even have special warning handling for it, introduces huge coding & maintenance effort forever - for absolutely tiny (if any at all) benefit.
Thirdly, if you're not able to determine type of shop while you're standing in front of it, you're even less likely to be able to do it when you're back at home. So once marked as useless shop=yes
will likely stay that way. We have quests to reduce number of shop=yes
; and not give it a way to easily increase it.
Then, you say "Manual tagging is insufficient due to lack of suggestion/auto-complete requiring switching to a browser constantly to manually verify tagging". I don't follow, as:
yes
to that shop=*
it is just three simple letters - there is not even a need for any fancy suggestion/auto-complete yes
" without help of an external website?Thus, my suggestions if you find indeterminable shops:
shop=yes
. Or,shop=convenience
or shop=hardware
or shop=beauty
etc.). That is actually useful, but takes some effort. Orshop=yes
even when you're home with full desktop power at your fingertips and all the hints left in a note - just delete it (both the note and shop=yes
). Likely nobody else be able to solve it either, and that shop=yes
will just cause people to waste their time and effort. Or, General shop
or whatever and use SCEE raw tag editor to change that shop=general
to shop=yes
. It is just a several clicks (and as you say, we want to discourage that and only use it as a last resort, so it should have even more clicks than that), with very low chance of error (but do proofread that you really wrote "shop=yes"). It will tag what you want, but at the detriment of everyone else. Please try some other solution if at all possible.
Use case Addition of shops that aren't in iD's tag list, or aren't easily identifiable, without adding a note that may go unnoticed for many years at a time due to lack of mappers in most areas. Manual tagging is insufficient due to lack of suggestion/auto-complete requiring switching to a browser constantly to manually verify tagging.
Proposed Solution
Allow for
shop=yes
points to be added as a last resort option, with a nag and requirement of other info before creation. I'd suggest a process similar to the following:Shop (generic)
?) to the list for places.shop=yes
points aren't possible to add in this manner.Automatic addition of
review_requested=yes
to the changeset for these sorts of points might be best.