Opened 2 years ago
Closed 2 years ago
#5963 closed defect (fixed)
[patch] Relation editor fails to detect closed path
| Reported by: | Zverikk | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | latest | Keywords: | relation_analyzer, patch |
| Cc: | Petr_Dlouhy |
Description
Download one of those relations: 1429033, 72196, 1111196. They consist of one closed path (made of several ways), but in relation editor those are not shown as closed. It was ok in tested version, I guess — it cannot be started after josm-latest, so I cannot test it. JOSM 3901.
Attachments (2)
Change History (11)
comment:1 Changed 2 years ago by stoecker
- Cc Petr_Dlouhy added
comment:2 Changed 2 years ago by Zverikk
For relations with one node and multiple ways removing that node solves the problem indeed. But, for example, relation 1059483 not only has a node, but also an unconnected way — but all closed areas are detected and displayed as such.
comment:3 Changed 2 years ago by Petr_Dlouhy
- Keywords relation_analyzer added
comment:4 Changed 2 years ago by Zverikk
More specific: closed path is not detected when a point is located (in the relation members order) inside or right after the area. For example: WWNWWWW (W=way,N=node) first path will be show as unclosed, second path — as closed. NWWWWWW (moving node to the head of the list) — both paths will be detected as closed.
comment:5 Changed 2 years ago by Petr_Dlouhy
I made patch for this issue. I tested only the case, I made for relation_analysis.osm, so please retest your relations.
comment:6 Changed 2 years ago by Petr_Dlouhy
- Keywords patch added
- Summary changed from Relation editor fails to detect closed path to [patch] Relation editor fails to detect closed path
comment:7 Changed 2 years ago by bastiK
Petr_Dlouhy: are you still working on the perfection of this tool? We are going to have a tested version soon, so it would be nice to see some improvement till then.
comment:8 Changed 2 years ago by Petr_Dlouhy
I haven't had enough time recently, but I might safe some time this weekend. I will take look on the remaining issues, but I can't promise to give it a large portion of work, if it became too complicated.
comment:9 Changed 2 years ago by bastiK
- Resolution set to fixed
- Status changed from new to closed
In [3925/josm]:



This is caused by the fact that there is a node in the relation. Seems this case is overlooked now.