<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>4 Feb 2020, 17:30 by phil@trigpoint.me.uk:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Tuesday, 4 February 2020, Mateusz Konieczny via Tagging wrote:<br></div><blockquote><div>Universities may have faculties, that often deserved to be mapped separately.<br></div><div><br></div><div>For example university may take a large area, possibly disjointed area across the city<br></div><div>but Faculty of dentistry, Faculty of forestry, Faculty of mathematics etc may be<br></div><div>possible to be mapped as an area/node.<br></div><div><br></div><div>Currently typical way to do that is to either<br></div><div>- map name on building<br></div><div>- create fake amenity=university with amenity=university<br></div><div><br></div><div>It seems to me that amenity=faculty would be useful.<br></div></blockquote><div>Or university=faculty and keep the amenity tag for the overall university, on the relation if it multi-site<br></div></blockquote><div>So you purpose one area with an<br></div><div>amenity=university (maybe multipolygon).<br></div><div>And nodes/areas with just university=faculty?</div> </body>
</html>