"Join Overlapping Areas" shows confusing dialogs when merging inner and outer ways of a multipolygon
What steps will reproduce the problem?
- Load attached sample 18744-sample.osm
- select all ways and press Shift+J to "join overlapping areas"
What is the expected result?
A notification that this is not supported, maybe "Cannot join inner and outer ways of a multipolygon"
What happens instead?
Conflict dialog pops up, asking which ways should be kept. Depending on the selection the dialog pops up again, maybe followed by a third popup asking for confirmation that a new way can be deleted.
Build-Date:2020-02-21 09:22:50
Revision:15887
Is-Local-Build:true
Identification: JOSM/1.5 (15887 SVN en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1903 (18362)
Memory Usage: 841 MB / 1820 MB (153 MB allocated, but free)
Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 1920x1080
Maximum Screen Size: 1920x1080
VM arguments: [-agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:58005, -ea, -Dfile.encoding=UTF-8]
Program arguments: [--debug]
Plugins:
+ OpeningHoursEditor (35250)
+ PolygonCutOut (v0.7)
+ apache-commons (35092)
+ buildings_tools (35248)
+ continuosDownload (91)
+ ejml (35122)
+ geotools (35169)
+ jaxb (35092)
+ jts (35122)
+ merge-overlap (35248)
+ o5m (35248)
+ opendata (35330)
+ pbf (35248)
+ poly (35248)
+ reverter (35313)
+ undelete (35313)
+ utilsplugin2 (35248)
Last errors/warnings:
- W: 1 problems occurred during upload/save
Change History
(10)
Description: |
modified (diff)
|
Resolution: |
→ fixed
|
Status: |
new → closed
|
The three popups:



The result is complete garbarge and there is probably no way to avoid that unless user presses Cancel early enough. Pressing Cancel in the last popup is never a good idea.