On Monday 13th February, we will make a minor change to our Unified API responses so that they will no longer return absolute URLs as references to other API entities. They will now return a relative URL instead.
We don’t anticipate many developers are relying on these URLs being absolute, but if we’re wrong, please let us know as soon as possible in the comments section below or through the API portal.
Next Monday we’re making a minor change to our Unified API responses, so that they will no longer return absolute URLs as references to other API entities
Following my previous post on January 19, I can now confirm specific dates and timings for the implementation of our new configuration to TLS 1.2 and 1.3.
We’re implementing our new configuration to TLS 1.2 and 1.3 as a phased approach, starting at 10.30 tomorrow morning
This is an update to the previous post I published on Wednesday 21 December 2016, letting developers know that they need to update to a newer version of TLS.
Update: Open data users should aim to update their tooling to support modern TLS versions (1.2 and 1.3) by Wednesday 25 January
On Tuesday 20 December at 14:40, we deprecated support for older cypher suites such as SSLv3, TLS 1.0 & 1.1. This is in line with security best practice and helps protect our free services from the security issues identified in older versions of these technologies.
We’ve rolled back our change, giving open data users extra time to update their tooling to support modern TLS versions (1.2 and 1.3)
Taxis are an important, trusted and iconic part of London’s transport system, and they also offer a vital service for disabled people. There are currently around 640 taxi ranks in the capital, serving key locations and one in five of all taxi journeys start at a rank. We have released the location of all London taxi ranks in our Unified API, allowing open data users to enhance or develop new apps and products for customers planning taxi journeys.
Taxi rank data for ranks closest to stations, such as this one outside Waterloo, is now available to app developers through our Unified API
The City of London Corporation are planning essential major maintenance works to Tower Bridge. The work will require a full closure of the bridge to all vehicle and cyclist traffic for three months. The closure will be in place 24 hours a day, 7 days a week from Saturday 1 October to Friday 30 December 2016.
As part of our open data policy, we’re releasing a full data set of the closure to allow developers to easily incorporate this data into their apps, helping Londoners to plan their journeys while the works are ongoing.
The City of London will be carrying out essential maintenance on Tower Bridge. Full details of the closure are in our data set.
In partnership with AWS and Geovation, we were delighted to launch our Data in Motion Hack Week, with two launch sessions taking place on Friday 23 September. The launch set the scene for the challenge “Managing the Capacity of London’s Transport Network,” and we can’t wait to see the amazing solutions that are created to support this challenge and help improve the experience of those travelling in London. There are some great prizes on offer for the winners who will be announced at the end of this week.
We launched our Data in Motion Hack Week on Friday 23 September at the AWS office in London. Judging will take place this Friday when we expect some fantastic ideas to have been developed
Join us for a Hack Week launching on 23 September in London in partnership with AWS and Geovation to provide some great products for transport users. The use of our open data sets are fuelling entrepreneurship, accelerating scientific discovery, and enabling Londoners and visitors to travel more easily across the capital.
This Hack Week provides the opportunity to win some great prizes, including 6 months worth of support i.e. office space, business mentoring, access to technical and subject matter experts. So, whether you’re a start-up or a developer, if you are in a position to develop a product that addresses the challenges outlined below, you should join us at the launch event on 23 September. All entries will be judged by a panel in a closed environment to protect your idea.
There are over 500 apps powered by TfL data used by millions of people every day – we would like to see more.
Where and When
Venue: Amazon’s offices – 60 Holborn Viaduct, EC1A 2FD, London and remote access (more detail to follow.)
View on Google Maps
When: Hack for a week: September 23 – September 30, 2016. There will be two launch sessions on 23rd September, at 12pm and 6:00pm, so join whichever one works for you.
Free drinks and nibbles will be provided at the launch sessions.
We’re partnering with AWS and Geovation for the Hack Week from September 23-30 and we want your solutions help to manage the capacity of London’s transport network
Our open data policy has been a key priority over the last few years, and we’re proud to be at the forefront of the open data revolution, supplying our data to over 8,500 developers who are creating important products to help keep London moving. Visualisation of our data can be particularly impressive, and there’s a great example of this with the “Tube Heartbeat.”
The Tube Heartbeat visualises the volume of passengers using the Tube. It also goes right down to the platform level, the number of entrances and exits, and even the number of people aboard each tube train.
The first Night Tube services launch on the Central and Victoria lines on Friday 19 August, offering a 24-hour service on Fridays and Saturdays. Services on the Jubilee, Northern and Piccadilly lines will follow in autumn. The Night Tube will be pivotal to London’s night economy, and with over 500 apps powered by our Open Data, we’re pleased to announce the addition of Night Tube data into our Unified API.
The Night Tube launches on the Central and Victoria lines on Friday 19 August – data is available in our Unified API