This object is in archive!
Difference in Altitude recording and dashboard
Answered
I use locus pro during mountain bike tours and noticed a difference in altitude recording and dashboard.
Today the dashboard shows 1020 meters in total climbing, whereas the stored track shows 798 meters in total climbing. Is there anything I do wrong? My feeling says that the stored climbing is correct.
I use an Sony xperia active mobile with barometric sensor. The sensor works well.
Locus is adjusted as follows:
- No altitude correction
- Barometric sensor on
- no optimization of GPS altitude data
- weak altitude filter
- no offset correction
- automatic pressure calibration
Thanks for your support
The same question
Hello Uwe,
what you see is not a perfect solution for now, because as you see, it's little bit confusing. Anyway reason for this is:
1. elevation on track that is currently recorded, is simple sum from all measure altitudes
2. elevation you see when track is already stored is firstly optimized (removed biggest noises) and then computed sum as in first step.
So result is, that second value is usually a lot closer to real values and value is also a little smaller.
Problem is that optimization is done on all points at once and it's compute also take some time. And instead of doing it after every new recorded points, Locus do it just once when track is stored/loaded etc.
Hope this helps you.
Just for your information. In database is still stored original measured elevation values. So when you export track from Locus, you get original values, not the one optimized and visible in track details (when track is already stored in folder)
Hello Uwe,
what you see is not a perfect solution for now, because as you see, it's little bit confusing. Anyway reason for this is:
1. elevation on track that is currently recorded, is simple sum from all measure altitudes
2. elevation you see when track is already stored is firstly optimized (removed biggest noises) and then computed sum as in first step.
So result is, that second value is usually a lot closer to real values and value is also a little smaller.
Problem is that optimization is done on all points at once and it's compute also take some time. And instead of doing it after every new recorded points, Locus do it just once when track is stored/loaded etc.
Hope this helps you.
Just for your information. In database is still stored original measured elevation values. So when you export track from Locus, you get original values, not the one optimized and visible in track details (when track is already stored in folder)
Thank you for your fast answer!
I can live with that for the sum of climbing is only of interest after riding. May be that someone is riding MTB because of reaching a certain amount of climbing. Not me :-)
Furthermore I noticed that the deviation is about plus 20 percent and so I can calculate from dashboard what is really made.
Thank you for your fast answer!
I can live with that for the sum of climbing is only of interest after riding. May be that someone is riding MTB because of reaching a certain amount of climbing. Not me :-)
Furthermore I noticed that the deviation is about plus 20 percent and so I can calculate from dashboard what is really made.
20%, hmm it also depend on terrain and quality of GPS. I believe that when will be some time, I'll make some better algorithm, that will optmize also currently recorded track, but for now ...
20%, hmm it also depend on terrain and quality of GPS. I believe that when will be some time, I'll make some better algorithm, that will optmize also currently recorded track, but for now ...
The stored sum of climbing is quite near the result shown by my very old cat eye cc at 100 which is barometrically only.
The stored sum of climbing is quite near the result shown by my very old cat eye cc at 100 which is barometrically only.
My hike yesterday of only 3.5 miles had a difference of just over 800 feet between the uphill elevation gain on the dashboard vs the final uphill elevation gain of the ended track. I was hoping to use this data during our hikes, but this is too great a distance error to be usable (for me). Looking forward to the better algorithm!
My hike yesterday of only 3.5 miles had a difference of just over 800 feet between the uphill elevation gain on the dashboard vs the final uphill elevation gain of the ended track. I was hoping to use this data during our hikes, but this is too great a distance error to be usable (for me). Looking forward to the better algorithm!
Hi guys,
I've just added small filter to altitude statistics during track recording. So it should be applied for recorded tracks only. Tracks stored in database use own, more complicated filtering system.
Anyway during my short tests, it show that recorded values are now a lot closer to values filtered in stored tracks, then before (in current public version).
So try it in next version, but I believe it will be a lot better.
Hi guys,
I've just added small filter to altitude statistics during track recording. So it should be applied for recorded tracks only. Tracks stored in database use own, more complicated filtering system.
Anyway during my short tests, it show that recorded values are now a lot closer to values filtered in stored tracks, then before (in current public version).
So try it in next version, but I believe it will be a lot better.
Awesome! Looking forward to it. Thanks for such a great app!
Awesome! Looking forward to it. Thanks for such a great app!
Replies have been locked on this page!