<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 22, 2022, 11:43 by marc_marc@mailo.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Le 22.07.22 à 10:35, Mateusz Konieczny via Imports a écrit :<br></div><blockquote>How you will avoid importing buildings demolished in 2014 and deleted since?<br></blockquote><div><br></div><div>it's the same issue with manual tracing no ?<br></div></blockquote><div dir="auto">Not in areas with more recent imagery.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><div>imho this is one of the reasons to use life cycle tags : if I delete<br></div><div>in osm a building destroyed yesterday and still present on all the imagery, it risks to be added again (because nowadays, the majority<br></div><div>of the buildings are traced from the imagery and not by going to make gps surveys all around each building<br></div><div>let's use was:building or destroyed:building or something similar + end_date for the few years it takes to update sat imaging<br></div></blockquote><div dir="auto">it makes sense to keep them until locally preferable imagery is up to date<br></div><div dir="auto"><br></div><div dir="auto">It does not make sense to keep them forever just because someone has <br></div><div dir="auto">dataset of machine-generated buildings from 2014 Bing imagery.<br></div><div dir="auto"><br></div> </body>
</html>