<![CDATA[V5.1.0 - 462 New altitude/heading shows incorrect Data]]>In version 5.1.0 build 462 the new altitude/heading circular indicator appears horizontally mirrored.
Examples:
riding west lights the east/right segment
riding northwest lights the northeast segment
North and south appear correct, suggesting the widget mirrors east/west directions instead of having a 180° offset.
The issue is independent of map orientation mode (North up / Dynamic / 3D).

]]>https://forum.myrouteapp.com/topic/11003/v5.1.0-462-new-altitude-heading-shows-incorrect-dataRSS for NodeMon, 25 May 2026 13:09:49 GMTMon, 25 May 2026 11:17:01 GMT60<![CDATA[Reply to V5.1.0 - 462 New altitude/heading shows incorrect Data on Mon, 25 May 2026 12:55:33 GMT]]>I did a little experiment with this. My house is just below a 50m contour line. My phone using MRA gives 341ft or 104M.

07e9184a-8270-474f-8212-54e40340381b-image.jpeg

Same with OSMand.

47c284ca-5f1a-4fb9-955f-ba021c3bf3af-image.jpeg

In OSMand you can download a correction file "World Altitude Correction"

4682ebb0-0a34-4b12-a684-e27bdbb84ca5-image.jpeg

This puts me at 157ft or 48M which would be within + or - 3m of my actual elevation.

324154c7-789f-4c80-bfc7-96f5fb80e52d-image.jpeg

Might be worth building in the correction file somewhere?

]]>https://forum.myrouteapp.com/post/78073https://forum.myrouteapp.com/post/78073Mon, 25 May 2026 12:55:33 GMT<![CDATA[Reply to V5.1.0 - 462 New altitude/heading shows incorrect Data on Mon, 25 May 2026 11:52:26 GMT]]>Oh and strangely it can be accurate at higher elevations. I was using MRA on a trip on Saturday crossing a pass at 448m and it was reading 447M passing the datum point??

]]>https://forum.myrouteapp.com/post/78062https://forum.myrouteapp.com/post/78062Mon, 25 May 2026 11:52:26 GMT<![CDATA[Reply to V5.1.0 - 462 New altitude/heading shows incorrect Data on Mon, 25 May 2026 11:45:41 GMT]]>Standard GPS satellites don’t track your height from the actual ground (valleys, mountains). They measure your distance from a theoretical, mathematical model of the Earth called an ellipsoid. Your phone then has to translate that to "Mean Sea Level" using a gravity model, which can easily throw off calculations by hundreds of feet. In short your phone is not that accurate on the vertical plane. Even specific GPS devices such as Garmin are only accurate to +/- 30m unless they also take data from a topographic database which triangulates horizontal position with a topographical datum. My phone is a 60m out using MRA or OSMand (reading high) and my Zumo XT usually under or over reads by 20-30m

]]>https://forum.myrouteapp.com/post/78061https://forum.myrouteapp.com/post/78061Mon, 25 May 2026 11:45:41 GMT<![CDATA[Reply to V5.1.0 - 462 New altitude/heading shows incorrect Data on Mon, 25 May 2026 11:25:29 GMT]]>Note: The displayed altitude is approximately 50 meters too high. Sometimes only 45 meters.

]]>https://forum.myrouteapp.com/post/78055https://forum.myrouteapp.com/post/78055Mon, 25 May 2026 11:25:29 GMT<![CDATA[Reply to V5.1.0 - 462 New altitude/heading shows incorrect Data on Mon, 25 May 2026 11:24:55 GMT]]>Note: The displayed altitude is approximately 50 meters too high. Sometimes only 45 meters.

]]>https://forum.myrouteapp.com/post/78054https://forum.myrouteapp.com/post/78054Mon, 25 May 2026 11:24:55 GMT