TIMS feed not working since Sat 31st Aug 2019 15:56

We haven’t seen any updates to the TIMS feed since 15:56 on Saturday 31/8/19.

We have checked our technical side and it look OK.

We have checked directly with a web browser and with curl both with the correct API keys and both show no update since Saturday.

  <PublishDateTime canonical="2019-08-31T14:56:00Z">Saturday, 31 Aug 2019 15:56:00 +01:00</PublishDateTime>

Thanks

Rob

Hi @rob - it appears TIMS was affected by a network issue that was resolved on Saturday, but the file publish appears to have been broken since then.

We’ve raised it with our colleagues who look after that system and we’ll advise once we’ve got an update.

Thanks,
James

@jamesevans

We figured it was something like that. Our system checks for published updates and so it’ll just start working when it’s fixed. We had a number of customers ask us what was going on and we assumed it was us. We worked back through our systems (checking for full systems, queues full) and finally realised we simply hadn’t got a feed from you.

We realise we are using the older TIMS system. It’s a major change for us to move to the new API. Whats the lifespan of the older system?

Thanks

Rob

hi @rwillett

The file that feeds the API and the legacy feed has not updated so this is actually affecting our API too and the data is stale.

Thanks,
James

@jamesevans

So you’re feeling the pain too :smile: Glad we’re all in the same boat.

Are there any plans to End of Life the older TIMS feed in place of the unified API? We looked at the unified API and couldn’t see how to get the whole datafeed, which is what we need.

Thanks

Rob

I think you can call the API with a date range to get the full list of disruptions.

eg

https://api.tfl.gov.uk/Road/all/Street/Disruption?startDate=2019-09-02&endDate=2019-09-02

Thanks
James

@jamesevans

Thanks for this. One thing we didn’t realise is that the dates can be ISO strings with times, so you can simulate the update type approach with the current TIMS XML files.

However we did notice that the coords that were passed in the older XML files are not passed in, only a simple array of two points. We’ll try and track down if this information is passed in in any other way.

We also need to test it against the XML to make sure we don’t miss anything. I can see a whole load of work coming along :frowning:

Rob

Good luck with that @rwillett

The issue with the feed has now been resolved. Please let us know of any further issues.

thanks,
James

Thank’s we saw that.

Rob