<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>Jul 4, 2021, 08:00 by bkil.hu+Aq@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>How would you specify the kind of shade, like whether it comes from a<br></div><div>man_made feature or foliage (tree or hedge)? <br></div></blockquote><div dir="auto">By mapping objects in detail as you described:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto">As an alternative, it would be possible to map each and every tree and<br></div><div>hedge, along with its taxon, height and crown_diameter, each fence<br></div><div>with fence_type and each building and other structure in 3D, each<br></div><div>sidewalk with exact material and geometry and compute shading based on<br></div><div>that, but this sounds like much more work<br></div></blockquote><div dir="auto">Do you see some workable solution? Tagging say shade=* tag would <br></div><div dir="auto">require ridiculous way splitting (in some cases, near every single tree)<br></div><div dir="auto">and/or require massive conditional syntax.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"> and it is implausible in<br></div><div>most parts of the world in the foreseeable future<br></div></blockquote><div dir="auto">shade=* also is implausible and would cause more negative effects<br></div><div dir="auto"><br></div><div dir="auto">And super detailed data is more objective, easier to verify, usable also for<br></div><div dir="auto">other purposes and more likely to be collected and easier to maintain.<br></div><div dir="auto"><br></div><div dir="auto">I also suspect that it may be also actually easier to collect.<br></div> </body>
</html>