-
Notifications
You must be signed in to change notification settings - Fork 1
/
apibugs
26 lines (23 loc) · 2.02 KB
/
apibugs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
NB: This an old list which applied to TrackerNet. Need to check which still apply to unified API
Bugs
* Chesham station missing from PredictionDetailed method.
* District / Circle Line stations between Paddington Circle and Notting Hill Gate missing from PredictionDetailed method.
* Hammersmith & City / Circle Line station between Paddington H & C and Ladbroke Grove missing from PredictionDetailed method.
* Hammersmith & City / Circle Line stations between Latimer Road and Goldhawk Road missing from PredictionDetailed and PredictionSummary methods.
* Barking station appears in Metropolitan line PredictionSummary method.
* District line trains between Tower Hill and Gloucester Road also appear in Hammersmith & City and Circle feeds.
* Piccadilly line trains showing on District line platforms between Hammersmith and Acton Town.
* Some trains report a setNo of 0 in the API despite having a number on the front of the train in real life.
* Some trains report a Destination which is just the name of a line, rather than an actual station.
* When the API has an error, it still returns 200 OK as a status code.
* When the API has an error, it serves html with a text/xml Content-Type.
Documentation issues
* It isn't clear whether setNo is unique to the network as a whole or just to a specific line or rolling stock.
* It isn't clear what TripNo actually means - seems to imply that it's unique for each route, but these IDs appear to change over time.
* No mention what timezone the TimeStamp attribute is in.
Feature requests
* Don't round secondsTo in PredictionSummary to nearest 30 seconds. At the moment to get precise data for all lines one has to query PredictionDetailed for every station individually.
* Split up Circle and H & C lines for PredictionSummary and PredictionDetailed methods.
* Use same line identifiers across all API methods (Currently LineStatus uses different IDs than.PredictionSummary and PredictionDetailed).
* Include DLR and Overground data for all API methods, not just LineStatus.
* A public bug tracker for the APIs.