Author: Michael George
Date created: 22 Nov 2025
Gybing is fun for windsurfers of all ages and abilities, yet extremely technical and highly worthy of GPS analysis.
The difference between a good and bad gybe is essentially the exit speed, and reducing the time it takes to get back up to speed. We already have alpha racing but that has the requirement to return to within 50 meters of the starting location.
What would be ideal is to have a collection of gybe metrics that can be used to rate individual gybes, even if they do not qualify for an alpha. This document has been created to jot down a few thoughts about the measurement of gybes and tacks.
This section shows what good and bad gybes look like using real GPS data. The examples show the most important 200 meters worth of GPS data in green, which will subsequently form the basis for gybe analysis.
The first example is a good windfoil gybe, entering at 25 kts and never dropping below 15 kts. The gybe was fully foiling and the speed of the final data point was slightly over 20 kts.

The second example shows a windfoil gybe which was initiated at 20 kts but dropping off the foil, and then chugging at 4 kts. Whilst the entry looks nice and smooth the slow exit speeds make it a bad gybe.

It can easily be seen how the data points for the gybe exit are bunched up due to the slow speeds, and thus making it a bad gybe.
Prior to calculating any gybe metrics it is necessary to decide which data points constitute each gybe.
One relatively simple approach would be to consider all of the possible mid-points for the gybe. An accumulated distance of 100 meters prior to the mid-point dictates the start point, and accumulated distance of 100 meters after to mid-point dictates the end point.
The straight-line distance between the start point and end point can be calculated for every possible mid-point. Theoretically, the “best choice” of mid-point for the gybe will be the one with the shortest distance between the start and end points.
The goal is to see a comparable entry (100 meters ) and exit (100 meters). The example below illustrates how the shortest possible grey line will result in the best possible mid-point, just by considering the preceding 100 meters and following 100 meters.

Once the mid-point of a gybe has been established it is easy to calculate a variety of useful metrics.
The speed metrics described above can also be used to produce percentage metrics.
Overall scores can be calculated by combining the average speed (200 meters) and min % metric.
Alternatively, it could be calculated by combining the average speed (200 meters) and exit % metric.
In both cases higher speeds have the potential for higher scores, but can be beaten by better executed slower gybes.
The ultimate goal is to minimise speed loss and maximise the speed throughout the gybe for the best possible score.
The fundamentals (e.g. calculation of start / end / mid-points) has been somewhat simplified.
Gybe detection also needs to consider course over ground (COG) for the entry and exit, not just accumulated distances.
Doppler-derived speeds should be used for all speed calculations and accumulated distances.
This is consistent with everything else in the speedsailing world, since it is the most accurate measurement.
Distance calculations should use the latitude + longitude values, just like the alpha racing algorithms.
Several algorithms exist, but optimisations for proximity detection in alpha racing can also be applied.
Regardless of how gybe metrics are calculated, they can only ever be as good as the underlying GPS data.
It is important that the device is recording unfiltered Doppler-derived speeds, and not using activity-specific filtering.
All of the ideas and metrics described in this document can also be applied to tacks.
The logic really isn’t any different, just the initial distinction of tacks and gybes.
How these ideas could be applied to Waterspeed is discussed in a separate document, accessible via this link.
This document describes some ideas for gybe (and tack) analysis, but without testing them in a prototype.
Getting the fundamentals right is really important, such as determining the start point, mid point, and end points.
Calculating the metrics is then relatively straightforward, allowing gybe scores to be produced for rankings, etc.