-
Notifications
You must be signed in to change notification settings - Fork 186
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
Parsing events? #94
Comments
Looking further into it, I can see how the profiles are being generated from the SDK. Looks like the best method of action is modifying a profile by hand until the events are released in an SDK version. |
If anyone is wanting a copy of profile.py which includes the correct field_types data for events 56 and 57 let me know, I have a modified version available that seems to work well for all current events as of OS version 6.0 |
Hey @rjjanuary, I too am trying to extract the extra events/fields that are populated by the Garmin Descent. I'm interested in your |
I apologize for missing your message before @gwtall. I'll dig the code back up. I've not tested it with any more recent version of python-fitparse, but it will at least be a good starting point. |
Hello,
I'm looking to possibly utilize this library to parse divelogs from the Garmin Descent. The files are standard ant files with some (currently) undocumented messages and events.
I do see that a number of the dive messages are currently supported, however there are a number of events that are included within the Descent files that I'm not seeing.
In particular, what I'm looking for are events 56 (Dive Alerts) and 57 (Gas Switches)
Does fitparse process events? If so, how do I access them?
The text was updated successfully, but these errors were encountered: