Open GoogleCodeExporter opened 9 years ago
I've had a similar behaviour when the "Exclude stop time" option is selected.
In my case, the GPS connection is toggling on/off every second, so when the
average
speed is calculated, half the time is considered excluded time (since that's the
default when the position is invalid), creating a higher than usual average
speed.
I have a possible code fix for that, a two line of code change to Form1.cs
That change is untested (I couldn't even check that it compiles).
Original comment by rdketc...@gmail.com
on 20 Apr 2009 at 6:30
Attachments:
I ran into this on 3.114 rdketchup, if you are still around, can you post a
diff of
your fix. Form1.cs has changed a lot since you posted.
Anybody working on this one? I could take a look at it.
Original comment by stephen....@gmail.com
on 20 Aug 2009 at 5:48
should be solved in version 4.2 (invalid speed data treated as stop).
If you use start/stop mode or your GPS signal is not stable for any reason the
position can "jump around" more than you actually move. The total distance will
be
higher than you actually moved. The average speed is computed as total distance
/
total (or ex) time. Therefore the average speed can be higher on unstable
signal.
There is an option to "Drop first x points" to get a better signal. Also there
is a
new (experimental) option "AVG" to average the data.
Original comment by kmb...@gmx.de
on 8 May 2010 at 8:26
Original issue reported on code.google.com by
harvey.o...@dsl.pipex.com
on 7 Apr 2009 at 8:13