<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Why not subtag for <br></div><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dlounger">https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dlounger</a><br></div><div dir="auto">?<br></div><div><br></div><div dir="auto">amenity=lounger lounger=wave<br></div><div dir="auto">amenity=lounger lounger=wave_lounger<br></div><div dir="auto"><br></div><div dir="auto">seems better to me as someone can map lounger without classifying<br></div><div dir="auto">it subtype (and we may have ideas to map more lounger classes in<br></div><div dir="auto">future)<br></div><div dir="auto"><br></div><div dir="auto">And mentioning how to distinguish amenity=lounger from<br></div><div dir="auto">amenity=wave_lounger would be useful in either case<br></div><div><br></div><div dir="auto">-----------------------------------------------------------------------<br></div><div dir="auto"><br></div><div dir="auto">"Generalisation should be up to the cartographers and not the mappers."<br></div><div dir="auto"><br></div><div dir="auto">1) it depends on generalization type, some generalisation<br></div><div dir="auto">is unavoidable at time of mapping and makes sense<br></div><div dir="auto">Any classification of real objects (tagging objects in OSM)<br></div><div dir="auto">already is some generalization<br></div><div dir="auto"><br></div><div dir="auto">2) It is not changing that <br></div><div dir="auto"><br></div><div dir="auto">(A) cascading tagging<br></div><div dir="auto">( amenity=general_class general_class=detail )<br></div><div dir="auto"><br></div><div dir="auto">(B) using properties <br></div><div dir="auto">( amenity=general_class property=value )<br></div><div dir="auto"><br></div><div dir="auto">is very often better<br></div><div dir="auto">than (C) direct superdetailed classification<br></div><div dir="auto">- amenity=super_detailed_subtype_a<br></div><div dir="auto">- amenity=super_detailed_subtype_b<br></div><div dir="auto">- amenity=super_detailed_subtype_c<br></div><div dir="auto">- amenity=super_detailed_subtype_d<br></div><div dir="auto">- amenity=super_detailed_subtype_e<br></div><div dir="auto"><br></div><div dir="auto">amenity=wave_lounger sounds to me like using natural=oak<br></div><div dir="auto">rather then natural=tree + separate property for mapping that<br></div><div dir="auto">it is an oak ( say, taxon:en=oak )<br></div><div dir="auto"><br></div><div dir="auto">or historic=memorial_bench instead of historic=memorial memorial=bench<br></div><div dir="auto">or historic=blue_plaque instead of historic=memorial memorial=blue_plaque<br></div><div dir="auto">or... (see other values at <br></div><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/Tag:historic=memorial?uselang=en#Tags_to_use_in_combination">https://wiki.openstreetmap.org/wiki/Tag:historic=memorial?uselang=en#Tags_to_use_in_combination</a> )</div><div dir="auto"><br></div><div>Jul 2, 2023, 00:55 by hungerburg@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Please weigh in on this proposed new tag, here, in the community<br></div><div>forum, in the wiki talk page:<br></div><div><br></div><div>https://wiki.openstreetmap.org/wiki/Proposal:Wave_lounger<br></div><div><br></div><div>Looking forward<br></div><div><br></div><div>_______________________________________________<br></div><div>Tagging mailing list<br></div><div>Tagging@openstreetmap.org<br></div><div>https://lists.openstreetmap.org/listinfo/tagging<br></div></blockquote><div dir="auto"><br></div> </body>
</html>