#12556 closed enhancement (fixed)
detect the same way forming a loop by being twice in a multipolygon
Reported by: | aceman | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 16.12 |
Component: | Core validator | Version: | latest |
Keywords: | multipolygon | Cc: |
Description
If a way is a member twice in the same multipolygon and the two occurrences are connected (their index in the relation is n and n+1), JOSM displays the relation fine, with a closed loop in the relation editor. There is also no warning about this. So while this "area" is closed, it is probably useless for a multipolygon.
You can observe this case in the history of way 188885975 .
Attachments (0)
Change History (11)
comment:1 by , 7 years ago
Keywords: | multipolygon added |
---|
comment:2 by , 6 years ago
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The test that produces these messages was introduced with r11157 (3 years ago)
comment:4 by , 6 years ago
Milestone: | → 16.12 |
---|
follow-up: 7 comment:5 by , 6 years ago
I tried to set the milestone but Trac only offers those in the future. Do I need special rights for this?
comment:6 by , 6 years ago
Yes, looks like those validator checks detect this error these days.
Thanks.
comment:7 by , 6 years ago
Replying to GerdP:
I tried to set the milestone but Trac only offers those in the future. Do I need special rights for this?
I wasn't aware of this. Please try to logout/login from Trac, I've given you full rights on milestones.
comment:8 by , 6 years ago
Milestone: | 16.12 |
---|
I see no change. The drop-down list contains only milestones in the future and I cannot edit the field.
comment:9 by , 6 years ago
Oops, seems I have the right to remove the milestone, but I cannot set it to 16.12 :(
comment:11 by , 6 years ago
Milestone: | → 16.12 |
---|
We have the errors
for this, so what is missing?