This object is in archive!
Wrong altitude in chart
Solved
Hi!
I discovered a bug in Locus. I`m not sure if the problem has already been reported, but I haven`t found it yet.
However the problem is that the chart doesn`t show the right altitude of tracks. I use the app BROUTER and the altitude data aren`t correctly displayed. For example my track has a maximum altitude of 953m, but the chart scale for altitude goes only from ca. 923m to 935m. This problem is not only by tracks from BROUTER it`s also by recorded tracks.
Devices: SGS Advanced and Samsung Galaxy Y (both Android 2.3.6)
I hope you can clear this bug, because the chart is very useful for biking.
Kilian
The same problem 
Hello Kilian,
first question - you wrote that "my track has a maximum altitude of 953m" - how you know that? You are sure that altitude that Locus display is not correct?
Also are you using "Altitude offset" in "Altitude manager" to modify recorded altitudes? http://support.locusmap.eu/hc/en-us/a...
Hello Kilian,
first question - you wrote that "my track has a maximum altitude of 953m" - how you know that? You are sure that altitude that Locus display is not correct?
Also are you using "Altitude offset" in "Altitude manager" to modify recorded altitudes? http://support.locusmap.eu/hc/en-us/a...
Yes , I`m sure that it is right.
I have another example with screenshots.
I have a route which is generated by BROUTER with the trekking-profile.
from: N 46°49.830 E 007°29.695
to: N 46°49.496 E 007°29.385
This is the gpx:
<!-- track-length = 950 filtered ascend = 107 plain-ascend = 107 cost=1104 -->
brouter_trekking_0
645.25
645.25
644.75
647.0
648.0
648.75
649.25
650.75
652.0
653.0
655.0
656.75
658.75
660.0
661.5
662.25
662.75
663.25
664.0
665.5
666.5
669.25
670.5
674.25
677.5
684.0
689.0
691.25
695.75
697.75
701.0
704.0
707.25
711.25
714.75
716.75
718.5
720.75
720.75
721.25
721.75
724.25
726.75
728.25
730.5
733.25
737.25
742.75
745.75
749.75
751.25
749.25
750.25
752.25
753.0
753.0
And I don` use the function of the altitude manager.
Kilian
Yes , I`m sure that it is right.
I have another example with screenshots.
I have a route which is generated by BROUTER with the trekking-profile.
from: N 46°49.830 E 007°29.695
to: N 46°49.496 E 007°29.385
This is the gpx:
<!-- track-length = 950 filtered ascend = 107 plain-ascend = 107 cost=1104 -->
brouter_trekking_0
645.25
645.25
644.75
647.0
648.0
648.75
649.25
650.75
652.0
653.0
655.0
656.75
658.75
660.0
661.5
662.25
662.75
663.25
664.0
665.5
666.5
669.25
670.5
674.25
677.5
684.0
689.0
691.25
695.75
697.75
701.0
704.0
707.25
711.25
714.75
716.75
718.5
720.75
720.75
721.25
721.75
724.25
726.75
728.25
730.5
733.25
737.25
742.75
745.75
749.75
751.25
749.25
750.25
752.25
753.0
753.0
And I don` use the function of the altitude manager.
Kilian
Hello Killian,
you are right. I found quite serious issue in my system for smoothing charts. Problem will be solved in next (probably tomorrow) versions. Thank you for your report, I hope it will work fine now.
Hello Killian,
you are right. I found quite serious issue in my system for smoothing charts. Problem will be solved in next (probably tomorrow) versions. Thank you for your report, I hope it will work fine now.
Replies have been locked on this page!