This object is in archive!
Additional waypoints from GPX not displayed
Solved
Hi!
Is there any possibility to import additional waypoins from GPX, even if they contain the same description?
I have tried to import the following GPX (see: http://pastebin.com/WLgh1KYn ) to make them unique, and now they are displayed.
Locus Pro, version 2.18.0, Android API v.16
Thanks for the great app!
Greetings,
Boguś
The same problem 
Hello,
I have to ask for a few things. Is this a common format used in OpenCaching? Because waypoint names are little bit different then in Geocaching.
In GC, cache has name GCABCD and all it`s waypoints has names XYABCD.
In OP, seems that cache has name OPABCD, but all your waypoints are named OPABCD-01 , OPABCD-02, etc. So I need to know if this is how OpenCaching waypoints are really named or if this is just your own creation. Thanks
Hello,
I have to ask for a few things. Is this a common format used in OpenCaching? Because waypoint names are little bit different then in Geocaching.
In GC, cache has name GCABCD and all it`s waypoints has names XYABCD.
In OP, seems that cache has name OPABCD, but all your waypoints are named OPABCD-01 , OPABCD-02, etc. So I need to know if this is how OpenCaching waypoints are really named or if this is just your own creation. Thanks
Ok, I have added exception for OpenCaching, to test on duplicate waypoints only on "code", and not also on "name" as for Geocaching waypoints.
So in next version of Locus, your cache, will correctly load all it`s waypoints. There should be anyway a problems with export of new opencaching waypoints attached to cache. There should be incorrect codes, but you`ll see. If there will be any problem, feel free to create a new issue here
Ok, I have added exception for OpenCaching, to test on duplicate waypoints only on "code", and not also on "name" as for Geocaching waypoints.
So in next version of Locus, your cache, will correctly load all it`s waypoints. There should be anyway a problems with export of new opencaching waypoints attached to cache. There should be incorrect codes, but you`ll see. If there will be any problem, feel free to create a new issue here
Hi!
Waypoint code ( tag) is created from the cache code (i.e. OP1234) with unique suffix (not necessary number) - so it gives OP1234-1 or OP1234-USER-COORDS. The waypoint description ( tag - which is used as a title in Locus) is created from waypoint type (i.e. parking, interesting place, point to visit in a multicache etc), and is fixed. The tag is the waypoint text, as entered by cache owner.
The waypoint codes ( tag) are globally unique in the generated GPX file.
Thanks for working on the solution!
Hi!
Waypoint code ( tag) is created from the cache code (i.e. OP1234) with unique suffix (not necessary number) - so it gives OP1234-1 or OP1234-USER-COORDS. The waypoint description ( tag - which is used as a title in Locus) is created from waypoint type (i.e. parking, interesting place, point to visit in a multicache etc), and is fixed. The tag is the waypoint text, as entered by cache owner.
The waypoint codes ( tag) are globally unique in the generated GPX file.
Thanks for working on the solution!
Hi!
Thanks a lot for your reply.
I`m not sure what do you mean saying "test on duplicate waypoints only on `code`, and not also on `name`".
From my experience, Locus uses desc tag (which is displayed as waypoint title) as a unique key within cache scope. I think, at least for OpenCaching it should rely on name tag, which is globally unique.
Greetings
Hi!
Thanks a lot for your reply.
I`m not sure what do you mean saying "test on duplicate waypoints only on `code`, and not also on `name`".
From my experience, Locus uses desc tag (which is displayed as waypoint title) as a unique key within cache scope. I think, at least for OpenCaching it should rely on name tag, which is globally unique.
Greetings
Hi, I understand this system. I was just curious if you named all waypoints like this in GSAK or if they were already downloaded with these names from OpenCaching site.
Anyway as I wrote, I believe this problem should be solved now. But because I play (rarely) only geocaching, not opencaching, Locus is not well tested in this way. So if you find any additional problems, just write me and I`ll gladly look at it
Hi, I understand this system. I was just curious if you named all waypoints like this in GSAK or if they were already downloaded with these names from OpenCaching site.
Anyway as I wrote, I believe this problem should be solved now. But because I play (rarely) only geocaching, not opencaching, Locus is not well tested in this way. So if you find any additional problems, just write me and I`ll gladly look at it
Replies have been locked on this page!