relation dialog doesn't handle inner/outer relations properly

[delta_foxtrot2]

The relation list shows a relation as not joined properly if the relation has both inner and outer relations.

For example, the NSW/ACT state/territory border, the ACT is contained within the NSW area, but it is it's own territory/state.

​http://www.openstreetmap.org/browse/relation/80372

[Gubaer]

What do you mean with "not joined properly"? Do you refer to the linking information in the third column of the relation member table?

[delta_foxtrot2]

Replying to Gubaer:

What do you mean with "not joined properly"? Do you refer to the linking information in the third column of the relation member table?

Yes, on a more simple relation it shows the relation as closed, in this case because there is an inner and outer relation the relation isn't showing as closed

[delta_foxtrot2]

This site claims the relation information is correct also.

​http://betaplace.emaitie.de/webapps.relation-analyzer/index.jsp

[Bürste]

I think closed ways should be grouped somehow, for inner and outer ways ... or mutiple inner and outer ways.

[Bürste]

But this not a bug, it's more an enhancement to show multiple types of members individual.

[delta_foxtrot2]

I still consider this a bug because the relation editor doesn't display the relations correctly. Just because this is an "advanced" feature doesn't make it less of a bug because the relation editor doesn't display closed ways correctly.

[stoecker]

In OSM API 0.6 the order of elements in a relation can have a specific meaning. The relation editor can no longer sort them according to some own ideas. There is a sort button which can be pressed explicitely to do so.

If this sort function can be improved, patches are welcome, but an auto-sort is out of question.

[anonymous]

This isn't entirely about sorting, but displaying if a relation is closed or not, the current relation editor doesn't convey this information so you spend time trying to work out why they aren't closed when in fact they are.

[stoecker]

We have only generic relation editor ATM. There is no editor for specific relation types. Requests for such editor enhancements are already in other tickets.