Report an error
GMO use in corn grown in South Dakota correlates with...
Variable | Correlation | Years | Has img? |
Kerosene used in Nepal | r=0.98 | 22yrs | Yes! |
Popularity of the first name Yasmine | r=0.98 | 23yrs | No |
Physical album shipment volume in the United States | r=0.97 | 23yrs | No |
Kerosene used in Japan | r=0.96 | 23yrs | No |
Popularity of the first name Dakota | r=0.95 | 23yrs | No |
Divorce rates in the United Kingdom | r=0.95 | 13yrs | No |
Google searches for 'snoop dog' | r=0.94 | 20yrs | No |
Kerosene used in South Korea | r=0.94 | 23yrs | No |
Popularity of the first name Rhiannon | r=0.94 | 23yrs | No |
Remaining Forest Cover in the Brazilian Amazon | r=0.93 | 23yrs | No |
Violent crime rates | r=0.9 | 23yrs | Yes! |
The marriage rate in South Dakota | r=0.9 | 22yrs | No |
Google searches for 'cia hotline' | r=0.89 | 20yrs | Yes! |
Google searches for 'attacked by a squirrel' | r=0.86 | 20yrs | No |
Career regular season goals scored by Sidney Crosby | r=0.82 | 21yrs | Yes! |
GMO use in corn grown in South Dakota 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.)