On Mon, 19 Aug 2019 at 12:16, Warin <61sundow...@gmail.com> wrote: That is a negative for me, I like property tags that can be used anywhere > appropriate. >
The authors of at least one editor disagree with you there. Unless all of the possible values are applicable to all objects for which that property is appropriate, they won't implement a preset for it. If objects of type A get one subset of values but objects of type B get a different subset of values then it won't get implemented. Because they populate drop-downs from the wiki and/or wikidata. In this particular case, all farm animals might be found in zoos but not all zoo animals will be found on farms. Having a common property tag would lead to a drop-down for farm animals including pandas, bears, gold eagles, reticulated pythons, etc. because it would be populated from the same (hypothetical) wiki(data) page that covers zoo and farm animals. I don't necessarily agree with the thinking of those editors in all the cases they've applied it to, but that IS what they think. And if a tag isn't supported by popular editors it won't get used much. In this case, I wouldn't want to have to wade through a drop-down of all zoo animals to add farm animals, so I tend to agree with them. OSM does not have separate height tags for buildings, bridges, signs, > fences etc etc. One tag makes much more sense. > A height is a height is a height, whatever it is applied to. Many zoo animals are not farm animals. A height is a numeric value, a list of animals is a list: editors handle numeric values and lists with different GUI interfaces to make life easier (type in a number versus add items in a list). -- Paul
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
