Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Better change managment on conflicts. #2151

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

Better change managment on conflicts. #2151

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments

Comments

@openstreetmap-trac
Copy link

Reporter: SpeedEvil
[Submitted to the original trac issue database at 9.52pm, Saturday, 8th August 2009]

If you are not saving immediately as you are editing - for example if you're trying to make a housing estate pretty - not uploading roads one by one - then the risk for edit conflict rises.

Also - if you have been editing unfamiliar places - '43334343 Blah street has been changed' - is almost useless. You will almost certainly not remember which way that was - or what shape it was.

I suggest something like after 'download new version' - you zoom onto the area of the way (as an aside - yahoo did not appear when this happened), and say 'The way as you edited it has changed. The selected way is the way as it has been changed. The way as you edited it is flashing in octarine - it will not be uploaded when you press save. You may edit the downloaded way to better match your changes, then save.'

But with better wording.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 10.01pm, Saturday, 8th August 2009]

I assume from the reference to online/offline mode that this is about Potlatch...

@openstreetmap-trac
Copy link
Author

Author: iandees
[Added to the original trac issue at 8.06pm, Monday, 9th September 2013]

Cleaning aging tickets.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant