| 9 | | If there are any differences in tags or relation memberships, JOSM will warn you and open up a dialog to decide manually for each one. |
| | 10 | * The order of selection matters, as the remaining way will keep the [wikitr:/Help/Concepts/Object#ObjectId object id] and [wikitr:/Help/Concepts/Object#ObjectHistory object history] of the first selected way with positive id. |
| | 11 | * The ways need to be connected to each other in their end nodes and need to form a single string otherwise JOSM will show a notification ([#Notification see below]) and refuses the action. |
| | 12 | * All [wikitr:/Help/Concepts/Object#Tags1 tags] with only a single value and all relation memberships from all ways will be added and the [#TagsMembershipsConflictDialog Tags/Memberships Conflict Dialog] will open if manual decisions are needed. In normal user mode it will additionally warn before adding any tag or membership the ways do not have in common. |
| | 13 | |
| | 14 | === Notification ===#Notification |
| | 15 | [[Image(josm_refuse_combine_warning_screenshot.png,link=,right,margin-right=10,margin-left=40,30%)]] |
| | 16 | If the selected ways are not connected in their end nodes and/or do not form a single string a notification is presented with following content: |
| | 17 | {{{ |
| | 18 | Could not combine ways |
| | 19 | (They could not be merged into a single string of nodes) |
| | 20 | }}} |
| | 21 | |
| | 22 | == Combine Confirmation ==#CombineConfirmation |
| | 23 | **Note**: Following warnings are not presented in [wikitr:/Help/ExpertMode Expert Mode]. |
| | 24 | |
| | 25 | === Tag ===#CombineConfirmationTag |
| | 26 | If there is any difference in [wikitr:/Help/Concepts/Object#Tags tags] or conflicting tag combinations, JOSM presents following warning and ask for confirmation.\\ |
| | 27 | The warning lists each conflicting key with its values in brackets and offers two options to hide this warning in future. Choosing "No" will cancel the whole action. |
| | 28 | |
| | 29 | [[Image(josm_combine_confirmation_tag_screenshot.png,link=,margin-left=15,45%)]] |
| | 30 | |
| | 31 | === Relation ===#CombineConfirmationRelation |
| | 32 | If there is any difference in relation membership or role, JOSM presents following warning and ask for confirmation\\ |
| | 33 | The warning lists each involved relation with its name, the number of members and if it is not complete downloaded in brackets and offers two options to hide this warning in future. Choosing "No" will cancel the whole action. |
| | 34 | |
| | 35 | [[Image(josm_combine_confirmation_relation_screenshot.png,link=,margin-left=15,45%)]] |
| | 36 | |
| | 37 | |
| | 38 | == Tags `direction` Conflict Dialog ==#TagsDirectionConflictDialog |
| | 39 | When ways are combined and one of them has to change direction, if on this way there are childnodes with stop, give_way or traffic_signals signs (with keys `*:direction`): JOSM presents a message and suggest to adapt the `forward/backward` value (since r17289). |
| | 40 | |
| | 41 | |
| | 42 | == Tags/Memberships Conflict Dialog ==#TagsMembershipsConflictDialog |
| | 43 | If there is any conflicting tag value, membership or role where JOSM cannot find a solution, the Tags/Memberships Conflict Dialog will open up in order to solve the conflict manually. |
| | 44 | |
| | 45 | The dialog is divided into two parts where the upper part is for tags and the lower part is for memberships and roles. |
| | 46 | |
| | 47 | [[Image(josm_TagsMembership_conflict_dialog_screenshot.png,link=,margin-left=15,45%)]] |
| | 48 | |
| | 49 | === Tags ===#TagsConflictDialog |
| | 50 | [[Image(josm_TagsMembership_conflict_all_screenshot.png,link=,right,margin-left=15,45%)]] |
| | 51 | |
| | 52 | ==== Filter ==== |
| | 53 | On top there are two check boxes to filter the tags: |
| | 54 | * **''Show tags with conflict only''** is checked by default to only show the tags not in common. Unchecking will reveal all tags. |
| | 55 | * **''Show tags with multiple values only''** shows only the tags with conflicts in values |
| | 56 | |
| | 57 | ==== Background Color ==== |
| | 58 | Additionally the background color indicates the conflicts: |
| | 59 | **white** - common tag (no conflict) \\ |
| | 60 | **green** - single value conflict \\ |
| | 61 | **red** - multiple values conflict |
| | 62 | |
| | 63 | ==== Value Column ==== |
| | 64 | With the drop down menus in the value column you can solve the conflicts and remove tags. |
| | 65 | The options are: |
| | 66 | * all single values of the different objects |
| | 67 | * ''**none**'' - the tag will be removed |
| | 68 | * ''**all**'' - all values are used for a key, separated by a semicolon |
| | 69 | |
| | 70 | If the key is representing a quantity like `capacity=*` or `step_count=*` there is one more option: |
| | 71 | * ''**sum**'' - sums up all numerical values of the selected objects |
| | 72 | |
| | 73 | === Memberships and Roles ===#MembershipsConflictDialog |
| | 74 | [[Image(josm_TagsMembership_conflict_membership_screenshot.png,link=,right,margin=15,45%)]] |
| | 75 | |
| | 76 | ==== Memberships ==== |
| | 77 | With the two columns on the far right, **''Keep''** and **''Remove''**, the decision on the membership can be made. |
| | 78 | |
| | 79 | ==== Background Color ==== |
| | 80 | The background colors are: |
| | 81 | **grey** - delete membership, remove object from relation \\ |
| | 82 | **green** - keep membership \\ |
| | 83 | **red** - undecided, needs to be set manually |
| | 84 | |
| | 85 | ==== Roles ==== |
| | 86 | Roles can be changed by editing the entry in the role column or with the **''Role''** text box beneath the membership list. |
| | 87 | ==== Tag modified relations ==== |
| | 88 | On the bottom line are a check box **''Tag modified relation with''** and a text box for **''Key''** and **''Value''** in order to add a tag to all modified relations by checking the box and entering a key-value combination. |
