Hi, Am Mi., 26. Dez. 2018 um 10:13 Uhr schrieb Markus <selfishseaho...@gmail.com>: > I don't see a problem that would prevent using the proposed tags > top_up:<type>[:<brand>]=yes/no for vending machines, ATMs, convenience
Tag-proposals in the form <tag_attr_name>:<type_value->[:<subtype_value>]=yes/no should be avoided. It's shifting values to attribute names! This detracts processing - given we/OSM already have a non-relational key-value schema. Specifically it makes processing with presets and any key-value analysis very hard. And by saying hard I don't mean it's because some programmers may be lazy. It's because having a value as part of an attribute-name is really a wrong data structure. In fact, "<tag_attr_name>:<type_value->[:<subtype_value>] = boolean" has to be officially considered harmful! There are so many tagging alternatives - like the usual tag scheme. :Stefan [1] https://2018.stateofthemap.org/2018/T061-An_excursion_in_to_the_world_of_OSM_tagging_presets/ Am Mi., 26. Dez. 2018 um 10:13 Uhr schrieb Markus <selfishseaho...@gmail.com>: > > I don't see a problem that would prevent using the proposed tags > top_up:<type>[:<brand>]=yes/no for vending machines, ATMs, convenience > stores, kiosks etc. too. > On Wed, 26 Dec 2018 at 09:59, Warin <61sundow...@gmail.com> wrote: > > > > There are some vending machines that offer 'top up' ... how are these to be > > tagged? Together with a payment tag too. > > > > There are some convenience stores that offer 'top up' services .. how are > > these to be tagged? > > > > > > On 26/12/18 19:31, Markus wrote: > > > Hi Daniele, > > > > > > From the proposal page: > > > > > >> It's possible to specify which brand/carrier vouchers are sold with the > > >> key brand=*. > > >> > > >> A bar that sells Vodafone phone vouchers: amenity=bar + top_up=yes + > > >> brand=vodafone > > > The brand=* key specifies the brand of the main tag, here amenity=bar. > > > In your example, this would mean that it's a Vodafone bar. > > > > > > Furthermore, top_up=yes doesn't say whether you can top up mobile > > > phones, public transport cards or something else, for example prepaid > > > credit cards. > > > > > > Therefore i would suggest someting like: > > > > > > top_up:mobile_phone=yes/no > > > top_up:mobile_phone:vodafone=yes/no > > > top_up:mobile_phone:lycamobile=yes/no > > > > > > top_up:public_transport=yes/no > > > top_up:public_transport:oyster=yes/no > > > top_up:public_transport:opal=yes/no > > > > > > top_up:credit_card=yes/no > > > top_up:credit_card:ok=yes/no > > > > > > Regards > > > Markus > > > > > > On Wed, 26 Dec 2018 at 02:45, Daniele Santini <danysa...@gmail.com> wrote: > > >> Link of the proposal: > > >> https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up > > >> Hi, I propose to introduce the top_up=* key to specify whether a > > >> shop/amenity sells top-ups (mobile phone credit recharge vouchers, > > >> over-the-air credit top up and/or public transport credit recharge > > >> vouchers). > > >> Kind regards > > >> -- > > >> Daniele Santini > > >> http://www.dsantini.it > > >> _______________________________________________ > > >> Tagging mailing list > > >> Tagging@openstreetmap.org > > >> https://lists.openstreetmap.org/listinfo/tagging > > > _______________________________________________ > > > Tagging mailing list > > > Tagging@openstreetmap.org > > > https://lists.openstreetmap.org/listinfo/tagging > > > > > > > > _______________________________________________ > > Tagging mailing list > > Tagging@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/tagging > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging