From: Gerhard Olsson <gerhard.nospam@gm...> - 2007-02-13 07:23:08
Thanks for a very useful application.
Time in tracklogs allows down to millisecond resolution.
However, GPSBabel seem to only write whole seconds.
(I write "seem" as I use xcsv<-> conversion, that may remove the precision.)
Can this be changed?
The reason to why I am asking is that a track can have trackpoints
quite close. I use it to "apply" splittimes on an existing track. The
speed noise get very high. 1 second resolution when there are
trackpoints every 4 second gives a very noisy speed.
I believe that using second resolution time in GPX only gives GPS
receivers a bad reputation because of this.
This question is possibly mostly interesting for fitness. I have seen
Robert stating that "GPSBabel is not in the fitness business", but I
really would like if GPSBabel supported a standardized extension for
GPS-Fitness with stuff like heart rate and cadence. Currently all
applications use their own way to represent the data. (Garmin
extensions as a basis?)
The sender address really contains .nospam.
From: Robert Lipe <robertlipe@gp...> - 2007-02-13 16:44:15
Gerhard Olsson wrote:
> Thanks for a very useful application.
> Time in tracklogs allows down to millisecond resolution.
> However, GPSBabel seem to only write whole seconds.
You're right. We could do better here. Internally we have a field for
1/100'ths of a second so we could do that pretty easily. Going to
milliseconds would require some internal shuffling.
> really would like if GPSBabel supported a standardized extension for
> GPS-Fitness with stuff like heart rate and cadence. Currently all
> applications use their own way to represent the data. (Garmin
> extensions as a basis?)
You've exactly hit the nail on the head. There are a few formats that
support HR and cadence (Garmin Training Center, some of our XCSV
formats, etc.) but none of them have individually gotten enough momentum
to justify the development.
Get latest updates about Open Source Projects, Conferences and News.