Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[2.19] GPX does not save speed information
#1
In Routeconverter 2.19, the speed information is removed from the GPX file on save. You can see this happen immediately after save the speed column in the position list is emptied.

It is also in the output GPX files.

My input file start with

Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<gpx creator="Mobile Action http://www.mobileaction.com/1.1" version="1.0" xmlns="http://www.topografix.com/GPX/1/0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd">
<trk>
<name>20170210-203645(1)</name>
<desc>Color:004000ff</desc>
<trkseg>
<trkpt lat="51.324043" lon="5.992455">
<ele>39.570000</ele>
<time>2016-09-17T14:25:04Z</time>
<speed>6.75</speed>
</trkpt>
<trkpt lat="51.324047" lon="5.992549">
<ele>39.529999</ele>
<time>2016-09-17T14:25:05Z</time>
<speed>6.85</speed>
</trkpt>
<trkpt lat="51.324001" lon="5.992729">
<ele>38.469997</ele>
<time>2016-09-17T14:25:07Z</time>
<speed>6.88</speed>
</trkpt>
<trkpt lat="51.323956" lon="5.992913">
<ele>37.090000</ele>
<time>2016-09-17T14:25:09Z</time>
<speed>7.02</speed>
</trkpt>
<trkpt lat="51.323914" lon="5.993102">
<ele>36.419998</ele>
<time>2016-09-17T14:25:11Z</time>
<speed>7.02</speed>
</trkpt>
<trkpt lat="51.323879" lon="5.993301">
<ele>36.230000</ele>
<time>2016-09-17T14:25:13Z</time>
<speed>6.50</speed>
</trkpt>

When it gets saved, it looks like this. All <speed> tags are gone and this is the output:
Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.topografix.com/GPX/1/1" xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v1" xmlns:gpxtrx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v2" version="1.1" creator="Generated by Christian Pesch's RouteConverter. See http://www.routeconverter.com">
   <trk>
       <name>20170210-203645(1)</name>
       <desc>Color:004000ff</desc>
       <trkseg>
           <trkpt lat="51.324043" lon="5.992455">
               <ele>39.6</ele>
               <time>2016-09-17T14:25:04.000Z</time>
               <name>Position 1</name>
           </trkpt>
           <trkpt lat="51.324047" lon="5.992549">
               <ele>39.5</ele>
               <time>2016-09-17T14:25:05.000Z</time>
               <name>Position 2</name>
           </trkpt>
           <trkpt lat="51.324001" lon="5.992729">
               <ele>38.5</ele>
               <time>2016-09-17T14:25:07.000Z</time>
               <name>Position 3</name>
           </trkpt>
           <trkpt lat="51.323956" lon="5.992913">
               <ele>37.1</ele>
               <time>2016-09-17T14:25:09.000Z</time>
               <name>Position 4</name>
           </trkpt>
           <trkpt lat="51.323914" lon="5.993102">
               <ele>36.4</ele>
               <time>2016-09-17T14:25:11.000Z</time>
               <name>Position 5</name>
           </trkpt>
           <trkpt lat="51.323879" lon="5.993301">
               <ele>36.2</ele>
               <time>2016-09-17T14:25:13.000Z</time>
               <name>Position 6</name>
           </trkpt>

I also notice that the <ele> gets rounded to one decimal. While this is not a big deal, I think it is bad form to change the contents of tags without reason or warning.
Reply
#2
(10.02.2017, 21:30)Maarten Wrote: In Routeconverter 2.19, the speed information is removed from the GPX file on save.

I cannot reproduce this with the information you've provided.

(10.02.2017, 21:30)Maarten Wrote: You can see this happen immediately after save the speed column in the position list is emptied.

Did you fiddle around with the hidden options?

(10.02.2017, 21:30)Maarten Wrote: I also notice that the <ele> gets rounded to one decimal. While this is not a big deal, I think it is bad form to change the contents of tags without reason or warning.

You're right but given the accuracy of elevation/GPS information and complaints of users about bloating files, I've reduced accuracy when writing to reasonable values. You might want to change this with the hidden options.
--
Christian
Reply
#3
I assume these hidden options are hidden? I am not aware of them or know how to access them and I have not changed any settings right before or after installing 2.19. When I start routeconverter 2.18.2, it still saves the speed info and I get output like this:


Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.topografix.com/GPX/1/1" xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v1" xmlns:gpxtrx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v2" version="1.1" creator="Generated by Christian Pesch's RouteConverter. See http://www.routeconverter.com">
   <trk>
       <name>20170210-203645(1)</name>
       <desc>Color:004000ff</desc>
       <trkseg>
           <trkpt lat="51.324043" lon="5.992455">
               <ele>39.6</ele>
               <time>2016-09-17T14:25:04.000Z</time>
               <name>Position 1</name>
               <extensions>
                   <nmea:speed>6.75</nmea:speed>
               </extensions>
           </trkpt>
           <trkpt lat="51.324047" lon="5.992549">
               <ele>39.5</ele>
               <time>2016-09-17T14:25:05.000Z</time>
               <name>Position 2</name>
               <extensions>
                   <nmea:speed>6.85</nmea:speed>
               </extensions>
           </trkpt>

FYI: this is the Windows build, I'm using windows 7 x64.
Reply
#4
I did some further testing and am sure that something changed in the save algorithm.

There are two specs for GPX: 1.0 and 1.1. Routeconverter can save to either of them. With version 2.18.2, saving to either GPX 1.0 or GPX 1.1 results in the same: speed gets saved as in my last example, with a <nmea:speed> tag between <extentions> tags:

Code:
               <extensions>
                   <nmea:speed>6.75</nmea:speed>
               </extensions>

With version 2.19, speed gets saved in the 1.0 GPX as a regular <speed> tag without use of <extensions>:
Code:
<speed>6.75</speed>

But it does not get saved in the GPX 1.1.

This behaviour seems correct as the GPX 1.1 spec does not specify speed anymore (IMHO a stupid decision). So 2.19 now apparently uses the GPX 1.1 spec when yo usave to GPX 1.1.
In 2.18.2, saving to either GPX 1.0 or 1.1 gives the header for GPX 1.1:
Code:
<gpx xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.topografix.com/GPX/1/1" xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v1" xmlns:gpxtrx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v2" version="1.1" creator="Generated by Christian Pesch's RouteConverter. See http://www.routeconverter.com">

While saving in 2.19, saving to GPX 1.0 now gives a different header.

I guess I'll be saving to GPX 1.0 then. Speed information for me is very important.
Reply
#5
Forgot to attach the file and the file saved with RouteConverter


Attached Files
.zip   files.zip (Size: 1.1 KB / Downloads: 58)
--
Christian
Reply
#6
(12.02.2017, 15:11)Maarten Wrote: But it does not get saved in the GPX 1.1.

This behaviour seems correct as the GPX 1.1 spec does not specify speed anymore (IMHO a stupid decision).

Sigh. You're right.

I just found that between 2.18 und 2.19 I've added support for reading and writing temperature via the Garmin Trackpoint extensions for GPX 1.1. And this has an unwanted influence on writing speed :-(
--
Christian
Reply
#7
So, I'm hoping you see this as a bug? Cool  I would like it a lot if you would save speed information in GPX 1.1 too.
Reply
#8
(12.02.2017, 21:36)Maarten Wrote: So, I'm hoping you see this as a bug? Cool  I would like it a lot if you would save speed information in GPX 1.1 too.

Dear Maarten,

it took a while to figure out what was the problem. I think I've fixed it. Please try the latest prerelease which I've just uploaded.
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)