<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 16, 2021, 20:35 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>This is not a matter of coding, as has been already mention in this<br></div><div>thread, we don't have the 3D data at a global level (or even at a<br></div><div>local level) for anyone to build a service for this with what we have.<br></div><div>And it is not realistic to have the data available in the coming<br></div><div>decades either.<br></div></blockquote><div dir="auto">The same is true for tagging shade as a property on ways.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Fri, Jul 16, 2021 at 8:25 PM Frederik Ramm <frederik@remote.org> wrote:<br></div><blockquote><div><br></div><div>Hi,<br></div><div><br></div><div>On 7/16/21 19:42, bkil wrote:<br></div><div>> Could you perhaps share your reasoning or what needs to be improved<br></div><div>> for you to accept it or could you propose a better alternative?<br></div><div><br></div><div>I'm sorry to have to say it so bluntly, but no improvement can fix this<br></div><div>proposal. Whether something is in the shade or not is dependent on time<br></div><div>of day and time of year. It cannot be mapped as a constant. And even if<br></div><div>you were to qualify that ("at noon during the usually hottest month of<br></div><div>the day") it would still mean that you'd have to split up the way in<br></div><div>tons of mini pieces AND the information would be useless for someone<br></div><div>seeking shade at four in the afternoon. This proposal has so many<br></div><div>problems that it should have been thrown out after the first few<br></div><div>exchanges. It has zero chance of being accepted.<br></div><div><br></div><div>If you want routing in the shade, your router will have to employ a<br></div><div>mathematical model during graph building to derive that property from<br></div><div>nearby shade-giving structures. Yes, that is more complex than the "few<br></div><div>lines of code" that you mention in your wiki page. But we can't pollute<br></div><div>our whole database with derived information just to save someone from<br></div><div>having to do the math.<br></div><div><br></div><div>Bye<br></div><div>Frederik<br></div><div><br></div><div>--<br></div><div>Frederik Ramm ## eMail frederik@remote.org ## N49°00'09" E008°23'33"<br></div><div><br></div><div>_______________________________________________<br></div><div>Tagging mailing list<br></div><div>Tagging@openstreetmap.org<br></div><div>https://lists.openstreetmap.org/listinfo/tagging<br></div></blockquote><div><br></div><div>_______________________________________________<br></div><div>Tagging mailing list<br></div><div>Tagging@openstreetmap.org<br></div><div>https://lists.openstreetmap.org/listinfo/tagging<br></div></blockquote><div dir="auto"><br></div> </body>
</html>