Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stadelmanma/fitparse-rs
Rust library to parse FIT formatted files
https://github.com/stadelmanma/fitparse-rs
ant crates fit fit-sdk fitparse garmin nom serde
Last synced: about 1 hour ago
JSON representation
Rust library to parse FIT formatted files
- Host: GitHub
- URL: https://github.com/stadelmanma/fitparse-rs
- Owner: stadelmanma
- License: mit
- Created: 2020-03-18T01:02:07.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2025-01-21T01:57:09.000Z (19 days ago)
- Last Synced: 2025-02-01T17:07:07.670Z (7 days ago)
- Topics: ant, crates, fit, fit-sdk, fitparse, garmin, nom, serde
- Language: Rust
- Homepage:
- Size: 1.72 MB
- Stars: 60
- Watchers: 4
- Forks: 12
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-garmin - fitparse-rs - Rust library to parse FIT formatted files (2025-01-21) (Tools / Older resources)
README
# Fitparser
[](LICENSE)
[](https://crates.io/crates/fitparser)
[](https://docs.rs/fitparser)
[](https://github.com/stadelmanma/fitparse-rs/actions/workflows/ci.yml)
## Overview
Parses FIT formatted files and exports their contents using
[Serde](https://github.com/serde-rs/serde). This code was heavily
inspired by the
[python-fitparse](https://github.com/dtcooper/python-fitparse) module
and uses the specifications defined by the Fit File SDK which is
maintained by [ANT](https://www.thisisant.com).
The goal of this crate is to parse valid FIT files according to the
defined FIT profile and export their data into a more usable format. To that
end we leverage the Serde framework which allows end users to export the
data in whatever format suits their needs. This library provides a
`fit_to_json` example executable to serve as a template for any
other serialization format implemented using Serde.
Notes:
- This library **does not** support writing FIT files at this time.
- Files with Developer Data fields can be parsed and the developer
fields are correctly extracted.
- The FIT SDK is regularly updated by Garmin/Ant this library may not
be up to date; check the `src/profile/messages.rs` for the packaged version.
Submit an issue and I will gladly bump it!
## Usage
See library documentation at [docs.rs/fitparser](https://docs.rs/fitparser)
for full usage information. Below is a basic example of calling the parser
on a FIT file.
```rust
use fitparser;
use std::fs::File;
use std::io::prelude::*;
println!("Parsing FIT files using Profile version: {}", fitparser::profile::VERSION);
let mut fp = File::open("tests/fixtures/Activity.fit")?;
for data in fitparser::from_reader(&mut fp)? {
// print the data in FIT file
println!("{:#?}", data);
}
```
For lower level control of the deserialization process, such as reading from
a streaming data source you can use the `de::FitStreamProcessor` struct. See
the `streaming.rs` example file for basic usage and manual processing of
`FitObject` variants.
Additional decoding options are also available to customize the output of the
parser. See the source code of the `fitparser/src/de/mod.rs` to view all options
(or view the crate docs). The `fit_to_json` example program demos all of the
currently available options as well.
## Updating the FIT profile
All FIT files are generated based on a customizable profile. The profile
used here is pulled from ANT's official SDK which can be accessed
[here](https://developer.garmin.com/fit/download/). The
cargo build command expects the environment variable `FIT_PROFILE` to be set to the
path of the desired Profile.xlsx file and the `FIT_PROFILE_VERSION` variable to
the appropriate version. To make updating simpler a script is provided
`./bin/update_profile.sh` that accepts the profile path the as first argument
and optionally a profile version as the second. The version can be omitted
if the path to the Profile.xlsx file contains `FitSDKRelease_XX.YY.ZZ`.
```sh
./bin/update_profile.sh ~/Downloads/FitSDKRelease_21.40.00/Profile.xlsx
```
A profile file is not required for building the library as the files
generated are committed to the repository. The profile only needs
updated to support custom extensions or when ANT releases an updated
version.