Changes between Version 27 and Version 33 of Help/Concepts/Conflict
- Timestamp:
- (multiple changes)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Help/Concepts/Conflict
v27 v33 4 4 = Conflict = 5 5 6 JOSM locally manages copies of [wiki:/Help/Concepts/Object OSM objects]. It [wiki:/Help/Action/Open loads them from a file] or [wiki:/Help/Action/Download downloads them from the OSM server] and keeps them in memory. If you modify objects or add objects to your map, you are working on copies. The reference objects are still kept on the server from where other users can retrieve them and where other mappers can send their updates to. 6 JOSM locally manages copies of [wikitr:/Help/Concepts/Object OSM objects]. It [wikitr:/Help/Action/Open loads them from a file] or [wikitr:/Help/Action/Download downloads them from the OSM server] and keeps them in memory. If you modify objects or add objects to your map, you are working on copies. The reference objects are still kept on the server from where other users can retrieve them and where other mappers can send their updates to. 7 7 8 This means that you don't ''own'' the objects you are currently working with, you still ''share'' them with others. If you exchange your local objects with the server your version may clash with the version somebody else sent in as update. JOSM does its best to hide these clashes from you, but sometimes it can't resolve the differences between two [wiki:/Help/Concepts/Object versions] automatically. In this cases it creates a '''conflict'''. 8 This means that you don't ''own'' the objects you are currently working with, you still ''share'' them with others. If you exchange your local objects with the server your version may clash with the version somebody else sent in as update. JOSM does its best to hide these clashes from you, but sometimes it can't resolve the differences between two [wikitr:/Help/Concepts/Object versions] automatically. In this cases it creates a '''conflict'''. 9 9 10 10 A '''conflict''' is a difference between two versions of an object which JOSM can't resolve automatically. 11 11 12 Each data layer maintains a list of unresolved conflicts in the [ wiki:/Help/Dialog/ConflictList Conflict List Dialog]. In this dialog you can launch a [wiki:/Help/Dialog/Conflict dialog for resolving a conflict].12 Each data layer maintains a list of unresolved conflicts in the [[JOSMImage(dialogs/conflict)]] [wikitr:/Help/Dialog/ConflictList Conflict List panel]. In this panel you can launch a [wikitr:/Help/Dialog/Conflict dialog for resolving a conflict]. 13 13 14 14 '''Resolving a conflict''' means that you have to decide for every difference between the two object versions whether you want to keep the version from the first or the second object, a process which is sometimes also called '''merging'''. 15 15 16 16 == Conflicts when downloading/updating == #WarningAboutDetectedConflicts 17 If you download objects from the OSM server into an existing layer, the objects from the server might "collide" with objects already present in the layer. Often, JOSM can handle these collisions automatically but sometimes this isn't possible. Here 's anexample:17 If you download objects from the OSM server into an existing layer, the objects from the server might "collide" with objects already present in the layer. Often, JOSM can handle these collisions automatically but sometimes this isn't possible. Here are some examples: 18 18 19 === Automatic management === 20 1. You have downloaded an area. 21 1. You modify the way of a landuse. In the meantime another user downloaded the same zone and deleted 4 nodes from a highway and uploads it. 22 1. You select the menu ''File -> [[JOSMImage(updatedata)]] [wikitr:/Help/Action/UpdateData Update data]''. Some nodes no longer exist on the server even though they are still on your layer. 23 24 JOSM notifies you by displaying the message: 25 26 [[Image(conflict-update-data-automatic.png,link=)]] 27 28 When you click on **Check on the server**: JOSM can resolve this automatically by deleting nodes on your layer that are no longer on the server and do not collide with your modification. 29 JOSM does not create a conflict. 30 31 === Conflict creation === 19 32 1. You've downloaded a node with id:1 from the server whose [osmwiki:Key:name name] tag is set to `"My name"`. 20 33 1. You edit the node and change its name to `"Or is it this name?"`. In the meantime another user downloaded the node too, changed its name to `"That's the name"`, and uploads it. 21 1. You select the menu ''File -> [[ Image(source:trunk/images/updatedata.png,middle)]] [wiki:/Help/Action/UpdateData Update data]''. The version of the node retrieved from the server will have a tag [osmwiki:Key:name name] set to `"That's the name"` which collides with `"Or is it this name?"`, the name you've been setting.34 1. You select the menu ''File -> [[JOSMImage(updatedata)]] [wikitr:/Help/Action/UpdateData Update data]''. The version of the node retrieved from the server will have a tag [osmwiki:Key:name name] set to `"That's the name"` which collides with `"Or is it this name?"`, the name you've been setting. 22 35 23 36 JOSM can't resolve this automatically. It creates a '''conflict'''. Typically JOSM displays an error message as follows: 24 37 25 [[Image(conflict-update-data.png)]] 38 [[Image(conflict-update-data-detected.png,link=)]] 39 40 and creates an unresolved conflict. 41 26 42 27 43 == Conflict when uploading == … … 35 51 JOSM can't resolve this automatically. It creates a '''conflict'''. Typically JOSM displays an error message as follows: 36 52 37 [[Image(conflict-upload-data.png)]] 53 [[Image(conflict-upload-data.png,link=)]] 38 54 39 55 == Conflicts when merging == … … 41 57 If JOSM can't resolve them automatically it creates '''conflicts''' too. 42 58 43 == Resolving conflicts == 44 Each data layer maintains a list of '''conflicts''' which are not resolved yet. You can consult this list in the [ wiki:/Help/Dialog/ConflictList Conflict List Dialog].45 For each '''conflict''' listed there you can (and should) launch the [wiki:/Help/Dialog/Conflict Conflict Resolution Dialog] and resolve it. 59 == Resolving conflicts ==#Resolvingconflicts 60 Each data layer maintains a list of '''conflicts''' which are not resolved yet. You can consult this list in the [[JOSMImage(dialogs/conflict)]] [wikitr:/Help/Dialog/ConflictList Conflict List panel]. 61 For each '''conflict''' listed there you can (and should) launch the [wikitr:/Help/Dialog/Conflict Conflict Resolution Dialog] and resolve it. 46 62 47 63 Resolving conflicts is important. For instance, you can't upload your updates to the OSM server unless the list of unresolved conflicts is empty. … … 51 67 52 68 == See also == 53 * [ wiki:/Help/Dialog/ConflictList Conflict ListDialog] - displays the list of conflicts in the current data layer54 * [wiki:/Help/Dialog/Conflict Conflict Dialog] - you can use the conflict dialog to resolve a conflict 69 * [[JOSMImage(dialogs/conflict)]] [wikitr:/Help/Dialog/ConflictList Conflict List panel] - displays the list of conflicts in the current data layer 70 * [wikitr:/Help/Dialog/Conflict Conflict Dialog] - you can use the conflict dialog to resolve a conflict 55 71 56 72 ---- 57 Back to [wiki :Help Main Help]73 Back to [wikitr:/Help Main Help]
