Hi,
I have been using the API for a personal project, and was looking at creating a search page similar to the one found in the TfL Go mobile application, seen here:
I am looking specifically at the colour indicators under ‘Mile End Station’ that denote the lines available at the station.
However, I noticed that the StopPoint/Search?query={} endpoint (here) does not return any line identifier information (only line modes i.e. tube), when the StopPoint?lat=.... endpoint (to search within a radius, here) has an optional returnLines parameter, defaulting to true, that returns lines, lineGroup and lineModeGroups objects on each StopPoint, allowing an application to read line identifiers at each StopPoint.
Essentially, I was wondering whether I am missing something and it is possible to return lineModeGroups for the search by query endpoint, and if it is not possible, could a returnLines parameter or similar be added so we can retrieve this information?
I noticed that the TfL Go application was using a different api, that does return line information by name query, and it would be nice to have that parity if it is not already available.
Yeah, this is basically the solution I came up with. It would be nice to have parity with the API TfL are using internally though and have everything returned in one API call, rather than keep this list separately.