Sorry, I meant to reply a while back and got… sidetracked.
Regarding my comments on the Unified API vs the legacy Countdown feed, it’s simple - the former returns too much information which isn’t always needed…
As an example, we want to know the next bus arrivals at a stop and the (basic) data we need to present to our user is route number, destination, bus registration and how long until it arrives.
I’m going to use the stop shown on https://api-portal.tfl.gov.uk/docs under “Arrival predictions (countdown/trackernet) for a stop”, 490005183E and use the example URL given on that page:
and for the Countdown legacy feed:
At the time of writing I’ve run both queries (and within a second or two of each other) the former returned 2,664 bytes of data and the latter 197 bytes! Do we really need the stop ID repeated for every bus arrival, the stop name, the ‘platform name’ (stop point indicator in legacy feed talk), towards or mode name?
I’ve tried the same queries against a stop at St Pancras - 490004722A, 11,908 bytes vs 729 bytes. I wonder what the difference is during the peak?
(As a passenger I have a similar complaint about Journey Planner on the TfL Website, say I want to get from one Underground station to another oddly enough by tube, I can de-select every other mode of public transport but you insist on giving me walking information, cycle hire and cycle information. Why? All you’re doing is wasting computing power on travel options I’m (potentially) not interested in)