07.08.2010 21:59:43 UTCgeändert am 07.08.2010 22:01:05 UTC
Inplausible training data because of wrong speed reported - would like to fix
My second mountainbike training took me through some foresty terrain, in which my GPS had trouble keeping a decent fix. I guess I should consider getting a better external GPS unit, as well as switching Run.GPS' speed calculation from GPS-reported to internal algorithm when going through this kind of terrain.
However, that doesn't fix the training at http://www.gps-sport.net/trainings/Nijmegen-Bisselt-Riethorst-Milsbeek-De-Horst-Wyler-Berg-en-Dal-N_362549 , which at timestamp 2010-08-07 18:13:58.970 suddenly goes up to 125 km/h, then loses fix, then goes down to normal again from 234 km/h. Now, I've tried to find a way to fix this myself, export the data as CSV and flatten the speed at that stretch to about 25 km/h, which I think should be about right, but I can't import such a training back into Run.GPS, nor GPS-Sport. Is there a way to fix this, and if so, how?
Same as the speed, the altitude seems to be extremely misrepresented on a number of occasions.
Apart from fixing this training: what can I do to prevent this from happening again?