<html><head></head><body>I would suggest watching Jochens talks on the subject and reading his report, as what you are referring to has been discussed in depth and there are mitigation measures (essentially editor based functionality) that would be part of any migration to a new data model.<br><br>Simon<br><br><div class="gmail_quote">On 6 September 2022 10:25:25 CEST, Marc_marc <marc_marc@mailo.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">Hello,<br><br>Le 06.09.22 à 09:33, Simon Poole a écrit :<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Doing away with shared geometries/nodes<br></blockquote><br>but the real world is full of shared nodes :<br>- a door is a shared node between a highway=* and<br>a building outer<br>- the limit between a wooded area and a grassland<br>is made by shared nodes<br>- etc...<br><br>with disconnected node or way with geometry,<br>you ajust one and lost the the connection with the other<br><br>apart from adding shared=yes on a node to force 2 ways to have<br>a shared node, I wonder how this aspect will be handled<br><br>Regards,<br>Marc<br><br><br></pre></blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br>Diese Nachricht wurde von meinem Android-Mobiltelefon mit Kaiten Mail gesendet.</div></div></body></html>