In recreating the pre-may 2016 Countdown site at http://eztfl.pectw.net/bus I’ve noticed that your https://data.tfl.gov.uk/tfl/syndication/feeds/bus-stops.csv file is chronically incomplete.
a. My site converts the user’s bus stop code to the naptan code using bus-stops.csv per these docs
b. The naptan code is used to generate the
https://api.tfl.gov.uk/StopPoint/<naptan>/arrivals API call to retrieve bus countdown data per documentation here
c. 100 of the bus stop codes in that CSV file do not have naptan entries
Example: Bus stop code 91623. CSV indicates on row 17250 (as of this date) that there is no naptan code assigned. However, when entering bus stop code 91623 at your main site we get page https://tfl.gov.uk/bus/stop/490001206P/new-malden-station/ which has the the naptan right there in the url. This has been so since mid-March 2017.
(Assuming my process above is otherwise sound)
Option 1. Can we have the bus-stops.csv file bought up to date, please? It would also help if we developers could determine when that file was last checked and considered current. HTTP Last-Modified: doesn’t cut that mustard. Adding a “Last checked current” row or column would work, as would using HTTP 302 to redirect from bus-stops.csv.latest to bus-stop.<timestamp-last-checked-current>.csv. Adding the date to the docs is less friendly to automation.
Option 2. Your main site’s behaviour in the example suggests your own developers have access to a superior file for converting bus stop codes to naptan. If so, where can we find it?
Option 3. Add support for
https://api.tfl.gov.uk/StopPoint/<bus stop code>/arrivals. This would also be closer to the Semantic Web ideal, as bus stop codes are available at bus stops, whereas naptans are not.