GPXLab
GPXLab copied to clipboard
BourgeoisLab
Add the effective time on the statistic of a track
The app I use on my mobile phone (A-GPS Tracker) has a couple more values in the statistic of the track to show the time you effectively walked/run (or anyway moved, so it exclude the time you wait at a closed rail crossing, for example) and use this value to calculate the average speed and so on.
It would be nice to add this values also to the statistic of GPXLab, eventually with the two set of values, the total one and the "real" one, with both average speed, min/km and so on.
Would it be possible ?
I am not actively working on this project anymore. So I probably won't implement it.
But you should at least provide an example gpx file.
Fair enough.
Here a file that has a closed rail crossing wait.
Where is the "pause" Time about 21 minutes in Distance about 1.791 Km (from the track)
I can't see any second time information from the file you provided. This information must be stored elsewhere.
It is not a real pause, is just that I was stopped at a rail crossing. But while looking for it, I find out that probably it's not going to be easy. I try to explain.
A-GPS Tracker store a point every 3/4 seconds or 5 meters and calculate the two times (total and walking time) when it compute the statistics for the track.
Looking at the track, you will find that between the 286th end 287th pointas there is a elapsed time of about 1:20 minutes, which is the time I was stopped. The same between the 725th and the 726th points, which have an elapsed time of about 1 minutes.
What I was trying is to remove are these two breaks from the total time, like A-GPS Tracker. but now I suppose that it will end to be specific to the tracker I was using on the phone, which is not a good idea, since other tracker can do something else.
At this point, I see two options: close the issue as not doable (feel free to do it BTW), or change the computation of the statistics taking into account the GPS tracker used to create the track file.
I see. Option 3 would be a configurable time. If there is no or little movement during this time, then it is remove from the alternative calculation. I guess all GPS trackers will do it more or less the same. So no need to be tracker specific.