GPS-Sport ForenRun.GPS SoftwareSome thoughts about pause detection, average speed and temp loss of GPSsignal
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
tomgps 04.09.2007 23:05:18 UTC

Pause detection in GPS Trainer UV has improved

IN the new version there are less faulty registered pauses due to GPS signal loss. I drove my 50km car ride without a pause and version 2.0.1 did not register any faulty pause or downward speed spikes although I had several GPS Weak signal calls when driving under trees. Measured distance during 3 subsequent rides were always between 52.5 and 52.7km. Only 0,2% variation. The same positive result during a 6km bike drive with several segments under trees.
However, during walking there still are some strange effects: faulty detected pauses and too low values for total distance when temporary signal loss has occured. It seems that 2.0.1 does not (or not always) compensate total distance and active time after a temporary GPS signal loss, even with a long smoothing buffer. Why only at low speeds? Maybe caused by the length of the signal loss?
I think RunGPS still can do a better job on total distance accuracy and average speed active accuracy by assuming average speed during signal loss and by correcting distance and active time after position detection is re-establised. Surely it must be possible to make the distinction between signal loss and a pause?

I will test on this further!

Thanks for the improvements in 2.0.1

Tom
tomgps 10.08.2007 23:50:14 UTC

my version is 1.2.8

Sorry forgot to mention that I use version 1.2.8

Tom
tomgps 10.08.2007 23:48:31 UTC



It is well known that GPS receivers may have problems with signal strength under trees. Good GPS software tries to compensate for this by trying to correct the data as soon as a new GPS fix is received. I think RunGPS does a fairly good job at this. Today I drove 50km's in my car comparing car tachometer with distance travelled in GPS. The difference was about 100m in 50km: 0.2%. During the drive I lost signal a few times because of trees. I know that because of downward spikes in the speed graph and because of a difference of about 1 minute between time travelled and time total although I never halted anywhere. It seems like RunGPS detected pauses that were not there in reality.

So it looks like that RunGPS does correct distance travelled after signal loss (good!) but does not correct for faulty assumed pauses after signal loss. In my case this resulted in 1 minute too little time travelled and 2% too high average speed active. Under bad conditions this error in average speed came become more severe.
So maybe a bug or maybe just an enhancement request for me.

I will this further on this and report back.

Thanks for the software! Tom
Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung