[Tagging] Bus route operator

[Volker Schmidt]

Put a website reference for the "union" in the route. That website will
show which bus lines are part of the union.


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, 24 Dec 2020 at 17:56, Nicolás Vieites Sueiro <vacamaribu at hotmail.es>
wrote:

> Hi everyone!
>
> I'm currently mapping some new bus routes in Galicia, Spain but I have
> encountered the following problem:
> Here, bus routes are managed by the local government that designates an
> operator every X years. Sometimes, multiple bus companies form a temporal
> union in order to be choosen to be the route operator. Sometimes the
> union's name is used as the brand on the buses operating the route,
> sometimes the brand used is from one of the bus companies, sometimes the
> union of companies create an specific brand different from their names, and
> sometimes are used buses from the companies forming the union indistinctly.
> So, as we have this complex situation, I don't know how to map correctly
> this.
>
> My current way of doing it is to use the operator tag to map the union
> name, since it is who actually operates the route, and then the brand tag
> to map the brand used on the buses but... How do I map the companies
> forming the union??
> I thought using operator tag for that, separating the companies with a
> semicolon, but then, I wouldn't have a tag for mapping the union's name...
>
> Thank you very much for your attention, and Merry Christmas to everyone!
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20201224/a0fb31e6/attachment.htm>