Changes between Version 33 and Version 34 of Help/Action/MergeNodes
- Timestamp:
- 2020-02-04T13:14:57+01:00 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Help/Action/MergeNodes
v33 v34 11 11 12 12 * The order of selection matters, as the remaining node will keep the position of the last selected node. 13 * Usually the [wikitr:/Help/Concepts/Object#ObjectId object id] and [wikitr:/Help/Concepts/Object#ObjectHistory object history] of the oldest node with lowest id is kept. 13 * Usually the [wikitr:/Help/Concepts/Object#ObjectId object id] and [wikitr:/Help/Concepts/Object#ObjectHistory object history] of the oldest node with lowest, positive id will be preserved (see #17866). 14 * Ways will be silently deleted if their child node number drops below two, see [#WaysToDeleteStillInUse below]. 14 15 * All [wikitr:/Help/Concepts/Object#Tags1 tags] with only a single value and all relation memberships from all nodes will be added and the [wikitr:/Help/Action/CombineWay#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 nodes do not have in common, like Combine Ways, see [wikitr:/Help/Action/CombineWay#CombineConfirmation Combine Confirmation]. 15 16 16 17 17 18 == Can't merge because way still in use == #WaysToDeleteStillInUse 18 The nodes you merge may be part of [wikitr:/Help/Concepts/Object#Ways ways]. If you merge them these "parent"ways may loose one or more of their nodes. In some cases the number of nodes left in these ways may drop below 2. Ways with less than 2 nodes don't make sense and JOSM tries to delete them.19 The nodes you merge may be part of [wikitr:/Help/Concepts/Object#Ways ways]. If you merge them these parent ways may loose one or more of their nodes. In some cases the number of nodes left in these ways may drop below 2. Ways with less than 2 nodes don't make sense and JOSM tries to delete them. 19 20 20 21 In some cases, though, a way to be deleted could still be in use, for instance, because a relation is referring to it. JOSM aborts merging nodes in these cases. Instead, it displays the following warning message: