Iregularity regarding MinimumTemperature

[Nigel Laws]

I don't know why I have not spot it sooner, but, when I display Max, Avg and Min temperature  in a "Tile" under "Overview"  , more often than not, the "Min Temperature" is always displayed as "32", regardless of the fact, the temperature has been no where near freezing.. If I recall, GC always displays temperature in Fahrenheit which in centigrade, that would be "0 C" and if it had been that, my ride would have been icy, and it was no where near being icy? Max and Avg temperature look correct

The same has happened for the past 7 days in a row, the 8th day it was recorded as "39.2" and before that it records again as "32" and so on

I have checked the "Fit" Files on the Garmin Edge 530, and in non of them can I find any record of "32" being recorded, yesterdays minimum was "48" in the FIT file, but in GC V3.7.Build ID 5006 it shows as "32"

The earliest record that I can find this happening is Aug 26 2025 and that is when the issue seems to have started? Was their a GC update???

Garmin Connect  shows yesterday as 8C as opposed to "32" in GC and the FIT file reader records min temp as 8C. And I have also checked the Edge 530 with a wall thermometer and it reads virtually the same bar a degree or two at the end of my ride.

Any ideas what could be happening that I can look at that could be causing a conflict or something to try?

[Ale Martinez]

The likely reason is some zeros in the Temp series which are displayed as 32 when using imperial units, you can look for them in Data > Raw Data, to check the FIT file you would have to attach a sample file.

[Nigel Laws]

Thanks for the quick reply,

 I have done a check on the FIT file on the Edge "530" for my last ride and I can see no "Zeros" in the temp series under Raw Data.

But when I look at the Raw Data in Golden Cheetah, I see there is a few groups of "Zeroes" in the Raw Data and it appears that this is happening when I have to stop at a road junction etc

And when I check again on the Edge 530, during these time periods when I am stopped, nothing has been recorded for anything, including temperature and it all restarts when I start riding again so I get the impression GC is filling in these gaps with records.

I have a theory what might be causing it now I can see the problem, a good few months back, I tried to get GC to download weather information into my rides just after I rode "London Edinburgh London" and it was unsuccefull, but, I never deleted or removed what I had done as I was going to try and make it work, but I forgot about it. so I am going to delete everything and see what happens when I upload yesterdays ride again

I appear to have resolved the issue, Under "Automation and Processors", I removed my "Weather" module which did not work, but also under "Automation and Processors" cancelled "Fix Gaps in Recording" ,Which I think was the culprit as I see it says that it will insert "Zeroes" if the gap is longer than what has been set. But, I have it set at "90s" so nothing should be happening as one gap I looked at was only about 35 seconds and the temperature was filled with "Zeros"

When I reuploaded yesterdays ride with todays date, the "Min Temp" was displayed correctly as "46.4"

Anyway, thanks for the help. I now need to find a quick way to alter all the records that become corrupted but I will try and do it in "raw data" using "Find and Replace"

[Nigel Laws]

I did some experimenting on my short ride today and can confirm that it is "Fix Gaps In Recording" that is causing the issue. 

Uploading my ride with it disabled, it records the minimum temp exactly as what I observed myself on the Edge 530 during the ride.

But, I also did two deliberate stops, towards the end of the ride to experiment with: - 

When I import into GC, regardless of what settings for length of stop and tolerance etc in "Fix Gaps in Recording" to try and ignore the length of Stop, it still fills the temperature data fields with "Zero's".

Do I presume correctly that the "default settings" for "Tolerance" and "Stop" are "Minutes:Seconds""?

If so, I have tried setting them to as large a "Stop" as possible to ignore the stops that I have done, and it makes no difference, "Zero's" still appear?

It seems the only way to avoid it happening is not to use "Fix Gaps in Recording"

I get the feeling, I'm either setting the Default Settings wrong or their is a bug. As no one else is reporting it, it must be user error somewhere!!!!

[Ale Martinez]

El miércoles, 17 de diciembre de 2025 a la(s) 11:56:31 a.m. UTC-3, laws...@gmail.com escribió:

I did some experimenting on my short ride today and can confirm that it is "Fix Gaps In Recording" that is causing the issue. 

Uploading my ride with it disabled, it records the minimum temp exactly as what I observed myself on the Edge 530 during the ride.

But, I also did two deliberate stops, towards the end of the ride to experiment with: - 

When I import into GC, regardless of what settings for length of stop and tolerance etc in "Fix Gaps in Recording" to try and ignore the length of Stop, it still fills the temperature data fields with "Zero's".

Do I presume correctly that the "default settings" for "Tolerance" and "Stop" are "Minutes:Seconds""?

It's seconds, but don't presume better RTFM

If so, I have tried setting them to as large a "Stop" as possible to ignore the stops that I have done, and it makes no difference, "Zero's" still appear?

It seems the only way to avoid it happening is not to use "Fix Gaps in Recording"

I get the feeling, I'm either setting the Default Settings wrong or their is a bug. As no one else is reporting it, it must be user error somewhere!!!!

I don't understand your insistence in using Fix Gaps in automatic mode if you don't like the filling with zeros since you can enable Smart Recording in General to interpolate short gaps and let the larger ones alone without using Fix Gaps tool.

[Nigel Laws]

I have always used "Smart Recording" and I have stopped using "Fix Gaps" in automatic mode, it was only something I started using in September but only recently noticed it has issues. Today, I was just experimenting with it for something to do

If the default settings are "Seconds", why have the format as  "01.00 s", are we using whole seconds and also "Tenths and hundreths" of a second? I do not see anything in the manual to show what information is represented? By my way of thinking, its "Mins:Secs"

Basically, why have a feature in GC which when enabled, causes issues by putting incorrect data in the form of "Zero's"  into the file which ultimately causes incorrect output of information?

[Ale Martinez]

El miércoles, 17 de diciembre de 2025 a la(s) 6:57:37 p.m. UTC-3, laws...@gmail.com escribió:

I have always used "Smart Recording" and I have stopped using "Fix Gaps" in automatic mode, it was only something I started using in September but only recently noticed it has issues. Today, I was just experimenting with it for something to do

If the default settings are "Seconds", why have the format as  "01.00 s", are we using whole seconds and also "Tenths and hundreths" of a second? I do not see anything in the manual to show what information is represented? By my way of thinking, its "Mins:Secs"

Basically, why have a feature in GC which when enabled, causes issues by putting incorrect data in the form of "Zero's"  into the file which ultimately causes incorrect output of information?

GoldenCheetah has several features which allow users to shoot their feet, that's a fact. Why this happens?

In my opinion -and this is not an official statement, just my personal take- it is a side effect of being a collaborative non-sponsored FOSS project, developers tend to be willing to collaborate developing features they are personally interested to use and/or to develop, but to make those features foolproof (besides being a kind of slippery slope concept, i.e. how "fool" is expected the target user to be?) means a lot of less satisfactory and ungrateful work not that many people are willing to do unpaid.