Recording Boulder

As to disapproval it took it from the interpretation of this

• Overriding the User’s Data. We do not allow apps to override information previously synced to their Connect account, where such data fields typically come from the Garmin device itself (e.g., speed or distance). We want to maintain the integrity and reliability of data values collected or generated by Garmin’s devices and software.

That is exactly why Garmin Connect ignores nativeNum in user data/fitcontrib fields.  But not all sites do,

Hi all, I tried again to write data into laps with no success. When using :sport=>Activity.SPORT_ROCK_CLIMBING, :subSport=>Activity.SUB_SPORT_BOULDERING Garmin doesn't realizes laps at all.

When I use :sport=>Activity.SPORT_GENERIC, :subSport=>Activity.SUB_SPORT_GENERIC laps are shown in Garmin.

I published the relevant code in a Github repo, just in case, one of you wants to have a look :-)

https://github.com/henry-1/Test_Garmin_Laps_with_Bouldering_Activity

Thanks again for all your help

Henry

This reminds me that there are some metrics that are not available in some activities. There was one that is not possible to add to a floor climb activity (I don't remember but maybe cadence or steps) And interestingly enough it's also not possible to add it via CIQ. It's just not present in floor climb. So maybe this is also some restriction that the bouldering activity has?

Last thought on this: It seems to be room for improvement of the Garmin documentation. At a first glance they allow us to create apps with their pre-defined and on the first look well documented APIs. But then and only with the help of the community I had to learn the hard way that there are undocumented dependencies and pitfalls like
- what are the miniumum fields to be defined
- what are their internal names (or numbers: nativeNum)
- why are their no laps if you define them in one profile but not in the other
And they could learn from this thread that not all sports profit from knowing the speed and distance. There are sports out there where those common numbers absolutely make no sense.
For now I am as disappointed as I was 5 months ago.
But
a) for all of you who joined this conversation => many thanks
b) if in the future something changes, please let me know, I am just a few steps away from finishing my app.

cheers, Henry

Some things are documents, but in the fit SDK,  Profile.xlsx if I recall.

https://forums.garmin.com/developer/fit-sdk/

Also, there can be things in the fit that aren't displayed in Garmin Connect based on the sport  The fit SDK has a few different ways to see what's actually in a fit file.

Henry, just out of personal interest, how are you recording the grading system and the grades as fit fields.

After I learned that Garmin doesn't allow to write their fields and as I am not interested in grades at all I do not manage a field for grades.

I am interested in the count of boulder and their hight, my heartrate and the active vs.  the inactive time. I looked up grade in the profile excel sheet and found avg_grade in line 539 for laps with the number of 45. I assume this would be nativenum for my custom field. But is it worth trying? As I said before I don't know what else is required to get a valid lap (missing in documentation). I could publish my code completely if you want to have a look? For my PoC I definied 3 fields. One for each: session, lap and summary.

Instead of measuring real values I calculate random numbers for hight and every 20secs I call addLap().

For session I use hight and I see a nice graph displayed in monkeygraph, the highest point of the current boulder I use for lap but it doesn't work and in the summary I just have a value for the total boulder count which means how often the 20secs run out.

Sounds like you could benefit from posting the code you use to create the 3 fields