A pharmacy may open in the evenings for prescriptions only.
Your example syntax with "sells:xxx" is another way of approaching it, but it has two disadvantages to my mind. Firstly, to find what the shop sells, you have to access all keys which start with "sells:". The namespace syntax (or whatever you want to call it) is also not officially normalised, so the this means accessing all keys and doing a pattern match on each of them. The second issue is that the value part of the KVP is redundant - the presence of the key is enough. I have an instinctive aversion to modelling multiple values (the real-world situation) onto multiple keys in OSM. It "fixes" the problem in the wrong place, and really just moves the problem. But formalising the colon syntax (documenting it as part of our information metamodel) might help - then we effectively have a proper hierarchy of keys, which can then be stored/indexed/processed appropriately. This would open the doors to many new things... including cans of worms.. Unless the discussion results in a clear consensus on a tagging model for such entities (whether you call them shops, amenities, offices or whatever) it's just a waste of energy. Again. And if a miracle does happen, we can put it on the wiki for all to see and get started on retagging all the others. --colin On 2015-11-02 11:00, Martin Koppenhoefer wrote: > 2015-11-02 10:34 GMT+01:00 Colin Smale <colin.sm...@xs4all.nl>: > >> Indeed.... >> >> So why not tag things objectively instead of discussing what things are >> called in different countries? >> shop=prescription_only_medicines;self_medication;pharmacy_only_medicines;household_cleaning > > I've not yet seen a "prescription_only_medicines" pharmacy, and I support > being pharmacies under "amenity" because they are different to a shop (they > also prepare medicines, are extremely regulated). > >> Doing it this way would of course require support for multi-valued keys >> (semicolons!) which many people are allergic to; > > no, you could do it like this: > sells:prescription_requiring_medicines=yes/only/no .... > sells:sunglasses=yes > .... > > the problem I see is how you would evaluate such a list in order to normalize > it to a few categories. > It's likely not impossible for pharmacies alone, but if you do it for all > businesses selling something, it will get extremely hard and complicated > (long) to do it. And you should know a lot of details about the places for > which you are offering your map... > > Cheers, > Martin
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
