Justin Bopp over at Beyond the Box Score has attempted to explicitly visualize UZR/150 through what he calls the “UZR TargetView method.” I think it’s an excellent idea, as defensive metrics are often difficult to consume numerically. Thus, a graphical depiction would appear to be ideal in today’s very visual society. However, while I think he’s on the right track, I do wonder if Justin has implemented his idea correctly. For instance, note the following visualization of the Yankees’ UZR per 150 defensive games.

The problem with this view that Justin and others are discussing in the comments section of his post, is that it appears to be a strict visualization of “ground covered” by the players, rather than of UZR/150 which incorporates arm runs, DP runs, and error runs, in addition to range runs. If Justin is trying to provide an illustrative representation of the team’s range, which seems to be the case in this graph, maybe it would be best to utilize range runs instead of UZR/150. In my opinion, this would make the visual a more accurate one (or at least it would eliminate some confusion).

For instance, according to UZR/150, Nick Swisher is worth -1.6 runs below average in right field, meaning that he is basically an average right fielder. Justin has mapped that out with his UZR depiction. However, in terms of actual range (RngR), Swisher is 5.5 runs above average. His overall UZR/150 is hurt by his below average arm, therefore, Swisher’s representation in this particular visual seems to imply that he has limited range in the outfield when, in fact, he’s one of the best outfielders—range-wise—in the American League. Again, perhaps using range runs would make the analysis better, or, perhaps adding other illustrative elements to the visual would allow for a more comprehensive look at each player (UZR/150 is a nuanced statistic—it’s not all about ground covered).

Still, I’d like to give Justin credit because this is an excellent idea. The execution needs some tweaking, but the visuals are extremely interesting. Beyond specific implementation exercised here, what do you think about the graph? For the most part, it still rings true for the players although if range numbers are used, the depictions can fluctuate (it would not change the general direction of the Yankees graph, however). Robinson Cano, Teixeira, Damon, A-Rod—they all seem to cost the team some runs, according to range and that’s represented in this graph, whereas Jeter, Swisher, and Melky have been above average, range-wise.

Tagged with:
 

8 Responses to Good idea, flawed execution?

  1. Moshe Mandel says:

    Great stuff, Chris. Is there anywhere we can see UZR by month? I’m wondering if Alex has gotten better or worse over the season.

    • Chris H. says:

      Thanks, Mo. I’ve looked for monthly UZR before and haven’t had much luck finding anything, although I could swear I found it somewhere. I’ll scour the web a bit for it, but I do believe A-Rod’s defense has gotten better in the second half (or at least in September-October). Early on, it was remarkably bad and the improvements were therefore noticeable as the season wore on.

  2. EJ Fagan says:

    That’s pretty awesome stuff Chris. I’d love to do it with a better defensive measure, such as +/-.

    EJ

  3. oldpep says:

    Cano cost the team runs? I don’t agree with that. I don’t think a lot of neutral observers do either.

    • The other Chris H says:

      He has much better range than this graph shows for sure he is a gold glove caliber second baseman this year. I also don’t give Jeter than much range, I think one thing UZR fails to take into consideration is the difference between athletic physical range and a smart veteran like Jeter who knows how set himself up in the right position in order to be closer to where the ball will be hit based on the pitches he knows are being thrown.

  4. [...] TargetView’s flaws, you can see how UZR is broken down. Range is valued higher than both Errors and Double Plays. [...]

  5. [...] TargetView’s flaws, you can see how UZR is broken down. Range is valued higher than both Errors and Double Plays. [...]

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Set your Twitter account name in your settings to use the TwitterBar Section.