[Tagging] How to solve the problem with relation overload?

Martin Koppenhoefer dieterdreist at gmail.com
Fri Nov 30 10:41:00 GMT 2012

2012/11/30 Pieren <pieren3 at gmail.com>:
> In the example you are pointing, 6 of the 9 relations are for the Bus
> 311. I never map public transport relations but I've seen its modeling
> expanding very far in complexity in recent time (fault is also because
> some routes are complexe anyway). The amount of route relations will
> increase in the future, this is unavoidable. I personally don't care
> about such relations until they make our normal edits unmanageable.

every (route) relation makes highway editing more complicated, e.g.
when you have to split a single highway into a dual carriageway you
will have to know on which of the ways you have to put the route
relation, and maybe you will also have to split the relation into 2
(forward, backward). You might do this with little interruption with 1
route, but when there are 10 of them, many mappers will most likely
move on and not split the highway.

> One solution could be to bring super-relations in general use.

+1, they are already in use, and I think in a case where 6 variants of
the same route are on the same single piece of way the use of
superrelations (route part relations, with which we could assemble the
route variants) could simplify the editing.

> Or find
> another modeling for routes (e.g. with intersection nodes only).

not a good idea IMHO, as it makes editing far more complex (you will
have to understand from just a collection of nodes which ways are
effectively part of a route relation).


More information about the Tagging mailing list