Bug: interval start_index/end_index all the time 0/whole for Open Water Swimming FIT actions – Bug Reviews

Hi,

I’m importing FIT recordsdata for freediving classes (sport=swimming / sub_sport=open_water) generated from a Suunto Ocean dive pc (JSON export).

I’ve two points I want to get assist with:

Issue 1 : start_index / end_index all the time 0 / whole for all intervals

All intervals in my exercise obtain incorrect stream indexes:

• start_index = 0
• end_index = whole variety of information (7746)
• elapsed_time = whole exercise period

This makes it unimaginable to compute per-interval statistics utilizing stream information (depth, temperature, and so forth.) through computed subject scripts, as all intervals learn the whole exercise stream as a substitute of their very own portion.

Test script used:

interval.start_index + " + interval.end_index + " + interval.elapsed_time

Result for each interval: 0 / 7746 / 7746

Issue 2 : FIT lap messages not appropriately mapped to intervals

My FIT file incorporates 34 lap messages with right timestamps (Plongee 1-17 + Recuperation 1-17). However intervals.icu detects a unique variety of intervals (30-34 relying on the session), and the mapping between laps and intervals is inconsistent.

Is there a selected technique to construction FIT lap messages in order that intervals.icu maps them appropriately for Open Water Swimming actions?

Context:

• Sport = 5 (swimming), sub_sport = 18 (open_water)
• 7746 information at 1Hz
• 34 lap messages with right begin/finish timestamps
• Activity period: 2h09

Thank you on your assist!