Modify

Opened 8 years ago

Last modified 4 years ago

#14426 reopened enhancement

"what changed but not yet saved" view

Reported by: nyurik Owned by: team
Priority: major Milestone:
Component: Core Version:
Keywords: diff change upload Cc:

Description

It would be highly useful to have an easy way to view what has changed but hasn't been saved. Something similar to the "history" view, but without downloading the entire history of an object.

Attachments (0)

Change History (8)

comment:1 by Klumbumbus, 8 years ago

There is a mappaint style: Styles/Modified

Last edited 8 years ago by Klumbumbus (previous) (diff)

comment:2 by stoecker, 8 years ago

Resolution: worksforme
Status: newclosed

There is a also a search function for modified objects.

comment:3 by nyurik, 8 years ago

Resolution: worksforme
Status: closedreopened

Clarification: At the moment, there is no easy way to view just what has been modified, rather than seeing the whole history - tags only. For example, if I change a tag on an object, for me to see that change I have to go to the object and click history. Then it shows me the difference between the OSM version and my changes as a side by side diff. The problem is when there are multiple objects changed, I have to go one by one through all of the objects, click history on each (which downloads the whole history, instead of just showing the local changes).

Even better, the "save changes" screen should show a table of all tag changes, combined (e.g. github's diff view, with each object as a section), or alternative view with the same changes combined into one line. E.g. object 1,2,3 tagX valA->valB, object 4,5 tagY valC->valD.

Basically, when uploading, there is no easy way to see what has changed, at least in tags. In Wikipedia, when I change an article, I can click "see diff with existing article", which shows my changes before i save. I think this would be a great addition to JOSM, and will help prevent accidental mistakes.

comment:4 by A_Pirard, 6 years ago

Yes I second that suggestion because it helps not destroying other people's mapping.
I just have before me an "upload check" window where I happened to catch elements I'm not supposed to have modified and I want to check everything anyway.
Some sort of clicking of an uploaded element could display its history with a "next changed" button. This is particularly handy when the elements are unnamed.
"without downloading the entire history of an object" may be too much asking but would in fact limit the comparison to between what's in JOSM memory and what's in the OSM database, no history download at all.
Proof BTW: one element I was not supposed to modify but to create was in fact a supposedly existing, totally tagless element reported by another mapper as "onbekende bushalte verwijderd" (unknown bus stop removed). How I could have modified a removed tagless bus stop is totally mysterious. But I knew I had done no harm.
TIA.

Last edited 6 years ago by A_Pirard (previous) (diff)

comment:5 by Don-vip, 5 years ago

Keywords: diff change added

comment:6 by Don-vip, 5 years ago

Keywords: upload added
Priority: normalmajor

comment:7 by Mashin, 5 years ago

+1

comment:8 by anonymous, 4 years ago

+1

Modify Ticket

Change Properties
Set your email in Preferences
Action
as reopened The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user. Next status will be 'new'.
Next status will be 'needinfo'. The owner will be changed from team to nyurik.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.

Add Comment


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