Opened 4 years ago
Closed 4 years ago
#2227 closed enhancement (fixed)
Copy between layers without move
| Reported by: | Grant Slater <openstreetmap@…> | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | latest | Keywords: | copy paste layers |
| Cc: | landwirt@…, guillaume.audirac@… |
Description
Copy - Paste between layers, offsets the paste location.
Copy - Paste between layers would be more useful if it kept the same location when pasted to another layer.
Identical location would make copy-paste much more useful for the controlled merging of imported data.
Attachments (0)
Change History (6)
comment:1 Changed 4 years ago by stoecker
comment:2 Changed 4 years ago by Landwirt
- Cc landwirt@… added
I'm working on the building import in Rostock. It would simplify the editing if I could work with two layers and move some edited buildings from one layer to another. Merging layers doesn't help and copy&paste is useless due to the shifted position.
PS: Is there a "Cut" function for cut&paste - can't see it?
comment:3 Changed 4 years ago by Guillaume Audirac
- Cc guillaume.audirac@… added
I suggest the paste not being too shifted, as it is currently far away from the initial position. And it is very useful to use a GPX trace from another layer, to copy it, paste it on the working layer and simplify it with Shift-Y.
A slight shift depending on the zoom factor would be fine.
comment:4 Changed 4 years ago by anonymous
Ticket #2499 has been marked as a duplicate of this ticket.
comment:5 Changed 4 years ago by anonymous
I would be happy if there was a second paste function that gave the choice of it moved or not.
Perhaps <ctrl>-<alt>-P or <ctrl>-<shift>-P for the same location paste.
comment:6 Changed 4 years ago by Gubaer
- Resolution set to fixed
- Status changed from new to closed
In r1887 there is a new "merge selected" action. It merge the selected primitives of the active layer into another layer you can select in a dialog.
It does keep the same location of the original primitives. It behaves like any other merge operation and will remember conflicts if it can't resolve them automatically.
It merges a slightly bigger set of primitives than just the selection:
- nodes are merged as is
- ways are merged including their nodes (even if the nodes are not in the selection)
- relations are merged including new members, even if they are are not in the selection (recursively). members with id>0 are merged as incomplete primitives unless they are in the selection, too.
I'm closing this one for the time being. Please reopen if you feel that there is still something missing.
Layer merging can do what you want. I'm unsure if Copy&Paste really should be modified, as when working in one layer it is better when the position is not identical.