Jordan Spieth's average finish in multiple historical metrics ahead of the 2017 US PGA Championship. Shows him relatively strong in his last five events and relatively weak in similar weather. |
As above, but with Padraig Harrington's data highlighted for extra legibility. |
I am pleased to announce the addition of useful new spider (also known as radar and less commonly, star) charts to Golf Predictor. Spider charts are a type of statistical chart that show the difference in multiple parameters visually at a glance and as such, are very useful for comparing certain stats on Golf Predictor. This can be seen in the screenshots above, for the 2017 US PGA Championship. The main components of a spider chart are:
- The spokes emanating from the centre of the chart. The spokes are displayed equidistant from each other and there is one spoke per parameter displayed.
- The data points are shown on the spokes. The further away the point is from the origin at the centre, the bigger the value is. On Golf Predictor, this usually means the worse the stat is.
- The points (the parameter values that make up the data set) are joined together to form a polygon. The number of sides to the polygon and its shape depends on the number of parameters displayed on the chart and their values.
- There may be more than one data set (polygon) displayed on the same chart, e.g. the data for more than one golfer may be displayed with different colour polygons. This is shown in the second screenshot above, where the polygons for the golfers in a tee-off group for the 2017 US PGA Championship are plotted in different colours.
- The concentric grid lines on the spider chart are for scale purposes. It is possible to number this scale, but it doesn't look good and was somewhat confusing with the charting library (see below) that was used.
While ideally, a golfer should have the best statistics possible, in the real world, most top golfers will have some mixture of relatively good, so-so and bad stats. A spider chart tells you immediately where a golfer's relative strength and weaknesses are. For example, the first screenshot above, you can see the average finishing position for Jordan Spieth in multiple relevant historical categories. This shows that his recent performances (last five events) have been relatively good as this value is close to the origin. This, of course, is thanks mainly to his win in The Open! You can also see at a glance that his results in similar weather to what was forecasted for Quail Hollow are relatively bad, being furthest from the origin of the chart.
The ideal spider chart for golfer performance (where small values are good) is a polygon with all data points being as close to the origin as possible. Spieth's chart above is not that far off this, except for his similar weather performance. Some notes on these new spider charts:
- There has to be at least three data points to draw a spider/radar chart (you can not draw a polygon without at least three points!).
- Initially, I wasted a lot of time trying to use the Flot spider charts plug-in (Flot is used for all the other charts on site, bar the box plots), but I was not happy with the features or the documentation. Eventually I found RGraph, which has some attractive and easy to use spider charts, so I switched to them instead.
- Zero data points (i.e. missing values) are left off the single polygon spider (i.e. single golfer) charts. This proved to be the best way to handle this situation. The number of omitted zero point categories is printed above the chart. Leaving them in caused readability issues for certain data sets, as did defaulting them to a high number, e.g. 250.
- Zero data points are included on the multiple polygon (i.e. multiple golfers) spider charts, as some of the golfers charted may have a value for that parameter. In this situation, the best option was to have the missing values default to a value slightly above the highest value plotted. When this happens, a message is printed above the chart with the default value.
- Despite the above point, some of the polygons (i.e. data for some golfers) on a multiple polygon spider chart may be difficult to read, depending on the values for the golfers chosen. For example, if you chose to compare stats for someone like Rory McIlroy and someone with poor or no stats, McIlroy's polygon will be hard to read, due to having to plot very good and very bad stats on the same chart. The only workarounds for this are to omit the golfer(s) with poor/no stats from the comparison or compare the stats for similar level golfers (this obviously is not an option if you are comparing a tee-off group!).
- Similar to above, a polygon on a spider chart with one or two bad values may be hard to read if all other values are good values. For example, the field ranks stats for Jordan Spieth ahead of the 2017 US PGA Championship are unbelievable, except for his tournament history rank (and his cut streak rank to a much lesser extent). This makes his field rank chart somewhat difficult to read.
- On multiple polygon (i.e. multiple golfers) spider charts, you can click on the golfer names in the legend (key) to highlight the values for that golfer. That is very useful for charts with data for more than one golfer, especially where the data overlaps considerably. This is shown in the third screenshot above, where the polygon for Padraig Harrington in the tee-off group for the 2017 US PGA Championship has been highlighted.
- The number of polygons (i.e. golfers) on a spider chart is limited to a maximum of four for legibility reasons. However, any more than two can be difficult to read, but as mentioned above, you can highlight a polygon to see the data for a golfer more clearly.
- Also for legibility reasons, polygons on multiple polygon spider charts are not filled in, while they are on single polygon charts.
- It was not possible to show the data point values on the chart. However, you can hover over a point to see its value, as shown in the first two screenshots above.
- The chart scales automatically, based on the biggest value to display. They may mean that a spider chart for a golfer with all good values may look similar to a chart for a golfer with all bad values. Clicking on a data point will indicate whether the values or all good or bad.
- Some of the new spider charts have average values displayed above the chart, where this is useful, e.g. the overall average on the early/mid/late season chart (see below).
- I have added a new icon for spider charts. At the very small size (14x14 pixels), it was difficult to create one that didn't just look like a blob!
- You may have to reload any page you have opened in the recent past in order to see these new chart links.
- The overview table on the Compare Groups page had slightly different columns from its counterpart in the Compare Golfer page. That has been corrected and the same region performance has been added to the table on the Compare Groups page instead of the world ranking (this is available by choosing the last option in the 'Stats to Compare' dropdown list.
- Only subscribers can see the great new multiple polygon charts on the compare pages (see below), so sign up today to see these useful new golfer comparison charts.
- Prediction Data page: two single polygon (i.e. single golfer) spider charts; one for field ranks and one for historical performance (e.g. same course, season, last five events etc.) for each golfer in the field. These two new charts are accessible from the General panel.
- Golfer Data page: one single polygon spider chart for regular/major/WGC/FedEx average result in each golfer's career.
- Season Segment Data page: one single polygon spider chart for early/mid/late season performance for each golfer.
- Compare Golfer/Compare Groups page: one multiple polygon (i.e. multiple golfers) spider chart for the historical performance (e.g. same course, season, last five events etc.) of the chosen golfers/tee-off group.
- Compare Field Ranks/Compare Groups page: one multiple polygon spider chart for the field ranks of the chosen golfers/tee-off group (see last two screenshots above).
No comments:
Post a Comment