Help fixing baroalt issues

The elevation reported by the various ConnectIQ APIs is the same. I believe that the value provided is already some combination of the GPS elevation and the barometric altitude, or maybe just the barometric altitude (as reported in this thread).

Travis

That is not possible.
I use the GPS ELEV data field for runs even though the watch is set on AUTO CALIB CONTINUOUS and I manually calib on the exact elevation at the beginning of each activity (wherever I am: at home, at the swimming pool or at locations I know the exact altitude). We need a FUSED-ALTI to compensate for the GPS inaccuracy.

Calibrated 158m (home) -> GPS ELEV reported can be up to 181m. An APP that shows you the medium between the 2 is already better than what we have now.

At the end of this run (which started with 158m manual calib -> Auto -> Continuous), I started a WALK activity (without re-calibrating) and a few minutes later, at a known altitude of 3m my GPS ELEV data field was showing 14m.

We can't go on like this for ever.

I know that if I set the auto-calib on continuous I may as well not manually enter the known elevation but I do not want to lose this good habit. I use the corrected data in my software so ELEV is not an issue for log studying purposes but during the activity it's truly a DISASTER IQ DEVs could mitigate.

If you or anyone else can build a FUSED-ALTI that may compensate the baro data and gps data into a new IQ field, that would be great and I would stop using the continuous auto-calibration. We REALLY need this app.

That is not possible. I use the GPS ELEV data field...

Is this GPS ELEV data field a ConnectIQ datafield, or is it built-in? If it is ConnectIQ, then perhaps I'm wrong. I'm not sure what device you are using that has a GPS elevation data field, but the devices I've tested on (and the d2bravo shown in the video linked above) don't currently use different elevation data in ConnectIQ.

An APP that shows you the medium between the 2 is already better than what we have now.

Perhaps, but I'm still not convinced that GPS elevation and barometric altitude are available as two unique bits of data. Granted I've not written code to prove it to myself recently, but there has been a lot of talk about issues relating to this over the last week.

An app has access to the barometric pressure provided by the ConnectIQ API, but as you know, this doesn't map directly to the barometric altitude.

Travis

Is this GPS ELEV data field a ConnectIQ datafield, or is it built-in? If it is ConnectIQ, then perhaps I'm wrong. I'm not sure what device you are using that has a GPS elevation data field, but the devices I've tested on (and the d2bravo shown in the video linked above) don't currently use different elevation data in ConnectIQ.

It's a standard data field. Device in use is Fenix3 v 4.4 FW.
You can theoretically set both fields independently to work either in a page or in 2 different data pages. However, since I use GPS ELEV, I have no idea what the ELEV data reported on Garmin Connect is. Even though I calibrated the baroalt, I also had the auto-calib on continuous so what I see on GC could be either of the 2 instruments.

Perhaps, but I'm still not convinced that GPS elevation and barometric altitude are available as two unique bits of data. Granted I've not written code to prove it to myself recently, but there has been a lot of talk about issues relating to this over the last week.

Is there a way to find out what can be done with these 2 different data fields? http://www8.garmin.com/manuals/webhelp/fenix3/EN-US/GUID-02713A0A-48C2-4EA1-BCD0-D5FC7D1EB68A.html

We REALLY need this app, it's not just me: look at this: https://connect.garmin.com/modern/activity/869288981

The least is 9m offset. That road winds by the seaside at 1m altitude.

LOL

Primoz the baroalt is not accurate because cabin is pressurized. GPS elev can't be accurate either because it takes the GPS altitude from a database of points clamped to the ground (and even in this case, at 1m level altitude, my GPS elevation data screen was giving me 10m this morning). :)

I have never used a screen with both baro and gps alt but before I say something else was auto calibration engaged and continuous?

LOL

Primoz the baroalt is not accurate because cabin is pressurized.

Grrr, do not insult me Z-74! Of course I know that!

I posted this photo only because it seems to me that Travis does not believe that Fenix 3 has built-in two different elevation data: barometric and GPS (unfortunately in .FIT files only barometric elevation is recorded).

Is this GPS ELEV data field a ConnectIQ datafield, or is it built-in?

Grrr, do not insult me Z-74! Of course I know that!

Didn't mean to insult you of course. :-)

Surely if Travis finds a way to build this app it might well be one of the most downloaded of all times and the same goes for the other one with temperature.

The sailing app im helping to test is amazing.

it seems to me that Travis does not believe that Fenix 3 has built-in two different elevation data: barometric and GPS

It isn't that I don't believe the built-in data fields don't support two concepts of elevation/altitude. The issue that you both don't seem to understand is that the ConnectIQ API doesn't allow access to both bits of information.

As an example, my fr920xt has a lap pace data field that is part of the device firmware. The ConnectIQ API provides access to current pace and average pace, but it does not currently provide a way to access (or generate) lap pace data in a custom data field.

As I mentioned in my initial post in this thread, there are multiple places in the ConnectIQ API that provide altitude/elevation data. If you watch the video I linked to, or read the post, you'd see a developer had shown a working app that displays the three elevation/altitude sources and concluded that they all provide access to the same data (barometric altitude on his d2bravo, but you'll see similar behavior from other devices like the fenix3).

What I'm trying to tell you is that this theoretical data field you want is not possible with the current ConnectIQ API.