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.

I did start on using GPX 1.1 but only got as far as supporting the 
'DisplayColor' extension.

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.

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].

--
Be Seeing You - Rob.
If at first you don't succeed,
then skydiving isn't for you.

________________________________________
From: ael via Viking-devel <viking-devel@lists.sourceforge.net>
Sent: 08 January 2019 18:16
To: viking-devel@lists.sourceforge.net
Subject: Re: [Viking-devel] GPX 1.1 and <speed> tags

On Mon, Jan 07, 2019 at 11:07:42PM +0000, ael via Viking-devel wrote:
>
> Loading a gpx 1.1 track file containing speeds
> using this sort of tagging:
>
> <gpxtpx:TrackPointExtension>
>             <gpxtpx:speed>5.051840</gpxtpx:speed>
>
> viking failed to recognise the values. The gpx file passed the xerces
> validation test, so it is well formed and matches the schema.

After a little more investigation, I find that these extensions are
defined in
https://www8.garmin.com/xmlschemas/TrackPointExtensionv2.xsd
as an extension using
http://www.topografix.com/GPX/1/1/gpx.xsd

Viking seems to know about <speed> which is not surprisng since it is in
version 1.0 of the gpx.xsd. I don't know enough about this area to know
whether it should fetch and parse

https://www8.garmin.com/xmlschemas/TrackPointExtensionv2.xsd

each time it sees such extensions which sounds expensive, or have have
common extended tags built in. Perhaps there are other extended tags
for speed other than Garmin's? Also in the Garmin xsd  are extensions for
course and bearing: I am not sure whether those are relevant for Viking.

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/


_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Reply via email to