Modify

Opened 6 years ago

Last modified 5 years ago

#9673 new defect

Create Multipolygon (Ctrl-B) shuffles the ways

Reported by: karljunk Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: create multipolygon Cc:

Description

In Version 6502, I have created a lot of multipolygons using CTRL-ALT-A, which is CTRL-B in version 6767 now. I do not mind the change of the keyboard shortcut (though such a thing should not happen too often). However, a new bug was introduced:

In Version 6502, when I created a multipolygon, the order of ways was exactly as I selected them. In Version 6767, the ways a shuffled somehow. So it is dangerous to use this function for creating multipolygons with more than 3 ways.

Minor issue: In Version 6502, the newly created multypolygon was selected in the relation list. In Version 6767, it is not selected. What I would prefer is that the tag list of the newly created relation is automatically selected, because the next thing I want to do after creating a multipolygon is always adding tags to the relation.

Another small issue: When creating a multipolygon this way, tags that are common to all member ways are transferred to the relation. This is nice. However, maybe disable the transfer for tags that make no sense when attached to a multpolygon, e.g. barrier=fence or highway=track.

Attachments (0)

Change History (6)

comment:1 Changed 6 years ago by naoliv

At least fence_type isn't moved anymore since [6765]. barrier and source too.

comment:2 Changed 6 years ago by simon04

In Version 6502, when I created a multipolygon, the order of ways was exactly as I selected them. In Version 6767, the ways a shuffled somehow. So it is dangerous to use this function for creating multipolygons with more than 3 ways.

The order of relation members shouldn't have changed in the recent versions. Could you please give a reproducible example (which worked before) to ease debugging.

comment:3 Changed 6 years ago by simon04

In 6807/josm:

see #9673 - Select newly created multipolygon in relation list (fixes regression)

comment:4 Changed 6 years ago by simon04

Another small issue: When creating a multipolygon this way, tags that are common to all member ways are transferred to the relation. This is nice. However, maybe disable the transfer for tags that make no sense when attached to a multpolygon, e.g. barrier=fence or highway=track.

It might be easier to specify a few tags that should be transferred? I guess most of the highway tags (like access, lit, …) shouldn't be transferred. On the other side, creating multipolygons out of such objects isn't very common, is it?

comment:5 in reply to:  2 Changed 6 years ago by karljunk

Replying to simon04:

In Version 6502, when I created a multipolygon, the order of ways was exactly as I selected them. In Version 6767, the ways a shuffled somehow. So it is dangerous to use this function for creating multipolygons with more than 3 ways.

The order of relation members shouldn't have changed in the recent versions. Could you please give a reproducible example (which worked before) to ease debugging.

I have created multipolygon 3487476 in northern Norway, a sea. I did first draw the shore as a polygon. Then I split the polygon with Ctrl-P in 14 different ways. Then I labeled them with way1 to way14, clockwise, starting with the way in the West of the sea. Then I selected the ways in the correct order, form 1 to 14, until all ways were selected. Then I pressed Ctrl_B.

comment:6 Changed 5 years ago by Don-vip

Summary: Create Multpolygon (Ctrl-B) shuffles the waysCreate Multipolygon (Ctrl-B) shuffles the ways

Modify Ticket

Change Properties
Set your email in Preferences
Action
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 karljunk
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.