| Transport for London Tech Lead here. In London, we have been collaborating with google waze - we provide them with information at the local level. Streets that waze should not use for route finding (e.g. roads with schools) can be blocked for use by Waze. Both local councils and TfL can provide this data. The main difference between Waze and Google Maps is that Waze uses real time traffic data. There are multiple map providers that do this in London. There is a plan to provide different data to different TfL data consumers in the future to try and get map providers to seperate traffic across roads (at the cost of surrendering absolute truth). London is also host to discussions of taxing roads - this is unsurprising when the roads are mostly paid for by the cost of the London Underground (LU makes the majority of public transport money, but 80% of revenue goes into road, traffic and bus management). The London Assembly (who supposedly keep the London mayor accountable) have written a paper "London Stalling" to suggest road taxing related to mileage across London. This, they no doubt expect, will cut down the traffic. However, from my understanding of embellished models of Braess' paradox, this will only result in similar traffic (on maybe slightly different roads) with an optimum equilibrium between how good a route is and what the cost of it is - meaning people may just take longer to commute and pay more tax. |
Google Maps has real time traffic data and the accuracy is staggering. I occasionally use Google Maps for navigation in the car and it even highlights traffic stationary at traffic lights and temporary road works as I’m approaching.
This level or real time detail really amazed me. I’ve not spent any time looking onto how they do it but assume they are continually tracking everyone with a phone, or at least running Google Maps Navigation, and using their real time location and speed.