<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Oct 11, 2022, 14:44 by marc_marc@mailo.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Le 11.10.22 à 14:31, Mateusz Konieczny via Tagging a écrit :<br></div><blockquote>though https://taginfo.openstreetmap.org/keys/crossing%3Aisland is still a property<br></blockquote><div><br></div><div>To caricature your example:<br></div><div>red=yes/no is a technically property<br></div><div>this is not a good idea though,<br></div><div>the hidden characteristic is color and the value is red<br></div></blockquote><div dir="auto">well, yes. Tagging red=yes would be tagging property<br></div><div dir="auto">(this would be a poor tagging scheme and boolean key is not fitting well here,<br></div><div dir="auto">but it would be tagging property of feature rather than being main key)<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote><div>1) never use multiple values in a main key, no tool manages it and<br></div><div> it is not a good idea to describe an object with multiple "features<br></div><div><br></div><div>there are some tools supporting this<br></div></blockquote><div><br></div><div>witch one for ex ?<br></div></blockquote><div dir="auto">someone mentioned some Mapbox rendering<br></div><div dir="auto">but in general, anyone can write tool processing OSM data so<br></div><div dir="auto">claims like "no tool exists using XYZ" are easy to change<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote><div>2) Properties can have a large number of possible values<br></div><div> key with only =yes/no value aren't a propertie, it's the value<br></div><div> for another key<br></div><div><br></div><div>both are properties, ATYL page is just confusing and should be fixed<br></div><div><br></div><div>I added "or can have short list of valid values" there<br></div></blockquote><div><br></div><div>I find it very strange to reverse the meaning of a sentence on the wiki to promote your vision when I have just opened the discussion<br></div><div>it's unfair<br></div></blockquote><div dir="auto">it was quite obviously wrong/incomplete<br></div><div dir="auto"><br></div><div dir="auto">it was giving following options for all tags<br></div><div dir="auto"><br></div><div dir="auto">- tag is property with many values (like width=*)<br></div><div dir="auto">- tag is main key (like highway=motorway)<br></div><div dir="auto"><br></div><div dir="auto">It was in effect claiming that properties with small number of values<br></div><div dir="auto">are not existing which is not true, there are many limited to yes/no values.<br></div><div dir="auto"><br></div><div dir="auto">if anyone disagrees with this edit - feel free to revert it<br></div><div dir="auto"><br></div><div dir="auto">I did it because I know from my experience that otherwise typical<br></div><div dir="auto">outcome is long discussion and nothing being changed on wiki.<br></div><div dir="auto">My request to people in general: after discussion ends, please<br></div><div dir="auto">make update at OSM Wiki - either to describe consensus or<br></div><div dir="auto">to describe that something is unclear, in both cases ideally<br></div><div dir="auto">with link to the discussion.<br></div> </body>
</html>