Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Probable issue in distance between Flow and SportTracks using Stride sensor #34

Closed
ldegiorgi opened this issue Aug 21, 2014 · 5 comments
Assignees
Labels
Milestone

Comments

@ldegiorgi
Copy link

Hi,

i want to signal a possible bug related to the distance how it is reported in Flow and how it is reported i other tools (eg SportTracks).
Today I've done a manual calibration of the Polar Stride Sensot through 3 round on a track. The watch reported 1.1km but when I exported and imported in SportTracks, it report 800m....
How it can be possible? I've the file to share with you.

Best regards

Luca

@pcolby
Copy link
Owner

pcolby commented Aug 21, 2014

Hi @ldegiorgi,

What format are you using? ie GPX or TCX? Would you mind attaching the file(s) to this issue? (Github allows attaching files by dragging them onto the section just below the text when adding a new comment). Note, doing so will make them public. If that's not acceptable, you can email them to me at git at colby dot id dot au.

Thanks.

@ldegiorgi
Copy link
Author

I use TCX. I Tryed to upload TCX files, but the system says "Unfortunately, we don't support that file type. Try again with a PNG, GIF, or JPG.".

@ldegiorgi
Copy link
Author

Hi,

in attach the TCX file and the Flow url (public):
https://flow.polar.com/training/analysis/23825755

Regards

Il
21.08.2014 12:53 Paul Colby ha scritto:

Hi @ldegiorgi [1],

What format are you using? ie GPX or TCX? Would you mind attaching the
file(s) to this issue? (Github allows attaching files by dragging them
onto the section just below the text when adding a new comment). Note,
doing so will make them public. If that's not acceptable, you can email
them to me at git at colby dot id dot au.

Thanks.

Reply
to this email directly or view it on GitHub [2].

Scopri istella, il nuovo motore per il web italiano.
Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video.
Usa istella, vai su http://www.istella.it?wtk=amc138614816829636

@pcolby
Copy link
Owner

pcolby commented Aug 21, 2014

I use TCX. I Tryed to upload TCX files, but the system says "Unfortunately, we don't support that file type. Try again with a PNG, GIF, or JPG.".

Bummer. I wasn't aware of that limitation.

https://flow.polar.com/training/analysis/23825755

Did that session have no GPS active, or is flow.polar.com simply obfuscating the location?

I haven't received the TCX and/or training session files yet.... are you going to / did you email them?

Thanks.

@pcolby pcolby added the TCX label Aug 22, 2014
@pcolby
Copy link
Owner

pcolby commented Aug 22, 2014

Thanks @ldegiorgi, I've got the TCX file now.

The short version: You've been bitten by issue #27 😦, and should upgrade 😄

Today I've done a manual calibration of the Polar Stride Sensot through 3 round on a track.

Looking at the session in flow.polar.com, I can see you have three laps, at around 400m each (actually the website indicates that the last one was only 300m, but could just be a precision / rounding issue.

Because these are recorded by the V800 as two splits, rather than three laps, the version of Bipolar you were using (0.2.1 - as indicated by the build info at the end of the TCX file), incorrectly failed to see the part of the run that follows after the two splits - ie, the final lap.

Anyway, that was fixed in 0.2.2, so I suggest you upgrade to that or later (I'd recommend 0.2.3).

Then, if you delete (or rename) the TCX file, Bipolar will simply recreate it with the final lap intact 😄

Let me know how it goes.

@pcolby pcolby added this to the 0.2.3 milestone Aug 24, 2014
@pcolby pcolby self-assigned this Aug 24, 2014
@pcolby pcolby closed this as completed Aug 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants