Altitude / Barometer - Possible to snap to GPS altitude?
-
Did a run this morning where the S7 registered a 200metre ascent in the space of about 1 minute, then gradually reverts ever closer to reality (but never quite gets there) for the rest of the activity.
I was running along a flattish river bank, so pretty sure I’d have noticed the steep incline!!
My RunAlyze is configured to ‘correct’ altitude on import >>
https://runalyze.com/shared/jw175It was constant drizzle rain conditions, and I was in short sleeves, so pretty sure it would have been the barometer getting blocked and gradually drying out or something, it happens I suppose.
But - is there any way of ‘correcting’ such obviously wrong data and using the underlying known height from GPS positioning instead, within SA?? It should be relatively easy to compare the ascent recorded from the Watch to the ascent expected from GPS data and if there’s a big discrepancy offer up the option to use alternative measure?
-
@nigel-taylor-0 weird jump there the graph
. Personally I’m hoping that SA gets the ability to correct altitude on workouts at some point. Every now and then the S7 baro hole will get dirty and I’ll get some ridiculous elevation data. It would be nice to be able to correct these when they happen. -
@nigel-taylor-0
Dont know if you removed that part of the file maybe - don’t know if any of these tools might assist:
https://www.fitfiletools.com/#/top -
@jamie-bg said in Altitude / Barometer - Possible to snap to GPS altitude?:
@nigel-taylor-0
Dont know if you removed that part of the file maybe - don’t know if any of these tools might assist:
https://www.fitfiletools.com/#/topYeah I can do it manually easily enough.
BUT - given SA has ability to measure altitude from GPS data (how it works for non-baro watches), surely it should be inbuilt to sanity check that baro vs GPS altitude is within 10 to 20%, and if not, allow the ability to ‘correct’ to the map data?? (I know that Strava for example can ‘correct’ obviously wrong data like this?).
To be honest, all I’d really like is some kind of marker that says, “by the way, this looks wrong, you might want to look at it”. I noticed in this instance because the jump was so massive, but it causes me to lose a bit of confidence in other data.
-
@nigel-taylor-0 non baro watches draw altitude data from GPS and not from SA (sadly as small hills barely get recognized). You might be referring to s3 which completely relies on phone’s GPS. But I’m not sure whether s3 gets altitude data at all? I think altitude corrections might come eventually as there were a lot of requests. We just have to wait!
