**This event is now fully booked.**

Join us for a TfL Open Data Evening at the AWS Loft on Thursday 21 April to gain a deeper understanding of how you can access and utilise TfL’s open data feeds through our Unified API.

Where and when

Venue: AWS Loft
Brew Eagle House 163 City Rd, London EC1V 1NR
View on Google Maps

21 April 2016 18:30 – 20:30

Register for the event here

Introduction

It was announced last week that over the course of the last six months, more than 2,000 new developers have signed up for access to our open data, making a total of around 8,200 developers now registered for TfL’s Unified API.

Almost 500 apps are now being directly powered by our open data, helping Londoners plan their journeys with real-time information about our public transport and road networks.

As Phil Young, Head of TfL Online explains:

“Across London, millions of people use apps powered by our open data to check the Tube, find a bus or see how the roads are running.

This same data powers our website, allowing customers to choose between using tfl.gov.uk or simply downloading apps which are directly powered by us. We’re committed to making our information freely available to help stimulate new products and services.”

Following our Traffic Data Hack Day hosted by Amazon Web Services earlier this month, join us for this week’s AWS Loft event on Thursday 21 April at 6:30PM to find out more about our open data and how developers can work with it.

AWS

Following the Traffic Data Hack Day earlier this month, AWS are again hosting us for this week’s Loft session

Agenda and Speakers

Phil Young, Head of TfL Online – Welcome and introductions

Dan Mewett, Solution Architect, TfL Online – Updates to the TfL Unified API

Lucy Fish, Customer Strategy Lead, TfL Travel Demand Management  – Crowding data

Ryan Sweeney, Data Services Manager, TfL – Opening up TfL’s ticketing data

Roland Major, Enterprise Architect, TfL Information Management – Improving our traffic data, part 1 – TDES

Duncan Elder, TfL Travel Demand Management – Improving our traffic data, part 2 – Planned Road Closures – trialling a standardised way to share data

Register for the event here

Posted by Stephen Irvine

Stephen is a TfL Community Manager and editor of the Digital Blog and Experience London blogs.

12 Comments

  1. Hi,

    I was going to come to the event also to ask a question but there is no more room in it now… I could not get an answer for this question otherwise when I sent emails (to the wrong people? in TfL)… I really need it 🙂

    We are building a journey planner using your tube and bus feeds but some data is consistently corrupt and I have no way to fix it. We are using the URL https://www.tfl.gov.uk/tfl/businessandpartners/syndication/feed.aspx?email=&feedId=15 to download the buses and tube XML feeds in a ZIP format.

    We have noticed that some of the data seems to be invalid. For example, if you look at the data for the Circle line, tfl_1-CIR-_-y05-330144.xml, you will see that it contains data about stops and journeys that have nothing to do with the Circle line. For example:

    grep -i “stamford brook” tfl_1-CIR-_-y05-330144.xml

    N0065206
    Stamford Brook

    Why is for example Stamford Brook mentioned in the Circle line XML? As we all know, this station has nothing to do with the Circle line. Going further:

    9400ZZLUSFB2

    Stamford Brook

    N0065206

    521876
    178804

    RPL

    000
    Stamford Brook

    This means there is a Stamford Brook StopPoint with ATCO ID 9400ZZLUSFB2 mentioned for the Circle line.

    Going even further:

    9400ZZLURVP2

    9400ZZLUSFB2

    698
    inbound

    pickUpAndSetDown
    9400ZZLUSFB2
    PTP

    PT1M
    pickUpAndSetDown
    9400ZZLUTNG4
    PTP

    RL_1-CIR-_-y05-330144-I-15-11
    PT1M

    Why are these entities mentioned in this Circle line XML file, if the Circle line never passes Stamford Brook?

    This causes huge issues in our application, which shows to our users that they need to take the Circle line to go to Stamford Brook, which makes no sense at all.

    Please let us know what is the planned resolution for this issue or what is the correct feed to use if this one is old or outdated?

    Cheers,
    Caroline

    Like

    Reply

    1. Hi Caroline, the source data you are looking at from the legacy syndicated feed is one that we have cleaned up for the Unified API. Information about stops, lines and routes are available from the Unified API /StopPoint and /Line endpoints. Please see the relevant blog posts, https://blog.tfl.gov.uk/2015/10/19/unified-api-part-3-rot-routes-of-things/ and https://blog.tfl.gov.uk/2015/10/08/unified-api-part-2-lot-location-of-things/ for details.

      Like

      Reply

      1. Tim, thanks.

        Is there an issue with the feeds I am using or just different API? Are you saying those feeds are outdated? It is what TfL offers developers on its portal…

        Help?!

        Like

      2. Missed this, but any other such events being planned?

        Like

      3. Stephen Irvine April 26, 2016 at 2:42 pm

        Hi Dave, please keep an eye out on this blog for news of any similar events coming up in the future

        Like

  2. I attended the TfL Open Data event and very much enjoyed the session. I was told that the slides presented would be made available to attendees. Can you please send me a copy of the slides? Thank you. Chris Peacock

    Like

    Reply

    1. Stephen Irvine April 22, 2016 at 4:32 pm

      Hi Chris, great to hear you enjoyed the event. Please keep an eye out on this blog on Monday, we’re aiming to publish the slides with a summary of the event then. Thanks.

      Like

      Reply

      1. Stephen

        Thank you. I’m keeping an ‘eagle eye’ open on the Blog and hope to see a link to the slides shortly.

        best regards

        Chris

        Like

      2. Stephen Irvine April 25, 2016 at 4:31 pm

        Hi Chris, looks like this will be tomorrow now. Apologies for the delay, should be first thing in the morning though.

        Like

      3. Stephen Irvine April 26, 2016 at 3:18 pm

        Hi Chris, the slides are now available on this post https://blog.tfl.gov.uk/2016/04/26/tfl-open-data-evening-event-review/

        Like

      4. Stephen

        Thank you very much for the information presented and for making the slides available following the session.

        best regards

        Chris Peacock NGA

        Like

  3. […] held an open data evening at the AWS Loft last week and the event saw experts from TfL discuss the recent and upcoming additions to […]

    Like

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s