Spike-noise in recorded track elevation while paused

Andrew Heard shared this problem 19 days ago
In Progress

I've unfortunately switched from a phone with pressure sensor to one without. Progress? No. After experimenting a long time with GPS "optimize GPS values" and filtering:( no | light | medium | heavy), Even with typically 38 satellites and 2m horizontal accuracy, I switched to "replace GPS values". This generally results in less vertical noise/ jitter in the recorded track elevation. However while the track recording is paused I often notice really bad elevations, today being an example of the worst.

track recording https://link.locusmap.app/t/maoar4

Here is the LM4 (Android) elevation because the web planner elevation doesn't show negative values for some reason (bug). I paused at 2km (half way) and clearly/ logically the elevation should remain close to 60m while stationary.

492dc2b56005a1b7562742149a63947a

Here is the GPS accuracy. +/-22m of positional jitter. Why is this level of jitter sufficient to cause a huge change in calculated elevation given that the values are derived from SRTM data & GPS elevation is ignored? "replace GPS values" is set. The land around this pause location is relative flat, so even moving the position +/-200m will not result in a significant change in elevation, and certainly not -40m!!

6820f1229ef9c4fd2d472d5ae3972136

The notional position when paused inside building seems quite reasonable:

3dcc7495ca5d1657be800005ef2f308a

Replies (1)

photo
1

Hello Andrew,

these negative peaks happs to you (almost) always when you stop for a moment? Interesting.

Best to do something with it >

  • Beta version, "Log to file" enabled + in "Setup logging" enabled "Location & GNSS"
  • record a track during the trip

If problem happen, track shared over our web portal + recorded log file > I may exactly see when and what comes from the system and probably simulate this problem. Thanks.

Btw. there is currently no Beta version as 4.27 version is published and awaits validation by the Google. But new Beta will be for sure in the end of this week.

photo
1

>"Log to file" enabled

OK, (eventually) found in Expert setting


>"Setup logging" enabled "Location & GNSS"

settings > GPS > in "NMEA recording" = Always?


A search in settings for "logging" only lists 2 geocaching settings

photo
1

Ha ha - my luck - the track today behaved itself; in fact of the last 13 recordings, only the one reported showed this 100m negative drop in elevation while paused, while 2 others record ~30m drop. So I will monitor & wait for the next time. It is interesting that with "replace GPS values" and identical route, identical walking speed, there is some variation in the elevation. Would you expect that when horizontal accuracy is +/-2.5m?

0e34e57d6879c469192dce12216cdb44

zoomed in - note 3 tracks clearly have significant negative elevation drop (2 x 30m, 1 x 100m):-

ca47e81889d5a63a360174b9f16d9a4a

graph from Garmin Basecamp - still has its uses ;-)

photo
Leave a Comment
 
Attach a file