Just created relation/8276636, which I have called an augmented_route. The idea is that it points to ‘the’ bus route (in a given direction), but also contains meta-data about that bus route, such as which bits are optionally not served etc. A simplistic rendered could still look inside and get the first member, which is a normal route and render that.

The other members of this augmented route are all relations, being variations to the route: alternative pathways and short runnings (and the reasons for those).

I don’t want to do it as a super_route as, that is already used to group many routes, not group routes with their variants

The idea is that routing or rendering software will optionally add/subtract these route variants, according to whatever conditions govern them. These variants generally involve matching node-pairs in them with the same ones in the ‘main’ route, and replacing them with their own contents. Obviously, this will require a bit of disambiguation to cope with self-crossers and the like, but I don’t want to add ‘role=junction-point-1’ or the like yet, to members in the main route.

I also need to have a think about how these variants can be made to affect ‘interval’ type tagging. E.g, adding an optional short-running might double the frequency from 2BPH to 4BPH.

Obviously, I haven’t thought this all the way through yet.