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
Bryton Rider 310 fit file #1788
Comments
Horrible ! I wonder if it is recorded with smart recording. Try enabling Gamin Smart Recording in preferences/options and re-import? |
Send me a file and I'll take a peek. |
I noticed differences between version 3100 and 3940, but still both wrong. |
"The fit file itself appears to be valid. While the format is not typical, we do not enforce having only one message per timestamp." |
There is a problem with altitude too. |
I did not check altitude yet because I live in a flat area, but Mario from the previous posted link (thisisant) says "The latitude and longitude values are reported in units of semicircles." |
The altitude is wrong only if import the fit in gc. |
Same issue with my 310. |
Duplicate #2029 |
It is closed but in 3.4 august the is not full support for file |
the issue is being tracked in #2029 |
Hi, the Bryton 310 .fit import is almost perfect, but the elevation data seems corrupt :( |
The fit file the Bryton Rider 310 produces is wrongly imported into GC, as can seen in the following screenshot.
Here is a fit file example, but named as zip file: 160109152536.zip
The text was updated successfully, but these errors were encountered: