On Monday night, the EvolvingWild twins, Josh and Luke Younggren,  discovered that the shot location data the NHL provides to the public has been grossly inaccurate so far over the beginning of this young season. This is a significant discovery and problem for fans and public analysts of the game who rely on metrics and models that use shot location data in their calculations.
Josh and Luke announced this discovery via twitter @EvolvingWild in a series of tweets.
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
Looking at some video, I noticed a weird trend in the distances of events &#8211; they were all recorded several feet further away from the net than in the past. In addition, xG values this year are down across the board. This Mantha goal was recorded 6ft from the net, 37% xG: <a href="https://t.co/d8BbCVdGbx">pic.twitter.com/d8BbCVdGbx</a>
&mdash; EvolvingWild (@EvolvingWild) <a href="https://twitter.com/EvolvingWild/status/1183922191496335362?ref_src=twsrc%5Etfw">October 15, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
This was the tip of the iceberg, which is one example of many that shows shot locations being recorded at a farther distance than they actually are. The twins note that the NHL said this goal was scored from 6 feet out by Anthony Mantha when we can see him poking the puck into the net as it sits loosely by Anton Khudobin&#8217;s pads.
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
This Johansen goal was recorded 9 ft from the net, 35.5% xG. These were the two highest xG events this season. We updated our model, which meant much lower xG values overall, but we were expecting a ceiling of ~70%, not 40%. <a href="https://t.co/7uGx6CRd1N">pic.twitter.com/7uGx6CRd1N</a>
&mdash; EvolvingWild (@EvolvingWild) <a href="https://twitter.com/EvolvingWild/status/1183923223047659520?ref_src=twsrc%5Etfw">October 15, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
This Ryan Johansen goal is another example where he pokes in the puck as it sits almost on the goal line. The NHL recorded this as a shot from 9 feet out.
The inaccuracy is clear in these two examples and also when we step back and look at the data league-wide.
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
Additional addendum: here are all fenwick shots through game 20077 from this season and the prior 2 seasons &#8211; coordinates have been flipped for visualization. It appears the locations this year are compressed towards center ice, but the blue line coordinates are still in line. <a href="https://t.co/MMex1hZZzK">pic.twitter.com/MMex1hZZzK</a>
&mdash; EvolvingWild (@EvolvingWild) <a href="https://twitter.com/EvolvingWild/status/1183948809862299648?ref_src=twsrc%5Etfw">October 15, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
In the graphic above we can see that there is a big difference in shots mapped around the crease. In the visualizations representative of the two previous seasons, many shots crowd the crease and are even in the blue paint, while shot locations from this season seem to be pushed back away from the crease.
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
Soooo, I might have been unable to stay asleep this morning, and pulled a few things together about the NHL shot location issues that <a href="https://twitter.com/EvolvingWild?ref_src=twsrc%5Etfw">@EvolvingWild</a> found. Time will tell if the bigger thing I did will be out there, but here&#39;s a sneak preview: <a href="https://t.co/upkm2Tcmpo">pic.twitter.com/upkm2Tcmpo</a>
&mdash; Bryan (@projpatsummitt) <a href="https://twitter.com/projpatsummitt/status/1184046565989724161?ref_src=twsrc%5Etfw">October 15, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
From this Viz created by Bryan Bastin (@projpatsummitt) we can see the overwhelming amount of teams that are overperforming their xG, including the Canucks. In total, we find 24 out of 31 teams are scoring more goals than expected, according to <a href="https://evolving-hockey.com/?_inputs_&amp;dir=%22Team%20Tables%22&amp;std_tm_adj=%22Score%20%26%20Venue%22&amp;std_tm_group=%22Season%22&amp;std_tm_range=%22Seasons%22&amp;std_tm_span=%22Regular%22&amp;std_tm_str=%225v5%22&amp;std_tm_table=%22On-Ice%22&amp;std_tm_team=%22All%22&amp;std_tm_type=%22Rates%22">Evolving-Hockey</a>.
When we combine the two video examples with this league-wide data, the problem is clear.
Why does this matter?
The inaccuracy is clear, but you may be left wondering what the big deal is. The reason this matters is that use of shot location data is integral for the growing analytic community in hockey made up of fans and public analysts like the Evolving Hockey twins who use shot locations to analyze xG, shot maps, high-danger chances and other visualizations.
I know for myself and other writers on this site, xG (expected goals) plays a large role in analyzing team and player performance during a game or over the course of the season. While shot locations have never been perfectly recorded, this level of inaccuracy in unfamiliar and significantly hurts those evaluations.
Besides members of the public, hockey teams are very likely to be using this inaccurate data as well. This is concerning because unlike us fans and armchair GMs, there are consequences to decisions made based on this data. These decisions may be related to ice time, team transactions and even future contract negotiations.
This may sound a touch overdramatic to some who aren&#8217;t as familiar with the role of shot locations in evaluation throughout the league, but I ask that you consider reading this <a href="https://hockey-graphs.com/2015/10/01/expected-goals-are-a-better-predictor-of-future-scoring-than-corsi-goals/">Hockey Graphs article</a> if you&#8217;re curious about the importance of metrics like xG that rely on accurate shot location data.
For those unfamiliar, xG has been found to be the best predictor of future goal scoring, which is why it matters so much. While Corsi plays a role in evaluation, xG is viewed by some, including myself, as the more telling metric for performance.
Why is this happening?
As of now, there isn&#8217;t a definitive answer as to why this is happening. There have been many theories as to why the locations are being pushed back, but it&#8217;s only speculation at this moment. It&#8217;s also unclear if the league had even known before Monday night. It&#8217;s also important to note that this change in shot location tracking was never announced from the league.
The league has since acknowledged the problem and is likely looking into much API and software that is involved in tracking shot locations.
What will be done to fix it?
In a perfect world, the NHL would begin tracking shot locations as they have in previous seasons and go back to fix shot locations in past games played this season. Instead, websites that run public models like Evolving-Hockey, HockeyViz, NaturalStatTrick, and MoneyPuck that give us xG and other tools may have to adjust their models to somehow account for the increased distances.
In the coming days, it will be interesting to see how the NHL, Evolving-Hockey and the other public hockey analytic websites react to this discovery. On Tuesday night, ESPN&#8217;s Greg Wyshynski said, &#8220;The NHL tells ESPN that it’s investigating an apparent change in the way shot distance is being measured in its game summaries. This week, the hockey analytics community noted a dramatic shift in shot distance, including video evidence that shots in the crease were being measured as having been several feet away. This could corrupt advanced stats like expected goals, and goalie analytics like high-danger saves. After observing the videos, the NHL is looking at potential catalysts.&#8221;
Since that comment on Tuesday, Josh and Luke have noticed the first correct shot location recording that we have had all year on Wednesday night in the Toronto &#8211; Washington game.
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
Alright, so this is the closest shot that was recorded tonight and it&#39;s basically spot on <a href="https://t.co/1tFPCHpfC6">https://t.co/1tFPCHpfC6</a> <a href="https://t.co/p2TLMvlOSq">pic.twitter.com/p2TLMvlOSq</a>
&mdash; EvolvingWild (@EvolvingWild) <a href="https://twitter.com/EvolvingWild/status/1184672708921118725?ref_src=twsrc%5Etfw">October 17, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
<blockquote class="twitter-tweet" data-width="550" data-dnt="true">
I think it&#39;s been fixed&#8230; based on what I&#39;ve seen.
&mdash; EvolvingWild (@EvolvingWild) <a href="https://twitter.com/EvolvingWild/status/1184681552103518208?ref_src=twsrc%5Etfw">October 17, 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
According to them, the problem may be fixed, but we have yet to hear on the league who will surely comment on the matter if a solution has been reached.

On Monday night, the EvolvingWild twins, Josh and Luke Younggren,  discovered that the shot location data the NHL provides to the public has been grossly inaccurate so far over the beginning of this young season. This is a significant discovery and problem for fans and public analysts of the game who rely on metrics and models that use shot location data in their calculations.

Josh and Luke announced this discovery via twitter @EvolvingWild in a series of tweets.

https://twitter.com/EvolvingWild/status/1183922191496335362

This was the tip of the iceberg, which is one example of many that shows shot locations being recorded at a farther distance than they actually are. The twins note that the NHL said this goal was scored from 6 feet out by Anthony Mantha when we can see him poking the puck into the net as it sits loosely by Anton Khudobin's pads.

https://twitter.com/EvolvingWild/status/1183923223047659520

This Ryan Johansen goal is another example where he pokes in the puck as it sits almost on the goal line. The NHL recorded this as a shot from 9 feet out.

The inaccuracy is clear in these two examples and also when we step back and look at the data league-wide.

https://twitter.com/EvolvingWild/status/1183948809862299648

In the graphic above we can see that there is a big difference in shots mapped around the crease. In the visualizations representative of the two previous seasons, many shots crowd the crease and are even in the blue paint, while shot locations from this season seem to be pushed back away from the crease.

https://twitter.com/projpatsummitt/status/1184046565989724161

From this Viz created by Bryan Bastin (@projpatsummitt) we can see the overwhelming amount of teams that are overperforming their xG, including the Canucks. In total, we find 24 out of 31 teams are scoring more goals than expected, according to <a href="https://evolving-hockey.com/?_inputs_&amp;dir=%22Team%20Tables%22&amp;std_tm_adj=%22Score%20%26%20Venue%22&amp;std_tm_group=%22Season%22&amp;std_tm_range=%22Seasons%22&amp;std_tm_span=%22Regular%22&amp;std_tm_str=%225v5%22&amp;std_tm_table=%22On-Ice%22&amp;std_tm_team=%22All%22&amp;std_tm_type=%22Rates%22">Evolving-Hockey</a>.

When we combine the two video examples with this league-wide data, the problem is clear.

Why does this matter?

The inaccuracy is clear, but you may be left wondering what the big deal is. The reason this matters is that use of shot location data is integral for the growing analytic community in hockey made up of fans and public analysts like the Evolving Hockey twins who use shot locations to analyze xG, shot maps, high-danger chances and other visualizations.

I know for myself and other writers on this site, xG (expected goals) plays a large role in analyzing team and player performance during a game or over the course of the season. While shot locations have never been perfectly recorded, this level of inaccuracy in unfamiliar and significantly hurts those evaluations.

Besides members of the public, hockey teams are very likely to be using this inaccurate data as well. This is concerning because unlike us fans and armchair GMs, there are consequences to decisions made based on this data. These decisions may be related to ice time, team transactions and even future contract negotiations.

This may sound a touch overdramatic to some who aren't as familiar with the role of shot locations in evaluation throughout the league, but I ask that you consider reading this <a href="https://hockey-graphs.com/2015/10/01/expected-goals-are-a-better-predictor-of-future-scoring-than-corsi-goals/">Hockey Graphs article</a> if you're curious about the importance of metrics like xG that rely on accurate shot location data.

For those unfamiliar, xG has been found to be the best predictor of future goal scoring, which is why it matters so much. While Corsi plays a role in evaluation, xG is viewed by some, including myself, as the more telling metric for performance.

Why is this happening?

As of now, there isn't a definitive answer as to why this is happening. There have been many theories as to why the locations are being pushed back, but it's only speculation at this moment. It's also unclear if the league had even known before Monday night. It's also important to note that this change in shot location tracking was never announced from the league.

The league has since acknowledged the problem and is likely looking into much API and software that is involved in tracking shot locations.

What will be done to fix it?

In a perfect world, the NHL would begin tracking shot locations as they have in previous seasons and go back to fix shot locations in past games played this season. Instead, websites that run public models like Evolving-Hockey, HockeyViz, NaturalStatTrick, and MoneyPuck that give us xG and other tools may have to adjust their models to somehow account for the increased distances.

In the coming days, it will be interesting to see how the NHL, Evolving-Hockey and the other public hockey analytic websites react to this discovery. On Tuesday night, ESPN's Greg Wyshynski said, "The NHL tells ESPN that it’s investigating an apparent change in the way shot distance is being measured in its game summaries. This week, the hockey analytics community noted a dramatic shift in shot distance, including video evidence that shots in the crease were being measured as having been several feet away. This could corrupt advanced stats like expected goals, and goalie analytics like high-danger saves. After observing the videos, the NHL is looking at potential catalysts."

Since that comment on Tuesday, Josh and Luke have noticed the first correct shot location recording that we have had all year on Wednesday night in the Toronto - Washington game.

https://twitter.com/EvolvingWild/status/1184672708921118725

https://twitter.com/EvolvingWild/status/1184681552103518208

According to them, the problem may be fixed, but we have yet to hear on the league who will surely comment on the matter if a solution has been reached.

Inaccurate shot location data sends ripples through hockey analytics

‘He’s going to bounce back’: Ex-Canucks coach Tocchet believes Pettersson will rebound in 2025-2026

The PWHL’s expansion rules seem to heavily favour Vancouver and Seattle

Canucks’ draft options at 15th overall: Braeden Cootes

How will players waiver eligibility changing impact the Canucks’ 2025/2026 roster?

Jeff Paterson's weekly Vancouver Canucks mailbag.

Recent articles from Michael Wagar

Breaking News