Travel Time vs. Toll Costs: A Traffic Case Study of Toronto’s 407 and 401
Discover how commercial vehicle data reveals the true cost of congestion on Toronto’s 401 vs. the 407 toll road in time, emissions and money.
Planners must make data-driven recommendations for new transportation infrastructure or road network improvements with a comprehensive understanding of vehicle movements in their regions. To facilitate this, data must be highly thorough and accurate in order to run effective traffic analyses. But does the vehicle data collection method make a difference in the analysis?
When it comes to collecting vehicle data, there are two generally accepted methods. One is connected vehicle data (CV data) from a telemetry source (like Geotab). This type of data uses actual engine-level data that is granular. It will contain contextual information like vehicle classification (Class 1-8), engine type (ICE, EV, PHEV) and more accurate GPS location information. It is very precise because connected car technology lets equipped vehicles send their location and other data directly to a manufacturer or fleet center.
The second data collection method is location-based service data (LBS data). Generally built on mobile data from cell phones and other mobile applications, LBS does not provide visibility into the contextual vehicle information described above with CV data. LBS data will instead infer the type of vehicle (i.e., it could be a heavy-duty truck based on how it moves) but lacks a definitive method to confirm the details.
LBS provides planners with enough insight to know that a vehicle drove down a particular road at a specific time but does not provide insight into vehicle class, engine type, etc. LBS is also more susceptible to GPS drift, a term describing a discrepancy between your actual location and the location recorded by a GPS receiver. LBS can be prone to over-counting biases or capturing duplicates if multiple connected phones are inside a vehicle.
Here’s a breakdown comparing the two data collection methods:
Connected vehicle Data | Location-based services data |
---|---|
Generated by vehicles equipped with various sensors or telematics systems
|
Derived from mobile devices equipped with GPS or other positioning technologies.
|
Includes data collected from the vehicle’s internal systems, such as classification, speed, acceleration, fuel consumption and engine diagnostics
|
Includes data related to the user’s location using GPS
|
Demonstrates movement patterns and paths of vehicles over time, which supports additional contextual information for analysis (e.g., machine learning for vehicle vocation, identifying vehicle’s home base and understanding the true origin and destination of vehicles)
|
Trips are identified individually, meaning any historical LBS data cannot be linked together to show vehicle patterns.
|
Real-time communication between vehicles and external networks or cloud platforms enables continuous data transmission
|
Data is collected and stored locally on the device or transmitted intermittently when network access is available.
|
95% location accuracy using antennas for consistent reception within 3 meters
|
Connectivity issues can surface, resulting in locational errors, especially if a mobile device is kept inside a pocket or plugged into OBD ports
|
Simply put, all vehicle location data are not created equal.
To solve complex transportation management issues, analysts need to have all the relevant information at hand. Connected vehicle data provides tremendous granularity into vehicle behavior and captures many data parameters for analysts to slice and dice the information and identify patterns and traffic trends. Transportation planners can start to understand the performance of vehicles and the efficiency of their local transportation networks on a more precise level.
While LBS data provides surface-level insights for traffic counts at a particular time, it does not tell the whole story. CV data can show which types of vehicles are on the road, their purpose for being on specific routes, where they are starting from, and where their destination is. This type of contextual information allows public and private transportation agencies to improve their road networks’ safety, efficiency, sustainability and profitability.
Connected vehicle data offers a comprehensive perspective that is crucial for transportation planners regarding infrastructure management, traffic optimization and safety considerations. Consider these real-world examples of where the added contextual information of CV data, like vehicle class and type, will play an integral role.
Having CV data makes completing necessary analyses, like the examples above, more accurate and provides better quality data, making the decisions more relevant and timely. This data provides the most user flexibility, with filtering capabilities to get an accurate picture of what kind of traffic is moving and how fast, to where, and for how long.
In addition to using connected vehicle data, analysts should look for data vendors that are their own data source vs. a third-party aggregation provider. This reduces the risk of loss of access to data. Geotab is the source for all of the data used in the Altitude platform, with over 3.6M connected vehicles and 55 billion data points.
For more information about the connected vehicle data analytics available in the Altitude platform, visit our webpage.