<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>Jan 6, 2023, 11:50 by valinora@gmx.net:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>To sum up: Coordinates can be used in the same wrong way as OSM id as<br></div><div>they're both not sufficient enough for the use case most people are<br></div><div>using it (indirectly).<br></div></blockquote><div dir="auto">But coordinates can be used correctly (shop updating their location<br></div><div dir="auto">when their location moves).<br></div><div dir="auto"><br></div><div dir="auto">It is impossible to guarantee it with OSM ids (in theory they could check<br></div><div dir="auto">OSM object daily to check whether its id changed but that would be absurd)<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto">There is no visible reason to me why adding another unstable<br></div><div>identifier like the osm id is a bad idea.<br></div></blockquote><div dir="auto">Coordinates are stable, information attached to coordinates can become<br></div><div dir="auto">outdated (shop relocated, landmass moved etc) but coordinate itself is stable.<br></div><div dir="auto"><br></div> </body>
</html>