Xtrazsteve Posted January 4, 2016 Report Share Posted January 4, 2016 Something has changed. Though it's not clear where the problem is. All we know is Nextbus hasn't sucked in the new TTC data. Is it because they can't be bothered, or because there's an integrity problem in the TTC data, that creates an error when they try and suck it in? It's no secret that TTC replaced the public-facing opendata for the November board after they first released it. So we know that TTC somehow messed up that dataset. The public-facing data for the January board is currently dated December 20th. Let's see if that changes ... I'm not sure if things have changed but on the nextbus newsgroup on Google, nextbus has started in 2013 they don't use gtfs from the ttc. Instead they get it from the ttc directly as it's less prone to errors. If this is still true, whatever gtfs is available from Toronto's open data doesn't matter. Link to comment Share on other sites More sharing options...
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now