Opened 3 years ago

Closed 8 months ago

#19288 closed defect (fixed)

Split way: Wrong position of new member with duplicate members used in different directions

Reported by: skyper Owned by: skyper
Priority: normal Milestone:
Component: Core Version:
Keywords: template_report split way route relation order duplicate member Cc:

Description (last modified by skyper)

This is a followup of #18596 and might be a duplicate of #19217, #18018 and #21856.

What steps will reproduce the problem?

  1. Have a PTv2 relation having the same ways multiple times as member running along in different directions, see josm_split_way_duplicate_members_example.osm.
  2. Split one of this ways (node "split")

What is the expected result?

The correct order is chosen individually for each occurrence of the member

What happens instead?

Only at the first occurrence the correct order is chosen

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

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-05-24 00:08:07 +0200 (Sun, 24 May 2020)
Build-Date:2020-05-24 01:30:48

Attachments (1)

josm_split_way_duplicate_members_example.osm (24.4 KB) - added by skyper 3 years ago.
example file

Download all attachments as: .zip

Change History (5)

Changed 3 years ago by skyper

example file

comment:1 Changed 3 years ago by skyper

Description: modified (diff)

comment:2 Changed 8 months ago by skyper

Description: modified (diff)

comment:3 Changed 8 months ago by taylor.smock

Owner: changed from team to skyper
Status: newneedinfo

This seems to be working in r18537 (josm-latest.jar) Can you still reproduce?

comment:4 Changed 8 months ago by skyper

Resolution: fixed
Status: needinfoclosed

Cannot reproduce it either with latest.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain skyper.
as The resolution will be set.
The resolution will be deleted.

Add Comment

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

Note: See TracTickets for help on using tickets.