|
|
Post by superteacher on Nov 5, 2019 21:18:11 GMT
Is there an issue with how apps are taking data from the new TBTC areas? Whenever I try to access Baker Street or Edgware Road, the apps just close down.
|
|
|
|
Post by howda62 on Nov 6, 2019 9:17:14 GMT
I've been wondering exactly the same. I tried to view Met trains at Baker Street shortly after SMA2 went live and the app just closes. Been the same every time I've tried since. I now end up checking for trains at Kings Cross or Finchley Road to see what trains might be near Baker Street.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 6, 2019 9:34:04 GMT
Is there an issue with how apps are taking data from the new TBTC areas? Whenever I try to access Baker Street or Edgware Road, the apps just close down. SSL has CBTC JN has TBTC Its probably to do with how app developers are getting the info or how if TfL have updated there data feeds to the public yet or not |
|
|
|
Post by goldenarrow on Nov 6, 2019 13:31:55 GMT
Stations between Hammersmith and Paddington (both) run off the H&C feed only. Circle line feed works in the Eastbound direction only from PAD heading east, Westbound Circle/H&C are merged as they’ve always been. The one size fits all algorithms that many apps use through the open data platform has obviously caught them out with many apps being unable to differentiate services given that most feeds go for line specific info rather than platform specific which much better suits the Sub-surface lines.  |
|
