extend confict message on upload and provide a button to update. (WAS: warn before upload old/outdated data)

[skyper]

Hi

Thanks for your work

It would be nice if JOSM displays a warning if you try to upload old or outdated data and give an advice/link to update the data first.

This is very useful if an upload fails and if you open an old file for example.

Thanks skyper

r3998

[mjulius]

What criteria do you think would be appropriate for deciding whether data is old or outdated.

[skyper]

Replying to mjulius:

What criteria do you think would be appropriate for deciding whether data is old or outdated.

This is not so easy but maybe something like 6 hours would be ok.
It is not useful if people get this message to often, otherwise they will just ignore it.

Premium goal should be the warning after fail upload. Myself almost missed it twice yesterday after confict resolution.

[mjulius]

Replying to skyper:

This is not so easy but maybe something like 6 hours would be ok.

Whether 6 hours is OK for you depends on your workflow and the area you are mapping in. So, I don't think there is a one-size-fits-all here.

Premium goal should be the warning after fail upload. Myself almost missed it twice yesterday after confict resolution.

When an upload fails there is a message telling you so. What other warning do you need?

[skyper]

Replying to mjulius:

Replying to skyper:

Premium goal should be the warning after fail upload. Myself almost missed it twice yesterday after confict resolution.

When an upload fails there is a message telling you so. What other warning do you need?

A warning and question if modified data has been updated before upload.

[mjulius]

Replying to skyper:

Replying to mjulius:

When an upload fails there is a message telling you so. What other warning do you need?

A warning and question if modified data has been updated before upload.

When one gets a conflict on upload isn't the normal course of action to update, possibly solve conflicts, and re-upload? I don't understand how one could miss the first step here.

[skyper]

Replying to mjulius:

Replying to skyper:

Replying to mjulius:

When an upload fails there is a message telling you so. What other warning do you need?

A warning and question if modified data has been updated before upload.

When one gets a conflict on upload isn't the normal course of action to update, possibly solve conflicts, and re-upload? I don't understand how one could miss the first step here.

It is not even mentioned on the conflict message to update, better even would be a botton to start it.

Seems instead of an extra warning the message needs to be extended.
( Think I found another problem investigating)

[D4RKL3G10N]

Replying to mjulius:

Replying to skyper:

This is not so easy but maybe something like 6 hours would be ok.

Whether 6 hours is OK for you depends on your workflow and the area you are mapping in. So, I don't think there is a one-size-fits-all here.

I agree, maybe we could add another criteria, which is the map area size. The bigger the map area that is being worked upon, the greater the chance of upload conflict. Combining both criteria (time and size), we could define the time when warnings show upm for instance like this: for a 1km² area, a warning message pops up every 12 hours. Each 1 km² incremented reduces this time by half (2km²=6 hours, 3km²=3 hours,...), up to a certain limit, let's say at most 15 minute warning interval. Plus I'd say the timer should start counting from the last time the file was modified, so people that save the changeset w/o uploading to work at a later time (such as me), get a warning when they open the file whose modified timestamp exceeded the time threshold. Finally, I think maybe this time interval should include an option for the user to define its size, maybe even an option to deactivate the pop-up if he finds it annoying.