Opened 15 years ago

Last modified 14 years ago

#5848 closed enhancement

Roundabouts are not analyzed correctly by relation analyzer, when they are connected to oneway part — at Version 5

Reported by: PetrDlouhy Owned by: PetrDlouhy
Priority: normal Milestone:
Component: Core Version: latest
Keywords: relation_analyzer Cc: NE2, bastiK, PetrDlouhy

Description (last modified by PetrDlouhy)

Roundabouts are not analyzed (sorted nor visualized) correctly by relation analyzer, when they are connected to oneway part like this:

 |
 |
 ⋀
| |
| |
| |
 O
 |

More examples are on ticket #5109, see testing cases in roundabout-and-oneway-loop_(tricky).osm and example 1 in more complicated cases in relation_analysis.osm.

Change History (5)

comment:1 by PetrDlouhy, 15 years ago

There is little controversy about this, which I am not sure, how to treat:

When the orientation of oneway loop is opposite to orientation of the roundabout, one part of the roundabout will be driven twice (or never in case of same orientations), when going from beginning of the relation to end and backwards.

This could be contradiction to system, in which oneway parts of the relation are understood. It inconsistency appear more intensively, when trying to split the roundabout into several forward/backward parts - the twice (or never) driven part should, probably be included twice (or never) in the relation.

This will lead to inconsistent relations, when somebody the roundabout without any knowledge about the relations on them.

comment:2 by PetrDlouhy, 15 years ago

Cc: PetrDlouhy added

comment:3 by stoecker, 15 years ago

NOTE: Validator component reports roundabouts in routes as broken as well.

comment:4 by PetrDlouhy, 15 years ago

Hm, even plain roundabouts are leading to inconsistency with forward/backward logics, when spitted. I am not sure, how JOSM should deal with that.

There should have been wider agreement about the relation treating in whole OSM, not just JOSM. I didn't find anything on OSM wiki, but I hope my improvements will provoke some discussion about this as well as other implementations.

comment:5 by PetrDlouhy, 15 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.