Opened 2 years ago

Last modified 2 years ago

#18377 new enhancement

Merge (selection) into a new layer

Reported by: anonymous Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: template_report merge new layer Cc:


What steps will reproduce the problem?

  1. Select any object.
  2. Choose "Merge selection"

What is the expected result?

When there is only one data layer, a useful enhancement would be to ask a user "Would you like the selection to be merged into a new layer?" and provide "Yes" and "No" buttons. "No" could be the default, but "Yes" would be appreciated because currently users have to create a new empty layer first, then make the source layer active again, and then do the desired merge. Likewise, when there are a number of data layers, having "New layer" as an option in the dropdown list of layers would be practical too.

What happens instead?

When there is only one data layer, message "There are no layers the source layer could be merged to." is shown with "Ok" button only.

Please provide any additional information below. Attach a screenshot if possible.

Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-11-01 23:59:01 +0100 (Fri, 01 Nov 2019)
Build-Date:2019-11-01 22:59:57
Relative:URL: ^/trunk

Identification: JOSM/1.5 (15492 en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1909 (18363)
Memory Usage: 1521 MB / 3641 MB (1028 MB allocated, but free)
Java version: 1.8.0_181-b13, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 2736x1824
Maximum Screen Size: 2736x1824
Dataset consistency test: No problems found

+ reverter (35084)
+ undelete (34977)

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.

Attachments (0)

Change History (1)

comment:1 Changed 2 years ago by skyper

Keywords: merge new layer added
Summary: Merge selection into a new layerMerge (selection) into a new layer

I miss this option for merge in general. Right now, I always need to clone my data layer to keep the original layers. This is really a pain when debugging merge/conflict problems.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to anonymous
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.