conflict manager: known elements from their's are named "incomplete"

[skyper]

I just "updated data" -> conflicts.

Trying to solve conflicts on members is quite hard, because known members from their's are named incomplete.
They should get the name instead and they are not incomplete.

I attach a screenshot and my osm-file.

r3074 and sun

[skyper]

screenshot

[skyper]

ID: 62.897

[skyper]

osm

[mjulius]

This happens when relation members are not in the downloaded dataset, e.g. when they are outside the download bounding boxes.

It is certainly not a blocker.

[skyper]

Replying to mjulius:

This happens when relation members are not in the downloaded dataset, e.g. when they are outside the download bounding boxes.

It is certainly not a blocker.

No this happend when using "update data" there for the bounding boxes are equal and the known ways should be the same !!!

It also happens when merging and smaller area (their) to a bigger area (my).

r3081

[anonymous]

Replying to skyper:

Replying to mjulius:

This happens when relation members are not in the downloaded dataset, e.g. when they are outside the download bounding boxes.

It is certainly not a blocker.

No this happend when using "update data" there for the bounding boxes are equal and the known ways should be the same !!!

Yes, but if you have downloaded incomplete members of a relation or somehow else merged relation members into the dataset they might be outside the bounding boxes and not be downloaded when doing update date.

It also happens when merging and smaller area (their) to a bigger area (my).

Of course, because some relation members that are in the bigger area won't be in the smaller area and therefore incomplete in the smaller area dataset.

And please, not everything that is annoying is a blocker. This issue does not cause any real harm. There are ways to find out what those relation members are. They are just not convenient. After all you have a list of most of them on the opposite side of the dialog.

[skyper]

Replying to anonymous:

Replying to skyper:

Replying to mjulius:

This happens when relation members are not in the downloaded dataset, e.g. when they are outside the download bounding boxes.

It is certainly not a blocker.

No this happend when using "update data" there for the bounding boxes are equal and the known ways should be the same !!!

Yes, but if you have downloaded incomplete members of a relation or somehow else merged relation members into the dataset they might be outside the bounding boxes and not be downloaded when doing update date.

No this happend with in the downloaded area but seems to be fixed now. Can not reproduce myself, but I have to say I have uploaded my changes yesterday.

It also happens when merging and smaller area (their) to a bigger area (my).

Of course, because some relation members that are in the bigger area won't be in the smaller area and therefore incomplete in the smaller area dataset.

This was different before and as conflict management is not that easy it is another trap to get caught with. In facts these members are on way with on ID and not 2 different ways. So I guess they should have the same name and yeah they might have been incomplete but through merging they exist and are not incomplete anymore.

And please, not everything that is annoying is a blocker. This issue does not cause any real harm. There are ways to find out what those relation members are. They are just not convenient. After all you have a list of most of them on the opposite side of the dialog.

Yes, with that bug fixed on "update data" you are right. Sorry

[skyper]

with r3313 this also happens if you first download a relation without primitives and afterwards download a small area. All elements of the privious downloaded relation outside downloaded area turn to incomplete in the relation-editor.

[skyper]

Replying to skyper:

with r3313 this also happens if you first download a relation without primitives and afterwards download a small area. All elements of the privious downloaded relation outside downloaded area turn to incomplete in the relation-editor.

Forget that this was my fault.

Sorry

[skyper]

Problem still exists with r3732.

[skyper]

Still some known members shown as incomplete:

relation id: 62897, way id: 27545690

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2012-02-15 02:32:11
Last Changed Author: xeen
Revision: 4934
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2012-02-15 02:44:53 +0100 (Wed, 15 Feb 2012)
Last Changed Rev: 4934

Identification: JOSM/1.5 (4934 en)
Memory Usage: 58 MB / 508 MB (1 MB allocated, but free)
Java version: 1.6.0_18, Sun Microsystems Inc., OpenJDK Client VM
Operating system: Linux

[skyper]

Can not reproduce with r5329, -> fixed.