Further to the Shakespeare Review which used TfL’s open data activity as a case study in 2013, we asked Deloitte to carry out a more comprehensive study on the value of open data to our customers, users and London overall.
We’re holding a consultation into our Transparency Strategy, and we’d love to hear from you about how we can improve.
The Strategy covers our open data products, so we want to hear from the developer community about our Unified API and open data. We want to know how we can improve our products to give you regular, up to date and useful information, as well as the formats in which this data should be published.
We’re also keen to hear how you think this data should be grouped or presented on the TfL website, and whether we need to give further support to developers, stakeholders and researchers who use it.
The consultation is running for six weeks, from 18 September to 29 October.
While we always encourage comments to these blog posts, to make sure your voice is heard visit our Consultation website to have your say.
It’s great to see so many customer-facing apps using TfL’s open data. With over 600 apps in areas of public transport, active travel and healthier streets, we are continually focused on releasing new data.
There are lots of people involved in the ecosystem, ranging from app developers and start-ups to accelerator programmes.
We are excited to launch our new TfL Oyster app on iOS and Android, which allows customers to top up their Oyster cards, purchase Travelcards and view their journey history. The app was launched last week, and has already received lots of great feedback. We wanted to offer you more insight into how we developed it.
An API – or application programming interface – is a set of subroutine definitions, protocols and tools for building application software¹. We already have a wide range of public APIs, which provide information such as line status, bus status and journey information. To build a mobile application allowing customers access to their Oyster card data through, we needed to write a new API to support this.
The Blackwall Tunnel (A102) is one of the busiest places on London’s road network. In recent years, journey times have increased and drivers can expect delays to their journey at some times of day. We’ve released this data to the open data community, to enable developers to build the information into their products.
What our data shows
1) The busiest time in the northbound tunnel on a weekday is from 07:00 – 07:30. In heavy traffic conditions, drivers’ journeys could be 15 minutes quicker if they travelled between 06.30-07.00 instead of 07:00 – 07:30.
2) The busiest time in the northbound tunnel on a weekend is from 13.30 – 15.00. In heavy traffic conditions, drivers’ journeys could be 15 minutes quicker if they travelled between 12.00-13.00 instead of 13.30- 15.00.
We have made this data available to the open data community so you can use it to create products which display the busiest times at the tunnel, allowing drivers to choose to travel outside of these periods or create products for planning quicker and more reliable journeys.
Tell us what you think
We encourage the community to provide feedback on our new data sets to help us continue to enhance and improve our open data products. Please let us know your thoughts in the comments section below or on our tech forum.
It was great to be part of London Tech Week through the excellent Hack Day on Friday June 16, put together by the teams at Ticketmaster and Transport for London. With over 600 apps powered by our data in the market place, I always look forward to these events as it allows me to raise awareness of TfL’s open data approach providing the opportunity for organisations and individuals to develop their own creative solutions.
This has helped to form new businesses, create jobs and launch new customer-facing travel products, giving customers more choice on their devices. A great part of this process is that this type of event is open to everyone at no cost, so we saw students, corporate professionals, freelancers, academics and participants from other sectors.
We’re proud to introduce our Facebook Messenger TravelBot, which has the ability to provide updates on bus arrivals as well as Tube and bus status updates.
Through our two Facebook pages – the main TfL page and the London Underground page – we deal with a huge number of queries every day, and we wanted to make it even easier for customers to get our information on the Facebook platform in a way that’s fast and straightforward. With the open data in our Unified API already helping to provide live information on many services like third-party apps and Twitter alerts, we hope this will be another big step towards enabling customers to quickly and easily access the information they need via social media.
As part of London Tech Week, TfL are teaming up with the market-leading ticketing company in the UK, Ticketmaster, to host a hackathon at their London HQ. Bring your ideas to life at the London Hack Day, hosted by TfL and Ticketmaster on Friday June 16.
It’s great to see that there are now over 600 apps using TfL’s datasets to develop customer facing products, and these products have a huge role to play in helping people to move around the capital. The Digital Partnerships team at TfL continues to engage with developers through this blog, the recently launched Tech Forum, as well supporting the introduction of new data with recent examples including Cycle Superhighways, Cycle Quietways and busiest times at stations. We are also looking at ways to improve our data based on your feedback.
We’re delighted to announce that the TfL Tech Forum is now live, and is ready for you to use right away. With more than 11,000 developers working with our open data to develop innovative products, the TfL Tech Forum will be a lively space where developers can connect with experts from the TfL Online team, providing a platform for discussion around all aspects of our open data and Unified API. With over 600 travel apps powered by TfL, it’s great to see new product features being developed, and a key area of focus is accessibility (see this previous blog) – we encourage you to develop new features for your product using our data.