Hi, Nathan Jones schrieb am 21.11.2011 20:12: > I'm not sure what you are saying the problem is. I think the graph is > wrong though - the straight line segment should have pace of zero.
No, the gap (where the straight line sits) must not exist at all. The straight line is also (wrongly) drawn to the maps. The problem is that in calculations which rely only on trackpoints any pauses are neglected. (BTW Same thing happens if device's autopause is active.) Calculations from laps info are fine of course. What I wanted to express is that in pytrainer's gpx all information *where* the pause happened is erased. As far as I understood non-connected parts of the way should be structured by the <trkseg> element. greetz Arnd ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
