Invalid XML in gps files

Former Member over 10 years ago

Basecamp is reporting that some files are not valid gpx files. Ordinarily that's not a big deal: just run it through validome.org and it will check and give you a report with some clues :cool:

However, now it seems that any gpx file exported by Basecamp will fail validation (even if they actually work in Basecamp!)

Validome.org reports that there is an error in:

http://www.garmin.com/xmlschemas/CreationTimeExtensionsv1.xsd

Error (1)
Line File name: http://www.garmin.com/xmlschemas/CreationTimeExtensionsv1.xsd
1 Column: 2
Error: Content is not allowed in prolog.
Error Position:
?

So, until that error is fixed by Garmin I am unable to repair gpx files that do have an actual error.

0 Former Member over 10 years ago

I only have GPX Export issues if the exported data has Trip Planner content. Header errors are of little concern most of the time.

0 JaVaWa over 10 years ago

Header errors are of little concern most of the time.

In this case they are... validome.org needs access to the schemas in order to check the gpx file. Actually it isn't an header error; it's just that the url to the xsd doesn't resolve properly.

@AUGUSTFALCON: use Google to find an online validator that does a check for well-formedness only (actually most of them don't do a full validation like validome.org); that's sufficient in the case of corrupt files.
validome.org has a checkbox "Well-Formedness only", but that doesn't work (it still performs a full validation)

0 Former Member over 10 years ago

Thanks @Javawa.

I found xmlgrid.net and ran my file against it. It came back as Well Formed! Its possible I ran the wrong file since I had at least 16 iterations. So I need to change back to the old library and try the import again to see which files fail :(

Also checked out www.garmin.com/xmlschemas and coud find no reference to any CreationTimeExtension in the docs.

0 JaVaWa over 10 years ago

That list on www.garmin.com/xmlschemas is far from complete... I'm missing AdventuresExtensionv1.xsd, CreationTimeExtensionsv1.xsd, PowerExtensionv1.xsd, PressureExtensionv1.xsd, TrackPointExtensionv1.xsd, TripExtensionsv1.xsd, TripMetaDataExtensionsv1.xsd, ViaPointTransportationModeExtensionsv1.xsd, VideoExtensionv1.xsd and WaypointExtensionv1.xsd

0 Former Member over 10 years ago

I've been using validome.org for quite some time and it does "Well-Formedness Only" check for me just fine.

EDIT: My apology Jack. It seems that it doesn't just do "Well-Formednes Only" checks when that option is checked.

0 JaVaWa over 10 years ago

As long as your gpx file doesn't contain a waypoint that uses the creation time tag validome.org doesn't have any problems with it, but when a waypoint with that tag is present validome gives an error; with our without "Well-Formedness Only" checked. That means that it does more than a well-formedness check in both cases...