Track length accuracy

[routeconverter]

My problem is:
-distances calculated by me with various methods ARE DIFFERENT from the distances shown by RouteConverter in the PositionList.

I guess that's normal when two implementations differ. They use different constants, algorithms, rounding accuracies.

In the cosine and haversine formulas, I use the earth radius for Romania, and I add also the elevation difference to the length distance calculations.
I do something wrong, I miss something or this is some "glitch" on RouteConverter?

I don't know. My algorithm is based on an algorithm from the Unidata Development Team. Start at BaseRoute#getDistance(int startIndex, int endIndex) to find it in the code base.

If the RouteConverter formulas are proven accurate, can you manage to be copied to clipboard all the enabled columns in the PositionList ?

I'm using the Navigating POI-Warner (.asc) when copying positions to the clipboard. Since a long time, I have a generic CSV format on my todo list that could include the distance and make the export via clipboard- and Excel-interaction easier.

Can the accuracy of calculations be verified somehow?

Certainly, but I don't know of any reference algorithm. Did you find some reference values or algorithms?

Also the autocomplete elevation on new/modified points should be very useful. Or some pop-up asking on save?

I prefer to leave this step to the user since completing the elevation might be very time consuming. There is a proposal in the forum to make completing the GPS data easier.

For example, 2 road tracks(different directions), with total length calculated by 3 programs:
RouteConverter EasyGPS MyProgram (R=6378137m)(should be smaller since Romania is not at Ecuator)
a) 642151m 642377.96m 641999.9m
b) 637646m 637746.13m 637418.8m
226.96m -151.1m
100.13m -227.2m
What (I do)/(is) wrong?

I don't know but I'm glad to see that RouteConverter calculates distances in the middle between EasyGPS and your program. The error is below 0,035% and so far that accuracy was enough for the users.

I can't give results with +/- 100m (every meter of a road cost about 1000$)

And then you're satisified with RouteConverter's results if put into the clipboard