Modify ↓

Opened 5 years ago

Closed 4 years ago

#17897 closed defect (duplicate)

relation editor: sorting and directions with forward/backward not working properly.

Reported by: skyper Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: template_report relation route sort dual-way Cc:

Description (last modified by skyper)

What steps will reproduce the problem?

  1. open a 2-way route relation with some members with role forward/backward
  2. select all members and sort them

What is the expected result?

I get a well sorted relation with full connection and direction indication

What happens instead?

  • Sort does not always work, especially, if there are more than one way to sort it and only one way is accepted
  • Perfectly sorted members are rearranged (see above) and connectivity is rendered wrong (not connected)
  • the direction of oneway is interpreted wrong

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

  • I made a small example file​.
  • moving some members down/up helps sometimes.
  • reversing simple relations like in the example should also be correct but JOSM does not like them. 
URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-07-07 14:17:28 +0200 (Sun, 07 Jul 2019)
Build-Date:2019-07-07 12:18:47
Revision:15221
Relative:URL: ^/trunk

Last errors/warnings:
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.

Attachments (1)

josm_17897_example.osm.xz​ (600 bytes ) - added by skyper 5 years ago.
example file

Download all attachments as: .zip

Change History (9)

comment:1 by skyper, 5 years ago

Description: modified (diff)

by skyper, 5 years ago

Attachment: josm_17897_example.osm.xz​ added

example file

comment:2 by Don-vip, 5 years ago

Resolution: → duplicate
Status: new → closed

Closed as duplicate of #17887.

comment:3 by skyper, 5 years ago

Resolution: duplicate
Status: closed → reopened

This is also happening with r15221 and is a different story

Last edited 5 years ago by skyper (previous) (diff)

comment:4 by skyper, 4 years ago

Cannot reproduce it with the example file of this ticket but route 66 in josm_18018_example_v4.osm.bz2 does not sort properly. At least roundabouts seem to be a problem.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-04-06 02:17:07 +0200 (Mon, 06 Apr 2020)
Revision:16239
Build-Date:2020-04-06 00:18:43
URL:https://josm.openstreetmap.de/svn/trunk
Last edited 4 years ago by skyper (previous) (diff)

comment:5 by skyper, 4 years ago

Keywords: route dual-way added; manager connectivity oneway removed

comment:6 by skyper, 4 years ago

Resolution: → duplicate
Status: reopened → closed

Closed as duplicate of #6930.

comment:7 by skyper, 4 years ago

Resolution: duplicate
Status: closed → reopened

comment:8 by skyper, 4 years ago

Resolution: → duplicate
Status: reopened → closed

Closed as duplicate of #6920.

Modify Ticket

Change Properties
Set your email in Preferences
Action
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 .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.