September 19, 2011 at 7:44 pm #74886
I had assumed that the xml feed here:
would be more accurate than scraping the map page:
but not so! The xml data feed has not been updated for some considerable time. This is what we are showing:Code:EasyBoris V2.02 – Data age: 4131m 17secs
Should we go back to scraping the map page?September 19, 2011 at 8:45 pm #84661
My understanding is that the XML feed is what the map page runs off, so either way you’ll end up with the same data – “one version of the truth” & all that…even if it’s wrong!September 19, 2011 at 9:00 pm #84662
Not again. Sigh…..September 19, 2011 at 9:04 pm #84663
The Map version is correct (or at least changing) but the XML is static as per it’s own timestamp.September 19, 2011 at 9:40 pm #84664
oops – my mistake.
As I recall (& I’ll admit to a bad memory!) something was said at the time the XML feed was made available about the feed & the map running off the same data….Ah, got it now! They both run off (supposedly identical) feeds from the same database. Looks like the public XML is having troubles then (
Could you potentially set up a back-up process of scraping the map if the XML hasn’t been refreshed in “x” minutes?September 20, 2011 at 9:02 am #84665
Little Fluffy Toys LtdParticipant
This is shocking. Our customers are complaining like nuts. Who can we complain to, that’s gonna listen?September 20, 2011 at 12:27 pm #84666
Replying to Little Fluffy Toys Ltd
e-mailing Caroline Pidgeon (email@example.com)Transport Leader at the GLA may get you a result to this unacceptable problem. She is also a cycle scheme member and usually responds within 24 hoursSeptember 20, 2011 at 6:36 pm #84667
Replying to @Little Fluffy Toys Ltd’s post:
Agree it’s crazy. Looks like it was fixed earlier today, but getting worse again. At least our users can make up their own mind as to the validity of the data. We are currently showing:
______________________________________________________________Code:EasyBoris V2.02 – Data age: 52m 43secs
Page refreshed: Tue 19:31:17
TFL last update: Tue 18:38:33
______________________________________________________________September 20, 2011 at 9:36 pm #84668
Woops – yes it really hasn’t updated for a while! Over 4 hours and counting (as of 2300 Tuesday)
Rather worryingly, the TfL map still shows icons – and also says “data as of 2300″ when you click on each icon – which is very misleading. It is taking the time the page was loaded, when in fact the data is from ~1830
This is especially bad, since TfL’s own developer guidlines for the feed say if it is over 30 minutes out, it should not be shown on the map. Yet TfLs own map is showing data 4 hours oldSeptember 21, 2011 at 4:14 am #84669
FWIW on Monday evening the app data was way off but the status of nearby docks at the terminal showed what appeared to be accurate data.
Ended up taking the bus instead.September 21, 2011 at 8:59 pm #84670
Actually looking a few days back, 12 hours outage is nothing…
It was down for 4 days from the 16th!November 13, 2011 at 12:26 pm #84671
Looks like the XML feed has been stuck for since 2011-11-09 23:45:35!
I was trying to dock yesterday while at the Lord Mayor’s Show and the data in the app I use (which I won’t even mention because it is not their fault) was completely rubbish.
I do feel for the developers who must get a load of unujustified stick in this case.
I’m not sure if the map on the official website is up-to-date or not.November 16, 2011 at 2:16 pm #84672
The data is now 6 days out of date!
This means we can’t rely on any apps to know about nearby docking station status.
Does anyone know who to alert at Serco / TfL? It looks like the feed crashed and no-one has noticed!
Is anyone at Serco / TfL watching this forum at present?November 16, 2011 at 3:05 pm #84673
Simon – have you tried giving them a call?
Serco don’t respond to this forum – though I think they do nose through it!November 16, 2011 at 7:45 pm #84674
It does seem to be fixed now.
I did get some contacts after raising this with them the first time, but they didn’t really seem interested in me reporting future outages.
Throughout this time the TFL map has been updated OK, so I may revert to using that as a feed. Clearly TFL do not trust their own xml feed
You must be logged in to reply to this topic.