GPS altitude meter

[freeheeler]

@fenr1r
not everyone can pull an A3P out of his drawer

[Fenr1r]

@freeheeler said in GPS altitude meter:

not everyone can pull an A3P out of his drawer

Ha! Good point. (Altho’, as detailed elsewhere, my A3P [FusedAlti] was outclassed by an SSU [Baro only] in a comparison a while back. So it may not be at its best.)

However, as long as there is postal delivery and selfless dedication to the scientific method …

It occurs to me that there is a more definitive test: against another 9Baro of known, recently-demonstrated accuracy.

You can fall back in affection with your Airboss in the interim.

[MRony]

@freeheeler today i was a Tour, and the gps failed~ 100m! Photo i will load up in 3houers!

[freeheeler]

@mrony
let’s say, without knowing details, the altitude was wrong… not GPS failed. at least that’s what I understand from the context, it could be misleading.
I’m curious about your details.

[Brad_Olwin]

@fenr1r said in GPS altitude meter:

@freeheeler

we need samples from @MRony where we can see the graph and have some fix points to indicate the deviation in altitude.

Preferably with simultaneous, co-located fixes from other devices with known generally superior accuracy.

All that is really needed is to get a fit file and compare corrections in Runalyze

[Fenr1r]

@brad_olwin Will that tell you the GNSS reception conditions for the route or the corrections made for a notionally optimum route?

[MRony]

@freeheeler - Now I have attached the pictures --------------------------------------------

[MRony]

@freeheeler – one more

[freeheeler]

@mrony
PTE 5.0, are you running with your skis??

The pics are nice and the data, but it would be good if we could associate the info better.
@Brad_Olwin mentioned runalyze, but I don’t use that, hence, no idea about that one.
If you would upload to QS and share the link it would help to see if there are unregularities in the graph.

[freeheeler]

@mrony

1. is 14m too high
2. 90m too low
3. 11m too high
   correct?

[MRony]

@freeheeler correct

[freeheeler]

@mrony
personally I would only worry about the 90m low.
let’s look at your 90m low activity isolated in quantified-self.io

[MRony]

@freeheeler -
My father-in-law - always makes sure that I work up a sweat.

What means QS an how i do this?

[freeheeler]

@mrony
you can upload exported activities to here… or do a complete sync, publish, share… if you’re concerned about privacy make it private again after we checked
https://quantified-self.io/user/jBm0qOhihUMykVYD8HBJMshQrJc2/event/e5b5d4f153619dbd9d24526cf725eb736779f29171438dc1a528c43aa3135019

[MRony]

@freeheeler i will try this tomorow - now i musst bring my kids to bed. Thanke you for your support. KR Rony

[MRony]

@freeheeler Hello, I spoke to Suunto Customer Service. There I was informed that a deviation of 1-3m would be normal (would also suit me) - my deviations (values) are too high. I should reset the clock to factory settings (test again) - if that doesn’t help, i shoud send it to customer service. Info will follow! BR Rony

[Dimitrios Kanellopoulos]

@mrony how high are the deviations and how is the refernce defined?

10meters is also ok. 20 no. only as an exception

[freeheeler]

@dimitrios-kanellopoulos
@MRony has sent samples with

1. 14m too high
2. 90m too low
3. 11m too high

[Dimitrios Kanellopoulos]

@freeheeler with a baro device ?

[Dimitrios Kanellopoulos]

If you want me to analyse what happend please provide a link from suunto app, the expected values and so on