Changes between Version 1 and Version 2 of Ticket #21594, comment 3


Ignore:
Timestamp:
2021-11-25T11:08:27+01:00 (4 years ago)
Author:
dieterdreist

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21594, comment 3

    v1 v2  
    1 Thank you GerdP, this was it, it happens when they are not sorted. IMHO as long as it is unambiguous (all ways that are combined are part of the same relation and not of others), it should not matter whether they are sorted.
     1Thank you GerdP, this was it, it happens when they are not sorted. IMHO as long as it is unambiguous (all ways that are combined are part of the same relation and not of others, maybe also tag comparison), it should not matter whether they are sorted.
    22The actual warning message is very strong:
    3 "Conflicts when combining ways - combined way is '0 (5 nodes)" is the title. I do not see any conflict at all in this situation.
     3"Conflicts when combining ways - combined way is '0 (5 nodes)" is the title. I do not see any ''conflict'' at all in this situation.
    44
    55Then there is a text which says "the default is to keep the first way and remove the other ways that are members of the same relation: the combined way will take the place of the original way in the relation".
    66
    7 If this is the default, why isn't it at least preselected?
     7If this is the default, why isn't it preselected?
    88
    99On a sidenote, while performing some tests, something really strange happened: made a multipolygon consisting of several outer ways and combined them, and on purpose decided to keep all results in the relation. As a result, the relation editor shows something crazy (2 closed outlines where one is basically 1 way going back and forth), i.e. the thing looks (almost) valid in the relation editor and validation does not see any problem. Please see attached screenshots and data.