[Tagging] Public transport routes with multiple reference numbers

[Martin Koppenhoefer]

sent from a phone

> Il giorno 03 ago 2016, alle ore 08:55, Michael Tsang <miklcct at gmail.com> ha scritto:
> 
> 1. There is a service identified by three different numbers, while in fact the 
> three numbers belong to the same service with completely no differences. This 
> is the case with minibus routes 52A/54A/56A in New Territories, where two 
> operators jointly dispatch minibuses onto these routes, sometimes with number 
> 52A, sometimes with 54A, and sometimes with 56A. However, they are identical 
> services.
> 
> Is using semicolon in the ref=* tag a good idea?


I would make three different (i.e. distinct but the same content) relations, one for each number 



> 
> 2. There is a service identified by two different numbers, where the two numbers 
> are always used simultaneously. This is the case with Shenzhen bus routes 
> M215-M218, where both numbers are always displayed side-by-side in bus stops 
> and on the number plates of the buses. They are almost never used 
> individually.
> 


if it's always and it's displayed like this, I would add "M215-M228" in the ref of the relation (only 1 relation)



> 3. There is a service, due to operational reasons, identified by two different 
> numbers. However, the two different numbers are used in different segment of the 
> service, but in fact, they belongs to the same service (i.e. passengers can 
> get a ticket and board the vehicle on the segment with the first number, and 
> alight at the end of the segment with the second number without intermediate 
> alighting or additional payment). This is the case with train route Z806/Z803 
> from Zhaoqing to Kowloon, where the number Z806 is used on the segment from 
> Zhaoqing to Guangzhou, and Z803 is used on the segment from Guangzhou to 
> Kowloon (i.e. it can be treated as a through service).


I would make 2 relations. Would be nice to invent a way to say that z806 will always become z803 (link the relations), but I don't know if there is already something in use for this 


cheers,
Martin