I don't see lap data in Activity::Info. Is it possible to add it in future release?
Apart from all the data that can be displayed using built-in data fields it would be nice to have startLocation and startTime too.
Thanks.
How do I do the session.addlap then? I guess the next point? And auto press the session.addlap?
The reason I said no access to the fit file is cos I can only anticipate and get the code to press autolaps.
But from CIQ, you'll see this at 5:02, so if you do a "markLap, it will be at 5:02 (1.01km), correct?
I though Nikeow was discussing computing laps within a data field, which can't create their own laps.
From an app context, this is not possible until controlling the Auto Lap setting is possible. I think this will be added sometime, but I don't know when it will get in.
You could still create your own "laps" within an app, but they would not be created in the FIT file unless the internal Auto Lap matched.
You roll your own. You can just take the simple approach and assume that speed was constant within the sampling period so if the period is 1 second and the previous distance was 0.99 miles and the next one is 1.01 then you just assume that the 1 mile mark was crossed at the 0.5 second mark. Simple.
If I were just trying to create a datafield and I only wanted to show which lap I am in (similar to the LAP field from garmin native fields) then I could do that.
I though Nikeow was discussing computing laps within a data field, which can't create their own laps.
From an app context, this is not possible until controlling the Auto Lap setting is possible. I think this will be added sometime, but I don't know when it will get in.
You could still create your own "laps" within an app, but they would not be created in the FIT file unless the internal Auto Lap matched.
I was actually referring to session.start/recording module where I can do an session.addlap.
Currently, my session.addlap is ROUGHLY correct at 1.01/1.02 etc whic represents 1-2% error.
I've not looked at the internal fit file (haven't managed to get it done yet) but... In GCM, I can see the lap sessions. I am able to get the 1.01/1.02/0.99 etc km as well as the time taken for each lap. I presume this comes from the fit file.
We have this on the books to be addressed, but the feature is not yet available. I've made notes on our ticket and have asked to see if we can move it up in priority.
Hi, any update on this request to make lap info accesible? It would be very useful to have current lap info (current lap number, current lap distance, etc.). Thanks.
Hi, any update on this request to make lap info accesible? It would be very useful to have current lap info (current lap number, current lap distance, etc.). Thanks.
Current lap, current lap time and current distance can all be done programmatically .. I just did it recently for my app and I am not a proficient Connect IQ developer yet. So it is not that hard to do.
In a watch-app, it's easy to know about laps, as addLap() is used by the app to mark laps in the .fit. It can be done based on time, distance, a button press, etc., but the watch-app knows about it in all cases.
In a data field, the info is not available yet.
A DF can guess at things based on distance (such as auto-lap is on and set for 1km/1mi). auto-lap default for cycling (IIRC) is 5km/5mi), but from a DF, you don't know if you're in a running app or a cycling one, or if the auto-lap is even on, or if the distance is something non standard, or if the manual lap button is enabled, (a manual lap may be involved which resets the distance if auto-lap is also used.)
So today, "laps" is easily known in a watch-app, but only a guess in data fields, but CIQ will be exposing lap data in a future update so lap data can be known in a DF.
