... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Issue with speeds in https://www.gpsvisualizer.com/
#1
I use the old but excellent Trekbuddy phone app for tracking, RouteConverter for editing the GPX files it produces, and https://www.gpsvisualizer.com/ for viewing.

Recently I've found that though the Trekbuddy GPX files are still fine, files that have been through RouteConverter are interpreted by GPS Visualizer as having insane speeds. I'm fairly sure that older versions of RouteConverter were ok.

I notice that within the Trekbuddy files speeds are as follows -
Code:
        <extensions>
          <nmea:course>8.1</nmea:course>
          <nmea:speed>17.4</nmea:speed>
        </extensions>

And RouteConverter changes them to -
Code:
                <extensions>
                    <nmea:course xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1">8.1</nmea:course>
                    <nmea:speed xmlns:nmea="http://trekbuddy.net/2009/01/gpx/nmea" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1">17.4</nmea:speed>
                </extensions>


I suspect that GPS Visualiser is attempting to interpret the URLs within the nmea extensions as speeds. So, is the issue here that RouteConverter is producing invalid XML/GPS data, or is GPS Visualizer incorrectly interpreting the data?

I'm using RouteConverter 2.31.2, and I'll attach an original and a converted GPX file.


Attached Files
.gpx   20220828-171522 routeconverter.gpx (Size: 277.88 KB / Downloads: 18)
.gpx   20220828-171522 Trekbuddy original.gpx (Size: 128.91 KB / Downloads: 20)
Reply
#2
Quick update: the author of https://www.gpsvisualizer.com/ has updated the service to cope with the extra data in the nmea extensions, and speed is now shown correctly.
Reply
#3
Hi sheepthief,

thank you for the quick update. So the problem is solved?
--
Christian
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)