<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>"but may not explain in the project
instructions how a "non-standard" building should be mapped"<br></div><div dir="auto"><br></div><div dir="auto">Especially in areas where such buildings are typical it is failure on HOT side and<br></div><div dir="auto">should be remediated on their side. If someone is looking for newbies and instructing<br></div><div dir="auto">them to edits it is their responsibility to provide necessary instructions to avoid ending<br></div><div dir="auto">with poor edits. I am quite surprised that this problem was not spotted so far by them,<br></div><div dir="auto">given HOT focus on building geometries.<br></div><div dir="auto"><br></div><div dir="auto">Though making some easy to use documentation would be useful in general.<br></div><div><br></div><div><br></div><div>Dec 16, 2021, 00:21 by jwhelan0112@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>What I'm interested in is something a new
mapper (probably HOT) can refer to when they are mapping. So it needs
to be fairly comprehensive to stop the young ladies and gentlemen from
being a little too creative in their tagging.<br></div><div> <br></div><div> HOT asks them to map buildings but may not explain in the project
instructions how a "non-standard" building should be mapped and I'm
seeing some very creative efforts as I search for duplicate buildings.<br></div><div> <br></div><div> Cheerio John<br></div><div> <br></div><div> <span>Martin Koppenhoefer wrote on 12/15/2021 6:03 PM:</span><br></div><div> <br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">Am Mi., 15. Dez. 2021 um 23:45 Uhr schrieb
John Whelan <<a href="mailto:jwhelan0112@gmail.com" rel="noopener noreferrer" target="_blank">jwhelan0112@gmail.com</a>>:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
solid rgb(204,204,204);padding-left:1ex" class=""><div>I'm noticing new mappers attempting to map more complex buildings. Do
we have something to cover an internal courtyard, a multi level building
ie
religious has a spire etc.<br></div></blockquote></div><div><br></div><div><br></div><div>there is
man_made=courtyard <a href="https://wiki.openstreetmap.org/wiki/Tag%3Aman_made%3Dcourtyard" rel="noopener noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Tag%3Aman_made%3Dcourtyard</a><br></div><div>for
multilevel buildings, it depends on the level of detail and aspects you
are interested in.<br></div><div><br></div><div>Things on different levels
(POIs) can get a level=* tag (not to be confused with layer) <a href="https://wiki.openstreetmap.org/wiki/Key:level" rel="noopener noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Key:level</a><br></div><div><br></div><div>if
you want to map the amount of levels, it is building:levels=n (plus
underground levels and roof levels, which have their own tags). <br></div><div><br></div><div>It
is even long standing, documented practice to map non existing levels,
voids, empty space, with the tag "building:min_level" (you get the value
by counting levels that do not exist), but these are borderline ;-)<br></div><div><br></div><div>Cheers,<br></div><div>Martin<br></div></div></blockquote><div><br></div><div class=""><div>-- <br></div><div> <br></div><div>Sent from <a href="https://www.postbox-inc.com" rel="noopener noreferrer" target="_blank"><span style="color:
rgb(0, 157, 247);">Postbox</span></a><br></div></div></blockquote><div dir="auto"><br></div> </body>
</html>