GPS accuracy - track and field

[surfboomerang]

@thomas-ma Nice artwork!
If you have a Suunto 9 you can find the information @Brad_Olwin asked for under settings->general->about

My own Suunto 9 was also struggling with GPS yesterday so it’s maybe just a bad day.

[zhang965]

Did you stop your move during your run?

[kamarasm]

@surfboomerang Hell yeah, I experienced some bouncing in GPS signal yesterday, however there was never problem like this before.
Interesting

[Mff73]

@thomas-ma
It doesn’t really look like non accuracy, as it is really “geometrical”
Have you eventually transfered the same workout to another plateform to compare the representation ?
SA activity link or fit file may help to see what is inside (wrong data, wrong representation, raw data behind for suuntoguys).

[TM0702]

Thanks all. So I followed the instruction above and switched to another GPS system to “Galileo.” Attached is the tracking map.

My next question is the accuracy: I ran 12.5 laps, which should end up equal to be 5k. However, the Suunto shows 5.38km. I ran on Lane 4 which is 423m per lap, and it should equal to 5.28m, I know 100m discrepancy is not huge but my friend is using another brand, Coros and his watch’s discrepancy is only 10m. We ran side by side as well.

[DMytro]

@thomas-ma i think coros has a special feature for lap running where it averages out gps descrepancies so you get nicer track + more reliable distance.

[TM0702]

@дима-мельниченко Agree. In general I am quite happy with my Suunto 9 tracking.

Does anyone know if there is any different GPS tracking function between “Track and Field” vs “Running” function? If no, should I just use “running” function for running at the sports ground going forward?

[surfboomerang]

@thomas-ma I noticed running profile does not record GPS every second, but a random interval between 1-4 seconds. On road races with distance of half a marathon I noticed the watch is always spot on in distance, but on a 400m track I can imagine it cuts the corners less accurate then it should do.

Maybe that explains the difference.

[isazi]

This is from this morning in Amsterdam. Standard running profile, GPS+Beidou.

[Dimitrios Kanellopoulos]

@isazi I know the place well

[DMytro]

@isazi image isn’t from SA, right?

[isazi]

@дима-мельниченко Runalyze with ESRI satellites view.

[TM0702]

@isazi said in GPS accuracy - track and field:

Interesting. Next time I will try the GPBeidou system and see if it reports better result.

And you can tell from the screenshot (from Strava) my GPS is completely off track.

[zadow]

@thomas-ma
Hi, have you tried “Track and Field” Sport mode for running on track? I can remember that I read somewhere that it (should) has some special setting for tracking running on Track. I have never tried it by myself. It just rang the bell for me, when I read your post…

[Dimitrios Kanellopoulos]

@thomas-ma keep in mind that the satelite overlay isnt always 1:1.

[TM0702]

Thanks. i understand it is not always 1:1.

May be next time I will try the normal “running” mode while running on track and see if there is any difference.

[TM0702]

So I run another 10k using the regular run function, and here is the map from Strava. 10k should be 25 laps, but I think I ran 24 laps + 250m(?) from the map.

[zhang965]

my 10k, it’s quite accuracy

[Bulkan]

@zhang965 Did you use loop? just curious if work well in a track.

[Shrek3k]

@thomas-ma 24 laps + 250m would be rather outstanding and excellent in terms of accuracy.
Just check how and where the 400m lap really is 400m long … I think it is nearly impossible to run the ‘perfect line’ for so long.