This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Remove spikes for Tempe graphs

I've seen discussions elsewhere dating 3 years ago.

I've just bought a Tempe to track temperature while running and hiking. I couldn't believe Garmin data filtering is so basic.

As you can see from the graph, it sometimes doesn't get any measurement from the Tempe sensor, thus reverting to the internal (useless) one.

How difficult is to understand that if 99% of the measurements come from the external sensor, even if a measurement is missing it should just duplicate the previous one, not creating a spike?

(note that the screenshot is from the iOS app, but this is the same for web)

0 trux over 5 years ago

Labronico said:
How difficult is to understand that if 99% of the measurements come from the external sensor, even if a measurement is missing it should just duplicate the previous one, not creating a spike?

Did you already suggest it to Garmin? https://www.garmin.com/forms/ideas/

0 Labronico over 5 years ago in reply to trux

Well, is removing noise from a signal… a feature request?

However no, I was asking for feedback from users first, given that users do respond quickly, unlike Garmin on other channels.

0 trux over 5 years ago in reply to Labronico

Labronico said:
given that users do respond quickly,

That's true, but how do you want that we filter your graphs? You need to speak to Garmin if you want to remove the noise signal. Perhaps they do not even know, there is such a problem. I would not know either, if you did not post it here.

0 Labronico over 5 years ago in reply to trux

Huh? I didn’t ask fellow users to solve my issue. I ask for confirmation regarding this bug.

0 Former Member over 5 years ago in reply to Labronico

I have continuous issues with elevation spikes. On a recent hike I went from 500 ft to 70,000 ft in about 30 secs. Quite a feat! As has been suggested it should be a very simple software fix to filter out spikes that are clearly non-sensical.

0 trux over 5 years ago in reply to Former Member

I have continuous issues with elevation spikes. On a recent hike I went from 500 ft to 70,000 ft in about 30 secs.

Most likely you pressed against the pressure sensor orifice, or it got clugged with sweat or with dirt. Actually, if the pressure reading suddenly dropped (showing high altitude), it was likely caused by a wind gust (Bernoulli's principle).

However, you can get rid of the wrong barimetric reading (and of the spikes) in the graphs, if you enable the Elevation Correction on the page of the respective activity in Garmin Connect Web.