Bugs in loading GPX file

[MoonBear]

Hi Christian,

Thanks for creating such a handy tool for us. It has quickly become one of my favorite programs when it comes to route review after my trips.

However, I've noticed that RC doesn't load all GPX files correctly. In the attached archive you can find two gpx files saved from Prune (http://activityworkshop.net/software/prune/). There seems to be nothing wrong with the syntax. They are also loaded in Google Earth correctly.

Please take a closer look and let me know if you need more samples. Thanks!

*Before I found your tool, I used Prune to remove "errors", join two or more tracks, and save them.

[routeconverter]

Thanks for creating such a handy tool for us. It has quickly become one of my favorite programs when it comes to route review after my trips.

Hi MoonBear,

I'm happy to hear that.

However, I've noticed that RC doesn't load all GPX files correctly. In the attached archive you can find two gpx files saved from Prune (http://activityworkshop.net/software/prune/). There seems to be nothing wrong with the syntax.

Actually both files are well-formed but do not validate against the GPX schema

BlueMountain Ski 01.gpx declares a GPX 1.0 namespace but states it's a GPX 1.1 file which is forbidden by the XML schema for GPX:

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" creator="Prune v6 activityworkshop.net"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.topografix.com/GPX/1/0" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd">

The other file, Disney World Trip Day 4 - Epcot Center.gpx, has no namespace declaration at all:

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" creator="Prune v5 activityworkshop.net">

If you fix the XML errors, the files load fine. How about notifying the Prune authors to fix their bugs?

They are also loaded in Google Earth correctly.

They have a very relaxed XML parser.

[MoonBear]

Hi Christian,

Thank you so much for the quick response. It looks like the bugs came from earlier versions of Prune (06), meanwhile Prune has fixed this problem in its latest version (Prune08).


MoonBear