You prefer routes to stay unordered? Or that edits damage routes?
Vr gr Peter Elderson


Op vr 3 mei 2019 om 16:08 schreef <o...@hjart.dk>:

>
> >>> For a non-roundtrip route consiting of two consecutive ways the route
> >>> direction can be deduced from the order of the ways in the relation.
> >>
> >> That's assuming the ways are ordered at all. I've cleaned up hundreds
> >> of routes (most created by Potlatch users though) and my advice is: do
> >> not rely on routes being ordered.
> >
> > In OSM a relation is by definition an ordered list, see
> > https://wiki.openstreetmap.org/wiki/Relation :
> > "A relation is a group of elements. To be more exact it is one of the
> > core data elements that consists of one or more tags and also an
> > ordered list of one or more nodes, ways and/or relations as members
> > ..."
> >
> > Also the elevation profiles for the routes (e.g. in
> > waymarkedtrails.org) only work if the routes are ordered and they
> > usually look ok, see also
> > https://wiki.openstreetmap.org/wiki/Relation:route#Order_matters .
> >
> > If some editors damage the order in the relations this is a bug that
> > should be fixed anyway.
>
> In order to sort the members of a relation in JOSM, you need to download
> all of them. The majority of edits to relations involve downloading only
> 2-3 members. If only 1 member is added or removed, that's how they
> become unordered.
> Personally I'd prefer it stays like that, because I've seen complete
> newbies make some really weird edits to cycleroutes, because they
> obviously didn't understand what it was.
> >
> > _______________________________________________
> > Tagging mailing list
> > Tagging@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
>
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to