The orange value in the upper left corner is the distance from the route. This means that not only distances from points but also distances from line segments are computed. Since exact calculation would take too long, we used an approximation algorithm that is correct only for distances < 25 km. Therefore the difference.
To solve this problem in the future, we will add an algorithm for distances > 25 km in the next release.
In navigation , in case far distances , in exemple France to Florida :
- GoogleEarth : 7671 km
- Run Gps Distance : 7655 km
- Run GPS navigation on upper left corner in orange : 16464640 m !!!
Is this a bug ?
I see. Of course I did not think of that.
Taking this into account makes it a simple issue which is actually hard to solve :-)
The only real solution I guess would be analyzing the route to see if it is circular and if so make the starting and the ending point the real starting point. but that would be overkill for such a little issue.
The intention of this is to allow the user to start at any section of a route. So, for instance, if you have a 10 km run, you could start at kilometer 9 and still be guided by Run.GPS navigation on the last kilometer. Maybe we'll implement a rule saying that it's allowed to enter at any point for the first 2/3 of the entire route distance.
I like the new more diverse navigation instructions in 2.2.5 build 1015.
I have just one issue with it. At least for me it's new since this version.
Most of my routes are circular. Whenever I now start navigating pretty much the first thing I hear is destination reached. Not exactly a big issue of course but could you possibly build something in like: Destination reached but traveling time is faster then the speed of light let's not say 'destination reached' just yet? :-)