<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Errata: link was supposed to be <br></div><div><a href="https://github.com/gravitystorm/openstreetmap-carto/issues/3453">https://github.com/gravitystorm/openstreetmap-carto/issues/3453</a><br></div><div><br></div><div><br></div><div>Dec 31, 2020, 08:59 by tagging@openstreetmap.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><div><br></div><div><br></div><div>Dec 31, 2020, 07:47 by tagging@openstreetmap.org:<br></div><blockquote style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;" class="tutanota_quote"><div><br></div><div><br></div><div><br></div><div>>While it's obvious to a human when looking at the rendered object, it's<br></div><div>>rather difficult to write software to interpret this clearly: an object is<br></div><div>>supposed to be an area or a line, not both<br></div><div>>-- Joseph Eisenberg<br></div><div><br></div><div>OSM elements are rarely interpreted independently of their tags, so I won't be so sure about this one. Of course if a data consumer is to do half of the job, then it's their choice. <br></div><div>Yves <br></div></blockquote><div><br></div><div>The problem is that area processing usually goes like that<br></div><div><br></div><div>- has area=yes -> area<br></div><div>- has area=no -> not an area<br></div><div>- has tags indicating an area (for example leisure=playground) -> area<br></div><div><br></div><div>This would make that much more complicated, with extra step:<br></div><div><br></div><div>if it has tags indicating an area and tags that are usually not an area<br></div><div>and no tags indicating area then object should be split in two, with<br></div><div>some tags going to one, some to another and probably some<br></div><div>going on both.<br></div><div><br></div><div>And such tagging is anyway violation of<br></div><div><a href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element" rel="noopener noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element</a><br></div><div><br></div><div>tl;dr Putting barrier=wall and leisure=playground is a bad idea,<br></div><div>please do not mix a barrier with whatever object is surrounding it<br></div><div>in one object.<br></div><div><br></div><div>PS:<br></div><div>Default map style is right now solving problem by rendering linear barriers<br></div><div>with styled line and area barriers with styled line on the outline.<br></div><div><br></div><div>What makes rendering border areas impossible<br></div><div>See <a href="https://github.com/gravitystorm/openstreetmap-carto/issues/4229" rel="noopener noreferrer" target="_blank">https://github.com/gravitystorm/openstreetmap-carto/issues/4229</a><br></div></blockquote><div><br></div> </body>
</html>