You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in the "records" on the my dashboard are some pretty unlikely values which probably come from GPS glitches. E.g. top speeds - 148.02 km/h for Cycling (transport) or 351.53 km/h for Walking.
How about some sanity checks for the records in the form of max. plausible speeds?
The text was updated successfully, but these errors were encountered:
It seems there are some invalid values left after gpxpy processing. I have sometimes the same issue when I forget to stop/pause the recording (in this case, I edit the file manually to remove some invalid points and let gpxpy removing the remaining ones, but that's not the best solution...).
Adding max values will make the records less relevant. But it can be a workaround before reworking gpx file processing (and adding gpx data edition).
A additional solution can be to let user edit max speed value on FitTrackee, to overwrite value calculated by gpxpy.
I noticed that in the "records" on the my dashboard are some pretty unlikely values which probably come from GPS glitches. E.g. top speeds - 148.02 km/h for Cycling (transport) or 351.53 km/h for Walking.
How about some sanity checks for the records in the form of max. plausible speeds?
The text was updated successfully, but these errors were encountered: