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.
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.