Modify

Opened 14 years ago

Closed 14 years ago

#4543 closed defect (invalid)

Merge problem: potential defect in merge logic

Reported by: Gubaer Owned by: team
Priority: critical Milestone:
Component: Core Version: latest
Keywords: merge Cc: skyper

Description

Creating a new ticket from a message in #4509, see also attached file.

Not qualifying as r-2010-01-blocker yet, needs analysis first.


Sorry for making so much work, but weekend is over and I am back again.

I think there is still a bug in merging. I have to older osm of the same region. I think the only thing I edit is deleting errors (overlaping way, doubled nodes). I do not find any id:0.

I merge this files and only get conflicts of nodes, but there exist ways in one osm that do not exist in the other one. I think there should be an conflict on but please tell me if I am wrong. Look for the round-about "Siegesdenkmal" and there at the low left. I also noticed that there is no conflict of a relation, but this way (42667459) still exists but lost its membership.

I merged the older file onto the new, but I think it also is not working right the other way round. May we have to open another ticket.

Cheers skyper

Attachments (0)

Change History (4)

comment:1 by skyper, 14 years ago

Keywords: merge added
Priority: normalcritical
Version: latest

comment:2 by skyper, 14 years ago

Cc: skyper added

in reply to:  description comment:3 by mjulius, 14 years ago

Replying to Gubaer:

I merge this files and only get conflicts of nodes, but there exist ways in one osm that do not exist in the other one. I think there should be an conflict on but please tell me if I am wrong. Look for the round-about "Siegesdenkmal" and there at the low left.

Why should there be a conflict? When an object in the source dataset is not in the target dataset it is simply added. That is the point of merging.

I also noticed that there is no conflict of a relation, but this way (42667459) still exists but lost its membership.

Because relation 71504 has a newer version in newer.osm and therefore this version is kept.

comment:4 by Gubaer, 14 years ago

Resolution: invalid
Status: newclosed

Doesn't look like a "conflict" in the sense JOSM is using the term. See #4509 for a discussion on how "potential map anomalies" could be treated in the future.

Closing as invalid.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.