-
Notifications
You must be signed in to change notification settings - Fork 23
Fix distance problem when data are not sorted by date #5
Conversation
…jacent entries of GPS data array
Thanks for looking into it and fixing it, that looks good! Would you be able to post the HiTrack file that caused problems? I haven't had a proper chance to look into your code yet (and won't until Thursday) but is there any reason you have decided to do that filtering of lost GPS points by default rather than keep it as an optional flag at the command line? |
For the filtering, there is no major reason, it's just that I don't understand how a lost GPS point can be useful in distance computation. For me, without any options, we must obtain the best result, maybe filtering can be set on by default and an option can still be available to disable it. |
That makes a lot of sense, thank you for your contribution! I've accepted your first commit with no changes, but I'd like to keep all of the filtering within the |
Yes, it's a pretty good one. Thanks |
I have a HiTrack file that I took from a backup of my Honor Watch Magic, I converted it with your tool and used gpsvisualizer.com Looks like there are some gaps come up when I import it. Might be just the way this website displays it though. |
I used http://www.gpsvisualizer.com/convert_input?convert_format=gpx to convert the tcx successfully to GPX and there is an advanced option on this page to "connect segments". I then imported the GPX into my maps on google maps and was able to view with a continuous line. |
Hi sir, im having issue running the latest version 2.3... im still using the old version with -v -b arguments... it is working with me but not the newest version 2.3... here are my batch file and error result... and how to use XML validation... i have internet and i already downloaded the XSD file... but still nothing... then how to use PIP INSTALL XMLSCHEMAS... thanks... batch file@echo off error outputInfo - External library xmlschema could not be imported. |
I created a new bug #36 for your last report, see also comments over there. |
First, thank you very much for this project.
I encountered a problem of distance calculation with data comming from my watch Huawei Pro Band 3, distance was too big for being a normal run (36 millions of meters 😄 ).
Problem comes from GPS data in anarchic order.
The first commit just add a sort on GPS data for fixing this problem.
The second commit is more a cosmetic one, I added some variables in process_gps for clearness. Special GPS lost points (90, -80) are now always ignore, so distance computation isn't wrong anymore when one of these points is part of data