[Talk-transit] West Mids Bus Routes

Thomas Wood grand.edgemaster at gmail.com
Wed Jul 1 15:51:15 BST 2009


>>    Also, what do the colours mean?


> blue = Naptan stop (no highway=bus_stop but a naptan:AtcoCode tag)
> yellow = plain OSM stop (highway=bus_stop but no naptan:AtcoCode tag)
> orange = Merged stop (highway=bus_stop and naptan:AtcoCode, but is still
>         unverified or has no shelter tag set*)
> green = Merged and verified stop
>
> * I do not remember off the top of my head if there is another rule. I think we discussed something about route tags on the mailing list. I need to check the code to provide reliable information.

2009/7/1 Christoph Boehme <christoph at b3e.net>:
> Andy,
>
> Andy Robinson (blackadder-lists) wrote:
>> Looking great.
>
> Thanks!
>
>> I didn't play for more than a couple of moments so I may be missing
>> something here, however if a stop has been merged, ie it appears to have all
>> the right data, then there will be no wish to merge it with another stop.
>> There could be a danger of losing data if we did? I think once a stop
>> reaches a certain level of tagging it should perhaps be possible to disable
>> a merge.
>
> You are right. That is one of the things that I need to do when I clean
> up the muddle of the map interaction code.
>
> My idea is that only plain osm and plain Naptan stops can be merged. As
> soon as a node has both a highway=bus_stop and a naptan:AtcoCode tag it
> cannot be part of a merge any more. The similar stops list accounts for
> this already but the map does not.

Be aware that some counties may go with the 'default on' option of
highway=bus_stop tagging for the import, so you're going to have to
rely on the verified tag.
Also note that it was proposed to change unverified=yes to verified=no.

-- 
Regards,
Thomas Wood
(Edgemaster)




More information about the Talk-transit mailing list