Skip to content

several functions to fix FIT files #1

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: write
Choose a base branch
from

Conversation

vlcvboyer
Copy link

several CLI functions to fix FIT files
-> smooth GPS trace (useful when bad weather corrupt GPS or for swimming activities)
-> combine several standalone activities into one multisport activity
-> change sport/subsport
...

@xmedeko
Copy link
Owner

xmedeko commented Jan 3, 2019

@vlcvboyer My repo is a fork of the upstream dtcooper/python-fitparse just to do PR to the upstream. Unfortunately, my PR for writing FIT files has not been accepted. I do not plan to develop this feature and maintain a fork. Comment and vote for:

To gently push the fitparse authors to add FIT file saving, too.

Note, some actions may be done through https://www.fitfiletools.com

@xmedeko
Copy link
Owner

xmedeko commented Jun 5, 2019

Update: I have decided do abandon FIT writing (and parsing, too) in pure Python since the FIT format is loosely specified and complex.
I recommend to make some FIT<-->JSON tool from the original FIT SDK (e.g. C#, Java, C++) and just call this tool from Python.

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

Successfully merging this pull request may close these issues.

2 participants