What's wrong with the xml feed?

Home Forums Data What's wrong with the xml feed?

This topic contains 16 replies, has 9 voices, and was last updated by  malcolmb1963 6 years, 10 months ago.

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #74886

    EasyBoris
    Participant

    I had assumed that the xml feed here:

    http://www.tfl.gov.uk/tfl/syndication/feeds/cycle-hire/livecyclehireupdates.xml

    would be more accurate than scraping the map page:

    https://web.barclayscyclehire.tfl.gov.uk/maps

    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?

    #84661

    7209
    Participant

    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!

    #84662

    cyclingnewbie
    Participant

    Not again. Sigh…..

    #84663

    EasyBoris
    Participant

    Actually, no.

    The Map version is correct (or at least changing) but the XML is static as per it’s own timestamp. :cry:

    #84664

    7209
    Participant

    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 :o (

    Could you potentially set up a back-up process of scraping the map if the XML hasn’t been refreshed in “x” minutes?

    #84665

    This is shocking. Our customers are complaining like nuts. Who can we complain to, that’s gonna listen?

    #84666

    Ruzzi
    Participant

    Replying to Little Fluffy Toys Ltd

    e-mailing Caroline Pidgeon (caroline.pidgeon@london.gov.uk)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 hours

    #84667

    EasyBoris
    Participant

    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

    ______________________________________________________________

    http://easyboris.org.org

    #84668

    dbrb2
    Participant

    http://cyclehire.eu/main/latency/plot.php

    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 old :-(

    #84669

    malcolmb1963
    Participant

    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.

    #84670

    dbrb2
    Participant

    Actually looking a few days back, 12 hours outage is nothing…

    It was down for 4 days from the 16th!

    http://cyclehire.eu/main/latency/plot.php?mins=10080

    #84671

    simon_macl
    Participant

    Looks like the XML feed has been stuck for since 2011-11-09 23:45:35!

    http://cyclehire.eu/main/latency/plot.php?mins=10080

    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.

    #84672

    simon_macl
    Participant

    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?

    #84673

    cyclingnewbie
    Participant

    Simon – have you tried giving them a call?

    Serco don’t respond to this forum – though I think they do nose through it!

    #84674

    EasyBoris
    Participant

    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 :lol:

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic.