Connected GPS feature SF3/Galileo supported smartphones

[Luís Pinto]

@slashas Elevation is on corner at left in app.

[Luís Pinto]

@slashas

[SlaSh]

@luís-pinto but why one the right it is stuck on 204?

[Luís Pinto]

@slashas Or there is a bug on graph or in values of table. The zone in question (maybe a valley) i bet that graph have right values.

[Luís Pinto]

@slashas We need also the specifications of watch and smartphone if have barometer or not…

[jthomi]

Its the Suunto Spartan Sport in shiny Blue, so without Baro.

And the iPhone7 with newest iOS.

But now that you mentioned it, the tracking of elevation in the app was with GPS not Barometer. And it may sound dumb, but my iPhone7 has a barometer? Oh, my, just seeing it right now, who knew…
I can switch the barometer on tomorrow for the other ride.

[jthomi]

Maybe the app was exactly 204 descent and ascent? The screenshot from the data in the app is also pretty close, only 0,40 meters off.

@slashas said in Connected GPS feature SF3/Galileo supported smartphones:

@luís-pinto but why one the right it is stuck on 204?

[Dimitrios Kanellopoulos]

@slashas said in Connected GPS feature SF3/Galileo supported smartphones:

@jthomi so why mygpsfile missing it?

This is ascent total ascent

[Dimitrios Kanellopoulos]

This is the elevation profile comparison

[Dimitrios Kanellopoulos]

Mygps files calculates its own way the ascent.

All day in comparison look fine do not create a problem out of this.

[Dimitrios Kanellopoulos]

Watch looks better. At the moment Galileo from.my tests does not give more than 4% improvement. Tested on Android and the test gps apps that support Galileo.

[Dimitrios Kanellopoulos]

@jthomi said in Connected GPS feature SF3/Galileo supported smartphones:

Maybe the app was exactly 204 descent and ascent? The screenshot from the data in the app is also pretty close, only 0,40 meters off.

@slashas said in Connected GPS feature SF3/Galileo supported smartphones:

@luís-pinto but why one the right it is stuck on 204?

I would not bother with ascent at this time. All services do it their own way. Especially mygps files.

[Dimitrios Kanellopoulos]

Also the correct term is ascent. Elevation is altitude. You can say elevation gain for example or altitude gain or ascent.

[Luís Pinto]

@dimitrios-kanellopoulos In this case we cannot make that extrapolation, because Suunto app in smartphone will get information from 3 or 4 systems. We don’t know which satellites device use in certain activity. Unfortunately we cannot select on iOS or Android what system to be on/off.

[jthomi]

I also think watch looks better, you can see the track points, App has 2317 points and the watch 11684, guess that why its more accurate.

And I guess nobody here would make a problem out of it. I think even if watch looks better, they seem pretty similar, don’t they…

@dimitrios-kanellopoulos said in Connected GPS feature SF3/Galileo supported smartphones:

Watch looks better. At the moment Galileo from.my tests does not give more than 4% improvement. Tested on Android and the test gps apps that support Galileo.

[Dimitrios Kanellopoulos]

@luís-pinto said in Connected GPS feature SF3/Galileo supported smartphones:

@dimitrios-kanellopoulos In this case we cannot make that extrapolation, because Suunto app in smartphone will get information from 3 or 4 systems. We don’t know which satellites device use in certain activity. Unfortunately we cannot select on iOS or Android what system to be on/off.

Afaik they use the system service. I can ask for you.

[Luís Pinto]

@dimitrios-kanellopoulos If we can have access to information of native file maybe is possible to get that information (each satellite have one id). But in smartphones i really don’t know.

[jthomi]

@luís-pinto We should need the raw data then?

[Luís Pinto]

@jthomi i’m affraid yes.

[jthomi]

I think the target market for the SF3 will be fine with the accuracy of the tracking. If you look really closely to the two tracks, sometimes watch is better, and sometimes the app. And some parts of the route both are way off, guess the way the data is displayed on the maps is a source of error itself.