This object is in archive!
GPX Import sometimes doesn`t work correctly
Solved
Some GPX Files exported by QuoVadis can`t be imported by Locus. Same files work fine with gpsies.com or other gpx import software.
The same problem 
If people shall help you need to provide such a file.
If people shall help you need to provide such a file.
How can I upload a file here?
How can I upload a file here?
Hello Uli
Please share your
Device/ Android version
Locus version
with us also...
Hello Uli
Please share your
Device/ Android version
Locus version
with us also...
hi,
if you need this immediately or you just want to play with it, I suggest to check latest locus test version here http://forum.locusmap.eu/viewtopic.ph...
if you do not want to waste a time with this, send you sample file on locus@asamm.com and I`ll check if import is working or not. In latest 2.9.2 version is small issue with GPX import that may cause this problem. Sorry for troubles ...
hi,
if you need this immediately or you just want to play with it, I suggest to check latest locus test version here http://forum.locusmap.eu/viewtopic.ph...
if you do not want to waste a time with this, send you sample file on locus@asamm.com and I`ll check if import is working or not. In latest 2.9.2 version is small issue with GPX import that may cause this problem. Sorry for troubles ...
No problem, if found a workaround: If I import the the gpx file to gpsies.com and export it as a gpx it works ;-). I send you the file. Perhaps it is a problem of QuoVadis?
No problem, if found a workaround: If I import the the gpx file to gpsies.com and export it as a gpx it works ;-). I send you the file. Perhaps it is a problem of QuoVadis?
Hi Uli,
thanks for email. Problem in GPX is probably caused by time stamp "2013-03-14T19:14:14.6721345Z" at start of file. Or just generally by problems with loading time from GPX files. I tested your file and in testing version of Locus it works fine, so in next version, this workaround will not be needed
Hi Uli,
thanks for email. Problem in GPX is probably caused by time stamp "2013-03-14T19:14:14.6721345Z" at start of file. Or just generally by problems with loading time from GPX files. I tested your file and in testing version of Locus it works fine, so in next version, this workaround will not be needed
Replies have been locked on this page!