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

Saving fit files? #77

Open
jcborras opened this issue Oct 15, 2018 · 3 comments
Open

Saving fit files? #77

jcborras opened this issue Oct 15, 2018 · 3 comments

Comments

@jcborras
Copy link

Not actually an issue but a feature request: I can't seem to find a way to make (write) a FIT file from a list of records.
Typical usage scenario: data merge from some GPX/TCX source.
I can open a FIT file using python-parse and I could even add records with the missing information but I can't find a method to write a FIT file out of the updated list of records.
Thanks in advance.

@xmedeko
Copy link
Contributor

xmedeko commented Oct 15, 2018

Duplicate of #8 some alpha code is in the PR #58 (not merged yet).

@jcborras
Copy link
Author

jcborras commented Oct 15, 2018

I dare to reopen the issue since #8 scope is significantly larger.
Writing a fit file with a different name from just parsed data requires far less work that dealing with (for instance) GPX/TCX files since the later involves XML parsing for varied document entities and possible extensions enduring the shortcomings of python libraries for (again for instance) dealing with XML namespaces. Been there.
Just saying.

@xmedeko xmedeko removed the duplicate label Oct 15, 2018
@xmedeko xmedeko reopened this Oct 15, 2018
@xmedeko
Copy link
Contributor

xmedeko commented Oct 15, 2018

IMO #8 is mostly about saving fit file, maybe some simple CVS or JSON parsing. It's not intention of this tool to do TCX or any other elaborate data format parsing, it should stay with low level FIT operations. So So I vote to merge these feature requests and close one as duplicate. @dtcooper what are your thought about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants