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

Henning Scholland osm at aighes.de
Fri Nov 30 13:21:46 GMT 2012


Am 30.11.2012 11:57, schrieb Pieren:
> On Fri, Nov 30, 2012 at 11:41 AM, Martin Koppenhoefer
> <dieterdreist at gmail.com> wrote:
>
>> 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).
> Not necessarily. Creating routes will be more or less the same if your
> editor highlights the ways between the nodes. But their are three
> advantages : intersection nodes are quite stable in OSM, more than
> single nodes or ways. Adding hundreds routes will not disturbe normal
> edits. And last but not least, routes will not have to split ways just
> because a bus is turning left or right at intersection.
There are several problems. To draw the route in editor you need at 
least two nodes in your downloaded data. Then editor have to guess, 
which ways are should used for the route.
Eg.:
     ___D___
    /       \
    |       |
---A---C---B----

Which way should editor display? Direct one or longer one?

If some adds a way between D and C and doesn't care about all relation 
(editor cant display every route), it gets even unclearer, which way 
belong to the route. In actual schema there will be at least A-C, C-B, 
A-D or D-B and it's possible to fix the route quite easy.

Implications aren't a better way, it's mainly guessing.

Henning




More information about the Tagging mailing list