<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><font face="Arial" size="2"> <b><span style="font-weight:bold;">> De :</span></b> Mike <mike.cuttlers@gmail.com><br> </font><br><font face="Arial" size="2"><b><span style="font-weight:bold;">> </span></b></font>I guess you are all both right and wrong on this matter and thus because <br><font face="Arial" size="2"><b><span style="font-weight:bold;">> </span></b></font>you are loking from single angle only.<br><br><font face="Arial" size="2"><b><span style="font-weight:bold;">> </span></b></font>[...]<br><br><font face="Arial" size="2"><b><span style="font-weight:bold;">> </span></b></font>If object is split, one part preserves existing ID and other parts are <br><font face="Arial" size="2"><b><span style="font-weight:bold;">> </span></b></font>considered as new objects with new ID's
assigned.<br><br><br>Hi<br><br>I quite agree with Mike.<br>Properties should have a stable ID and geometrical objects ( way,node,relations) should refer to this ID to be qualified and on the other way it should be possible to find these objects from the ID.<br>By this way it would be easy to refer to a complex object like a motorway or country boundary even if it is made of a lot of subobjects. It would also solve the issue repeating a lot of tags on a lot of objects just because there is one change on part of the way<br>It would be a kind of everything is a "relation" but I'm afraid it could mean a change in OSM API<br><br>my 2 cents<br>Julien<br><div><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;"><br><br></div> </div></body></html>