Hi Friso, > a few days ago I bought a Garmin Fortrex 401 + heart-rate sensor. > It does not record TCX-files but a GPX-version with an extension: > > <trkpt lat="47.864417" lon="8.214991"> > <ele>722.57</ele> > <time>2011-09-05T17:05:49Z</time> > <extensions> > <gpxtpx:TrackPointExtension> > <gpxtpx:hr>79</gpxtpx:hr> > </gpxtpx:TrackPointExtension> > </extensions> > </trkpt> > > > Fiddeling with the existing plugins of pytrainer does not result in a > proper import of the heart rate data. > > So my question is, what is the best way to implement support for this > file format? > > 1) hack some text replacement to convert into the pytrainer-format > (looks quite easy)
I see 2 different problems: 1.- It seems that you would replace (in some automated way) text on your box and then trying to import output file. Alhough it may be quickest approach, then only you can benefit for it. 2.- I am not sure trying to import GPX+ (pytrainer format) file would work directly because as no device outputs this format, there is no filter for it. > 2) Start a new plugin similar to TCX with XSLT (quite sophisticated, but > no XSLT experience so far) >From my point of view this one would be the best approach and also XSLT is not that difficult, give it a try! Keep in mind that this option allows you to launch a complete automated process (see unified import) or at least with minimal human interaction. In addition, others can benefit from it. > 3) Use gpsbabel if possible. Not a bad idea (is it garmin logbook format, right? http://www.gpsbabel.org/htmldoc-development/fmt_glogbook.html), but might be a little bit oversized for your purpose. Anyway GPSBabel integration might be reviewed at certain point. > May be there exist some prior work for this, too. Actually yes: on November last year a person who owns a Garmin Oregon 400 sent me a patch to import heartrate data correctly among other fixes. The problem with that patch was that changes were made in gpx.py file (basically looking for another hr tag if main one were not found). Initially I discarded making such change because I didn't like the idea to introduce "small workarounds" in gpx.py file: we were aware of one small "deviation" but if more showed up then parsing xml files would turn gpx.py into a mess (which currently is, but this a different story). Moreover I would need to check if there is any side effect on unified import. > cheers, > friso > > > p.s.: How many file formats has garmin invented for the same thing? There is another one (Garmin Edge 500): FIT (http://thisisant.com/pages/ant/fit-license) Regards, David ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
