Why has course_point message a timestamp field 1 and not 253?

According to the documentation a timestamp field is one of the 'common fields' that have a reserved field number, in this case 253 (see section 4.7).

Given that, why does the course_point message have a timestamp field with number 1 (at least in in profile 21.89)? Or will compressed timestamp headers never occur in combination with this message?

0 Ben FIT over 2 years ago

All timestamp fields should have the id 253.The course_point message may have been added before the rule was put in place. That message was one of original messages back when the SDK was first created in ~2009.

0 BESSELING.FRANK over 2 years ago in reply to Ben FIT

Thanks!