Nathan Jones schrieb am 21.11.2011 20:12: > I'm not sure what you are saying the problem is.
me again ;) let me give you the part of pytrainer's gpx where the break happened: <trkseg> ... <trkpt lat="52.41535239" lon="12.56883723"> <ele>70.7941895</ele> <time>2011-11-20T12:02:21+01:00</time> </trkpt> <trkpt lat="52.43373617" lon="12.61950558"> <ele>29.4575195</ele> <time>2011-11-20T12:13:07+01:00</time> </trkpt> ... </trkseg> our logic cannot deduce from this that there is any pausing, or? Though this information exists when I either look to an gpsbabel import: <trkseg> ... <trkpt lat="52.415352389" lon="12.568837227"> <ele>70.794189</ele> <time>2011-11-20T11:02:21Z</time> </trkpt> </trkseg> <trkseg> <trkpt lat="52.433736166" lon="12.619505581"> <ele>29.457520</ele> <time>2011-11-20T11:13:07Z</time> </trkpt> ... </trkseg> or a garmintools dump: ... <point type="304" time="2011-11-20T12:02:21+01:00" lat="52.41535239" lon="12.56883723" alt="70.7941895" distance="698.061279"/> <point type="304" time="2011-11-20T12:02:22+01:00"/> <point type="304" time="2011-11-20T12:02:48+01:00"/> <point type="304" time="2011-11-20T12:13:02+01:00"/> <point type="304" time="2011-11-20T12:13:06+01:00"/> <point type="304" time="2011-11-20T12:13:07+01:00" lat="52.43373617" lon="12.61950558" alt="29.4575195" distance="698.061279"/> ... therefore I guess we just lost information. 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
