In many cases within the Arrivals feed for the tube, the destination of the train returned is ‘Check front of Train’ or similar. This is apparent on lines where the signalling system doesn’t return a destination to the Trackernet feed.
A thought occurred to me that this could be overcome by using the destination of the train itself rather than the signalling data. So, for example, on the Uxbridge branch where Met train destinations are unknown to the signalling system, the destination generated by the train itself could be used. This must surely be possible given that the leading car number and train numbers are returned to the system - these are unknown to the signaling and must therefore be taken from the train itself. So why not the destination too? This would be a much improved benefit to end users.
Another added benefit (fairly unique to the Met line) would be to return stopping patterns, where trains can be ‘All Stations’, ‘Semi Fast’ and ‘Fast’, another aspect that the API doesn’t currently factor in.