Dimitrios Kanellopoulos

You can try my fork has many things updated plus the timer time [https://github.com/jimmykane/fit-parser](https://github.com/jimmykane/fit-parser)

I checked and I cannot see in the fit sdk that there is timer_time for records. Also should that be there. There is already elapsed time. Timer time should be...

Could you try my fork and lets continue there? I think @pierremtb is a bit busy the latest time https://github.com/jimmykane/fit-parser

At least I am trying to maintain this lib in a fork. I am picking up issues also from here, but would be great if it's not fixed to report...

I ll get back to this. Have not forgotten you. Need to get some free time :-) On Thu, Mar 28, 2019 at 7:19 PM svrpeakers wrote: > any idea...

@svrpeakers Can you provide a fit file to test against? Thanks!

Thanks

I dont see any issue on the processing but I am also kind clueless about the `avg_stance_time_percent `. To me it looks like you are looking at `avg_vertical_oscillation ` Could...

@svrpeakers are you maybe looking for `avg_stance_time_balance ` ? I think that is missing from this importer. Looking at it.

@svrpeakers example on full decoded file ``` --- timestamp=921336141=2019-03-12T14:42:21Z --- start_time=921333655=2019-03-12T14:00:55Z --- start_position_lat=405952636=34.0265569 deg --- start_position_long=-1413915656=-118.5130412 deg --- total_elapsed_time=2455715=2455.715 s --- total_timer_time=2400626=2400.626 s --- total_distance=662501=6625.01 m --- total_strides=3170=3170 strides ---...