Month: April 2016

Journey Planner

TfL Journey Planner Updates – April 29

Welcome to the latest installment from the Journey Planner team, with this week’s summary of our data updates. The Unified API is updated with new Journey Planner data up to five times a week – to receive notifications of when new data has been added, including a summary of what has changed, please email GetThePoint@tfl.gov.uk
Read More

DevelopersNews

TfL Open Data Evening – Event Review

TfL 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 our Unified API, alongside other new datasets which could be released in the future.

Lucy Fish

Lucy Fish, Customer Strategy Lead in the TfL Travel Demand Management team discusses crowding data at the AWS Loft event

Read More

DevelopersNews

London Data City | Data Nation Challenge – Extra Info

As previously posted on this blog, London Data City | Data Nation was launched on 12 April, with a series of 6 month-long challenges being undertaken by teams in London and Singapore.

The first in the series of challenges is the Transport and Mobility challenge, which is now underway and runs until Monday 16 May.

At the launch event for the challenge Rikesh Shah, Lead Digital Relationship Manager at TfL, introduced our open data policy and set the scene for the challenge. Following up on the launch event, Rikesh has a message for the participants with some handy extra info:

Dear all,

I hope you’re all enjoying the challenge.

At the launch of the Data Nation challenge I promised that I would provide more information about TfL, with a particular focus on customer insight. So, I am delighted to provide a link to some useful information.

In particular, have a look at Chapter 7 which focuses on Customer Experience.
http://content.tfl.gov.uk/travel-in-london-report-8.pdf

Good luck!

All the best,

Rikesh Shah,
Transport for London

Journey Planner

TfL Journey Planner Updates – April 22

Welcome to the latest installment from the Journey Planner team, with this week’s summary of our data updates. The Unified API is updated with new Journey Planner data up to five times a week – to receive notifications of when new data has been added, including a summary of what has changed, please email GetThePoint@tfl.gov.uk

TransXChange data is normally supplied to the London Datastore on Thursday mornings, and should reflect changes described in this post.

As ever, if there are any points of interest you’d like to see added to Journey Planner, just let us know. You’ll find the email address at the bottom of this post.

This is a brief summary of this week’s new data highlights:

Timetables

Buses

From Sunday 24 April, buses on route 123 and 144 will not serve Turnpike Lane bus station towards Edmonton / Tottenham, and Routes 121 184 221 232 and 329 terminate in Wood Green High Road, just to the north of Turnpike Lane station.

From Saturday 30 April, Route 35 will operate 24 hours a day, with Route N35 withdrawn, whilst Routes 62 and 368 are converted to full double deck operation; Route 62 will operate more frequently on Monday to Saturday evenings and during the day on Sunday, whilst Route 366 and 368 service frequency during the day on Monday to Saturday is improved to every 10 minutes.

In addition, from this date, Route 153 is revised to operate between Finsbury Park Station and Liverpool Street Station, instead of to/from Moorgate, Finsbury Square. Routes 11 23 133 N11 and N133 will also return to Liverpool Street Bus Station from this date, and there will be local routeing changes to Routes 112 and 611 at Neasden, as well as the 145 at Dagenham, whilst Sunday to Thursday night frequency on Route N28 is improved to every 30 minutes. There has been a change to the date for Aldgate reopening – Routes 15 25 67 115 205 and 254 now return to their normal routes on this day

Sunday 1 May sees a further diversion of Routes 11 133 N11 and N133 between Bank and Liverpool Street due to the northbound closure of OId Broad Street. Routes N15 N253 N550 and N551 return to normal routes at Aldgate on this date.

Tuesday 3 May:  Tooley Street will close eastbound, affecting Routes 343 381 N381 and RV1.

Saturday 7 May: Route 147 will transfer operation to Blue Triangle

London Underground

New base timetables for the Bakerloo, Circle, District, Hammersmith & City and Victoria lines start on Sunday 15 May and are now available. Early closures on Monday to Wednesday nights on the Metropolitan line between Aldgate and Wembley Park also begin on this date.

River

All Spring and Summer timetables are now available on Journey Planner, the unified API and in TransXChange.

Tramlink

A new timetable started on Monday 4 April, and is now available on Journey Planner and the unified API, as well as in the TransXChange upload.

Stops:

A small number of coordinate and name changes have been made this week including the removal of redundant stops

Points of Interest

As ever, we welcome any suggestions for new Points of Interest or categories to getthepoint@tfl.gov.uk

London Underground

Engineering works timetables for trains and replacement buses are now in place for the next FOUR weekends including the May Day Bank Holiday weekend.

buses

This week’s update includes details of many changes to bus routes for the London Marathon and Hackney Half Marathon in the coming weeks

Read More

News

TfL Open Data Evening 21 April – Register Now

**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

Read More

DevelopersInformation

Unified API: Live Tram Arrivals Added

We’ve recently integrated live tram arrivals into our predictions API, and I’ve updated the information on my previous API post Unified API Part 5: AoT – Arrivals of Things to reflect this.

This means that the live trams information is available on our website and through our Unified API, as well as in the many ESUB status boards that are found in stations around London.

We have a total of 408 ESUBs on TfL Rail, Tube and DLR, as well as over 160 on National Rail and 40 on London Overground that are now showing the new trams information.

See Unified API Part 5: AoT – Arrivals of Things in the last section at the end of the post for more details.

Journey Planner

TfL Journey Planner Updates – April 15

Welcome to the latest installment from the Journey Planner team, with this week’s summary of our data updates. These include all forthcoming bus service 1and stop changes for timetables which are available on Journey Planner, as well as in the Journey Planner API.

As ever, if there are any points of interest you’d like to see added to Journey Planner, just let us know. You’ll find the email address at the bottom of this post.

This is a brief summary of this week’s new data highlights:

Timetables

Buses

Routes 15  25 and 67 will resume serving Aldgate Station from Sunday 24 April, and Route 205 will return to its original routeing via Liverpool Street, instead of operating via Commercial Street

From Saturday 30 April, Route 35 will operate 24 hours a day, with Route N35 withdrawn, whilst Routes 62 and 368 are converted to full double deck operation; Route 62 will operate more frequently on Monday to Saturday evenings and during the day on Sunday, whilst Route 366 and 368 service frequency during the day on Monday to Saturday is improved to every 10 minutes. In addition, from this date, Route 153 is revised to operate between Finsbury Park Station and Liverpool Street Station, instead of to/from Moorgate, Finsbury Square. Routes 11 23 133 N11 and N133 will also return to Liverpool Street Bus Station from this date, and there will be local routeing changes to Routes 112 and 611 at Neasden, as well as the 145 at Dagenham, whilst Sunday to Thursday night frequency on Route N28 is improved to every 30 minutes.

Sunday 1 May sees a further diversion of Routes 11 133 N11 and N133 between Bank and Liverpool Street due to the northbound closure of OId Broad Street

Tuesday 3 May:  Tooley Street will close eastbound, affecting Routes 343 381 N381 and RV1.

London Underground

New base timetables for the Bakerloo, Circle, District, Hammersmith & City and Victoria lines start on Sunday 15 May and are now available. Early closures on Monday to Wednesday nights on the Metropolitan line between Aldgate and Wembley Park also begin on this date.

River

All Spring and Summer timetables are now available on Journey Planner, the unified API and in TransXChange.

Tramlink

A new timetable starts on Monday 4 April, and is now available on Journey Planner and the unified API, as well as in the TransXChange upload.

Stops:

A large selection of coordinate and name changes have been made this week including the removal of redundant stops and addition of new stops for the forthcoming rerouteing of Route 145 in Dagenham.

Points of Interest

As ever, we welcome any suggestions for new Points of Interest or categories to getthepoint@tfl.gov.uk

Keep up to date with new timetables, stops and points of interest across various TfL modes of transport including DLR

Keep up to date with new timetables, stops and points of interest across various TfL modes of transport including DLR

Read More

DevelopersNews

Data City | Data Nation Launch – The Challenge is Underway

The London Data City | Data Nation challenge was launched on the morning of Tuesday 12 April at an event hosted by Digital Catapult. The launch event outlined the context and details of the 6 month-long challenge being undertaken by teams in London and Singapore, starting with the Transport and Mobility challenge that runs until Monday 16 May.

In partnership with TfL, the Greater London Authority and Ford, Digital Catapult are setting challenges based around 2 key questions:

Public Transport Challenge

How can we accurately identify, filter and characterise transportation delay events across large-scale, dynamic, multi-modal transportation systems?

Enabling users to make seamless progress towards their destination. People need help to very quickly identify breaks in the system and need greater help for decision making in case the system breaks and when to abandon their plans for a better option. Participants need to choose data sources (from sandbox or beyond) to achieve the end goal.

Road Network Challenge

How can we enhance customer service and experience across London’s road network?

Through Data City | Data Nation we intend to deliver new technology solutions that help understand and predict events on London’s road network and go about enhancing the overall customer experience whilst travelling that network. TfL will provide SCOOT traffic data (described in more detail here) to participants of the challenge that is not yet publicly available.

We’ll update this blog as key milestones in the challenge are met, and will of course announce the winners in May. Good luck to all taking part!

Setting the scene for the challenge

There were many expert speakers setting the context and details of the challenge, and their presentations are summarised below.

Rikesh Shah

Rikesh Shah, Lead Relationship Manager at TfL, introduced our open data policy and what data would be released for the challenge

Introduction – Chirdeep Chhabra, Digital Catapult

  • Digital Catapult’s 4 main areas of focus: Sharing of data between organisations, personal data, content and licensed data and data generated across the Internet of Things
  • Data City | Data Nation overview: Brings together London and Singapore and private sector closed data in a sandbox for innovation, 6 months duration for the whole challenge. Transport and Mobility starts today
  • Aim is to produce new insight into public services and private products
  • Email dcdn@digitalcatapult.org.uk for more info

Read More

DevelopersNews

Traffic Data Hack Day – Event Review

As previously outlined in our post on March 30 on this blog, the Traffic Data Hack Day was hosted by Amazon Web Services on April 6. The event was attended by TfL employees, academics working within this subject area, data scientists, transport app developers and data visualisation developers.

Another key event in our engagement with those working with our open data, the day was split into two areas, with one focussed on visualising TfL data and the other on extracting data from the source and providing it for analysis.

I’ve not attended a hackathon or hack day before, so it was really interesting to see how they work and to meet participants from all sorts of backgrounds, including universities, consultancies, government agencies and other parts of TfL.

At the beginning of the day we split the focus into two areas; ‘EMR (Elastic Map Reduce)’ where the group was looking at ways to improve the feed of, access to and processing of the SCOOT data and ‘Redshift’ where the group made use of data that had been uploaded to the system and was ready to analyse.

teams working

A team working on ‘Redshift’ which made use of data that had been uploaded to the system and was ready to analyse.

Read More