Hi Arnd,
2011/11/26 Arnd Zapletal <a.zaple...@gmail.com>
> Hi skew41,
>
> skew 41 schrieb am 26.11.2011 17:30:
>
> > When importing from my Garmin Forerunner 305, the .dump files under
> > ~/.pytrainer/tmp/2011/11 do not contain anymore the <track> section, but
> > only one for <run> and another for <lap>. Also the corresponding .gmn
> file
> > is much smaller in size than others usually.
> >
> > Interestingly, if I run
> >
> > $ garmin_save_runs
> >
> > manually, I obtain .gmn files of normal size (I guess they include the
> GPS
> > information).
>
>
> well, <track> alone isn't of too much interest, it doesn't contain a lot
> of information e.g.
> <track type="311" index="0"/>
>
> but do you also miss all the
> <point type=" ... />
> afterwards?
>
Yes, it does contain many <point ...> entries afterwards.
> Did you try to manually 'garmin_dump' one of your .gmn files and then
> compare to those living in ~/.pytrainer/tmp/...
>
When I take the .gmn file from my manual garmin_save_runs export and
compare it with the .dump files in ~/.pytrainer/tmp/..., then the
difference consists exactly in the <track ...> and <point...> entries.
I guess the .dump files under ~/.pytrainer/tmp/... are generated from the
.gmn files using garmin_dump during the import.
Are the .gmn files there results of running garmin_save_runs? If so, what
is the exact call of this command?
Best regards,
skew41
------------------------------------------------------------------------------
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
