Recently we uploaded several MTBO courses, where they were biking too fast ; ) Some controls were missed that during slower tests could be even punched.
Is there a recommended value for punching tolerance for events planned for bikers? If we increased the tolerance from 15 m to 25m, would it better to have more stable gps recognition around the controls?
Let's say a rider rode directly through a control and there was no GPS error and no error in the position of the control. With a 15m punching tolerance they would be in range of the control for 30m.
If they were riding fast ... let's say 37.5km/hour, then they are moving at 10metres per second. This may mean that if their GPS is getting a good signal and providing a new location every 1second, there would be two data points within the punching circle.
So, in this case MapRunF should punch the control.
However, there is very little margin for error:
- slower GPS updates
- faster rider
- GPS error
- Control location error.
Increasing the punching tolerance would help.
I would be interested to look at any GPS tracks you have to analyse this, if you could email some through or point me to the particular event.
As a final comment... I thought that in a "normal" MTBO event, riders needed to slow down enough to punch with SportsIdent (or even SIAir). I don't think you can do that at 30-40km/hour?