Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#4367 closed defect (duplicate)

merging 2 osm files: incomplete members are not adjusted

Reported by: skyper Owned by: team
Priority: major Milestone:
Component: Core Version: latest
Keywords: confict merge Cc: skyper


I have merged to osm. One had a bigger area than the other. I had several conflicts in route-relations. When trying to solve these conflicts I had some "incomplete" members from the smaller osm-file that had a corresponding complete member on the bigger osm-file. All these members were highlighted as differences.
To solve the conflict I did what I usually do: I take all the members with no differences and the complete members from my (bigger osm-file) with differences + all "incomplete" members from their (smaller osm-file).
I did not get any information that some complete members in my were "incomplet" members in their.
Opening the relation-editor I had several members marked as "doubled", one "incomplete" and one complete. Deleting the complete and keeping the "incomplete" results in data lost because these members are vanished in the merged osm.

I think, these "incomplete" members with a complete member in the bigger osm should be adjusted in conflict-management and they are not "incomplete" anymore.

Thanks skyper

version 2854

Sorry, I did not save before merging -> no osms.

Attachments (0)

Change History (5)

comment:1 by skyper, 14 years ago

Cc: skyper added

comment:2 by skyper, 14 years ago

Priority: normalmajor

comment:3 by skyper, 14 years ago

It happend again and this time a have osm-files. Please look at #4412.

comment:4 by jttt, 14 years ago

Resolution: duplicate
Status: newclosed

comment:5 by anonymous, 14 years ago

Closed as duplicate of #4412.

Modify Ticket

Change Properties
Set your email in Preferences
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.