On Thu, 9 Jul 2009, Christiaan Welvaart wrote: >> > It was mentioned that the sort feature is not really useful. Why is >> > that, and >> > how could it be made (more) useful? >> >> I should have been more verbose. I did not deep-analyse the mechanism but >> it seems you only sort the first block of ways. This does not work for >> splintered relations. > > Sure, that is a limitation of this simple feature. But I do not see how one > could sort a branched two-way route relation into a linear list.
Not branched two-way. Unfinished single way. This will consist of multiple snippets which are unconnected, but should be connected by the ways inbetween. The sort function should leave a sorting, which makes fixing remaining bugs much easier than it is now. So the general tasks is to leave as many connected parts as possible (i.e. minimize unconnected parts). >> In multipolygon drawing of mappaint I choosed to join all ways at there >> end points and the as a result I have multiple groups of joined ways. This >> can be done in relation sort as well. The last step would then be to >> bring these groups in correct order (i.e. sort them by minimal distance of >> end points. > > Since multipolygons are often nested, it would make sense to group those in > nesting order. But then such groups should be marked in the relation editor, > e.g. in a tree structure. Maybe this can be implemented in a separate > multipolygon editor... I don't talk about multipolygons. I only took that as demonstration how it can be done. Currently route relations are the relation type which needs sorting most (at least from my point of view). Ciao -- http://www.dstoecker.eu/ (PGP key available) _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
