Thanks for clarifying, Grant. By this logic, the "Gautrain bus" master route relation is then definitely not the correct usage of the tag. I think it should be removed, and only used for *variants* of the same route, as stated before (i.e. different day / night routes or stops, or weekday vs weekend, etc)
We should be consistent in the "operator" tagging of the bus routes then. Do we use "Gautrain" or "Gautrain Bus" ? Though I myself used "Gautrain Bus" based on previous examples, I am leaning strongly towards just "Gautrain" (the name of the company - there isn't a publicly-mentioned, separate "bus" division or anything like that.) If you guys agree, we should all update our routes to just state "Gautrain" - and use the same tag across the rail and bus routes. kind regards, Dawid Op Do, 2013-11-07 om 15:48 +0000 skryf Grant Slater: > On 7 November 2013 14:53, Gerhardus Geldenhuis > <gerhardus.geldenh...@gmail.com> wrote: > > > A relation that contains all of the Gautrain routes is arguably valid but I > > think stretches the intended usage a little bit. So where do you draw the > > line? You could then also have a relation that contained all of the bus > > routes in Gauteng or even the whole of South Africa, or a relation for all N > > and M highways. > > Using relations for collections is generally frowned upon... > > * OK: relation for ways which make-up a dedicated route. > * NOT-OK: relation for all metrorail routes in Eastern Cape. > > Querying overpass api (or XAPI etc) based on tags is a much better solution. > > Example: all metrorail routes in Eastern Cape: http://overpass-turbo.eu/s/1qO > > Regards > Grant > > _______________________________________________ > Talk-ZA mailing list > Talk-ZA@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-za
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Talk-ZA mailing list Talk-ZA@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-za
