Opened 10 years ago

Closed 10 years ago

#10019 closed enhancement (fixed)

Order of nodes in relations after unglueing

Reported by: rayquaza Owned by: team
Priority: normal Milestone: 14.05
Component: Core Version:
Keywords: Cc:


Yet another way to break a bus route: ;-)

  • Create two ways (A and B) with a common endnode (N)
  • Create a relation with the following objects: N, A, B
  • Unglue the two ways

Usually one would now delete one of the doubled nodes (so it's no longer doubled). But have a look at the relation: It contains N1, A, B, N2. So you've got a 50% chance to delete the wrong node. A (hopefully) better result would be N1, N2, A, B.

Attachments (0)

Change History (3)

comment:1 by Don-vip, 10 years ago

Milestone: 14.05

comment:2 by skyper, 10 years ago

In general it is a good idea to include the new clone members just below their origin.

comment:3 by simon04, 10 years ago

Resolution: fixed
Status: newclosed

In 7152/josm:

fix #10019 - Order of nodes in relations after unglueing

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.