Talk:London public transport tagging scheme
Discussion on the end points of the route (2016-ongoing)
Re "Both ends of each route should be the bus stands or depots, not the first or last bus stop"
But the subsequent tables contain no instructions or easily-searchable examples for tagging a bus stand or depot :( I think they probably should :(
TFL is changing parts of some routes to Hail and Ride, with "suggested places" rather than specific stops. There is no physical stop on the ground but they have Naptan codes. It is still useful to map H&R locations and to include them in routes so that the suggested stops can be shown on maps and used for journey planning, but the stops need to be identified as H&R so that editors do not delete them when they find no physical stop at the location.
- Is there any benefit in including the route to and from the bus stand / depot, as part of a bus route? Surely a bus route logically begins at the first stop position and ends at the last stop position. What happens to the bus beyond those stop positions doesn’t seem to have any relevance to the route.
I agree -- there seems to be little point. The bus will not be displaying a route or destination when it travels those parts of the route. Nor would an passengers (or editors) be allowed to remain beyond the final stop to verify the route taken. Plus in many cases the bus will not return to the depot at the end of its journey, it will instead begin another route which may or may not be the same as the one it was on.
As Amaroussi, I tagged the whole course of the route because, I used to be interested in trying to find out where they would be waiting before changing direction. I also had more than just regular passengers in my target audience at the time, but also people who wanted to do simulations and more. We could add more information to emphasise the non-service sections but this is a first since I do not know if a standard for non-service sections has been created before.
The current situation is that some editors have mapped bus routes strictly between the first and last stop only and some have mapped the routes beyond the first and last stop. Although in the latter case, sometimes this arises because the way hasn't been split at the appropriate stop position and the mapping is simply a general continuing of the way, rather than an explicit mapping to a stand or depot. That doesn't seem to serve the primary audience (the bus travelling public) of bus route mappings very well, as it presents a misleading picture of the extent of the bus routes at their terminus locations. I propose that we remove this ambiguity from the current bus route mapping by changing the guidance accordingly. I'll do that in the next few days, unless anyone has an objection. In parallel with continuing to map bus routes on that basis, we can discuss how we might unambiguously map the not-in-service components of bus routes. I can see two possible methods of doing that:
a) Add the ways in the corresponding route relations with new special roles, for example "forward_not_in_service" and "backward_not_in_service". Renderers would obviously need to show these ways in a different format to the regular ways, to distinguish the service component of the bus route from the not-in-service component of the bus route.
b) Add route relations to the route master relation with a new role of, for example "not_in_service", that map only the bus route through last stop -> stand/depot -> first stop. Typically, there would be one of these new relations for each terminus of a bus route, unless of course the last stop is also the first stop. The ways within those routes could be mapped using the usual roles of "forward" and "backward". As above, renderers would need to show these route relations in a different format to the regular route relations.