By: Laura Schewel on June 6th, 2017

Print/Save as PDF

Introducing StreetLight Volume: 2016 AADT Metrics

Validation  |  Smart Cities  |  Big Data  |  Transportation  |  Software Updates  |  Location-Based Services

After many years of client requests, we’re releasing the first cut of our StreetLight Volume: 2016 AADT Metric on the StreetLight InSight® platform. These beta Metrics provide a very robust estimate of 2016 Annual Average Daily Traffic (AADT) for almost any road in the US.  To learn more, keep reading this blog post, or watch our recorded webinar on the new Metrics. Click here to watch the webinar. 

We believe this Metric provides estimates that are comparable or better than most of the standard AADT estimation practices for three reasons:

  • They can be obtained in just a few minutes from the cloud-based StreetLight InSight platform,
  • They are built by integrating four sources of data (including both GPS and Location-Based Services data, which is our new and better alternative to “cellular tower” data), and
  • They cost less than half as much as typical AADT data collection and estimation processes.

In this blog post, we’ll walk you through our process for creating this Metric. It covers defining goals and developing our methodology as well as the validation and QA work that make us very confident in this Metric. In short, we predicted ~25,000 Virginia Department of Transportation AADTs with an R2 of 0.87 and average error of 22% (see Figure 1 below).

 

StreetLight AADT vs VDOT 2015.png

Figure 1: Scatter plot of StreetLight Volume: 2016 AADT values and VDOT AADTs for continuous loop VDOT counters (type A).

 

1. Defining Our Goals

For this initial release, we’re focusing on simple AADT. Our goal for this beta release is to ensure the technique works on large and small roads, in rural and urban parts of the country. Collecting AADT data on far away, rural roads is particularly expensive for our clients, so we hope this is a high value place to begin. We’ll expand to other types of count estimates in the future, such as hourly, seasonal, and more. 

 

2. Our Data Sources

This Metric is our most advanced yet. It combines both Location-Based Services (LBS) and navigation-GPS data, as well as the US census and a set of well-validated loop counters. We know others have previously tried to build volume analytics and estimated counts from probe data with varying levels of success. For us, these Metrics are only feasible because we have both GPS data (this data source excellent spatial precision and limited sample size) and LBS data (this data source has better normalization potential and larger sample size), and we are able to integrate these unique data sets. 

 

3. Developing the Algorithm

First, we used the census data to normalize the LBS data (see our sample normalization blog for more on this). Next, we used the navigation GPS data and LBS data to balance each other and scale most of the way up to AADT.

Finally, we used a few high-quality AADT counters from some of our DOT partners and a subset of the TMAS database to fine-tune the algorithm. We determined that the algorithm works best for roads with over 400 AADT. 

 

4. Running the Algorithm

After we developed the algorithm, we looked for large sets of AADT to test it against. In this blog post, we will show you the test we performed on VDOT’s public AADT file.

To do this test, we used our algorithm to generate estimated AADTs for ~25,000 links in VDOT's public AADT file. These links cover the entire state: big roads and small, urban and rural. We ran the algorithm “blind,’ which means we did not use VDOT’s AADTs when creating the algorithm.

Note: To generate 25,000 links effeciently for use in StreetLight InSight, we had to make some assumptions when we uploaded the VDOT shapefile. (Check out our tutorial on "Making Road Segment Zones" to see why.) We hypothesize that this quick assumption-making to draw the location of the gates could be a source of error, and that these errors could be avoided by our clients who know their own links in detail.

 

5. Quality Assurance

We had to drop out a few segments for obvious flaws. For example, VDOT had a value of 0 or “NA” for some AADTs. Next, we calculated the error for each link (the difference between the VDOT AADT estimate and StreetLight Volume: 2016 AADT, as a percent of the VDOT AADT). We also took a deeper look at some of the outlier error locations.

For example, we had three Zones that were classified as “A”, or high-quality continuous loop counter data from VDOT, that were also outliers. These loop counters are located in Bristol, VA (see Figure 2 below). The pink lines are VDOT’s road segments. The blue bar is our AADT gate. VDOT has three different values on West Main Street (14000 at A, 8800 at B, and 23000 at C). StreetLight InSight estimated an AADT of 22,944 for the bidirectional segment. 

For the A and B segments, we see two different values - even though there is no way for a car to get off the road between them. This immediately raises questions about the VDOT data. Perhaps one link is misplaced or mislabeled.

Next, all three VDOT values purport to be the bidirectional AADT. Thus, both sides of the street should show the same value, as is common in other split roads in the VDOT file. If we look at Segment C, our estimates are extremely close (less than 2% off). Thus, we considered the errors on A and B to be outliers, and we dropped them from the analysis.  We eliminated points like this from the sample. 

StreetLight AADT_Bristol Outliers Example.png

Figure 2: Bristol outliers -- as shown above, StreetLight Volume: 2016 Metrics match Segment C extremely closely. 

 

6. Validation 

Next, we compared our results to the cleaned VDOT data for validation purposes. We wanted to see three outcomes:

  1. Good overall correlation and small average errors.
  2. Better correlations and fewer errors when compared to the higher-quality VDOT estimates versus the lower quality estimates.
  3. Similar outcomes across the state and across different sized roads.

As shown in Table 1 below, the average absolute error and the correlation are very low and high, respectively.  The worst average absolute error is for Class N- AADT of Similar Neighboring Link, which is the lowest quality form of (non) count.

StreetLight AADT_VDOT Count Class breakdown.png

 

As shown in Figure 3 below, the algorithm works similarly well for the smaller roads and the large highways. The slight staircase shape of the scatter plot is a result of the fact that we followed VDOT’s rounding conventions (to the nearest hundred or thousand).

 

StreetLight AADT vs. VDOT 2015 Scatterplot.png

Figure 3: Scatter plot of StreetLight Volume: 2016 AADT and VDOT AADT for ~2500 locations.

 

7. We Need Your Feedback

This is the first public iteration of our StreetLight Volume: AADT Metric. We’d like to hear from you:

  1. Do you have counts that you can share for another validation study?
  2. Did this Metric not work for you in a certain location?

Leave a comment below to share your feedback, or send us an email at [email protected]. For a more detailed overview of these Metrics, join our webinar on June 16th at 12pm PT. Click here to register for the webinar. 

We know that our clients want other types of estimated counts – such as by time or day, weekday/weekend, season, and for origin-destination and other studies. These are coming soon! We want to collect feedback on our initial AADT Metric, and then use that feedback to guide upcoming product developments.

 

Tranport and Urban Planning mobile analytics