Christian PERRIER schrieb am 22.11.2011 07:06: > I confirm this. When I switched from the Garmin Training Center > software (on Windows) to pytrainer, I was "surprised" by this. [...]
Thx Christian for your explanation (maybe somewhat clearer than mine ;) I tried to look a bit deeper into our code: When using garmintools the gpx+ file is produced within 'import/file_garmintools.py': By using the XSL transformation 'translate_garmintools.xsl' the original garmintools-(dump)-XML is mapped to pytrainer's gpx+. Here line 29 is the place where always one (and only one) surrounding <trkseg> is created. Line 32 shows how "empty" trkpts are ruled out, but these are _exactly_ those denoting end & start of tracksegments. See [1] >From now on this information is gone :( Well, I'm sure XSL can be improved, but... I haven't found any <trkseg> processing afterwards so far. So probably one had to extend the mapping (Google, OSM), the data for graphing and maybe also some statistics & summary stuff. Or rewrite (?) cu Arnd [1] http://www.garmin.com/support/pdf/IOSDK.zip page 44, end of section 7.4.26 D304_Trk_Point_Type ------------------------------------------------------------------------------ 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
