Opened 8 months ago

Last modified 8 months ago

#15522 new enhancement

always save layers locally

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


josm has had autosave for a while, and it has saved me a few times.
still, there are at least two cases where a terribly long time spent on editing some area is not visible in the data. the reason is not known - maybe josm crashed, maybe the upload failed behind the scenes, maybe the api ate the changeset. or maybe i'm having vivid dreams about editing osm for hours.

it would be great if there was a way to have "permanent" autosave - one that saves frequently, and be preserved after uploading. for uploaded layers, storing upload time and status would be very useful.

it would be optional, to avoid filling up the disk for unsuspecting users.

Attachments (0)

Change History (3)

comment:1 Changed 8 months ago by mkoniecz

"and be preserved after uploading" permanent preserving all data will quickly cause problems

It would be better to investigate what is causing data to disappear.

comment:2 Changed 8 months ago by richlv

indeed - admittedly, i was thinking about such a feature more as a debug for dataloss. if i remember editing an area and don't remember a catastrophic crash that could have wiped out my edit and all autosaves, but the edit is not there, where do i go from here ?

maybe it was some weird network setup that accepted but nuked my upload, and it never got to the api ? who knows. but without a detailed information on the originating side, i have no information.

comment:3 Changed 8 months ago by richlv

and this is not something that happens frequently. so far, i have two such cases. i vividly remember editing two areas in josm, based on photos - lots of edits, lots of detail, a lot of time spent. in both cases, there's no evidence whatsoever on the server about my edits. no stray autosaves in josm, nothing.

these were years apart. i'm not sure whether there's any other data that might be lost, but with such rare occurrences, it's a bit hard to track down without some debugging data being logged/saved.

Modify Ticket

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