Importing GPX file

The file you posted is invalid (you can check with http://www.validome.org/xml/ or any XML validator).

I fixed it by re-writing it in GPS Babel and fixing the version (there is no 1.1.4 version of GPX to my knowledge, I changed it to 1.1, the official current version, see http://www.topografix.com/gpx.asp).

The file I attached will hopefully work for you, it does import for me with VIRB Edit 2.8.

Ok.

Dashware, RaceRender, Google Maps and Google Earth all loaded it just fine in it's original version. I guess this free software is very touchy.

We get what we pay for.

Falagar,

From the looks of it YKnot880's file was from a Cateye Stealth 50. I am receiving the same error ("The GPS or FIT file selected has no valid GPS logs, or the GPS logs in the file have no timestamps.") as he did. Can either tell me how to rewrite it myself, direct me somewhere that will tell me, or make it so that VIRB Edit auto recognizes files from Cateye Stealth 50.

Keep up the good coding. Thanks in advance for the rapid response!

I used http://www.gpsbabel.org/ and "converted" the file from gpx to gpx to fix the invalid tags. I then had to use a text editor (Notepad will work) and changed the version from 1.1.4 to 1.1.

You might be able to avoid the last step if you e.g. convert from gpx to gdb, and then from gdb to gpx. (So that the version gets correctly written.)

We are looking into reading such invalid files, we are however a bit hesitant because there is an official standard that we would like to follow. But it seems like that battle has been lost, with lots of software not validating their gpx, or (worse) writing invalid files like the one you are looking at.

FLAGAR,

Before answering this thread, you should do a little bit of real homework. The tool you used, http://www.gpsbabel.org/, says that the file is not valid because it lists version 1.1.4 instead of 1.1.

If you actually take a minute to look at the file, you'll see that the 1.1.4 is the version of software used to create the .gpx - not the .gpx version as you insist on saying. Everything beyond that is nonsense, since you don't even know what the first line of the file says.

My file was able to load into EVERY other piece of software & web site that reads .gpx files.

If you're going to be in this business, then you really need to learn more about it.

And if it is the version of the gpx schema that is required and not that of the software?

http://www.topografix.com/GPX/1/1/gpx.xsd

The version tag specifies the version of gpx, not the version of the software. It should be 1.1, any other value makes the file invalid.

My final thoughts . . .

You can debate the nuances online all you want. You could even be right. But the bottom line is - this is a BUSINESS trying to sell a product. Your product fails where ALL other competing products succeed.

Everything else is irrelevant.

Good luck to you. I'll be at the RaceRender forum talking about all the cool videos we made with files that Garmin couldn't load.

We are looking into reading such invalid files, we are however a bit hesitant because there is an official standard that we would like to follow. But it seems like that battle has been lost, with lots of software not validating their gpx, or (worse) writing invalid files like the one you are looking at.

Well, how hard it can be to write proper GPX files? The standard is well-documented, and anyone who knows a bit of xml should also know that you can't add random stuff without adhering to the standard. Clearly the makers of the software that creates invalid gpx files are to blame, not the ones that validate input before importing...

And you know: garbage in = garbage out. Without validation you'll run into other problems sooner or later (like <time> tags that don't contain UTC timestamps, but a number of seconds; have seen that once)