Modify

Opened 2 years ago

Last modified 2 years ago

#13678 new defect

Problem with closed multipolygon displaying and test

Reported by: naoliv Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: multipolygon Cc:

Description

I am unsure if there is something related with #13677, but validate the attached file and see that there are some warnings about unclosed multipolygons.

But they all seem to be closed, like:

https://i.imgur.com/EUNpS9p.png

↑ this is the relation with id 298025

What is strange is that it seems that all the relation members are downloaded, while they aren't fully visible (there are some missing ways). Asking to download the members the ways are downloaded and appear.

One problem is: shouldn't the test ignore multipolygons/relations with missing members, specially if they are outside the downloaded area?

Another problem is: since it's possible to see that the we can't call Download incomplete members, we can suppose that all the ways are already downloaded. Shouldn't they all be visible?

(I am reporting it against Core for this second problem)

JOSM:

Build-Date:2016-09-21 12:23:43
Revision:11037
Is-Local-Build:true

Identification: JOSM/1.5 (11037 SVN en) Linux Debian GNU/Linux testing (stretch)
Memory Usage: 247 MB / 10206 MB (67 MB allocated, but free)
Java version: 1.8.0_102-8u102-b14.1-2-b14, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1600x900, :0.1 1280x1024
Maximum Screen Size: 1600x1024
Java package: openjdk-8-jre:amd64-8u102-b14.1-2
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-9
VM arguments: [-Dawt.useSystemAAFontSettings=on]
Dataset consistency test: No problems found

Attachments (1)

problem.osm.bz2 (679.8 KB) - added by naoliv 2 years ago.

Download all attachments as: .zip

Change History (4)

Changed 2 years ago by naoliv

Attachment: problem.osm.bz2 added

comment:1 Changed 2 years ago by Don-vip

Keywords: multipolygon added

comment:2 Changed 2 years ago by bastiK

The data file is corrupt, e.g. way 42847113 contains node 536220159, but this node is not in the data file.

Of course it would be nice to show some kind of warning or error in this case.

comment:3 Changed 2 years ago by naoliv

It could warn, indeed.
But there is one problem before this: this file was created with JOSM. If it somehow missed some data, then there is another problem there.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to naoliv
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.