Locus 2.01 Geocaching GPX export
I got the problem that after updating to the actual (2.01) version of Locus pro CompeGPS Twonav can`t open from Locus exported Geocaching GPX files. V.1.6.3 is doing that fine.
Analyzing the GPX file showed several strange things:
1) Most cache descriptions and logs are empty, except the description from the last open cache.
2) In the tags from the last open cache this line is causing the trouble:
----------------------------------------------------------------------------------------
<![CDATA[Auf T5-Tour mit FatBoyDrive und Makaveli-Bass war dieser hier der gelungene Abschluss für heute.
Die errechneten Koordinaten führten uns natürlich ersteinmal in einen Wald indem weit und breit keine Dose zu finden war.
Also setzte FatBoyDrive ein zweites Mal den Taschenrechner an und schlug uns neue Koordinaten vor, die, wie sich später zeigte viel besser passten.
Mittlerweile war es schon verdammt dunkel, aber trotzdem: jetzt sind wir hier und ein Abbruch kommt nicht in Frage.
Schon der dritte Schuss saß perfekt und so gings, mit diversen Hilfsmitteln in der Tasche, zügig aufwärts.
Am Ojekt der Begierde angekommen, war der erste Gedanke: Wo ist jetzt der Haken.
Beim zweiten Blick war dann schnell klar, es wird doch schwieriger als Anfangs geglaubt.
Ohne zu viel zu verraten, war es eine super originelle Idee.
Für das Objekt absolut angemessen und eine schöne Herausforderung.
Hier steckt nicht nur Ideenreichtum sondern auch viel Mühe und Arbeit in dem Cache.
Vielen Dank dafür,
sagen [purple]FD&CL[/purple]]]>
-------------------------------------------------------------------------------------------------
Deleting this Log between from GPX is resulting in a working GPX.
I wonder why this cache has either description and logs in it and the other caches do not have descriptions or logs in it.
Could You please have a look at it? I would prefer to have some more export option regarding gpx export (include/don`t include desciption/include-don`t include logs). Could this be done?
The same problem 
answer why some cache have logs and description and some not is simple. Data imported from GSAK or GeoGet addon are incomplete. To be whole system as fast as possible (and also to allow transfer more caches to Locus), these addons send only partial data to Locus. Rest is loaded when you tap on cache and data are firstly needed. So when you export your caches, only points that was shown previously are contained full. Anyway I`ll look at it but I`m worried that export will be very very slow when I`ll load all data from addons
second problem with description. Are you sure that problem is in description and not in program you wanna import to? Did you tried any other program? Because whole description is in CDATA tag, there shouldn`t be any problem ...
answer why some cache have logs and description and some not is simple. Data imported from GSAK or GeoGet addon are incomplete. To be whole system as fast as possible (and also to allow transfer more caches to Locus), these addons send only partial data to Locus. Rest is loaded when you tap on cache and data are firstly needed. So when you export your caches, only points that was shown previously are contained full. Anyway I`ll look at it but I`m worried that export will be very very slow when I`ll load all data from addons
second problem with description. Are you sure that problem is in description and not in program you wanna import to? Did you tried any other program? Because whole description is in CDATA tag, there shouldn`t be any problem ...
Hi Menion,
thanks for clarifying this.
1) If this is slowing down the export dramatically it would be better to have no description at all in the GPX. Anyway it seems that I`m the only one who is using Locus as a kind of database manager for other programs too.
2) Checking the GPX with other programs was something I did first. I tried it with GSAK and everything imported fine but with every CompeGPS product I got that failure. Exporting the same from GSAK and importing it in any CompeGPS product went well. The relevant part from the working GSAK-Export looks like this:
EDIT: Strange I don`t see the XML TAGS in the brackets, think to show them better I`ll replace < with { and > with }
--------------------------------------------------------------------------------------------------------
{groundspeak:text encoded="False"}Auf T5-Tour mit FatBoyDrive und Makaveli-Bass war dieser hier der gelungene Abschluss für heute.
Die errechneten Koordinaten führten uns natürlich ersteinmal in einen Wald indem weit und breit keine Dose zu finden war.
Also setzte FatBoyDrive ein zweites Mal den Taschenrechner an und schlug uns neue Koordinaten vor, die, wie sich später zeigte viel besser passten.
Mittlerweile war es schon verdammt dunkel, aber trotzdem: jetzt sind wir hier und ein Abbruch kommt nicht in Frage.
Schon der dritte Schuss saß perfekt und so gings, mit diversen Hilfsmitteln in der Tasche, zügig aufwärts.
Am Ojekt der Begierde angekommen, war der erste Gedanke: Wo ist jetzt der Haken.
Beim zweiten Blick war dann schnell klar, es wird doch schwieriger als Anfangs geglaubt.
Ohne zu viel zu verraten, war es eine super originelle Idee.
Für das Objekt absolut angemessen und eine schöne Herausforderung.
Hier steckt nicht nur Ideenreichtum sondern auch viel Mühe und Arbeit in dem Cache.
Vielen Dank dafür,
sagen [purple]FD&CL[/purple]{/groundspeak:text}
Hi Menion,
thanks for clarifying this.
1) If this is slowing down the export dramatically it would be better to have no description at all in the GPX. Anyway it seems that I`m the only one who is using Locus as a kind of database manager for other programs too.
2) Checking the GPX with other programs was something I did first. I tried it with GSAK and everything imported fine but with every CompeGPS product I got that failure. Exporting the same from GSAK and importing it in any CompeGPS product went well. The relevant part from the working GSAK-Export looks like this:
EDIT: Strange I don`t see the XML TAGS in the brackets, think to show them better I`ll replace < with { and > with }
--------------------------------------------------------------------------------------------------------
{groundspeak:text encoded="False"}Auf T5-Tour mit FatBoyDrive und Makaveli-Bass war dieser hier der gelungene Abschluss für heute.
Die errechneten Koordinaten führten uns natürlich ersteinmal in einen Wald indem weit und breit keine Dose zu finden war.
Also setzte FatBoyDrive ein zweites Mal den Taschenrechner an und schlug uns neue Koordinaten vor, die, wie sich später zeigte viel besser passten.
Mittlerweile war es schon verdammt dunkel, aber trotzdem: jetzt sind wir hier und ein Abbruch kommt nicht in Frage.
Schon der dritte Schuss saß perfekt und so gings, mit diversen Hilfsmitteln in der Tasche, zügig aufwärts.
Am Ojekt der Begierde angekommen, war der erste Gedanke: Wo ist jetzt der Haken.
Beim zweiten Blick war dann schnell klar, es wird doch schwieriger als Anfangs geglaubt.
Ohne zu viel zu verraten, war es eine super originelle Idee.
Für das Objekt absolut angemessen und eine schöne Herausforderung.
Hier steckt nicht nur Ideenreichtum sondern auch viel Mühe und Arbeit in dem Cache.
Vielen Dank dafür,
sagen [purple]FD&CL[/purple]{/groundspeak:text}
so point 1. - fixed
because there is need to load all data from addon and not just export incomplete cache, it takes instead of half a minute, almost three minutes. Anyway, I think this is not a problem
point 2.
when exported file from Locus works in other program (and because seems you`re only one with this issue), I can expect then this is caused by CompeGPS and not Locus itself, correct?
Also I don`t understand information about {} bracers: So if you find problem with exported files in Locus (best is to point me to one specific mistake in export), I`ll gladly fix it.
I think, this topic should be closed
so point 1. - fixed
because there is need to load all data from addon and not just export incomplete cache, it takes instead of half a minute, almost three minutes. Anyway, I think this is not a problem
point 2.
when exported file from Locus works in other program (and because seems you`re only one with this issue), I can expect then this is caused by CompeGPS and not Locus itself, correct?
Also I don`t understand information about {} bracers: So if you find problem with exported files in Locus (best is to point me to one specific mistake in export), I`ll gladly fix it.
I think, this topic should be closed
Point 2:
found the problem and it is the Compe XML Parser which is causing the problem:
That is coded right but not working in Compe:
... sagen [purple]FD&CL[/purple]]]>
that is coded wrong but working in Compe:
... sagen [purple]FD&CL[/purple]]>
that is coded right and working in Compe but requires another [SPACE] after the text section:
... sagen [purple]FD&CL[/purple] ]]>
So Compe has a problem with ]]]> . Only way to solve this is removing the CDATA-tags from the logentries or ending the text with a spare SPACE character.
Since the problem is not caused by Locus but by Compe it doesn`t belong here.
Thanks for your effort and support!
Topic can be closed.
Point 2:
found the problem and it is the Compe XML Parser which is causing the problem:
That is coded right but not working in Compe:
... sagen [purple]FD&CL[/purple]]]>
that is coded wrong but working in Compe:
... sagen [purple]FD&CL[/purple]]>
that is coded right and working in Compe but requires another [SPACE] after the text section:
... sagen [purple]FD&CL[/purple] ]]>
So Compe has a problem with ]]]> . Only way to solve this is removing the CDATA-tags from the logentries or ending the text with a spare SPACE character.
Since the problem is not caused by Locus but by Compe it doesn`t belong here.
Thanks for your effort and support!
Topic can be closed.
Replies have been locked on this page!