On Tue, Jan 08, 2019 at 07:01:52PM +0000, Robert Norris wrote: > > Basically ATM Viking does not support newer tags in the GPX 1.1 standard, > especially for the Extension style ones. > > See: https://sourceforge.net/p/viking/feature-requests/96/ > > It would be nice to support the common speed, cadence, heart rate data, > temperature but as yet no one has done it.
Well ordinary <speed> is supported, of course: as in examining the properties of a track, and plotting speed/time. Which is where I discovered the problem. A quick fix might be to just to allow both <speed>...</speed> and <gpxtpx:speed>...</gpxtpx:speed> in the hardcoded tags. That would fix the existing problem. As for extending Viking to do something useful with cadence etc., that obviously depends on someone offering to do the work. > So some open questions are: > 1. When saving to a GPX file do you: > a) If from a existing GPX file save in whatever version it was based on? > and/or for any thing: > b) Ask which version to save in each time? > c) Default to 1.0 or 1.1 as set in may be in the advanced options somewhere. I would choose a) with maybe a preference setting to support c) as well. > > 2. Do you want to try to do something useful with this extra HR, cadence data > etc... when reading in a file. > a) Extend the track point dialogs to show it somehow > and/or > b) Have some useful graphs of this data. [Obviously even more coding work > required]. I personally don't have any interest in those tags, at the moment. My message was really about what seemed to be something like a bug/deficiency in the current version. Thanks for the reply, ael _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
