Category: News

News

Active Travel Hackathon 2018

on March 29, 2018

**UPDATE** Unfortunately, we will be postponing this event until late May/early June due to a series of conflicting events. We have had a great number of diverse registrants so far and look forward to seeing you all with many more registrants in a number of weeks.

We will be updating the registration website with a new date very soon.

For those already signed up, you will receive the new date via email and you will not need to re-register.

We apologise for any inconvenience this causes.

Join us for the Transport for London (TfL), Met Office, and Amazon Web Services (AWS) London Hackathon at Amazon’s office in London.

This is a two-day event sponsored by Cloudreach, where you will have the opportunity to compete against other teams of developers to create the most innovative application running on AWS.

Learn from subject-matter experts from TfL, Met Office, and Cloudreach to help address some of London’s key challenges.

The Vision

The recently published Mayor’s Transport Strategy sets out a vision “to make London a city where people choose to walk and cycle more often by improving street environments, making it easier for everyone to get around on foot and by bike, and promoting the benefits of active travel.”

This vision aims to reduce traffic, pollution, and noise; and to create more attractive, accessible, and pedestrian-friendly streets for citizens. A more engaged, physically active society leads to a healthier people.

The plan includes a target that 80 percent of all Londoners’ trips will be made by foot, bike, or public transport by 2041. Achieving this goal will require a considerable shift in behaviour citywide.

This is where you come in! We want to open this challenge to the wider developer community to find innovative solutions to this key challenge. Through teamwork, TfL believes we can provide our audience with the best information, tools, and encouragement it needs, to help influence behavior toward more sustainable and active travel.

Ahead of the event, we encourage you to think about the challenges below and will provide you with the data concerning cycling, walking, air quality, weather, and roads.

The Challenges

Encourage a mindset shift:

Encourage active travel for the first and last miles. Drive good behaviour through social influence by making it easier to share travel plans and through wearables. Inspire the development of new travel planning technology and features. Encourage combining TfL and Met Office data to develop air quality/active travel products.

Enable and support more active travel:

Improve the functionality and personalisation of existing active travel journey-planning and navigational tools (e.g. routing features enhanced by new cycling and walking data), and build new resources and technology.

Empower users to share feedback:

Develop new tools and enhancements to allow crowd-sourcing of customer feedback and reporting of data errors (to support management and maintenance of cycling and walking datasets). Provision new mechanisms for communicating expectations for healthy streets and the barriers / improvements that can inform future policy development.

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 10 April.

Where and When

Venue: Amazon’s offices – 60 Holborn Viaduct, EC1A 2FD, London

When: April 10 – April 11, 2018

Free drinks and nibbles will be provided at event.
Through this transport-focused Hack event, TfL, AWS and Met Office are keen to work with the start-up community, app developers, UX and design specialists, and anyone with a passion for data in order to build new applications and unlock new insights from the data.

We’ll ‘hack’ on 10 April from 10:00 to 18:00, and resume on 11 April from 10:00 to 16:00.

You will receive AWS Promotional Credits, which will help you take your project from idea to implementation. Subject-matter experts from TfL, AWS solutions architects, and developers from Cloudreach and Met Office will be onsite to provide support and mentorship. At the end of the two-day hackathon, a panel of experts will choose the most innovative application, and prizes will be awarded.

What you’ll need

You will need to bring a laptop and you will need an AWS account. AWS credits and an API will be provided to access the data.

Places are limited so please register quickly at https://travelhackathon2018.splashthat.com/ to not miss out on this great event!

We look forward to seeing you there!

APIDevelopersNews

Unified API: New data – Electric Vehicle Rapid Charging Points

on March 19, 2018

Zero emission capable (ZEC) vehicles have environmental and financial benefits, and are vital to London becoming a zero carbon city by 2050. We are working with partners to develop a network to help you charge them quickly and efficiently.

Rapid charge points can charge an electric vehicle battery in 20-30 minutes. This is quicker than regular charge points that can take 7-8 hours for a full charge.

The majority of these charge points allow for pay as you go payment using a credit or debit card – you don’t need to be a member.

They allow high mileage users, such as electric taxi and private hire drivers and freight and fleet operators, to quickly charge their vehicle. We have committed to install 150 rapid charging points by the end of 2018 and have at least 300 by 2020.

Electric Vehicle Rapid Charge Point (ECP) data is supplied to us from a number of concessionaires who install and manage charge stations across the UK and Europe. These concessionaires include British Gas, Charge Master, FastNed, Bluepoint and ESB, although at present not all of them have facilities in the Greater London area.

We consolidate the data, which is provided in a client-specific format, into a common structure available through the TfL Unified API that third-party users can consume in a simple, generic way. We have worked closely with Zap-Map, the leading source of information on EV charging points for the UK, to fine tune our API data for third party users. You can view the TfL points on their map and filter on taxi only rapid charge points.

Screenshots of Zap-Map app showing TfL Charge Point for taxi use only at East Finchley LU Car Park

Although the physical ECPs can differ considerably between concessionaires and even a single concessionaire can have different models of charge stations, we transform the data associated with them into a consistent, dynamic parent-child structure of ChargeStation with one or more ChargeConnectors.

As part of our import process of this data, we exclude ChargeStations (and therefore related ChargeConnectors) that are considered outside of the Greater London area.

Charge Stations and Connectors

A ChargeStation is the physical appliance, that may be one of several in a specific location. It has a unique identifier and name, as well as being designated to a latitude-longitude position.

It is also possible that a single ChargeStation can support multiple parking spaces.

A ChargeStation can have one or more ChargeConnectors. The connectors represent the physical connecting alternatives that can be accessed at a time, and each one has a unique identifier and name, as well as an occupancy status associated with this element, along with the other properties, detailing the type of connection, power, etc.

Unified API

From the TfL Unified API, both the ChargeStation and ChargeConnector core data is available via the existing Place endpoint(s) and the current availability of a ChargeConnector is through the Occupancy endpoint(s).

The core data is the key information that describes the Station and Connector, and the information that comes from the concessionaires is accessible via the additionalProperties field collection. The most relevant attributes of each additionalProperty are the category, key, and value. Common keys for all ChargeStations are “ConnectorCount”, “Location”, “Name”, “Reference”, “PricingUrl” and “Restrictions”. Common keys for all ChargeConnectors are “ConnectorDescription”, “ConnectorType”, “ParentStation”, “Power”, “Status”.

Special Note: The “Restrictions” field will identify if the charge station is for Taxi Use only.

The core data is updated daily from the independent concessionaires and we recommend this data is downloaded and stored on local servers for reference and performance.

You can specifically request the different Place Types, but in doing so you will not get the parent-child mapping between the two. The recommended request is as follows, which will return all Greater London ECPs.

https://api.tfl.gov.uk/Place/Type/ChargeStation,ChargeConnector

The response to this request would include a collection of all ChargeStations with child ChargeConnectors, as well as ChargeConnectors as top-level objects. A request can be made using the Place endpoint and the unique id to return just a single Place.

[{
 "$type": "Tfl.Api.Presentation.Entities.Place, Tfl.Api.Presentation.Entities",
 "id": "ChargeMasterChargePoint_ChargePointCM-24114",
 "url": "/Place/ChargeMasterChargePoint_ChargePointCM-24114",
 "commonName": "Q-Park, Oxford Street, Cavendish Square Station 24114",
 "placeType": "ChargeStation",
 "additionalProperties": [
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Name",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Q-Park, Oxford Street, Cavendish Square Station 24114",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Reference",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "ChargePointCM-24114",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Location",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Q-Park, Oxford Street, Cavendish Square, London, W1G 0PN, GB",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Url",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "https://chargemaster.com",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorCount",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "3",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "PricingUrl",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "https://polar-network.com/tfl-pricing/",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Restrictions",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Public",
 "modified": "2018-02-24T17:44:21.223Z"
 }
 ],
 "children": [
 {
 "$type": "Tfl.Api.Presentation.Entities.Place, Tfl.Api.Presentation.Entities",
 "id": "ChargeMasterChargePoint_ChargePointCM-24114-49925",
 "url": "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49925",
 "commonName": "Q-Park, Oxford Street, Cavendish Square Station 24114 Connector 1",
 "placeType": "ChargeConnector",
 "additionalProperties": [
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ParentStation",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "ChargePointCM-24114",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Status",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Available",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorType",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "CCS",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorDescription",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Combined Charging System",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Volts",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "400",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Amps",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "125",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Power",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "50kW",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Phase",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "DC",
 "modified": "2018-02-24T17:44:21.223Z"
 }
 ],
 "children": [],
 "childrenUrls": [],
 "lat": 51.516525,
 "lon": -0.144647
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.Place, Tfl.Api.Presentation.Entities",
 "id": "ChargeMasterChargePoint_ChargePointCM-24114-49926",
 "url": "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49926",
 "commonName": "Q-Park, Oxford Street, Cavendish Square Station 24114 Connector 2",
 "placeType": "ChargeConnector",
 "additionalProperties": [
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ParentStation",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "ChargePointCM-24114",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Status",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Available",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "OriginalConnectorType",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "CHADEMO",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorType",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "CHAdeMO",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorDescription",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Type 4 CHAdeMO",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Volts",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "400",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Amps",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "125",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Power",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "50kW",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Phase",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "DC",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Cost",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "",
 "modified": "2018-02-24T17:44:21.223Z"
 }
 ],
 "children": [],
 "childrenUrls": [],
 "lat": 51.516525,
 "lon": -0.144647
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.Place, Tfl.Api.Presentation.Entities",
 "id": "ChargeMasterChargePoint_ChargePointCM-24114-49927",
 "url": "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49927",
 "commonName": "Q-Park, Oxford Street, Cavendish Square Station 24114 Connector 3",
 "placeType": "ChargeConnector",
 "additionalProperties": [
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ParentStation",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "ChargePointCM-24114",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Status",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Available",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "OriginalConnectorType",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "IEC62196_2TYPE2CONNECTOR",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorType",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Type 2",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "ConnectorDescription",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "Type 2 Connector",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Volts",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "400",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Amps",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "63",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Power",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "43kW",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "ElectricalCharacteristics",
 "key": "Phase",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "AC3",
 "modified": "2018-02-24T17:44:21.223Z"
 },
 {
 "$type": "Tfl.Api.Presentation.Entities.AdditionalProperties, Tfl.Api.Presentation.Entities",
 "category": "Description",
 "key": "Cost",
 "sourceSystemKey": "ChargeMasterChargePoint",
 "value": "",
 "modified": "2018-02-24T17:44:21.223Z"
 }
 ],
 "children": [],
 "childrenUrls": [],
 "lat": 51.516525,
 "lon": -0.144647
 }
 ],
 "childrenUrls": [
 "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49925",
 "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49926",
 "/Place/ChargeMasterChargePoint_ChargePointCM-24114-49927"
 ],
 "lat": 51.516525,
 "lon": -0.144647
 }]

To check the current status, use the Occupancy endpoint, passing the type name of ChargeConnector and comma delimited array of relevant ChargeConnector ids.

https://api.tfl.gov.uk/Occupancy/ChargeConnector/CPBP-ccecd35e-94b1-4056-878b-aa99bf8b5e58-1,CPBP-0a06d81f-a489-40b7-b866-a52fe3da71aa-1

You can exclude the ChargeConnector ids, but this is not recommended as it will return the current status of every connector across the Greater London area, and may take a few seconds to download.

The status is updated within our system every five minutes, but the response is only cached for 60 seconds. The response includes

[{
        "$type": "Tfl.Api.Presentation.Entities.ChargeConnectorOccupancy, Tfl.Api.Presentation.Entities",
        "id": 41441,
        "sourceSystemPlaceId": "CPBP-0a06d81f-a489-40b7-b866-a52fe3da71aa-1",
        "status": "Available"
    },
    {
        "$type": "Tfl.Api.Presentation.Entities.ChargeConnectorOccupancy, Tfl.Api.Presentation.Entities",
        "id": 41440,
        "sourceSystemPlaceId": "CPBP-ccecd35e-94b1-4056-878b-aa99bf8b5e58-1",
        "status": "Not Available (Fault)"
}]

Current status values include: “Available”, “Broken”, “Future”, “In Use”, “Not Available (Fault)”, “Not Available (Future)”, “Operational”, “Unknown”, “Unknown (Not Available)”

If an invalid ChargeConnector id is supplied, then a 404 response will be returned indicating any charge connectors not recognised.

https://api.tfl.gov.uk/Occupancy/ChargeConnector/CPBP-ccecd35e-94b1-4056-878b-aa99bf8b5e58-1,CPBP-0a06d81f-a489-40b7-b866-a52fe3da71aa-1,jkhjkashdkjh

The response to the above request would be:

{
    "$type": "Tfl.Api.Presentation.Entities.ApiError, Tfl.Api.Presentation.Entities",
    "timestampUtc": "2018-01-24T14:55:27.980254Z",
    "exceptionType": "EntityNotFoundException",
    "httpStatusCode": 404,
    "httpStatus": "NotFound",
    "relativeUri": "/Occupancy/ChargeConnector/CPBP-ccecd35e-94b1-4056-878b-aa99bf8b5e58-1,CPBP-0a06d81f-a489-40b7-b866-a52fe3da71aa-1,jkhjkashdkjh",
    "message": "The following charge connectors are not recognised: jkhjkashdkjh"
}

Additional Place endpoints allow for Places (and of a specific type) within a bounding geobox.

As always, we love to hear what you are building with the API, or if you have any questions, let us know in the comments below or on our Tech Forum.

* As always, the API usage examples in this blog are anonymous, so the quota is strictly limited. For a real application, developers should register for an API key.

News

Help solve city wide challenges at City Data Hack (16–18 March 2018)

on March 8, 2018

 

cityhack2

City Data Hack 2018 at The Urban Innovation Centre in Clerkenwell will bring together talented and passionate participants, mentors and challenge partners who are keen to transform the experiences of citizens through data and digital solutions. TfL’s challenge is to ask participants to come up with ideas on how to improve Travel Plans to help us meet our targets for increasing use of public transport and active travel (cycling and walking) in the city.

cityhack

Future Cities Catapult have partnered with three organisations who influence the way that the city is experienced by millions in London each day — Greater London Authority, Transport for London, and London Borough of Barking and Dagenham.

Challenge partners have set City Data Hack 2018 three challenges to be solved over the weekend, each with a strong social or economic focus.

Why are we supporting City Data Hack 2018?

Like Future Cities Catapult, we believe that collaboration with multi-skilled experts is essential for solving city problems — and that embedding data, analytics and AI into service provision will generate better outcomes for future generations.

Future Cities Catapult and Space Syntax’s Tombolo project has spent the past two years researching how public organisations are using data and developing products to help solve city data challenges. They soon realised that there’s a growing number of people with the same mission and that’s why they organised City Data Hack 2018.

Aims for the weekend

  1. Most importantly, Future Cities Catapult want to make sure that all hackers and mentors have fun
  2. We would love it if participants created something amazing, and we have a hunch that multi-skilled teams with the right mentorship will achieve a rewarding outcome
  3. Future Cities Catapult want to show other public sector organisations that events like this can spur on grassroots innovation and investment

Prizes

The main purpose of the Hackathon is to bring together passionate people to tackle city challenges. But Future Cities Catapult are offering an additional incentive for your time. A chance to win up to £1,000 worth of prizes, which will be split across the winning team and individuals who take part in the weekend.

Plus, they’ll be offering individual prizes for social media and GitHub contributions across the weekend.

How can you get involved?

An overwhelming number of people have already registered their interest in the event but you can still take part.

Participants

There are a handful of places left for next weekend’s Hackathon.

Sign-up now if you would like to take part. Once they’re gone, they’re gone.

Mentors

Future Cities Catapult are still looking for mentors. If you have experience mentoring Hackathons and would like to help guide participating teams to success get in touch with the organisers on twitter @tombolo_ or by emailing info@tombolo.org.uk

Partners

We’re excited to be part of this event but Future Cities Catapult have also lined up some other amazing partners:fccpartners

If you attend the event, let us know your experiences in the comments below. We’d love to hear from you!

NewsTech Partnerships

Waze partnership: Reducing congestion at Blackwall Tunnel

on January 11, 2018

36 million journeys are made through London’s Blackwall Tunnel every year making it one of the busiest and most congested sections of London’s road network.  It is also one of the worst locations in the city for breakdowns which cause nearly 400 hours of delays and cost Londoners almost £7m in wasted time.  TfL’s Travel Demand Management Team reviewed historical data on breakdowns in the tunnel and found that vehicles running out of petrol were one of the highest frequency causes.

 In order to target this hyper local problem, we partnered with Waze and used their advertising platform to remind drivers approaching the tunnel to refuel.  As a result, from end of May 2017 to end of November 2017, we saw 459 Waze users re-route to a nearby petrol station, drastically reducing the risk of breakdowns from fuel shortages in the tunnel.

Due to the success of the Blackwall Tunnel adverts, we are now looking at how we can use advertising in the Waze app to provide peak time congestion information to drivers and encourage them to avoid the busiest times at specific locations in order to have a quicker journey.

News

AECOM CityHack event

on December 12, 2017

Digital technology and data are transforming London’s future. Just from our open data activity alone, there are over 600 apps in London being powered by TfL data and economic benefit of £130m per year in terms of customer, TfL and city-wide value being generated.

However, we want to further harness our data to make the capital a more healthier, liveable and connected place.

Alongside a number of other public bodies: City of London, Environment Agency and the Greater London Authority, we have partnered up with AECOM for their CityHack event that will take place over the weekend of 26th – 28th January 2018.

AECOM will bring together some of the best and brightest minds who are passionate about harnessing data and technology to develop a digital solution to those challenges each of us have set forth that will have a positive impact on London.

For TfL, we want to provide customers with the best information, tools and encouragement that can influence behavioural change towards more sustainable and active travel. We hope to encourage:

  • Active forms for the first and last miles
  • Better promotion of active travel routes
  • Active travel as a more preferable option on planning tools
  • Use of wearables
  • Development of new complementary products that support active travel i.e. not just digital

 Key details for the event:

  • 80 hackers
  • 30 hours
  • 4 challenges
  • AECOM will be awarding a £7,500 prize

 Please see https://cityhack.aecom.com for more details.

We look forward to seeing the results of this hackathon across the weekend and will post about the event in February.

#CityHack18

@AECOM

DevelopersInformationNews

New study quantifies value of open data to London

on October 13, 2017

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.

Northern ticket hall entrance to Kings Cross St. Pancras Underground station

There are more than 600 apps powered by TfL’s open data, and these are used by as much as 42% of Londoners.

Read More

DevelopersNews

Developers – help us improve our open data

on September 20, 2017

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. 

 

DevelopersNewsTech Partnerships

Accelerator programme for mobility start-ups

on September 18, 2017

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.

Read More

DevelopersNewsProducts

How we built the TfL Customer API

on September 15, 2017

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.

app_feature_graphic_1024x500

The TfL Oyster app launched last week – let us know what you think in the comments section below.

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.

Read More

DevelopersNewsProducts

New open data: Busiest times at Blackwall Tunnel

on July 4, 2017

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.  

Our data shows the busiest times at Blackwall Tunnel so developers can include this information in journey-planning apps

What our data shows

*Follow this link to find the data.

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.

1 2 3 … 12