Combining bus stops into a single display

I'm wondering if there's a way to combine multiple bus stops into a single "departures" display? Most commonly, this would be for inbound and outbound departures.

So, in the example given in your "About..." posting, instead of having 4 separate bus time displays, they could be 2 (e.g. inbound, outbound - or even Busway and non-Busway), or even 1 (all stops in the vicinity of Shire Hall - until it moves to Alconbury, of course...).

The fact you haven't done it in your example leads me to suspect it's not currently possible - but doesn't the Bus departure display at the Railway Station do this? And even the display inside John Lewis gathers together departure info from a number of different stops.

Thanks, as ever.

It's not currently possible, but we realise it would be useful and it's certainly possible.

The major dificulty is working out how to display which stop each journey will depart from without taking up too much space. For the station it's easy becasue all the relavent stops are numbered, but for somewhere like the Drummer Street/Emanuel Street/Regent Street area it's far harder. We'd probably have to associate a multi-stop timetable with a map that assigned an identifier with each relavent stop. The stop names are far to long for this purpose.

Good point. As it happens, the main city centre stops (excl the Bus Station) are the least problematic since they're already "numbered" (E2, D4, etc). One might need to invent a code for the Bus Station bays, but that's all. I suppose it partly depends whether the ability to merge stop data would be restricted to those where it makes sense (inbound/outbound pairs, for example), or is simply a free for all on the users' part. The latter could indeed be problematic. Whereas the former could be time-consuming for the developers! Anyway, just an idea. Perhaps worth considering for a few obvious locations (Addenbrooke's Bus Station, for example)?

Thanks for pointing that out. It looks as if those short identifiers turn up in the NaPTAN stops database 'Indicator' field ('Bay 6', 'Stop S3', 'Stop 4', 'Stop E1', etc.) so they are at least accessible to us. Trouble is, 'Indicator' is less useful elsewhere where it contains things like 'Adj' (adjacent), 'Opp' (opposite) etc., giving the stop's relation to information in other fields like 'Landmark'. But yes, this seems like a way forward.

I've noted it for possible future development.