Its done that essentially since day one. As Bryce points out doing so keeps the object a valid "area" (and iD makes a valiant effort to stop you from breaking that).

It is also one of my favourite examples in talks why trying to keep things simple for the user is very difficult and some times counterproductive.

Lots of people have had the wtf moment when they come along a multi-polgon consisting of just one ring built from two ways. The problem is that once the user has split the polygon, there is no obvious point in time were you can be sure that the user is finished with it and you could simplify, particularly when you are trying to get the user to save often and early. So the simplification for the iD user comes at the expense of wtf's of everybody else.

Simon

Am 27.10.2020 um 02:05 schrieb Dave F via talk:
Hi

I don't use iD editor much, but I've just discovered it auto-converts closed polygons which are split (Shortcut Key = X) into MP relations.

I'm struggling to comprehend a logical reason for this. Is there one? If there's been a previous discussion which I've missed please post a link.

There's a couple of threads on iD's github issues, bhousel closed them with "wontfix - I Saw A Thing I Didn't Like (but is valid in OSM).

It may be valid, but is it desirable or helpful? I split closed ways, in P2, for various reasons without wanting them to be converted. How many newbies would even know what a MP relation is?

Having them as as split tagged ways is just as "valid". More so, considering splitting long ways is desirable.

DaveF




_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Attachment: OpenPGP_0x4721711092E282EA.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Reply via email to