<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>Apr 4, 2021, 19:28 by steveaOSM@softworkers.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>+1<br></div><div><br></div><div>On Apr 4, 2021, at 7:38 AM, Martin Koppenhoefer <dieterdreist@gmail.com> wrote:<br></div><blockquote><blockquote><div>On 4 Apr 2021, at 12:53, Jeroen Hoek <mail@jeroenhoek.nl> wrote:<br></div><div><br></div><div>For the currently proposed landuse=education it shouldn't be harmful to<br></div><div>follow the currently accepted practice of naming landuses where<br></div><div>appropriate. I agree that such naming might point to the need for<br></div><div>further refinement (such as a dedicated 'campus'-tag or a tag for the<br></div><div>'integral child centres' I mentioned, which I suspect have a German<br></div><div>equivalent)<br></div></blockquote><div><br></div><div><br></div><div>I would generally discourage creating features as landuse (with additional tags like campus), because it would essentially block further landuse refinements (you might find different landuse within the same feature)<br></div><div><br></div></blockquote></blockquote><div>Why it would block anything? landuse=* areas may overlap or one landuse=* are<br></div><div>may be inside another landuse=* area.<br></div><div><br></div> </body>
</html>