In the profile file, in the fit_base_type, any reason why Bool was not included? If it is not considered a base type, then it is not listed as a type of its own either. Any reason for its special treatment?
There was no reason for bool to be excluded. We'll get that fixed.
With respect to localtime_into_day, I can see the argument here, but, as I am sure you can understand, it is not possible for us to change the names of types without breaking backward compatibility of our libraries.
In device_info and software, the scale of software_version is 100, but in in file_creator it seems to not have any.
When trying to make sense of the GPS data, by looking at the numbers and knowing where I was, I have managed to get it close to where I expect by dividing by (2^32/2). It feels quite exciting to finally be able to plot all the running parameters out of my watch, but there might be an off by one error there. I think that the Profile file should have the right scale in it.