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

Richard Mann richard.mann.westoxford at gmail.com
Tue Dec 4 11:28:34 GMT 2012

I think Martin is complaining about long-distance coach services. Splitting
them into within-urban and extra-urban segments would seem fairly sensible
to me.

On Tue, Dec 4, 2012 at 11:08 AM, Jo <winfixit at gmail.com> wrote:

> 2012/12/4 Richard Mann <richard.mann.westoxford at gmail.com>
>> Martin's problem would be solved if the extra-long relation is broken up
>> into segments. Which you are just as free to do as splitting a way in two.
>> Keep the relation tags on each segment, just like you'd do if you split a
>> way.
>> (This is rather different to Jo's proposal, which involves shifting tags
>> onto a parent relation)
> A bus line goes from a starting point to a terminus. It would seem strange
> to me to split such relation at arbitary places in the middle in order to
> avoid conflicts when editing. So it's not comparable to splitting a street
> because the properties or relation membership changes. It would still
> render correctly, but you lose the semantics of what the relation stood for.
> The proposal for the route segments was made 1,5 years ago, but never went
> to a vote.
> I agree that it should not simply apply to route relations. There are some
> relations where it is already in use. If I'm not mistaken long foot/hiking
> routes.
> Rather than 'winning' a vote we should try to get support from öpnv-karte,
> transportmap and OSMtransport. Once those big players render it, the rest
> will most likely follow.
> Jo
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20121204/f90234b8/attachment-0001.html>

More information about the Tagging mailing list