How is speed calculated? The GPS recorder doesn't record speed, so chances are it is calculated from the difference in locations over time.
The GPS position can wander slightly over time, and I guess if the data is used without filtering then that could be what's causing the spike you are seeing.
The GPS recorder could easily average the last X seconds worth of data for each reading it wrote which would help with this (we could make that an option) but I've been hesitant to do that as it might have the effect of 'blurring' the data that has been recorded.
With no averaging, you're going to see only points on the track that you followed, but with the averaging you're going to see yourself at locations that you may not ever have been at (for instance if you turn a sharp corner during the averaging interval). Maybe that's not an issue though
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
How is speed calculated? The GPS recorder doesn't record speed, so chances are it is calculated from the difference in locations over time.
The GPS position can wander slightly over time, and I guess if the data is used without filtering then that could be what's causing the spike you are seeing.
The GPS recorder could easily average the last X seconds worth of data for each reading it wrote which would help with this (we could make that an option) but I've been hesitant to do that as it might have the effect of 'blurring' the data that has been recorded.
With no averaging, you're going to see only points on the track that you followed, but with the averaging you're going to see yourself at locations that you may not ever have been at (for instance if you turn a sharp corner during the averaging interval). Maybe that's not an issue though