Modify ↓

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#4571 closed defect (duplicate)

Deleted primitives referenced after update

Reported by: skyper Owned by: team
Priority: blocker Milestone:
Component: Core Version: latest
Keywords: Cc: skyper

Description

Hi

JOSM does not open a justed saved osm-file.

  1. update data.
  2. ignore deleted
  3. solved all conflicts
  4. did some more changes (mostly deleting)
  5. saved osm-file
  6. closed JOSM
  7. start JOSM
  8. opening file failed

I used josm 2998 to do the edits, but does not open the files with 2998 nor 3015.

Attachments (2)

screenshot.png​ (534.5 KB ) - added by skyper 14 years ago.
screenshot
josm_bug_4571.osm.bz2​ (124.6 KB ) - added by skyper 14 years ago.
osm

Download all attachments as: .zip

Change History (6)

by skyper, 14 years ago

Attachment: screenshot.png​ added

screenshot

by skyper, 14 years ago

Attachment: josm_bug_4571.osm.bz2​ added

osm

comment:1 by skyper, 14 years ago

for the original osm look at #4568

comment:2 by mjulius, 14 years ago

Summary: josm produces broken osm-file → Deleted primitives referenced after update

@skyper: Please be as specific as possible in your bug reports. JOSM is refusing to open your file because there is a relation that refers to a missing primitive with ID -5227. The error message is pretty clear about that. This would have been an interesting detail to mention instead of just "broken".

Anyway, I could not reproduce this particular issue, but I noticed that the data contains after update a bunch of ways that refer to deleted nodes.

comment:3 by mjulius, 14 years ago

Resolution: → duplicate
Status: new → closed

comment:4 by mjulius, 14 years ago

Closed as duplicate of #4572.

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 .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.