Issues altitude diagram

Stefan Kersting

@Mff73 no have iOS. But it could be nice to have information about the signal quality. Maybe a azimuth Display or something like that. But I don’t know if the problem lies there

Stefan Kersting

Did everything you guys recommend. Used Auto calibrate, manual calibrating, had the watch for half an hour in warm water. But when your supposed to start at 4 masl and finish at masl this result is absolutely unacceptable

Stefan Kersting

Brad_Olwin

@Stefan-Kersting It could be the sensor is faulty too, hard to say.

Stefan Kersting

@Brad_Olwin when Auto calibrating, do you get a confirmation? I just have this screen even when outside and trying to auto calibrate

Dimitrios Kanellopoulos

@Stefan-Kersting I think no on Spartans. However you can set the altitude to 1000m and check if its changed

sartoric

@Stefan-Kersting
Never, but it say “in background” so … I never expected it but I noticed a blink in the watch face

Stefan Kersting

@Dimitrios-Kanellopoulos I get a gps position but after a manual calibration on 500 masl tja altitude isn’t adjusted when using auto calibration. Have to do it manually

Dimitrios Kanellopoulos

@Stefan-Kersting it needs up to 15 mins

Stefan Kersting

@Dimitrios-Kanellopoulos ok then I have to wait more than 2-3 minutes…

Stefan Kersting

@Brad_Olwin now I did a hike and not a run in order to have enough time to follow the altitude on the watch. The interesting thing was that I started at an altitude of 5 masl and with a fast ascent to 30 masl and after a short time the altitude was at 13masl which was realistic. So that must be an issue with the satellite fix at the start. BUT I have never seen a negative altitude on the watch and when downloaded I see that the lowest point was registered with -15 below sea level. So now I don’t understand anything. The watch displays another altitude than SA…

johann.fuehrer

Hello, I’m surprised that this “my altitude does not match with my map reading” topic is coming up ever and ever again. I have written about this somewhere in the past, so here some information from guys who know what it is about: https://www.usgs.gov/faqs/why-dont-elevations-your-maps-agree-those-provided-my-gps-system-which-ones-are-correct?qt-news_science_products=0#qt-news_science_products

This is one of the reasons, Garmin brought in DEM data to Fenix models (I think mesh points in 30m grid)…

That is why I suggested a local offset which CAN be set manually and would shift the GPS altitude calculated by this offset for EVREY altitude value - right ones and wrong ones (bad GPS, abro i.e.). So also fused alti would work. It would not touch the GPS altitude reading and calculation directly, but after getting GPS altitude + fused alti calculations, it would add/sub the local offset of the GPS_geoid_to_real_map_alti difference which has been set manually. my5c

(which would mean: exact the same altitude profile but shiftet to real altitude due to offset…)

Fenr1r

@johann-fuehrer said in Issues altitude diagram:

TruFusedAlti. Do we know if Suunto uses the datum elevation or that from satellite triangulation? Or one and then the other?

my5c

Inflation?

Dimitrios Kanellopoulos

@johann-fuehrer afaik Suunto uses mean sea level. What am I missing ?

johann.fuehrer

@Fenr1r said in Issues altitude diagram:

@johann-fuehrer said in Issues altitude diagram:

TruFusedAlti. Do we know if Suunto uses the datum elevation or that from satellite triangulation? Or one and then the other?

Dont know. BTW: This was the thread & post I referred to, needed some time to find it again … https://forum.suunto.com/post/36919

Fenr1r

@johann-fuehrer Thank you. Very interesting and now my head hurts.

johann.fuehrer

@Dimitrios-Kanellopoulos said in Issues altitude diagram:

@johann-fuehrer afaik Suunto uses mean sea level. What am I missing ?

The physical model of Earth and the mathematical model of GPS geoid do not match. Not in altitude (and also not in horizontal offsets, but let’s forget this by now). Maps are not based on the GPS geoid but of some agreed MSL - but not to the same over the whole world (https://en.wikipedia.org/wiki/Vertical_datum)
There is lot of stuff about this on the internet, and to what funny results this led like tunnes planned by two different countries which did not met, bridges and other stuff. But the main conclusion is: GPS watches calculate the altitude based on a “ideal” world shape, which does not 100% match. For some parts of the world the altitude calculated match perfect, on others it’s way off (there is some map about the offset here: https://www.esri.com/news/arcuser/0703/geoid1of3.html) . DEM models have correction information based on the location for the GPS calculated values.

So for places on earth where the GPS and map data have a “natual” offset, you need an additional correction, if you want to be precise - or live with the altitude profile being OK but have a small or bigger offset.

johann.fuehrer

@Fenr1r said in Issues altitude diagram:

@johann-fuehrer Thank you. Very interesting and now my head hurts.

I’m sorry for your headaches…

Dimitrios Kanellopoulos

@johann-fuehrer I have a headache as well

Dimitrios Kanellopoulos

@johann-fuehrer at the same time I hear / read in other groups of garmin that the DEM is not ok. Am I wrong ? I am asking not to downplay Garmin, I love DEM, but I want to know in practice. At least if it solves issues like @johann-fuehrer has or even @Stefan-Kersting