how to correct GPS error?
-
I was just checking my wife’s Suunto 5. And I found the exact same error
-
Screenshot_20210606-093232_Suunto.jpg
Hi. I had the same strange behavior yesterday , but it seems the sum of km during trip is ok.
-
@mike-h Looks like more people have this problem.
-
Based on the last graphs it doesn’t look as a GPS error to me (HR graph ? ) … maybe some sort of electrical/magnetic interference ?
-
@mike-h more information and a link to the activity would help.
-
@sartoric said in how to correct GPS error?:
Based on the last graphs it doesn’t look as a GPS error to me (HR graph ? ) … maybe some sort of electrical/magnetic interference ?
Right, why would the GPS affect also HR?
-
@isazi correct.
So what could affect all the data?
A time issue (either in display or recording)
What else? -
@egika no way to know without access to raw data. Maybe someone at Suunto could check.
-
Hmmm, nobody help?
I’ve got some more knowledge. My dad had the same problem yesterday. Me too, of course. We were cycling together. He has a Spartan Sport.
I re-examined the trouble spots in the charts. I found that the problem is only in the chart with map. The individual charts are ok. See pictures.
I also checked for trouble spots in QS, Fatmap and Strava. Everything is ok. No jumps in the map, etc.
I see the problem only in SA and SportTracker (same platform?)
-
@pavlas so it is not your watch. It is either environmental, or a bug in the app. Which version of the app are you using?
-
@isazi I’m on beta 4.41.1. My father has non-beta 4.41.1.
It’s not the environment. The trouble spots are random and different every time. Maybe UFO
-
@pavlas we are aware of this chart / map issue
-
@pavlas can you give me a link for that activity ?
-
-
@pavlas thanks. Lets fix this
-
@dimitrios-kanellopoulos Thank you!
-
@pavlas is this activity synced from iOS or android ?
-
@dimitrios-kanellopoulos Android 10
-
@pavlas thanks. From a quick look it looks like some timestamp issue. Will report back when its fixed
-
@pavlas issue is fixed on 4.42 release
The issue was that you had a couple of pauses. Those pauses when they were displayed on the map had a bug that caused this only on the map view.
