Report an error
The marriage rate in Tennessee correlates with...
| Variable | Correlation | Years | Has img? |
| Popularity of the first name Jessica | r=0.99 | 23yrs | No |
| Popularity of the first name Laura | r=0.99 | 23yrs | No |
| Popularity of the first name Haley | r=0.98 | 23yrs | No |
| Popularity of the first name Cameron | r=0.98 | 23yrs | No |
| Popularity of the first name Deja | r=0.97 | 23yrs | No |
| Popularity of the first name Clayton | r=0.97 | 23yrs | No |
| Popularity of the first name Katarina | r=0.96 | 23yrs | No |
| Popularity of the first name Diane | r=0.94 | 23yrs | No |
| Popularity of the first name Kristofer | r=0.94 | 23yrs | No |
| Total annual sales of Ford Motors in the United States | r=0.91 | 23yrs | No |
| Annual US household spending on books | r=0.9 | 22yrs | No |
| Air pollution in Memphis | r=0.89 | 23yrs | Yes! |
| Air pollution in Memphis | r=0.86 | 23yrs | Yes! |
| Air pollution in Nashville | r=0.85 | 23yrs | Yes! |
| Air pollution in Knoxville, Tennessee | r=0.81 | 23yrs | No |
The marriage rate in Tennessee also correlates with...
<< Back to discover a correlation
You caught me! While it would be intuitive to sort only by "correlation," I have a big, weird database. If I sort only by correlation, often all the top results are from some one or two very large datasets (like the weather or labor statistics), and it overwhelms the page.
I can't show you *all* the correlations, because my database would get too large and this page would take a very long time to load. Instead I opt to show you a subset, and I sort them by a magic system score. It starts with the correlation, but penalizes variables that repeat from the same dataset. (It also gives a bonus to variables I happen to find interesting.)