On Mon, 11 May 2020 at 13:51, Marc M. <marc_marc_...@hotmail.com> wrote:
> Le 11.05.20 à 14:42, Paul Allen a écrit : > > On Mon, 11 May 2020 at 10:58, s8evq wrote: > > What's you counter argument to the people suggesting that contact:* > > makes it easier for data consumers to gather all contact info in one > > go, instead of hard coding all the possible keys. What if next year > > a new way of contacting comes up? > > > > For mappers, no purpose. They use the editor preset > > your answer is precisely the *problem* in the question > every new contact need a new preset in stead of query taginfo > and show top X contact:* > Good point. And, since we have hundreds of new ways of tagging contacts appearing every day, very much needed. Oh, we don't have new ways of tagging contacts appearing every day. Or even every month. On average, maybe once a year (if I'm being generous). I'm not entirely convinced this is a problem worth solving. same problem for the user of the data. if somebody wants to display > all the details of a shop, he has to make a hardcoded list of phone > website... instead of being able to display all the contacts:* that > the osm contributor has filled in. > Good point. I can't count all the times I've wanted all the contact details of a POI but NONE of the other details like the name, the address, what type of POI it is, etc. Well, actually, I can. Zero. OTOH, there are a lot of times I've wanted to know more about a POI but not been interested in the contact details. But even if you're correct, why are the results of the query tool in standard carto unsuited to your needs? Are you going to propose changes to the tool so that, if the user wishes, it returns only the contact details and no other information about the POI? -- Paul
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
