Hi, thank you so much for publishing these data. I have looked into the stats.json file but find something confusing about the indexing of objects.
It is quite obvious that the data for 2014, 2015 and 2016 are indexed by their nlc_id. However, for other years, the labels are completely different and cannot be matched with the nlc_id of London metro stations. For example the first object of the stats.jsom file is 0853 which doesn't match with any nlc_id in the tflstations.json file.
May I ask do you happen to know the rules behind these indexing? Since the app can show data up to 2003.
Hi, thank you so much for publishing these data. I have looked into the stats.json file but find something confusing about the indexing of objects.
It is quite obvious that the data for 2014, 2015 and 2016 are indexed by their nlc_id. However, for other years, the labels are completely different and cannot be matched with the nlc_id of London metro stations. For example the first object of the stats.jsom file is 0853 which doesn't match with any nlc_id in the tflstations.json file.
May I ask do you happen to know the rules behind these indexing? Since the app can show data up to 2003.