GPS data - clipping redundant bits

[familyguy]

Anyone know of a way to clip redundant GPS data? Such as when you ride 3.71km and you think you've stopped the Garmin but it didn't and you record 32 minutes of sitting still which affects a few things like average speed and power calculations?

Jim

[find_bruce]

Viking GPS Data and Topo Analyzer, Explorer, and Manager
https://sourceforge.net/p/viking/wikiallura/Main_Page/

EDIT: Viking is good for the GPS trace but doesn't work for the embeded data in a fit file. The easiest way to crop a fit file is using Fit File Tools - unlike Strava you can even crop in the middle

[kb]

Garmin::FIT and fitsed is my choice (https://pub.ks-and-ks.ne.jp/cycling/GarminFIT.shtml) but command line stream editors (and Perl!) are an acquired taste...

[familyguy]

Was also pointed towards this one: https://www.fitfiletools.com/#/top

Jim

[ValleyForge]

I have auto-pause enabled at 4kph for training rides. It avoids that post-coffee discovery of the timer still running. Means I don't have to shave the .fit files.

[familyguy]

So do I, but for some reason it tracked 40 minutes of standing still as run time.

[ValleyForge]

What a PIA. I remember my 705 did it once or twice when it didn't connect to the wheel sensor and was only using GPS for speed. Wildly inaccurate especially parked beside a building in the CBD.

[RonK]

What a PIA. I remember my 705 did it once or twice when it didn't connect to the wheel sensor and was only using GPS for speed. Wildly inaccurate especially parked beside a building in the CBD.

That is because the GPS was receiving multi-path (ghost) signals bouncing off the buildings which fooled it that the bike was in motion.

[familyguy]

Whenever I ride up Kent St, the GPS track looks like I've visited a dozen buildings and even a few side streets

Jim