explanation & KML fix for unrealistic track lengths

[tempg...@gmail.com]

Hi folks,

I put together this very detailed page to describe the issues I'm having with bogus track lengths:

https://jagbev.ca/_temp/gpse/err.html

It's safe - it's on my server, handcoded HTML, no javascript, etc.

I also mention a few other problems. All of these are minor (to me) and I can work around them. I hope the explanation and examples will help you understand why you're getting bogus track lengths, and it shows you how you can fix them by editing the KML file.

Note that you should have some experience editing HTML/XML/KML files with a text editor before tackling this. Make a copy of your KML file first!

Michael has referred to Android 10's permission model as a possible cause of the problem, but my device still has only Android 7, and the problem started about 2 months ago. When I view "Permissions" for GPSE, I only see Camera, Location, & Storage with a on/off button beside each one. They are all "on". I don't see anything about background permissions.

Although (0,0) is a valid location, it's not likely that any of "us" are going to be travelling in that area - it's 400 km from land. Perhaps a quick fix is an option to "skip (0,0) points" for us landlubbers.

jag