We actually work with a lot of different data providers to be able to deliver a seamless experience in one window. Although this is a complex work for developers due to all the different data formats, it provides a failsafe in case there is a technical issue with just one dataset as it won’t make the whole journey planner unavailable to you. Bellow are the main data providers and datasets we use: Map layers Car Clubs: We connect to a dataset in Open Data Bristol which combines data from each car club to retrieve locations for their bays. This updates every 24 hours. Charge Points: We connect to the Data.gov.uk’s National Charge Point Registry to retrieve charge point locations. Cycle Hire: We connect to YoBike for live locations. Train Stations: We connect to data from National Rail’s Darwin API. Rider Zones: We connect to an API available at https://opendata.bristol.gov.uk/explore/dataset/rider-zones/, updated by our own team. Travel information Bus and rail live arrivals and departures: For bus live arrivals we connect directly to the same supplier who provides the information for the real time displays at bus stops in the West of England. We also use National Rail’s Darwin API for rail information. Bus stops (including Park & ride), bus routes and timetables: This data is sent separately by bus operators to each of the Local Authorities in the West of England. It’s then manually sorted and quality checked by Local Public Transport Teams and uploaded into a system used by Traveline Southwest (aka SWPTI) for sorting. The sorted  data is then sent back to us in a different format and combined into one single developer friendly data source by a process designed internally so that we can use it in our Journey Planning tools. This guarantees that our data is always the most recent. Public Transport (Bus + Rail) + Walk Journey Planning: We connect directly to the SWPTI API provided by Traveline Southwest for these results. Traveline uses their own smart algorithm to calculate the best journey options using public transport data from bus and rail operators. Drive Journey Planning: We connect to the Google Directions API for these results. Cycle Journey Planning: We connect to the Cycle Streets API for these results. Walk Journey Planning: We connect to the Google Directions API for these results.