On Thu, 8 Nov 2018 at 22:28, Paul Allen <[email protected]> wrote: > > All of them. :) > > Seriously, which one I'd want would depend upon circumstances. >
Agree with you, but I don't think we need to provide all those options, just get the viewer to the right website, because once they're there, there are links provided by the operator to go to other pages etc. I think that the "next bus" page would be better one to land on, as it's simpler / easier to read, while the "full timetable" page may be a bit unwieldy on a mobile phone? > Maybe have the tag more general so it can link to non-gtfs > timetables on operator websites too. Maybe we don't even have to specify > gtfs > "Timetable" with the URL? Had a quick search & can't see that timetable is yet in use as a tag. Perhaps "schedule" but I personally prefer timetable for bus & so on times. And please don't forget the possibility of a single route having two > operator whose GTFS feeds > list only their own vehicles on that route. The tag has to deal with > that. And semi-colon separators > aren't viable > Simple way may just be multiple timetable tags - "timetable:red_busline=URL*" "timetable:blue_busline=URL*" Here's another stop nearby, which is a fairly major hub https://jp.translink.com.au/plan-your-journey/stops/300018, which has 12 separate routes stopping there. These are all controlled under one network "Translink", but the actual buses using these routes belong to 3 different bus companies. There're also long-distance / interstate coaches that stop here, but they aren't covered by Translink so their times aren't shown. Thanks Graeme
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
