<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 4, 2021, 15:13 by osm@tobias-knerr.de:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 04.10.21 14:46, Martin Koppenhoefer wrote:<br></div><blockquote><div>I am wondering what the meaning of the object types for tags is. (on node: yes, etc.)<br></div><div>Is this about possible use? Actual use?<br></div></blockquote><div><br></div><div>I consider it to be about what object types the tag _should_ be used on (either according to proposals/consensus or, failing that, according to what can be inferred about mappers' intention from existing use in the database).<br></div><div><br></div><div>If it was about actual use, it would be redundant with the Taginfo statistics in the same template.<br></div></blockquote><div dir="auto">Not really, due to lack of dedicated area object.<br></div><div dir="auto"><br></div><div dir="auto">Note "not on way" where used for closed ways (landuse=forest)<br></div><div dir="auto"><br></div><div dir="auto">Note "not on relation, except multipolygon" (likely also landuse=forest).<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote>Do we really have tags where usage on certain element types is "forbidden"?<br></blockquote><div><br></div><div>There are plenty of tags which data consumers will (rightfully) not expect to be used on certain element types, and which other mappers will probably treat as an error as well.<br></div><div><br></div><div>For example, a highway=motorway tag on a node is very likely a tagging mistake, and won't be useful for many applications.<br></div></blockquote><div dir="auto">I would say that in many cases it is always a mistake (landuse=forest on<br></div><div dir="auto">unclosed way for example).<br></div><div dir="auto"><br></div> </body>
</html>