Skypro KML files issue

[niko geens]

I have a Dual XGPS160 gps logger, using it as an external bluetooth receiver. 
Logfiles can be downloaded from the device with their SkyPro GPS Status Tool app.
(check http://gps.dualav.com/explore-by-product/xgps160/ for more product details... )

However: the kml files it generates somehow don't load very well.  In some apps, they work, in other ones (including Locus) they fail.  As a workaround I can convert them to gpx using gpsbabel for example.  But that's not really convenient when in the field.

Looking for a solution, I'm wondering, what's actually wrong with these files for not being loaded in Locus...
maybe somebody has an idea?
For an example file, check this url:
https://drive.google.com/open?id=112s9ikUKgsG-9QqjtczOds7Q5xoUuYwC


---
I know, i know: I can use Locus to have our tracks recorded, and actually, I'm doing that already :-)  but I'd like to have the device's internal log as an extra backup, especially when in competition circumstances.

[Menion]

Good day niko,
as I see, content of this file IS valid KML file format, but have to say that quite un-typical.

Track in file is based on gx:coord definition. As you may confirm in specification here: https://developers.google.com/kml/documentation/kmlreference#gxcoord, this format should have three numbers separated by spaces.

In your file, there is a comma separator and value "8" on the end of line
<when>2018-04-17T05:30:01Z</when><gx:coord>4.516515 51.0406 167515,8</gx:coord>

That's why Locus Map fail. Hard to say what this means. Maybe ask manufacturer?

EDIT: when you remove them, it really works correctly (see attachment)

[niko geens]

Thnx menion!

I'll contact the manufacturer indeed, and hope they can clarify.
I'll post here again if there's more relevant info for the benefit of others in the same situation.

[Menion]

Oki fine. Meanwhile, I made small improvement so even this invalid (probably) value will be loaded in next version (just with '0' altitude values).

[niko geens]

You're a hero !   

[niko geens]

Fwiw: I got a short reaction from the manufacturer stating that they 'will contact the developer team about this issue.'   

Not sure what this means, but I will check again when the next version of the firmware (ever) arrives...
(Currently at version 2.5.4 since ??)